IBM Books

Administering Satellites Guide and Reference


Chapter 2. Batches

Partial Table-of-Contents

  • Batch Modes
  • Group Batches
  • Types of Group Batches
  • Application Versions
  • Levels of an Application Version
  • States of an Application-Version Level
  • States of an Application Version
  • Application Version Life Cycle
  • Update Batch in a Test Level
  • Promoting a Test Level to a Production Level
  • Creating a Test Level from a Production Level
  • Obsoleting a Production Level
  • Relationships Between Batches and Batch Steps
  • How Satellites Execute Batch Steps
  • Scripts and Batch Steps
  • Components of a Batch Step
  • Parameterizing Scripts
  • Script Storage on the Satellite During a Synchronization Session
  • Fix Batches
  • You use batches to ensure that the satellites in a group remain as similar as possible. All the group satellites execute the same group batches that set up and maintain the database definition and data for their version of the end-user application. They also execute the batch steps of these batches in the same order. Because the group satellites execute the same group batches and batch steps, each satellite in the group will be similar.

    You can also use batches to fix satellites that either report problems, or require an adjustment. The function of a batch depends on its mode. For more information, see Batch Modes.

    A batch is an ordered set of batch steps. A batch step is the combination of a script, the target against which the script is to execute, the authentication credentials required for the script to execute against a DB2 instance or database, and a success code set to indicate whether the script completed successfully or not. The script can be a DB2 command, SQL statement, or an operating system command that you want a satellite to run. For more information, see Components of a Batch Step.


    [ Top of Page | Previous Page | Next Page | Table of Contents | Index ]

    [ Top of Page ]