If you choose to register change packages when importing a CICSĀ® Configuration
Manager export file, the
following considerations apply:
- If a change package of the same name already exists in the importing CICS Configuration
Manager repository, then
the import adds the resource definitions and commands from
the export file to the existing change package. The import updates
the existing change package with the following change package details
from the export file:
- Change package description
- External reference
- Approval profile
- If you used filters to select the resource definitions and commands to import, the import only adds those
selected resource definitions and commands to
the registered change packages. This means that the registered change
packages might contain only a subset of the resource definitions and commands that were migrated to the export file.
- The registered change packages refer to the imported resource
definitions in the target CICS configuration of the import,
not the resource definitions in the export file. For example, in Figure 1,
the registered change package on the importing system refers to resource
definitions in the "Staging" CICS configuration,
not the "Import" CICS configuration. Similarly,
imported commands added to registered change packages are associated
with the target CICS configuration of the import.
- To use the registered change packages to migrate
the imported resource definitions and commands to
another CICS configuration, you must use a migration
scheme that specifies the target CICS configuration
of the import as a source CICS configuration. For example,
in Figure 1,
you would use a migration scheme that specifies "Staging" as
a source CICS configuration.
- The registration appears in the change package history
as an Import command. Although the Import command does not use a migration
scheme, the name of the target CICS configuration
of the import appears under the migration scheme column. This is for
documentation only. Registering a change package does not create a
migration scheme of this, or any other, name.
- To import commands, you must select
the option to register change packages. If you do not select this
option, the import ignores commands in the export file.
- When importing commands, CICS Configuration
Manager applies the commands
to the target CICS configuration of the import, and also adds
the commands to the registered change packages. If the target CICS configuration
of the import does not support a command (for example, CSD-based CICS configurations
do not support Add or Remove commands), then CICS Configuration
Manager still adds the
command to the registered change package.
- If you select the option to register change packages,
and the import of a command or a resource definition that was migrated to
the export file fails, then CICS Configuration
Manager rolls out the import
of all commands and resource definitions that were migrated to the
export file.
If you do not select this option, and an import fails,
then the import stops, but no roll out occurs.
Regardless
of whether or not you select the option to register change packages,
roll out does not occur for resource definitions that were copied to
the export file without using a change package.
- You can back out the Import command for a registered
change package, in the same way that you can back out a Migrate command.