"Importing resource definitions" means copying resource definitions
from an export file to a CSD file or a context. How you do this depends
on the format of the export file:
- BATCHREP export files
- You cannot use CICS® Configuration Manager to
import a BATCHREP export file. To import resource definitions from
a BATCHREP export file, you must invoke the CICSPlex® SM BATCHREP command from the CICSPlex SM user interface.
- DFHCSDUP export files
- To import resource definitions from a DFHCSDUP export file, you
can either use CICS Configuration Manager to
generate a batch job that calls the DFHCSDUP utility (as described
in the procedure below), or use your own batch jobs to call this utility.
- CICS Configuration Manager export
files
- There are several ways to copy resource definitions from a CICS Configuration Manager export file:
- Display a list
panel of the resource definitions in the export file, enter C (Copy) next to one or more resource
definitions, and then specify a target CICS configuration.
- Display a list panel of the resource definitions in the export
file (as above), enter P (Package)
next to one or more resource definitions, select the change package
that you want to add the resource definitions to, and then migrate
that change package to one or more target CICS configurations.
- Follow the import procedure described below.
To import resource definitions from a DFHCSDUP export file or a CICS Configuration Manager export file:
- Define a CICS configuration
that refers to the export file (if you have not already done this):
- Select primary menu option 1.2 CICS Configurations.
- On the command line, enter DEF.
For
details, see Defining CICS configurations that refer to export files.
- Select primary menu option 2 CICS Resources.
This displays
a list of CICS configurations.
- Enter IMP next to either the
source CICS configuration (that
refers to the export file) or the target CICS configuration (where you want to copy the
resource definitions to).
- Select the other (source or target) CICS configuration.
- Specify the import options.
For DFHCSDUP export files, you
specify the batch job stepped library for the DFHCSDUP utility, and
then either press Enter to submit the DFHCSDUP batch job, or edit
the JCL, and then enter SUB on the edit
panel to submit the job.
For CICS Configuration Manager export files, you
can choose one of several options for selecting which resource definitions
to import:
Figure 1. ISPF panel:
import processing options for a CICS Configuration Manager export file File Menu Settings Help
──────────────────────────────────────────────────────────────────────────────
Import IMPORT CICS Resources
Command ===>
Choose a processing option and press Enter to continue
Import source and target CICS Configurations
Source . . : IMPORT (KSM.EXPORT.DNF)
Target . . : CCVPLEXD (CCVPLEXD)
Choose a processing option
1. Display packages
2. Display resources
3. Import entire file
4. Import packages . . . + (Masking supported)
5. Import using filters
Filter name . . . . *
type . . . . * +
group . . . *
F1=Help F3=Exit F4=Prompt F5=Rlocate F6=Zoom F7=Backward
F8=Forward F12=Cancel
- Display packages
- Displays a list of the change package migrations
to the export file, if any. If you have migrated a change package
to the export file more than once, this list shows each migration
as a separate item.
If resource definitions were migrated to
the export file, rather than copied or saved to the export file without
using a change package, then the export file contains information
about which change package the resource definitions belonged to.
To
select all of the resource definitions in a change package migration,
enter IMP next to the change package
migration.
To display a list of the resource definitions in
a change package, enter S next to
the change package. To find out what actions you can perform
on the items in the list, enter / next to an item.
- Display resources
- Displays a list panel of the resource definitions in the export
file. This is similar to the panel displayed if you select the CICS configuration for the export
file via primary menu option 2 CICS Resources, except that
this panel also includes a column showing which change packages (if
any) were used to migrate the resource definitions to the export file.
- Import entire file
- Selects all of the resource definitions and commands in
the export file.
- Import packages
- Selects the resource definitions and
commands in the export file that were migrated to the export
file by the change packages that you specify. This option selects
all migrations of the specified change packages; to select a particular
occurrence of a migration for a change package, use the Display
packages option instead.
- Import using filters
- Selects resource definitions and commands in
the export file that match the name, type, and group values that you
specify.
- CICS Configuration Manager export
files only: after you select which resource definitions and
commands to import, a pop-up window appears with the following
options for specifying how to process the selected resource definitions and commands:
- Register change packages on import
- If the file contains change package details, then selecting this
option "registers" (creates or updates) the change packages that
contain the resource definitions and commands that
you have selected to import.
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.
For
more information on registering change packages, see Registering change packages when importing.
- Purge imported records from import file
- Deletes resource definitions and commands from
the export file after importing them.
Is it an export file or import file?
You can use the terms "export file" and "import file" to refer to the same file depending on how it is being used. At
the site where the file is created, the file is typically referred
to as an export file. At the site where the contents of the file are
imported, the file is typically referred to as an import file. For
the sake of consistency, and to make it easier to search for related
information, this documentation uses the term "export file" throughout.