Using change packages for actions and migrations

You can perform install, newcopy, and phase-in actions on active CICS® regions with either an ad-hoc selection of resource definitions or a change package. (You cannot perform discard actions with a change package; the discard action is limited to ad-hoc selections of resource definitions from CSD-based CICS regions.) You can perform these actions using the same change packages that you use for migrations. Table 1 lists the differences between using change packages to perform actions and migrations:

Table 1. Using change packages for actions versus migrations
Action Migration
Affects the in-memory resource definitions used by active CICS regions. Affects the resource definitions stored in CSD files or CICSPlex® SM data repositories.
For CSD-based resource definitions, uses the remote system connections defined in the target CICS configurations. Does not use remote system connections.
Does not require the change package to be ready. Requires the change package to be ready.
Does not require the change package to be approved. May require the change package to be approved.
Uses the resource definitions in the target CICS configurations of the specified migration scheme. Migrates the resource definitions from the source CICS configurations of the specified migration scheme.
Affects all CSD-based target CICS configurations in the migration scheme.

Affects only the first context-based target CICS configuration in the migration scheme. Ignores any subsequent context-based target CICS configurations in the migration scheme.

Affects all CSD-based and context-based target CICS configurations.
Does not use transformation rule sets. Can use transformation rule sets to modify resource definitions during migration.
Cannot be undone. Can be undone (backed out).
Attempts the action on each of the resource definitions in the change package individually, regardless of whether the action succeeds or fails. Migrates all or none of the resource definitions in the change package. (Stops at the first failure, and then automatically rolls out any resource definitions that have already been migrated.)

There is also a difference between performing an action on a CSD-based CICS region using a change package and using an ad-hoc selection of resource definitions:

You can use a change package as a convenient way of displaying a list of resource definitions for an "ad hoc" action. This is different to performing the action with the change package, because it does not involve a migration scheme. For details, see Processing a change package.


Information Information

Feedback


Timestamp icon Last updated: Friday, 1 November 2013


http://pic.dhe.ibm.com/infocenter/cicsts/v5r1/topic//ccv-packages-actions.htm