• VSAM Record Level Sharing (RLS) is a major extension to VSAM.

• You can access VSAM data sets in RLS mode from users that run in just one z/OS image (monoplex).
NOTE: Although it was designed for use by CICS, it can be used by any application. NOTE: Even in a monoplex environment a Coupling facility is required. The reason for doing that is to use the better serialization
• VSAM RLS extends the DFSMS storage hierarchy to support a data-sharing environment across multiple systems that is provided by RLS. For example, in a non-RLS mode two jobs cannot simultaneously access for update a VSAM data
in a Parallel Sysplex.. set with total read and write integrity. That is, for SHAREOPTIONS (1,3), just one can open the VSAM data set. The other must
- This support is primarily for VSAM data sets that online-transaction-processing applications use. wait for the first to close the data set. The granularity of the serialization
- It provides multi-system VSAM data sharing at a record level for CICS applications. is at data set level.
- The VSAM RLS product is designed to exploit z/OS’ Coupling Technology. • If the two jobs access the data set in RLS mode, both the OPENs z/OS System
• VSAM RLS provides read-only access by non- CICS applications concurrent with read/write by CICS applications succeed. Batch1 Batch2
CICS
to recoverable data sets.
- It allows any number of users within your Parallel Sysplex to share your existing VSAM data sets.
VSAM Page 1 - Both in parallel can then update the VSAM data set.
- The serialization is at logical record level.
- It can provide full data integrity (read and write). Record of 2
• VSAM SHAREOPTIONS are ignored when you access your data
SMSVSAM
NOTE: The serialization is at record level. However, to implement recoverable VSAM data sets the Level Sharing set in RLS mode.
users must have their own backout log, as CICS has. - You can have any number of read/write users who can
• VSAM RLS does not introduce new types of VSAM data sets; rather, it introduces a new way of accessing access the VSAM data set in RLS mode.
VSAM RLS is a data set access CDS
existing data sets. mode that enables multiple address NOTE: There is one exception to this rule about SHAREOPTIONS(2 x).
- Apart from the need to open data sets in RLS mode, the same VSAM record management interfaces are used. spaces, CICS application-owning VSAM data sets defined with SHAREOPTIONS(2 x) can be accessed by
• You can specify the RLS mode in the MACRF parameter of the ACB macro that you use to open the data set in regions on multiple systems, and any number of read/write users in RLS mode. They can also be
your program or you can also specify the RLS mode by using the new keyword RLS in your DD card batch jobs to access recoverable accessed by any number of read users in non-RLS mode. However, the
that points to your VSAM data set in your JCL. VSAM data sets at the same time. non-RLS users do not have any read integrity. A read user in non-RLS cache
NOTE: RLS mode can be used with KSDS, RRDS, VRRDS, and ESDS VSAM data sets. PATH (AIX) access for mode can be a batch job for printing the data set. Or it can use the
IDCAMS repro to create a copy of the data set for test purposes. cache cache
KSDS and ESDS is allowed with RLS. VSAM RLS processing involves
- Extended format, extended addressability, spanned, and compression are also supported by RLS. support from multiple products: • An RLS client is any address space that starts an RLS function IGWLOCK00
- Beginning with z/OS 1.12, VSAM stripping is also supported for VSAM data sets being accessed in RLS mode.
CICS Transaction Server that results in a call to the SMSVSAM address space.

CICS VSAM Recovery (CICSVR)

DFSMS Examples of RLS functions are OPEN, CLOSE, GET, PUT, and Coupling Facility
RLS and non-RLS VSAM data sets can coexist. DELETE.
If you need to share a data set among Couple data set (CDS)
NOTE: Access method services do not use RLS when performing an IDCAMS EXPORT, IMPORT, PRINT, or Examples of application that can be registered as RLS client address maintain status data
REPRO command. If the RLS keyword is specified in the DD statement of a data set to be opened by access address spaces, multiple systems, or about the current use
both, consider using record-level spaces are CICS, batch jobs, and DFSMShsm. VSAM of CF Sysplex resources..
method services, the keyword is ignored and the data set is opened and accessed in non-RLS mode.
sharing (RLS) instead of GSR. • A record lock is an XES lock resource that is obtained by SMSVSAM
• Both CICS and non-CICS jobs can have concurrent read or write access to non-recoverable data sets. on behalf of a user and associated with a logical record.
NOTE: there is no coordination between CICS and non-CICS, so data integrity can be compromised. RLS is not supported for control RLS in a Monoplex
- The lock resource name is based on a 16-byte hashed version of the record's
- Non-CICS jobs can have read-only access to recoverable data sets concurrently with CICS jobs, which can interval mode access or for HFS files. key (or RBA, or RRN), and the data set name and component name.
have read or write access. - There are also other locks to serialize CI/CA splits.
• VSAM RLS uses a coupling facility to perform data set-level locking, record locking, and data caching. VSAM RLS requires that the data sets be NOTE: SMSVSAM maintains two different types of record-level locks in its coupling-facility lock structures: Exclusive
- VSAM RLS uses the conditional write and cross-invalidate functions of the coupling facility cache structure, System Managed Storage (SMS) data sets. locks, and shared locks. Exclusive locks are used for any update request, whereas shared locks are used to support
thereby avoiding the need for control interval (CI) level locking. VSAM RLS uses the coupling facility caches Example - RLS diagnostic command See
as store-through caches. D SMS,SMSVSAM,DIAG(contention)
read integrity. The lock includes the name of the corresponding lock owner, which is the application ID (CICS,
Page2
NOTE: When a control interval of data is written, it is Displays latch contention on SMSVSAM resources DFSMStvs or any other), and the unit of work ID.
written to both the coupling facility cache and to direct VSAM internally performs cross-address space accesses
*** ***
access storage device (DASD). This ensures that and linkages between requestor address spaces and
problems occurring with a coupling facility cache do CICS CICS CICS CICS CICS CICS CICS CICS
* * * * * * the SMSVSAM server address space. The SMSVSAM
not result in the loss of VSAM data. AOR * * * AOR AOR * * * AOR AOR AOR AOR AOR server owns two data spaces. One data space is called
• VSAM RLS uses a Coupling Facility to perform the SMSVSAM data space. It contains some VSAM RLS
data-set-level locking, record locking, and data caching. control blocks and a system-wide buffer pool. The other
- VSAM RLS uses the conditional write and cross- data space is used by VSAM RLS to collect activity
invalidate functions of the Coupling Facility cache VSAM monitoring information used to produce SMF records.
structure, thereby avoiding the need for control interval • VSAM RLS data buffers occupy the largest share of the SMSVSAM
(CI) level locking. VSAM RLS VSAM RLS data-space storage.
• VSAM RLS uses the Coupling Facility caches as CICS Instance 1 Instance n - In some cases, storage limits on the data buffers may create
store-through caches. FOR performance slowdowns in high-volume transaction environments.
- When a control interval of data is written, it is written VSAM NOTE: To avoid any storage limits and potentially enhance performance,
SMSVSAM SMSVSAM
to both the Coupling Facility cache and the direct access VSAM RLS offers the option to move RLS data buffers into 64-bit
Address Space Address Space addressable virtual storage. This option can be activated by assigning
storage device (DASD). VSAM
- This ensures that problems occurring with a Coupling z/OS 1 z/OS n z/OS 1 z/OS 32 VSAM data sets to a data class with ISMF that specifies
Facility cache do not result in the loss of VSAM data. RlsAboveTheBar(YES). IBM recommends that you use this option,
CICS VSAM non-RLS CICS VSAM with RLS especially for applications with a high rate of critical CICS transactions.
• RLS does not support the following options and capabilities:
- Linear, KEYRANGE, IMBED, and temporary data sets • VSAM record-level sharing allows multiple levels of CF caching for
Prior to VSAM RLS, a CICS VSAM data set was owned and directly Coupling Facility (CF) DFSMS cache structures that are defined in the active storage
- Addressed access to KSDS data sets accessed by one single CICS. Shared access across CICS
Application Owning Regions (AORs) to a single VSAM data set was management subsystem (SMS) configuration.
- Control Interval Access Benefits of VSAM RLS • VSAM RLS has multiple levels of CF caching.
- User Buffering (UBF) provided by CICS function shipping. With function shipping, one The benefits of VSAM RLS are:
CICS File Owning Region (FOR) accesses the VSAM data sets on - The value of the SMS DATACLAS RLS CF Cache Value keyword
- GETIX and PUTIX requests
Enhances cross-system data sharing - scope is sysplex determines the level of CF caching.
- MVS Checkpoint/Restart facility behalf of other CICS regions
Improves performance and availability in CICS and also -The default value, ALL, indicates that RLS caches both the data and
- ACBSDS (system data set) Problems non-CICS VSAM environments index parts of the VSAM data set in the coupling facility.
specification There are a couple of problems with this CICS configuration:
Provides data protection after a system failure NOTE: If you specify NONE, then RLS caches only the index part of
- Hiperbatch
CICS FOR is a single point of failure.
Provides automation for data recovery the VSAM data set. If you specify UPDATESONLY, then RLS caches
- Catalogs, VVDS, the JRNAD exit, and any
Multiple system performance is not acceptable.
Provides full read/write integrity to your existing VSAM data in the coupling facility only during write operations.
JCL AMP= parameters in JCL
Lack of scalability. files; the user does not need to serialize using ENQ/DEQ macros - All active systems in a sysplex must have the greater than 4K CF
- Data that is stored in z/OS UNIX System Services
Allows CICS to register as a recoverable subsystem, which will caching feature before the function is enabled.

Over time the FORs became a bottleneck because CICS automate recovery processing as well as protect the data
- Requests that are issued while the caller is running in environments became increasingly complex. CICS required • When an application opens a VSAM data set, RLS processing
records to be recovered.
these modes: a solution to have direct shared access to VSAM data sets determines which lock structure to use by checking the storage
Cross-memory mode, SRB mode, or under an FRR. from multiple CICSs. The SMSVSAM address space VSAM RLS does not support record locks class defined for the data set.

Need to commit remotely. automatically starts at IPL when for a single VSAM sphere (index / data - If the storage class specifies a secondary lock structure, RLS
CICS function shipping allows for writing CICS Application the RLSINIT (YES) keyword components) to be placed in multiple lock processing uses the secondary lock structure for serializing

VSAM’s HURBA/HARBA are updated only when CICS is specified in the IGDSMSxx
programs without regard to the location of the requested closes the data set, causing conflicts along shared updates. member of SYS1.PARMLIB. structures. access to records in the data set. Otherwise, RLS processing
resources although this technique limits program independence NOTE: These issues are fully addressed by VSAM RLS. uses IGWLOCK00 for all record locking (see illustration above).
 Two RLS Diagnostics Commands
This helps determine which
D SMS,SMSVSAM,DIAG(contention) systems are actually experiencing D SMS,SMSVSAM,QUIESCE
a hang, as opposed to which
are victims.

Will display any latch contention on SMSVSAM resources
The quiesce display wil show any outstanding quiesce events

Latches are 8 bytes of storage used as a logical means
A quiesce event is a decision to allow unhindered CICS access
to serialize resources. They are either held, or waited on;
VSAM Page 2
Record of 2 to an RLS dataset.
there are no shared requests.
Any CICS regions that are part of the quiesce event will show

The contention displayed will show the latch address, the Level Sharing up in the display.
holder and any waiters if the latch is in contention.
If there is not an event in progress you will receive an IGW540I

The display will show elasped time for how long a message rejecting the command.
latch was in contention.
With quiesce activity

Without quiesce activity

Sample display fro DIAG command #1

• SPHERE NAME: Name of dataset being quiesced/unquiesced.

• SYSTEM NAME: System where command was issued.
• SUB-SYSTEM NAME: Name of CICS region involved in quiesce event.
- SCHEDULED: Time when the quiesce event was issued.
- COMPLETED: Time when CICS region responded to event.
- ELAPSE: Time between when the quiesce event was issued and
it was finally responded to by CICS.

NOTES:
Sample display fro DIAG command #2 • The Quiesce command is invaluable to determine what CICS
| - - RESOURCE - - | regions are holding up a quiesce request.
TYPE: Resource in contention (Almost always a Latch) • Any CICS regions that have 00.00.00 in the completed section
ID: Address location of the 8 byte latch are most likely in trouble and should be dumped along with
| - - WAITER - -| NOTES: SMSVSAM before termination.
JOB NAME: Job name of Waiter • DIAG should be used in conjunction with D GRS,C • In most scenarios, the CICS region, instead of SMSVSAM, can
ASID: Address space ID of Waiter to determine if any of the latch holders are waiting on ENQs. be terminated to allow the quiesce event to finished. Thus saving
TASK: TCB of Waiter • Any latch contention with an elasped time of more than a few a SMSVSAM wide outage.
| - - HOLDER - - | seconds is most likely stuck.
ASID: Address Space ID of Latch Holder • Sometimes the holding ASID id not SMSVSAM, but another
TASK: TCB of Latch Holder address space like a CICS region. Canceling that region
| - ELAPSED TIME - - | could avoid an SMSVSAM wide outage.
The amount of time that the latch was
in contention.
___