Creating a batched repository-update (BATCHREP) input file

A batched repository-update facility input file consists of control statements that describe the updates you want to make to the data repository.

The input file must adhere to the following requirements:

Control statements must be in uppercase.
Each control statement must be terminated with a semicolon (;).
Comments must be delimited with /* at the beginning and */ at the end. (Any line with * in column 1 is also treated as a comment.)

Control statements and comments can span multiple lines.

When creating your input file, you must first identify the context (CMAS or CICSplex) to which the updates apply. To do this, use the control statement:

   CONTEXT [plexid]

where plexid is the name of the local CMAS or of a CICSplex associated with the local CMAS (the local CMAS is the CMAS on which the batched repository-update job runs). If you specify a CICSplex as the context for the update, the local CMAS must be the maintenance point for that CICSplex. If you omit this parameter, the local CMAS is assumed to be the context.

Once you have established a context, it remains in effect for the batched repository-update job until you explicitly change it with another CONTEXT statement.

The rest of the control statements in an input file vary according to the type of updates you are making. The following sections describe the control statements for each type of update in detail.

eyua7a2.html | Timestamp icon

Last updated: Thursday, 27 June 2019

Creating a batched repository-update (BATCHREP) input file

Subtopics