Description:
Some PTFs, such as RO41423, update the SVC identified within the SMP/E environment. Clients may want to apply this update to other SVCs within their overall CA IDMS environment. This document outlines the procedures to accomplish that.
Solution:
When a PTF affects the SVC, the PTF contains HOLDDATA to notify you that the SVC is being modified. This Knowledge Document tells you how to install the PTF without affecting your production systems and how to create an alternate SVC to exercise the new code using your test systems. This Knowledge Document pertains to all PTFs affecting the SVC, but uses RO41423 as a specific example.
Installing PTF RO41423 updates your existing CA IDMS SVC load module in the SMP/E APFLIB loadlib. If you don't want your production system to use the updated SVC before you have tested it, ensure that CAIRIM loads SVCs from a different loadlib, not the SMP/E APFLIB loadlib. Doing so ensures that applying the APAR does not impact the live CA IDMS environment(s), even if your site has an unexpected IPL and CAIRIM is executed. For example, the CAIRIM job could be loading the CA IDMS SVC used by your CA IDMS CVs from a SYS1.LINKLIB loadlib that is not modified by any IDMS SMP/E process. In this case, installing PTF RO41423 re-links the CA IDMS SVC in your SMP/E controlled loadlib (APFLIB), but the updated CA IDMS SVC does NOT replace the current production SVC in the SYS1.LINKLIB loadlib. The updated SVC is not picked up by CAIRIM since it is not in the production CAIRIM loadlib.
Once you have updated your SVC load module in APFLIB, you can use it to create an alternate SVC load module (with a different SVC number) for testing. It is recommended that you create the alternate SVC load module outside of SMP/E. Since the alternate SVC load module name is different from your current one, you can link the alternate one into APFLIB without destroying your current one. You can then use a different set of CAIRIM JCL to load the alternate CA IDMS SVC load module containing the changes introduced by RO41423. This alternate SVC can be used by your test systems.
CA IDMS Support does not recommend using SMP/E to create any additional SVC load modules. That can be complicated and can result in difficult-to-correct errors. Instead, CA IDMS Support recommends that any additional SVCs be created outside of SMP/E using the following process.
//ASM EXEC PGM=ASMA90//SYSLIB DD DSN=SYS1.MACLIB,DISP=SHR// DD DISP=SHR,DSN=idms.smpmts// DD DISP=SHR,DSN=idms.distmac//SYSPRINT DD SYSOUT=*//SYSLIN DD DISP=(NEW,PASS),DSN=&&TEMP,// UNIT=SYSDA,SPACE=(TRK,(1,1)),// DCB=(RECFM=FB,LRECL=80,BLKSIZE=8880)//SYSIN DD *#SVCOPT SVCNO=ttt,ENVIRON=MVS,CVKEY=xEND/*
//LINK#SVC EXEC PGM=HEWL,PARM='LET,MAP,LIST,NCAL' //SYSUT1 DD UNIT=SYSDA,SPACE=(CYL,(20,20)) //SYSPRINT DD SYSOUT=* //APFLIB DD DISP=SHR,DSN=your.apflib //SYSLMOD DD DISP=OLD,DSN=your.apflib //SYSLIN DD DISP=(OLD,DELETE),DSN=&&TEMP // DD * ORDER IGCttt REPLACE IGCnnn INCLUDE APFLIB(IGCnnn) ENTRY IGCttt NAME IGCttt(R) /*