Setting up CAIRIM for Version 14.0 and 15.x Program Call (PC) modules alongside Version 12.0 SVC
Article ID: 39858
Updated On:
Products
Issue/Introduction
I am installing CA Datacom/DB version 14.0 (or 15.0), and also have version 12.0 MUFs running. How do I install the PC Calls in my CAS9/CAIRIM process along with the version 12.0 SVCs?
Resolution
Setting up the CAS9/CAIRIM processing for CA Datacom version 12.0 (v12) SVC can be a bit tricky when you add version 14.0 (or 15.x) into the mix. Here is a quick overview of the CAIRIM processing for CA Datacom, followed by an example of how to set up both types of control statements.
First, the CAIRIM control statements use a module called DBRIMPR to initialize the Version 12.0 SVC. DBRIMPR is loaded from the STEPLIB, so the CA Datacom version 12.0 base loadlib (CAAXLOAD or CABDLOAD) must be part of that concatenation. DBRIMPR will then fetch the SVC module, called DBSVCPR in your PARM statement, from a file allocated to DD statement DBLIBxxx (there can be multiple DBLIB statements for various release levels and uses of the CA Datacom product).
Starting with Version 14.0, the process changes. CA Datacom no longer uses SVCs for communication, but now use PC (Program Call) modules. The processing has also changed so that only the LOADLIB() statement is used in the control statements, and there are no more JCL statements needed for STEPLIB or DBLIBxxx. We load DBPCCPR and DBPCSPR in Version 14.0 and DBPCSPR in Version 15.x from the loadlib identified in the LOADLIB() statement.
Because every client might have a different configuration for their environment, with a mix of versions (11.0, 12.0, 14.0 and 15.x), and possibly multiple SVCs for 11.0 and 12.0, as well as a Test or Prod version of the PC modules for Version 14.0 and above, this process can become complex. It is not possible to illustrate every scenario in the manuals, and unless a client is familiar with the intricacies of these variations, it is easy to make a simple mistake that prevents the initialization from completing successfully, or that prevents the MUF from starting.
Now, what does this look like when all of this is put together?
Your CAS9/CAIRIM STEPLIB needs to have the CA Datacom Version 12.0 base loadlib for DBRIMPR. There is no JCL needed for CA Datacom Version 14.0 and above.
Your DBLIBxxx statement is used to find the SVC module (DBSVCPR) for Version 12.0, so the base loadlib is again specified here. Your input to CAS9/CAIRIM for CA Datacom version 14.0 and above will use the LOADLIB() statement to identify the location for the PC modules. The input statements are all that is needed for these versions.
Here is an example of how your CAS9 setup might look for the CA Datacom component:
//CAIRIM EXEC PGM=CAIRIM
//STEPLIB DD DISP=SHR,DSN=<<your CA Common Services loadlib if needed>>
// DD DISP=SHR,DSN=<<your CA Datacom v12 CAAXLOAD or CABDLOAD>>
// DD ... (other needed loadlibs for other products)
//PARMLIB DD DISP=SHR,DSN=&OPTLIB(&RIMPARM)
//DBLIB DD DISP=SHR,DSN=<<your CA Datacom v12 CAAXLOAD or CABDLOAD>>
//KEYS DD DISP=SHR,DSN=&OPTLIB(&KEYS)
//AUTOCMDS DD DISP=SHR,DSN=&OPTLIB(&AUTOCMD)
Here is an excerpt of the PARMLIB file:
...
*----------------------------------------------------
* CA DATACOM DATABASE - VERSION 12.0
*----------------------------------------------------
PRODUCT(CA-DATACOM) VERSION(BD12) INIT(DBRIMPR) -
PARM(D247,DBSVCPR,TYP=3)
*
...
*----------------------------------------------------
* CA DATACOM DATABASE - VERSION 14.0
*----------------------------------------------------
PRODUCT(CA DATACOM) VERSION(BD14) INIT(DBCR4PR) -
LOADLIB(<<your CA Datacom v14 CAAXLOAD or CABDLOAD>>) -
PARM(PC=PROD,PCC=DBPCCPR)
PRODUCT(CA DATACOM) VERSION(BD14) INIT(DBCR4PR) -
LOADLIB(<<your CA Datacom v14 CAAXLOAD or CABDLOAD>>) -
PARM(PC=PROD,PCS=DBPCSPR)
...
*----------------------------------------------------
* CA DATACOM DATABASE - VERSION 15.0
*----------------------------------------------------
PRODUCT(CA DATACOM) VERSION(BD15) INIT(DBCR5PR) -
LOADLIB(<<your CA Datacom v15 CAAXLOAD or CABDLOAD>>) -
PARM(PC=PROD,PCC=DBPCSPR)
...
Once you understand the processing changes and the control statements needed, it is easy to set this up correctly for both old- and new-style formats.
Additional Information
As always, please contact Broadcom support for CA Datacom if you have further questions.
Feedback
