As a z/OS Datacom customer, can I place the Datacom loadlibs in my Linklist?
CA Datacom libraries are not normally a good choice for placing in your system's Linklist. The Best Practice recommendation is not to use the Linklist library for this product's libraries.
For this discussion, when we refer to a MUF (Multi-User Facility), we refer to a MUF instance with a unique CXX and MUFname. Data Sharing or MUFPLEX modes A and B are not part of this discussion.
Most shops today have more than one instance of a MUF on any given LPAR within a SYSPLEX. Some shops have multiple SYSPLEXs. The reasons for having multiple instances of a MUF are many and allow customers to have as much flexibility as needed for a Production, Development, and SYSPROG environment. There are other conditions in which sites may have different CA Datacom products that should not be co-mingled into the same MUF.
A Production CA Datacom environment can have many instances. CA has customers running CA Datacom with as many as 50 MUFs, and as few as 1 MUF. If a customer has many instances, what is common practice at these sites is do what is called "a rolling rollout of maintenance" to a set of MUFs that are in Development and Production. The goal is to certify the maintenance from a less-used environment to the most-used instances.
Eventually an upgrade to the next release of CA Datacom will have to be scheduled and performed on each MUF instance. By having private libraries on each MUF instance you can control when to perform the upgrade process without impacting any of the other MUF instances.
Each upgrade process is a unique process for a given release of the product. Most of the time spent on an upgrade path has to do with how much work has to run on each Datadictionary (DD), Datadictionary Directory (DDD), and for each CXX (Directory). Because each release of the product has new features or functions which require changes to the DD/DDD, and these have to be cataloged to the CXX, it is important to ensure the definitions are current before beginning the upgrade process. And each unique CXX and MUF instance must go through the same process each time you upgrade the product.
Therefore, due to the potential complexity of having all these different MUF instances, CA recommends that the Llinklist NOT be used and instead use private libraries within the STEPLIB or JOBLIB JCL.
Even if you have one instance of the MUF running, this is still the recommended procedure for running CA Datacom. It is difficult to predict when your site may require a new MUF instance or a product that CA is requiring use of CA Datacom/AD in the future. Business requirements may cause any shop to be dynamic and fluid to any changes and having private libraries gives you the most flexibility to accomplish your business needs.
As always, please contact Broadcom support for CA Datacom if you have further questions.