IDMS SVC configurations for multiple IDMS releases

book

Article ID: 18700

calendar_today

Updated On:

Products

CA IDMS CA IDMS - Database

Issue/Introduction

This document describes the CAIRIM input needed to support multiple releases of CA-IDMS on the same LPAR.

 

Environment

Release: All supported releases.
Component: CA-IDMS

Resolution

When multiple releases of IDMS are running on the same z/OS LPAR, it is possible to either share one SVC for all releases, or use a different SVC for each release.
It is recommended to use the same SVC but either configuration is possible.

The following examples assume an LPAR currently running IDMS 18.5 and using SVC 172, and that you are about upgrade to 19.0 but need to run both releases for some time.

In this case, before the upgrade, the CAIRIM input used at z/OS IPL time should be this:

//PARMLIB DD *
PRODUCT(CA IDMS) VERSION(GJI5) INIT(GJI5INIT) PARM(SVC=172)

Sharing the same SVC

To support both releases, SVC 172 should be recreated using the 19.0 software and CAIRIM job run at z/OS IPL time should point STEPLIB to the 19.0 APFLIB and use this input:

//PARMLIB DD *
PRODUCT(CA IDMS) VERSION(GJJ0) INIT(GJJ0INIT) PARM(SVC=172)
PRODUCT(CA IDMS) VERSION(GJI5) INIT(GJJ0INIT) PARM(REFRESH(SVC=172))

To support the 19.0 CV from the point of installation until the next z/OS IPL, the following one-off CAIRIM job should be run with STEPLIB pointing to the 19.0 APFLIB:

//PARMLIB DD *
PRODUCT(CA IDMS) VERSION(GJJ0) INIT(GJJ0INIT) PARM(REFRESH(SVC=172))
PRODUCT(CA IDMS) VERSION(GJJ0) INIT(GJJ0INIT) PARM(REFRESH(RHDCSSFM))
PRODUCT(CA IDMS) VERSION(GJJ0) INIT(GJJ0INIT) PARM(REFRESH(IDMSMSVA))
PRODUCT(CA IDMS) VERSION(GJJ0) INIT(GJJ0INIT) PARM(REFRESH(CAIXDOA$))
PRODUCT(CA IDMS) VERSION(GJJ0) INIT(GJJ0INIT) PARM(REFRESH(PMRTDATA))

Using a different SVC

If you choose to use a different SVC for release 19.0, say SVC 173 for example, then SVC 173 should be created using the 19.0 software, and the CAIRIM job run at z/OS IPL time should point STEPLIB to a concatenation of the 19.0 and 18.5 APFLIBs (in that order) and use this input:

//PARMLIB DD *
PRODUCT(CA IDMS) VERSION(GJI5) INIT(GJJ0INIT) PARM(SVC=172)
PRODUCT(CA IDMS) VERSION(GJJ0) INIT(GJJ0INIT) PARM(SVC=173)

To support the 19.0 CV from the point of installation until the next z/OS IPL, the following one-off CAIRIM job should be run with STEPLIB pointing to the 19.0 APFLIB:

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

Additional Information

There can only be one version of the modules RHDCSSFM, IDMSMSVA, CAIXDOA$ and PMRTDATA loaded in an LPAR at any time.
They are always backward compatible so the latest version should always be used.
The above instructions will ensure that.

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.

CAIRIM at the IDMS TechDocs pages.