This section describes some considerations for applying maintenance to agents that run within the
DBC
subsystem.
The installation will customize pppvvrm members (where ppp is the 3-character product code and vvrm is the version, release, and maintenance level of the product being installed) and place them in the data set referenced on the DBCENV DD of the DBC started task. These members will contain one or more LOADLIB keywords that reference the execution libraries that the agent should use.
The DBC started task is meant to be a long-running address space service that remains active for the life of an IPL, similar to the RTCS started task. The purpose of the LOADLIB keywords is to enable recycling an agent (not the DBC started task) when maintenance is applied.
As generated by the Installation System, only the load libraries that the agent needs are specified in the pppvvrm member. If you specified to use a single runtime load library, that same library will be in the definition for each agent. The DBC started task needs to be recycled only when DBC maintenance is applied.
The DBC creates a TASKLIB consisting of any product libraries defined to the DBC followed by any libraries in the STEPLIB. If neither of those are defined, the load modules should be in LINKLIST.
Product load libraries can be defined to the DBC as follows:
Check the pppOPTS members in the DBCENV data set (where ppp is the 3-character product code). If the keyword USELOADLIB=NO is set for all of the pppOPTS members, the STEPLIB of the DBC$STC should contain the product load modules or they should be in LINKLIST.
If the keyword EXEC-LOADLIB is specified in the pppOPTS members (and USELOADLIB is missing or set to YES), those data sets are allocated by the DBC. (The EXEC-LOADLIB can reference alias names for data sets.)
If the keywords USERLOADLIB=NO and EXEC-LOADLIB are not specified in the pppOPTS members, check the pppvvrm members (where ppp is the 3-character product code and vvrm is the version, release, and maintenance level of the product). Any LOADLIB data sets are allocated by the DBC.