Ensuring VSAM Transparency custom load modules are current
Article ID: 124476
Updated On:
Products
Issue/Introduction
The recommended approach to loading Datacom VSAM Transparency subsystems into an LPAR is to use the CAIRIM program in the CAS9 proc. Here is an example of the control statements used, defining two subsystems - VTP1 and VTD1:
PRODUCT(CA DATACOM VSAM/T) VERSION(BG14) INIT(DVCR4PR) - PARM(DVSSN=VTP1,SFX=P1) - LOADLIB(VSAM.TRNSPRNC.CUSTOM.LOADLIB) PRODUCT(CA DATACOM VSAM/T) VERSION(BG14) INIT(DVCR4PR) - PARM(DVSSN=VTD1,SFX=D1) - LOADLIB(VSAM.TRNSPRNC.CUSTOM.LOADLIB)
In this example, there is a suffix variable (SFX) that is also unique. The suffix is used to identify the name of a specific load module that is copied and renamed in the custom loadlib as the primary module for that particular subsystem. In this example, the DVVSIPR module is copied and renamed to DVVSIP1 and DVVSID1.
Environment
Component:
Resolution
To initialize and use this subsystem, there are seven modules that need to be copied into the custom loadlib without renaming and one module that is renamed for each subsystem. In order to ensure that the most current version of the copied modules is used, we would recommend adding a step to the beginning of the CAS9 proc that will copy the necessary modules from the Datacom VSAM Transparency base loadlib into the custom loadlib. A single IEBCOPY step will copy the seven required modules and the single DVVSIPR module that needs to be renamed based on the SFX parameters used in the CAIRIM control statements.
Here is an example of the JCL for the IEBCOPY:
//*
//* COPY CA DATACOM VSAM TRANSPARENCY MODULES TO CUSLIB
//*
//IEBCOPY1 EXEC PGM=IEBCOPY
//IN DD DISP=SHR,DSN=your.DBVT140.CABGLOAD
//OUT DD DISP=SHR,DSN=your.DBVT140.CUSLIB
//SYSUT3 DD UNIT=SYSDA,SPACE=(CYL,(1,1))
//SYSUT4 DD UNIT=SYSDA,SPACE=(CYL,(1,1))
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
* -- COPY ALL REQUIRED MODULES TO THE CUSTOM LOADLIB
COPYALL COPYMOD INDD=((IN,R)),OUTDD=OUT
SELECT MEMBER=(DVCR4PR,DVVSCPR,DVVSIPR,DVVSOPR)
SELECT MEMBER=(DVVSSPR,DVVSUPR,DVV39PR)
*
* -- FOR EACH SSN, COPY MODULE DVVSIPR TO DVVSI.. WITH DESIRED SUFFIX
COPYVSI COPYMOD INDD=((IN,R)),OUTDD=OUT
SELECT MEMBER=((DVVSIPR,DVVSIP1))
*
* -- FOR EACH SSN, COPY MODULE DVVSIPR TO DVVSI.. WITH DESIRED SUFFIX
COPYVSI COPYMOD INDD=((IN,R)),OUTDD=OUT
SELECT MEMBER=((DVVSIPR,DVVSID1))
*
* -------------------- END OF COPY COMMANDS
/*
Each COPYMOD command is a new function, and will allow us to select the DVVSIPR module multiple times. COPYMOD is used to allow reblocking of the DVVSIPR module if the custom loadlib has a different blocksize from the base loadlib.
All clients would have the first COPYMOD with the seven modules that are SELECTed. Then, for each new SSN (with a new suffix), they only need to add these two lines:
COPYVSI COPYMOD INDD=((IN,R)),OUTDD=OUT
SELECT MEMBER=((DVVSIPR,DVVSIxx))
By copying the seven required modules and the specially-named DVVSIPR module, everything should be set to initialize the Datacom VSAM Transparency environment successfully.
Additional Information
For more information about configuring the Datacom VSAM Transparency version 14.0 environment, please review the Knowledge Base article KB000009452, titled Subsystem Install (CAIRIM) Changes in CA Datacom VSAM Transparency Version 14.0 and the documentation found at the Datacom VSAM/t Home.
As always, please contact Broadcom support for Datacom if you have further questions.
Feedback
