Changing references to the product load library

To change the names of the product load libraries

The installation process updates the LOADLIB keywords in the pppvvrm members (where ppp is the 3-character product code and vvrm is the version, release, and maintenance level of the product being installed) of the DBCENV data set with the latest runtime libraries specified in the installation panels. If you have renamed those libraries or want to use different names, use the following procedure:

1. Edit the pppvvrm member in the DBCENV data set:
   1. Change the values for the LOADLIB keywords to the new names. The order listed will be the concatenation order that the DBC uses. 
   2. Delete any LOADLIB values that you do not want to use. The unwanted lines can also be commented out by placing an asterisk (*) in the first column of that line.
       

2. Issue the following console command to refresh the product agent and have the change take effect:

   /dbcssid DBC,EXEC,ppp
   
   In the command:

   • dbcssid is the DBC subsystem identifier
   • ppp is the three-character product code matching the first three characters of the pppvvrm member name

To specify alias names or a designated set of execution libraries for the product load libraries

If you prefer to use alias names or a designated set of libraries from release to release, you can edit the pppOPTS members. Doing so will be a one-time update since the pppOPTS member is not updated by the installation process nor the DBC once it has been created. 

1. Edit the pppOPTS members in the DBCENV data set (where ppp is the three-character product code):   

   1. Add a line for the keyword EXEC-LOADLIB and specify your alias name or designated execution library.

      Replicate the line if needed to specify more libraries. The order listed is the concatenation order that the DBC uses. The number of EXEC-LOADLIB keywords does not have to match the number of LOADLIB keywords from the pppvvrm member (where ppp is the 3-character product code and vvrm is the version, release, and maintenance level of the product being installed). 

   2. Ensure that USELOADLIB keyword is not used, is commented out, or is set to YES.
       
2. Switch the alias definitions to the new set of underlying data sets or reload the designated set of libraries if necessary.
    

3. Issue the following console command to refresh the product agent and have the change take effect:

   /dbcssid DBC,EXEC,ppp 
   
   In the command:

   • dbcssid is the DBC subsystem identifier
   • ppp is the three-character product code matching the first three characters of the pppvvrm member name

To use a STEPLIB or LINKLIST for the product load libraries

If you prefer to have the product agents find their load modules from the STEPLIB of the DBC$STC started task or from LINKLIST, you can edit the pppOPTS members. Doing so will be a one-time update since the pppOPTS member is not updated by the installation process nor the DBC once it has been created.

1. Edit the pppOPTS members in the DBCENV data set (where ppp is the three-character product code).
   
   Ensure that the USELOADLIB keyword is set to NO, which sets the search order for product load modules to look in the STEPLIB of the DBC$STC started task followed by LINKLIST.
    
2. Ensure that the product load modules are either in the DBC STEPLIB or in LINKLIST. 
    

3. Issue the following console command to refresh the product agent and have the change take effect:

   /dbcssid DBC,EXEC,ppp 
   
   In the command:

   • dbcssid is the DBC subsystem identifier
   • ppp is the three-character product code matching the first three characters of the pppvvrm member name

Runtime data sets used by product agents

Use the following information to determine which runtime data sets to use for specific DBC agents.

During the installation process, you are offered the following options for naming the low-level qualifiers (LLQ) for your runtime data sets:

The following table lists the SMP/E target load library names and the corresponding runtime LLQs if option 2, for runtime LLQs, was chosen. If during installation you chose to customize directly to the SMP/E target data sets themselves, use the names in the SMP/E Target load library names column.

^{1 The GUD agents used by BMC AMI Command Center require that the Db2 DSNLOAD library be included in the GUD concatenation. Add the Db2 DSNLOAD library to the list of LOADLIB keywords. If the Db2 DSNLOAD library is included in the LINKLIST, you do not need to include it in the concatenation.}

^{2 If you have selected runtime LLQ option #1, all the data set names will have BMCLINK as the low-level qualifier.}

The following table lists load libraries that the DBC needs.

^{1 If you have selected runtime LLQ option #1, all the data set names will have BMCLINK as the low-level qualifier.}