Sharing the SVC among different CA-IDMS releases

Document ID : KB000018700
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

This document describes the CAIRIM input needed to support sharing one SVC across multiple releases of CA-IDMS.

Solution:

When installing a new release of CA-IDMS, it is recommended that clients install the latest version of the CA-IDMS SVC and use it for all releases. To avoid sysgen changes etc., the latest SVC should be linked with the same SVC number that your releases are currently using.

For example, if you are running r17.0 with SVC 173, install the latest release of the CA-IDMS SVC using that same SVC 173. When all CVs using that SVC number are shut down, use CAIRIM to install the new SVC using the latest GJxxINIT program.

The CA-IDMS SVC and all of the related APFLIB load modules that are loaded when an SVC is installed using CAIRIM are always downward compatible and thoroughly tested by CA.

Therefore, when sharing an SVC across multiple releases, the SVC from the latest release should be used.

This document describes the nature of the CAIRIM statements required to set up such a configuration.

The following example assumes that the SVC number being used is 173, that you are currently running both r17.0 and r18.0, and that you are upgrading to r18.5.

In such a case, the existing CAIRIM statements that you run at IPL would probably look like this:-


//PARMLIB  DD *
PRODUCT(CA IDMS) VERSION(GJI0) INIT(GJI0INIT) PARM(SVC=173)
PRODUCT(CA IDMS) VERSION(GJH0) INIT(GJI0INIT) PARM(REFRESH(SVC=173))

Note that the second statement still refers to the r18.0 GJI0INIT module but VERSION(GJH0) - this specifies that your LPAR will be running CA IDMS release r17.0 as well as the r18.0 release.

When you run the r18.5 install or configuration jobs to upgrade CA-IDMS, you need to run a CAIRIM step to make sure the new SVC will be used, that any existing APFLIB modules are refreshed, and that any new ones are loaded. Note that any CV using SVC 173 must be shut down while this CAIRIM job is run. This syntax will refresh all modules in the LPA with the 18.5 versions.

This is the syntax required in the CAIRIM job for release 18.5:-


//PARMLIB  DD *
PRODUCT(CA IDMS) VERSION(GJI5) INIT(GJI5INIT) PARM(REFRESH(SVC=173))
PRODUCT(CA IDMS) VERSION(GJI5) INIT(GJI5INIT) PARM(REFRESH(RHDCSSFM))
PRODUCT(CA IDMS) VERSION(GJI5) INIT(GJI5INIT) PARM(REFRESH(IDMSMSVA))
PRODUCT(CA IDMS) VERSION(GJI5) INIT(GJI5INIT) PARM(REFRESH(CAIXDOA$))
PRODUCT(CA IDMS) VERSION(GJI5) INIT(GJI5INIT) PARM(REFRESH(PMRTDATA))

Note that running the above CAIRIM is required only to allow r18.5 to use this SVC until the next IPL of z/OS. For the next and all subsequent IPLs, all you need is the following CAIRIM statements:-


//PARMLIB  DD *
PRODUCT(CA IDMS) VERSION(GJI5) INIT(GJI5INIT) PARM(SVC=173)
PRODUCT(CA IDMS) VERSION(GJI0) INIT(GJI5INIT) PARM(REFRESH(SVC=173)) 
PRODUCT(CA IDMS) VERSION(GJH0) INIT(GJI5INIT) PARM(REFRESH(SVC=173))

The second line above is needed to support the r18.0 version on the LPAR, and the third line supports the r17.0 version on this same LPAR. Note that no statements of the form PARM(REFRESH(module-name)) are required because the first line will have loaded the r18.5 versions of all modules required for all releases (as they are downward compatible).

Please also note the following related to CAIRIM:

* Be sure that the STEPLIB concatenation of the CAIRIM job points to the APFLIB containing the correct modules - in this case those from the r18.5 configuration.

* Do not run any CAIRIM jobs while the related CVs are active. If you do, ERUS tasks will not work against those CVs until they are cycled.

* The following is a list of the APFLIB modules and the released at which they were added to CA-IDMS:-


   RHDCSSFM r12.0
   IDMSMSVA r17.0
   CAIXDOA$ r18.0
   PMRTDATA r18.5