SYSB-II
Eliminate Downtime. Unlock Growth.
In today's 24/7 economy, downtime isn't an option. Yet most mainframe shops still accept long nightly batch windows that force them to take CICS® applications offline. That means stale data, lost transactions, and frustrated users.
SYSB-II® changes the equation. It lets CICS and batch share VSAM files concurrently, so you can run batch anytime — without shutting down CICS or showing outdated data.
Why SYSB-II?
With SYSB-II you can:
Problems Solved
Downtime During Batch Windows
Stale Data
Complex Manual File Management
Risky or Slow Recovery
Key Benefits for Your Business
How SYSB-II Works
-
Intercept batch VSAM requests.
SYSB-II uses VTAM or TCP/IP and cross-memory services to communicate between the batch job and CICS to ensure compatibility with future releases of CICS Transaction Server and z/OS.
-
Translate the I/O requests into EXEC CICS data set commands.
SYSB-II runs as a legitimate command-level CICS transaction and follows CICS rules and standards. CICS processes batch jobs as a regular CICS transaction and retains CICS-provided capabilities for data integrity, recovery, tools, record locking, and updating files.
-
Function ship the requests to perform the VSAM operation on behalf of the batch job step.
SYSB-II is present in the CICS address space only when file sharing batch jobs are processing. It intercepts the I/O requests only for the specified batch files. This approach keeps the CICS I/O path as short as possible, provides greater control, and preserves terminal response time.
SYSB-II accesses CICS facilities in the batch environment. Unlike CICS programs, batch programs that execute EXEC CICS commands can access batch resources. The batch code between the EXEC CICS calls executes under the batch address space instead of under CICS.
Customer Success Stories
Get Started
