Deploying maintenance to agents

Use the following procedures to apply maintenance to the agents that run within the DBC and to DBC.

To apply maintenance for agents

Use this procedure to apply maintenance to the agents that run within the DBC:

1. Issue the following console command on the LPAR where the DBC started task running:
   
   /ssid DBC,DISP,DSNS 
   
   ssid is the DBC subsystem identifier.
   
   
2. Review the output in the DBCPRINT DD in the active DBC started task.
   In the DISP,DSNS display, any data sets labeled as PRODUCT come from LOADLIB values in 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) or from EXEC-LOADLIB values in the pppOPTS member located in the DBCENV data set for this DBC.
   
   If you have defined alias names for the EXEC-LOADLIB values, look for the “Objects Using DSNs” section of the DISP,DSNS output to see which DBCagents are using that data set or alias. Those agents will need to be stopped before redefining the alias to the new data set name.
   
   
3. Review the PTFs that are being applied to determine which FMIDs will be affected.
   
   
4. Based on how you organized your runtime load libraries in the installation, cross-reference these lists with Changing-references-to-the-product-load-library to determine which agents will need to be refreshed.
   
   

5. Perform one of the following actions:

   • If the DBC is using a data set or alias identified in the output from the DISP,DSNS command issued in step 1, stop the DBC. 

   • If you did not stop the DBC, issue the STOP command for each agent that is receiving new maintenance.

     Best practice
     BMC recommends deploying new maintenance when no users will be attempting to use the product. Stopping agents when users are in the product can cause error messages that indicate the agent is stopping or is unavailable.

   The following table lists commands to stop agents. The ssid value represents the identifier of the DBCsubsystem.

   To stop agent	Issue this console command
   BRD	/ssid BRD,STOP Warning The BMC Subsystem Optimizer for zEnterprise (BRD) agent in the DBC should not be stopped and then started until a planned outage as because it can cause interruptions for Db2, IMS, CICS, or MQ for which BRD may be redirecting server connections. During a planned outage, such as at IPL time, redefine the alias to point to the new libraries.
   DOM	/ssid DOM,STOP
   GUD	/ssid GUD,STOPALL
   LGC	/ssid LGC,STOP
   NGL	/ssid NGL,STOP,piid The piid value identifies the NGL ID. Warning Not stopping the  NGL  client products that require  NGL  before recycling their  NGL  agents can result in the clients and agents running at different levels which might cause problems. Issuing a STOP for  DBC agents DOM and MVL will also stop their  NGL  PIIDs.
   MVL	/ssid MVL,STOP

6. Copy the changed members from your target zone to your runtime libraries, observing the following guidelines:

   Note

   Maintenance usually updates the load library but can sometimes include other libraries such as PLIB, XML, and so on. Do not forget to copy these libraries to the runtime data sets, too.

   • If you have an alias defined to your runtime load library and you typically copy new maintenance to a second load library, delete the alias from the old library and define it to the new library.
   • If you apply maintenance to a new set of libraries and want to use them in place of the current runtime data sets, follow the instructions in Changing-references-to-the-product-load-library.
   • If you are using LINKLIST instead of LOADLIB elements or the DBC STEPLIB, issue the LLA REFRESH command.
     
     
7. If you are going to start the any BRD, DOM, or GUD agents, issue the DBC,EXEC,LGC command.
   
   

8. Issue the following commands for each agent that is receiving new maintenance and that was previously stopped.
   The ssid value represents the identifier of the DBC subsystem.

   
   

   To start agent	Issue this console command	Comments
   BRD	/ssid DBC,EXEC,BRD	Issue the DBC,EXEC,LGC command before starting the BRD, DOM, or GUD agent.
   DOM	/ssid DBC,EXEC,DOM	Issue the DBC,EXEC,LGC command before starting the BRD, DOM, or GUD agent.
   GUD	/ssid DBC,EXEC,GUD	Issue the DBC,EXEC,LGC command before starting the BRD, DOM, or GUD agent.
   LGC	/ssid DBC,EXEC,LGC	None.
   MVL	/ssid DBC,EXEC,MVL	None.

To apply maintenance to the DBC

1. Ensure that all users have been notified of the maintenance window.

2. Stop the DBC started task by using the following console command, where ssid is the DBC subsystem ID:

   p ssid
   
   

3. Copy the changed members from your target zone to your runtime libraries.

   Note

   Maintenance usually updates the load library but can sometimes also include other libraries such as PLIB, XML, and so on. Do not forget to copy these libraries to the runtime data sets too.

   • If you have an alias defined to your runtime load library, and you typically copy new maintenance to a second load library, you must delete the alias from the old library and define it to the new library.
   • If you apply maintenance to a new set of libraries and want to use them in place of the current runtime data sets, edit the DBC$STC PROC and change the STEPLIB to point to the new runtime data sets.
   • If you are using LINKLIST instead of <LOADLIB> elements issue the LLA REFRESH command.
     
     

4. Start the DBC started task by issuing the following console command, where dbcproc is the name of the DBC$STC started task member in your PROCLIB:

   s dbcproc