Although the satellites of a group run the same end-user application, they do not have to run the same version of this application. Each version of the end-user application may require a database definition that is different from the other versions of the same application. To set up and maintain the database definition and the data to support a particular version of the end-user application, you use group batches for the application version. Each application version of a group is associated with its own batches.
Each batch is a collection of one or more batch steps. You create these batch steps to set up and maintain both the database definition and the data for the application version. The batch step is executed on the satellite when the satellite synchronizes.
A batch step is made of the following components:
The batch steps within a batch are always executed in the sequence in which they appear in the batch. When one batch step within a batch is executed successfully, the next batch step is executed. If, as defined by the success code set, an error occurs when a satellite is executing a batch step, that satellite stops executing its group batches, and reports an error back to the DB2 control server. When the error is fixed, the satellite can continue executing from the batch step that caused the error.
The application version is set at the satellite, typically during the installation and configuration of the end-user application on the satellite. When a satellite synchronizes, it reports its application version to its DB2 control server before it downloads and executes the scripts associated with the group batches for the application version.
For more information about batches, batch steps, and application versions, see Chapter 2, Batches.
[ Top of Page ]