Preparation for rolling IPL

BMC AMI Utilities products can run server jobs on multiple LPARs and have an BMC AMI Utilities Subsystem started task, also known as CDBSS running on each LPAR. This topic describes what to do in preparation and response to a server shutting down.

Shut down process

Normally, before an LPAR shuts down, work on it is quiesced to prevent interruption of transactions and jobs. When this occurs, the only concern is the CDBSS. Provided that the CDBSS is up when all the Db2s terminate, the CDBSS can ensure that no Db2 changes are missed and product work on other members of the data sharing group can continue. The same is true for startup: provided that CDBSS is started before the Db2, the CDBSS ensures that no changes were missed.

The CDBSS will probably have captured changes from Db2 transactions on objects that BMC AMI Utilities products have processed. When the CDBSS shuts down, it transfers these changes to the CDBSS on the LPAR on which the master job is running. This transfer occurs via a channel adapter on which I/O is very fast (normally, only a few seconds). If the transfer fails, all related BMC AMI Utilities products fail to prevent the loss of any transactions.

If a server is actively working on an object when the Db2 subsystem is stopped, that work fails and the object is excluded from processing. Work on the other objects will complete and, in most cases, the master submits a replacement server on one of the remaining LPARs to complete the work using the same number of servers originally planned.

Preparation and response

1. Set up your IPL procedures and configureBMC AMI Utilities as described in Shutting down BMC AMI Utilities Subsystem. This configuration ensures that the Db2 subsystems terminate before the CDBSS terminates, and are restarted after the CDBSS restarts.
2. Perform one of the following actions with the excluded objects caused by the Db2 subsystem shutting down:

   • Rerun the job to restart the UID and process it. For more information, see RESTART.

   • Perform QUICKEXIT to clean up and skip it. You can make this decision in advance with the +CLEANUP parameter to avoid the need to perform RESTART or QUICKEXIT.