Different clients have different ways of managing their system product loadlibs. For some, having a single product loadlib (CABDLOAD for CA Datacom/DB, and CAAXLOAD for CA Datacom/AD) for all MUFs on a single LPAR, or in a single tier of LPARs helps them to better accomplish their objectives.
Can the CA Datacom product loadlib (CABDLOAD for CA Datacom/DB, and CAAXLOAD for CA Datacom/AD) be coded as a dataset alias in the STEPLIB of our JCL?
As an example, you might want to use alias SYS3.DATACOM.PROD.LOADLIB in your STEPLIB, so that with incremental or version releases, it is not necessary to change the JCL. This is especially useful when coded in different database utility jobs - backups, restores, etc., as a change to the loadlib name could require updates to many JCL members.
Using a dataset alias in this case is not a problem, as the alias is resolved to the actual file name when the step (or job, when using a JOBLIB) is run.
As always, please contact CA Technologies support for CA Datacom if you have further questions.