Export and import of commands

Export and import of commands extends the concepts involved in export and import of resource definitions and migration of commands.

In addition to exporting and importing resource definitions between sites, you can export and import the following commands from one CICSĀ® Configuration Manager system to another:

Add
Adds a resource definition to a resource group (RESGROUP) in a context-based target CICS configuration.
Remove
Removes a resource definition from a resource group in a context-based target CICS configuration.
Delete
Deletes a resource definition from either a CSD-based or a context-based target CICS configuration.

"Exporting a command" means storing a copy of the command in a CICS Configuration Manager format export file on the exporting system. You do this by migrating the command to the export file. Then, using whatever method you prefer, you transfer the export file to the importing system.

"Importing a command" means adding the command that is stored in the export file to a change package on the importing system and applying the command to a CICS configuration on the importing system. You do this using the Import command.

Here is the procedure for exporting and then importing commands:

  1. On the exporting CICS Configuration Manager system:
    1. Define a CICS configuration that refers to a CICS Configuration Manager export file. (This is the only type of export file that supports CICS Configuration Manager commands.)
    2. Define a change package, and then add the commands to the change package. Associate the commands with either:
      • The CICS configuration that you have just defined (that refers to the export file).
      • A CICS configuration that is the source in a migration path where the export file CICS configuration is the target. Choose this option if you want the migration to transform the command before storing it in the export file.
    3. Migrate the change package to the export file. That is, migrate the change package using a migration scheme that nominates the export file CICS configuration as a target CICS configuration.

    This stores copies of the commands in the export file.

  2. Transfer the export file to the importing system, using whatever file transfer method you prefer (for example, FTP).
  3. On the importing CICS Configuration Manager system:
    1. Define a CICS configuration that refers to the export file.
    2. Run the Import command with the export file CICS configuration as the source, the CSD-based or context-based CICS configuration to which you want to apply the commands as the target, and with the option selected to register change packages.
      Note: If you do not select the option to register change packages, the import ignores commands in the export file, and only imports resource definitions.

      The import applies the commands to the target CICS configuration (along with any selected resource definitions), and also adds the commands (and selected resource definitions) to a change package of the same name in the CICS Configuration Manager repository of the importing system.

Example

The following figure shows the migration of a Delete command to an export file:

Figure 1. Migrating a Delete command to an export file

The change package specifies that the Delete command is associated with CICS configuration DEVT. This matches the source CICS configuration of the migration path in the migration scheme, so CICS Configuration Manager transforms the command before storing it in the export file. In this example, the migration path refers to a transformation rule set that transforms group names from *DEVT to *TEST. So the command that CICS Configuration Manager stores in the export file refers to the transformed group name PAYTEST, not the group name PAYDEVT of the original command.

The following figure shows the import of the Delete command to a separately managed system, after you have transferred the export file from the exporting system:

Figure 2. Importing a Delete command

Importing the command has two effects: