Multi-Sysplex data centers are not uncommon in large scale computing enterprises. Normally, VSAM cannot be shared across a Sysplex boundary. When VSAM applications must be split across these separate Sysplexes to migrate interconnected applications from one Sysplex to another, for example, during a merger, acquisition, or reorganization. Another example is Production Isolation from Application Development as required when a banks size in assets exceeds a certain level. In either case VSAM files can only be shared across Sysplex boundaries using SYSBII (from HWCS.com).
If you have a CICS File Owning Region on Sysplex A with the VSAM file defined, and your application on Sysplex B, you should install SYSBII on both Sysplex z/OS LPARs.
When the batch application accesses the VSAM file, SYSBII can transmit all VSAM I/O requests over VTAM or TCP/IP from Sysplex B to the CICS on SysPlex A and return the data over the same connection.
This allows your VSAM application to access data in another Sysplex. All that is required is to share network configuration information with help from the SYSB-II application.
|
|
For Sysplex A, Configured in SYSBII on Sysplex B
|
|
TCP/IP
|
IP address & CICS CSKL Listener Port number
|
|
VTAM
|
NetID and APPC LU Name Range for SYSBII
|
The SYSBII control file on Sysplex B must have the network location information for Sysplex A, and how to connect (VTAM or TCP/IP). The SYSBII control file lets batch programs concurrently access and update CICS-owned VSAM datasets. Its Control File dictates exactly how the system routes, recovers, and tracks these concurrent requests without forcing application refactoring. The SYSB-II Control File is the centralized repository for managing system parameters. It governs the following key operational aspects:
Table Tracking & Rebuilding: Tracks all changes made to the SYSB-II environment and automatically applies or rebuilds the internal SYSB-II control tables at customizable intervals.
Resource Routing: Defines which CICS regions and datasets are eligible for transparent VSAM function shipping.
Sync Point Processing: Configures how batch I/O commits record updates (e.g., job-step completion, LUW boundaries) and rollback parameters to ensure data integrity.