Ian_Hill

CA Tuesday Tip: (CA IDMS) Different PMSMFEX versions

Discussion created by Ian_Hill Employee on Feb 19, 2013
Latest reply on Feb 20, 2013 by antyv01
CA IDMS Tuesday Tip by Yves Anthoons, Principal Support Engineer for February 19, 2013.

If a CA-IDMS (dictionary) environment is upgraded from one release to another, and is also used for different releases concurrently is the short upgrade period, a problem may arise with regard to the PMSMFEX (SMF extraction) module.

Assume that a 17.0 CA-IDMS system is upgraded to 18.0. During this upgrade, a new PMSMFEX module (release 18.0) is uploaded into your (SYSDIRL) dictionary, overwriting the previous (release 17.0) module.

As such, this PMSMFEX module cannot be used anymore to extract SMF records written by Performance Monitor from release 17.0.

Question: How to avoid this?
Answer :

1. Before doing the upgrade install, rename the existing PMSMFEX module, for example to PMSMFEX170 (if the current one is from release 17.0).
2. When you need to extract SMF records written by Performance Monitor release 17.0, adapt the SYSIN parameters for the CULPRIT job accordingly:

//CPS EXEC PGM=CULPRIT
//SYSIN DD *
DATABASE DICTNAME=SYSDIRL
PARAM=NOLIST
=MACRO 'PMSMFEX170' (230)
=MEND

3. When you need to extract SMF records written by Performance Monitor release 18.0, use the "default" SYSIN parameters for the CULPRIT job :

//CPS EXEC PGM=CULPRIT
//SYSIN DD *
DATABASE DICTNAME=SYSDIRL
PARAM=NOLIST
=MACRO 'PMSMFEX' (230)
=MEND

Outcomes