Set up the CICS environment for remote VSAM access

To set up the CICS environment

1. Provide access to the VSAM file control table data set in each CICS region that can participate in file sharing. Add the following DD statement to the CICS startup JCL:

   //ARVFCTAB DD DSN=HLQ.arvfctab

   where HLQ.arvfctab is the name of the VSAM file control table data set that was allocated and initialized for your environment. The ddname must be ARVFCTAB.

2. Set up the CICS environment to support MRO (or XCF/MRO) communication. See the CICS documentation for instructions about enabling MRO support.
3. AR/CTL requires access to selected CICS modules to provide remote VSAM access services, but CICS execution libraries are not usually available to batch VSAM application programs. Therefore, include the CICS library containing the DFHACEE module in the STEPLIB, JOBLIB, or LNKLST concatenation of the batch job. This module does not require APF authorization.
4. Copy module DFHIRP (from the highest CICS release available in the SYSPLEX) to the link pack area (LPA) of each z/OS system where a batch file sharing job can execute. This module is already in LPA of systems that are running CICS.

5. Make selected AR/CTL modules available to CICS by including the following AR/CTL programs in the DFHRPL DD concatenation:

   Program	Description
   ARVRCIS0	Provides remote VSAM access services
   ARVRCIS3	Scans FCT entries; builds remote VSAM access file table
   ARVRCIS5	Removes remote VSAM access file table
   ARVRFCXT	Driven by the XFCSREQC exit in CICS to update file table after a file state changes

   You can copy the modules to a DFHRPL library, or you can include the AR/CTL execution load module library in the DFHRPL DD concatenation.

6. In the Program List Table Program Initialization (PLTPI), add the following entry to the phase 2 section (after the DFHDELIM statement) before any other phase 2 programs:

   DFHPLT TYPE=ENTRY,PROGRAM=ARVRCIS3
7. Set up security definitions for the AR/CTL transactions and sessions. The AR/CTL transactions (ARCF, ARCB, and ARCD) must be defined as having global authority in the system security package (such as RACF or ACF2). Also, set up the appropriate rules in the system security package to allow MRO (or XCF/MRO) traffic from batch VSAM jobs.To prevent unauthorized access to a data set that is being shared with CICS, the check for authority in the installation security package occurs within the batch region. This check ensures that the batch application program has authority to access the shared data set.