You can use any export file format to export from one CICSĀ® Configuration
Manager system to another,
but using the CICS Configuration
Manager format
offers the most flexibility:
- Browse exported resource definitions
- You can use CICS Configuration
Manager to
browse the resource definitions in a CICS configuration that refers
to a CICS Configuration
Manager export
file in exactly the same way you browse a CICS configuration that
refers to a CSD file or a context. You cannot browse CICS configurations
that refer to DFHCSDUP or BATCHREP export files.
- Export change package details along with resource definitions
- If you migrate a change package to a CICS configuration that refers
to a CICS Configuration
Manager export
file, then the export file contains not just the migrated resource
definitions, but also details of the change package. When importing
the export file on another system, you can either ignore these change
package details, or use them to register the
change package on the importing system. If you choose to register
the change package, then, in addition to copying the resource definitions
from the export file to another CICS configuration, the import:
- Defines the change package on the importing system (if a change
package of that name does not already exist).
- Adds to the change package the migrated resource definitions that
have now been imported (copied to another CICS configuration on the
importing system).
You can then use this change package to migrate the resource
definitions to other CICS configurations on the importing system.
Registering change packages enables you to seamlessly manage resource
definition changes across separate installations of CICS Configuration
Manager. For details, see Registering change packages when importing.
- Copy resource definitions from an export file using a variety
of methods
- You can use the following methods to copy resource definitions
from a CICS configuration that refers to a CICS Configuration
Manager export file to
another CICS configuration:
- These methods are exactly the same as for CICS configurations
that refer to CSD files or contexts.
- Copy
- Browse a list panel of the resource definitions, select one or
more to copy, and then specify the target CICS configuration (where
you want to copy the resource definitions to).
- Save as
- Similar to copying: select a resource definition to view its attributes,
and then save it to the target CICS configuration.
- Package
- Browse a list panel of the resource definitions, select one or
more to add to a change package, and then migrate the change package
to one or more target CICS configurations.
- The Import
command applies only to CICS configurations
that refer to CICS Configuration
Manager export
files. To import, you select the CICS configuration that refers to
the CICS Configuration
Manager export
file, select the target CICS configuration where you want to import
the resource definitions to, and then you specify which resource definitions
you want to import:
- All resource definitions in the export file
- Resource definitions that were migrated to the export file by
particular change packages
- Resource definitions in the export file that match your criteria
for name, type, and group
Figure 1. Exporting from one CICS Configuration
Manager system to another
Importing resource definitions from a CICS Configuration
Manager export file is
equivalent to a "copy with replace": it replaces any existing
resource definitions that have the same name, type, and group.
When importing resource definitions from a CICS Configuration
Manager export file, you
can optionally choose to purge resource definitions from the export
file after importing them. This is one way to confirm that you have
imported all the resource definitions in an export file: when the
export file no longer contains any resource definitions, it means
that you have imported all the resource definitions from that file.