We are upgrading DATACOM from R15 to R15.1 this weekend and noticed that the CAS9 Proc contained the below two entries for CAAXLOAD.
. . .
//CAIRIM EXEC PGM=CAIRIM,TIME=1440
//STEPLIB DD DSN=SYS1.CA1.LOAD,DISP=SHR
// DD DSN=APFPCA7.UCC7SPC.HTF1.CAL2LOAD,DISP=SHR
// DD DSN=APFPDCOM.HTF1.R14.ENF.CAAXLOAD,DISP=SHR
. . .
//DBLIB DD DSN=APFPDCOM.HTF1.R14.CAAXLOAD,DISP=SHR
. . .
Component : Datacom/AD
Component : Datacom/DB
These CAS9 JCL entries are left over from older versions and have not been cleaned up.
These entries are in your PARMLIB member:
* CA DATACOM AD 14.0
PRODUCT(CA DATACOM) VERSION(BD14) INIT(DBCR4PR) -
LOADLIB(APFPDCOM.HTF1.R14.CAAXLOAD) -
PARM(PC=PROD,PCC=DBPCCPR)
PRODUCT(CA DATACOM) VERSION(BD14) INIT(DBCR4PR) -
LOADLIB(APFPDCOM.HTF1.R14.CAAXLOAD) -
PARM(PC=PROD,PCS=DBPCSPR)
This set of modules is loaded for Datacom Version 14.0. As you can see, it uses APFPDCOM.HTF1.R14.CAAXLOAD for both modules (DBPCCPR and DBPCSPR).
* CA DATACOM AD R15.0
PRODUCT(CA DATACOM) VERSION(BD15) INIT(DBCR5PR) -
LOADLIB(APFPDCOM.HTF1.R15.MUF111A.CAAXLOAD) -
PARM(PC=PROD,PCC=DBPCCPR)
This is for the Datacom Version 15.x load of DBPCCPR (there is no DBPCSPR any longer). This module is loaded from APFPDCOM.HTF1.R15.MUF111A.CAAXLOAD.
These Parmlib entries appear correct as entered, and they are all you need for your Datacom environment. In previous releases (r12.0, 11.0, etc.), we handled this sort of processing in a different way, and these required the STEPLIB and DBLIB entries to load the SVC that was used in those versions. You mentioned in your note that you will be removing the 14.0 entries, and I think you can clean all this up at the same time.
If you know for certain that you are only running Version 15.x Datacom MUFs, then this will be what you need to do.
As always, please contact Broadcom support for Datacom if you have further questions.