BMC AMI Copy job statements
To build an
job, you must create a JCL that includes several statements.
The following statements are required:
- A JOB statement (JOB-statement)
- An EXEC statement that includes
utility parameters that specify whether the utility job is a new job, a restart, or a termination and (optionally) specify a user-named installation options module (EXEC-statement and Utility-parameters-on-the-EXEC-statement)
- Data definition (DD) statements (BMC-AMI-Copy-data-set-DD-statements) that specify the following data sets:
- The
and Db2 load libraries to use, and optionally, the Db2 exit library to use
- The SYSPRINT output data set to use for
messages
- The ACPPRT nn output data set to use for task level messages (if not specified,
dynamically allocates the data sets to SYSOUT)
- The ACPERROR or ACPERR output data sets in which
can write messages of type E and W
- The output data sets to use for the copies if copies are made (not required when you dynamically allocate the copy data sets)
- The SYSIN input data set (the OPTIONS, COPY, COPY IMAGECOPY, OUTPUT, RECALL, MODIFY, or TEMPLATE commands and options)
- The ACPGDG data sets can be used to provide a GDG model for newly created output data sets
- The
The descriptions in the following sections provide more details. You can also see the examples of
JCL in Examples-of-BMC-AMI-Copy-jobs and to the JCL samples provided in members ACPEX nn of the HLQ.ACPSAMP installation data set (where HLQ is the high-level qualifier specified during installation).
You can also use the
, DASD MANAGER PLUS, ALTER, and Change Manager products to generate
jobs. For more information, see the reference documentation of these products.
This section contains the following topics:
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*