V-Share Modernization Guide

V-Share enables batch jobs to directly access VSAM files managed by CICS without requiring CICS to shut down or quiesce the files. This eliminates downtime and contention.

V-Share uses a shared data space architecture. Batch jobs use standard VSAM access methods, while V-Share intercepts and redirects I/O requests to the CICS VSAM files. V-Share manages concurrency and data integrity.

V-Share supports standard VSAM access methods (ESDS, KSDS, RRDS). It works with CICS TS regions.

V-Share provides configuration options to control the level of data sharing, locking granularity, and transaction isolation. These parameters are set in the V-Share configuration file.

V-Share intercepts VSAM I/O requests using z/OS authorized services. It redirects these requests to the appropriate CICS region and manages data integrity using locking mechanisms.

V-Share uses a configuration file, often named VSADMIN. The file specifies the CICS regions to connect to, VSAM datasets to share, and various control parameters.

V-Share does not expose a direct API. Batch jobs use standard VSAM access methods. V-Share transparently redirects the I/O.

The main components are the V-Share intercept module (running in the batch address space), the V-Share server (running in a dedicated address space or CICS region), and the VSADMIN configuration file.

V-Share uses z/OS cross-memory services for communication between the batch address space and the V-Share server. VSAM data is transferred through shared data spaces.

V-Share reduces downtime by allowing batch jobs to access CICS VSAM files online. This eliminates the need to quiesce CICS regions for batch processing.

By enabling online access to VSAM data, V-Share improves the efficiency of batch processing. Batch jobs can access data in real-time, reducing delays and improving data accuracy.

V-Share can reduce operational costs by eliminating the need for dedicated batch windows and the associated operational overhead.

V-Share allows for faster data integration between CICS and batch applications, improving the overall agility of the IT environment.

V-Share supports standard z/OS security mechanisms, including RACF, ACF2, and Top Secret, to control access to VSAM files.

V-Share uses an access control model based on z/OS security profiles. Access to VSAM files is controlled by defining appropriate security rules in RACF, ACF2, or Top Secret.

V-Share does not encrypt VSAM data. Data is transferred in clear text between the batch address space and the V-Share server. Encryption can be implemented at the VSAM level using VSAM encryption features.

V-Share provides audit logging capabilities. All access to VSAM files is logged, including the user ID, date, time, and type of access. These logs can be used for security auditing and compliance.

V-Share provides a command-line interface (CLI) for administrative tasks. The CLI is used to configure V-Share, monitor its status, and manage user access.

User management is handled through z/OS security. V-Share relies on RACF, ACF2, or Top Secret to authenticate users and control access to VSAM files.

The main configuration parameters are defined in the VSADMIN configuration file. These parameters include the CICS regions to connect to, VSAM datasets to share, and various control options.

V-Share provides monitoring capabilities through the CLI and SMF records. The CLI can be used to display the status of V-Share components, while SMF records provide detailed information about VSAM access.