You can use the batch command program to process existing change
packages; for example, to ready, approve, or migrate change packages
that you have already created using the ISPF dialog. Each of the batch
commands for processing change packages calls an API command of the
same name:
- READY
- Indicates that the resource definitions in
a change package are ready for migration.
- UNREADY
- Indicates that the resource definitions
in a change package are no longer ready for migration.
- APPROVE
- Adds to a change package the approval of
a particular approver role.
- DISAPPROVE
- Removes from a change package the approval
of a particular approver role.
- MIGRATE
- Copies the resource definitions in a change
package from source to target CICS® configurations,
and invokes commands in the change package on target CICS configurations, according to the specified
migration scheme.
- BACKOUT
- Backs out a previous change package migration.
- INSTALL
- Dynamically makes resource definitions
available to an active CICS region.
- NEWCOPY
Reloads in-memory copies of
resource definitions associated with a CICS program
definition or document template definition.
- IMPORT
- Imports resource definitions from an export
file received from another CICS Configuration
Manager system. Optionally,
if the export file contains change package details, also registers
change packages in the importing CICS Configuration
Manager repository.
These batch commands represent only a subset of the API commands.
For a complete list of API commands, see Using the SOAP API.
Figure 1. The batch command program
translates batch commands into API commands of the same name
These batch commands provide a simple batch interface
for integrating CICS Configuration
Manager with
change control products such as IBM® Rational Team Concert™ (RTC).
The reference topics for each batch command contain only brief
descriptions of the commands and their formats. For more detailed
information, see the descriptions of the equivalent API commands in Using the SOAP API. For descriptions of the command
parameters, see API parameters.
For sample JCL to use these batch commands, see JCL to invoke the batch command program.