Implementing VSAM Record-Level Sharing (RLS) for Concurrent Batch and CICS Access
Executive Summary: Implementing VSAM Record-Level Sharing (RLS) for Concurrent Batch and CICS Access
VSAM RLS enables concurrent update access across multiple CICS regions and batch jobs across a Parallel Sysplex without closing files or causing File Status 93 contention. Discover SMSVSAM configuration, Coupling Facility lock structures, and JCL changes.
1 Problem Statement & Architecture Context: Implementing VSAM Record-Level Sharing (RLS) for Concurrent Batch and CICS Access
An enterprise operating 24/7 banking operations cannot take CICS regions offline to allow nightly batch processing jobs to update core VSAM accounting datasets. Batch jobs attempting to run concurrently fail with File Status 93 or wait indefinitely on dataset enqueues, blocking time-critical transaction feeds.
2 Technical Root Cause & Architecture Mechanics
Standard VSAM uses operating system file-level enqueues (SHAREOPTIONS). When an application opens a file for output, it acquires exclusive serialization for the entire dataset.
To achieve continuous 24/7 operation without database conversion, IBM introduced VSAM Record-Level Sharing (RLS):
- Serialization moves from whole-file enqueues to individual records via the SMSVSAM address space and the Coupling Facility (CF).
- Multiple CICS Application Owning Regions (AORs) and batch jobs across any LPAR in the Parallel Sysplex can update different records in the same KSDS simultaneously without locking each other out.
3 Implementation Guide & Modernization Strategy
# 1. Verify Storage Class & SMSVSAM Prerequisites
Ensure the Coupling Facility has allocated the lock and cache structures:
-
IGWLOCK00: The sysplex-wide CF lock structure. - Assign an SMS Storage Class with a defined cache set name:
//STEP1 EXEC PGM=IDCAMS
//SYSIN DD *
ALTER PROD.KSDS.CUSTOMER -
LOG(NONE) -
BWO(TYPECICS)
/*
-
LOG(NONE): Non-recoverable (orLOG(UNDO)/LOG(ALL)for CICS dynamic transaction backout via CICS System Log).
# 2. Update Batch JCL for RLS Mode
To access the dataset in RLS mode in batch jobs, specify RLS=NRI (No Read Integrity) or RLS=CR (Consistent Read) in the JCL AMP parameter:
//CUSTFILE DD DSN=PROD.KSDS.CUSTOMER,
// DISP=SHR,
// RLS=CR
For update operations:
//CUSTFILE DD DSN=PROD.KSDS.CUSTOMER,
// DISP=SHR,
// RLS=CRE
# 3. Update CICS FCT / CSD Definitions
In CICS, update the file definition:
CEDA DEFINE FILE(CUSTFILE) GROUP(FINAPP)
DSNAME(PROD.KSDS.CUSTOMER)
RLSACCESS(YES)
RECORDFORMAT(F)
STRINGS(20)
Install the definition:
CEDA INSTALL FILE(CUSTFILE) GROUP(FINAPP)
Now, batch jobs and CICS transactions can run simultaneously with zero lock contention!
Technical Specifications Matrix
| Attribute | Specification |
|---|---|
| Target Environment | IBM z/OS • CICS & VSAM Architecture |
| Key Technologies | VSAM, VSAM RLS, CICS |
| Delivery SLA | Accelerated Sprint Delivery via StackMF Pods |
| Technical Reviewer | Anshu, Chief Technology Architect • StackMF Architecture Pod |
Production Readiness & Verification Checklist
- Ensure the Coupling Facility `IGWLOCK00` structure is sized adequately to prevent false lock contention.
- Use `RLS=CR` for batch read jobs to prevent reading uncommitted 'dirty' records while CICS transactions are in-flight.
- Configure Backup-While-Open (`BWO(TYPECICS)`) to allow DFSMSdss backups without closing CICS files.
- Monitor SMSVSAM address space performance via `D SMS,SMSVSAM`.
? Frequently Asked Questions
What is the root cause of Implementing VSAM Record-Level Sharing (RLS) for Concurrent Batch and CICS Access? ↓
How do you resolve Implementing VSAM Record-Level Sharing (RLS) for Concurrent Batch and CICS Access in production? ↓
How can teams prevent Implementing VSAM Record-Level Sharing (RLS) for Concurrent Batch and CICS Access in enterprise pipelines? ↓
Recommended Technical Runbooks
Diagnosing VSAM File Status 92 and 93: Enqueue Locks & Dynamic Allocation Contention
Eliminating Performance Degradation from VSAM KSDS CI/CA Splits: IDCAMS REORG Automation
Troubleshooting VSAM File Status 35: Dataset Not Found during Dynamic Allocation in Batch & CICS
Authoritative Reference Documentation
Official IBM manuals, Redbooks, and vendor technical advisories:
This diagnostic runbook is published by StackMF Technologies LLP for educational and architectural reference only. All code snippets, JCL, and procedures are provided "AS IS" without warranty of any kind. Always test changes thoroughly in non-production sysplex environments prior to production rollout.
IBM, z/OS, CICS, Db2, IMS, RACF, and IDz are registered trademarks of International Business Machines Corporation. Broadcom, CA-7, and Endevor are trademarks of Broadcom Inc. All other trademarks belong to their respective owners and are referenced under the Nominative Fair Use Doctrine (US Lanham Act 15 U.S.C. ยง 1125 / Section 30 of the Indian Trade Marks Act, 1999) solely for technology compatibility and diagnostic identification. StackMF Technologies LLP is an independent consulting entity not affiliated with or endorsed by these vendors. View Full Legal & IP Policy →
Struggling with Critical Mainframe Incidents or Vendor Renewal Pressure?
StackMF deploys certified Senior Mainframe Engineers fluent in both z/OS legacy internals (COBOL, DB2, CICS, VSAM, CA-7, Endevor) and modern cloud stacks (React, Kafka, AWS, Git). Onboard dedicated pods in 48 hours or cut Broadcom licensing by 60%.