Monday, September 25, 2017

Concurrent access to VSAM files from batch and CICS


SYSB-II ® is mainframe software that allows CICS and batch to have concurrent access to VSAM files, while maintaining data integrity. This means you can process batch whenever needed, while CICS applications and VSAM data remain fully available for updates.

Traditionally when batch updated VSAM files, organizations had to take CICS applications offline or
employ techniques like showing read-only data to CICS users. SYSB-II changes all of that.

With SYSB-II, organizations can:

-Keep CICS applications running 24/7 so they can be available on PCs and mobile devices, without
downtime.

-Accept new business because organizations have more time both to process online transactions and run batch.

-Expand to more time zones because CICS applications can be online during traditional “nighttime” hours.

How SYSB-II works

SYSB-II uses the documented MVS subsystem interface to intercept batch VSAM requests, translate the input/output (I/O) requests into CICS I/O protocol, and then allow CICS to perform the VSAM operation on behalf of the batch job. SYSB-II communicates between CICS and the batch job using TCP/IP, VTAM, and cross-memory services. This architecture ensures that SYSB-II is upwardly compatible with future releases of CICS Transaction Server and z/OS.

SYSB-II runs as a legitimate command-level CICS transaction, following CICS rules and standards. Batch jobs look any other CICS transaction to the CICS application.

With SYSB-II, batch can take advantage of CICS’s data integrity, recovery tools, and file-locking and updating capability. SYSB-II also supports, but doesn’t require, VSAM RLS, a CICSplex, a sysplex, coupling facilities, and TCP/IP and VTAM protocols.

No comments:

Post a Comment

Note: Only a member of this blog may post a comment.