Export and import with CICS Configuration Manager

CICS® Configuration Manager treats export files as CICS configurations. With some restrictions, CICS Configuration Manager allows you to work with resource definitions in export files in exactly the same way that you work with resource definitions in CSD files or contexts. This enables you, for example, to copy or migrate resource definitions to an export file in exactly the same way that you copy or migrate to a CSD-based CICS configuration.

You can use CICS Configuration Manager to write export files in three formats:

DFHCSDUP export file (write only)
To import resource definitions from this file to a CSD file, you use the DFHCSDUP utility supplied with CICS Transaction Server for z/OS®. You can write the JCL yourself to call the DFHCSDUP utility, or you can use the CICS Configuration Manager ISPF dialog interface to generate the JCL for you.
BATCHREP export file (write only)
To import resource definitions from this file to a context, you use the BATCHREP utility supplied with CICS Transaction Server for z/OS. CICS Configuration Manager does not provide an interface to this utility: to import a BATCHREP export file, you must use the CICSPlex SM BATCHREP command interface supplied with CICS Transaction Server for z/OS.
CICS Configuration Manager export file (read and write)
To import resource definitions in this file to either a CSD file or a context, you use CICS Configuration Manager.

All of the export file formats are QSAM files: for file allocation details, see Defining CICS configurations that refer to export files.

Figure 1. CICS Configuration Manager treats export files as CICS configurations
 1 
If a CICS configuration refers to a CICS Configuration Manager export file, then you can use CICS Configuration Manager to browse and explore its contents in exactly the same way as if the CICS configuration referred to a CSD file or a context. However, writing to such a CICS configuration either appends to the file or overwrites its entire contents; you cannot "update in place". You specify this append or overwrite option when you define the CICS configuration.

For example, if you choose the append option, and then you migrate change packages to that CICS configuration, the export file grows as you migrate each change package. However, if you choose the overwrite option, then each migrated change package overwrites the previous contents of the export file; similarly, if you edit a resource definition, and then enter the SAVEAS command, that single edited resource definition replaces the entire existing contents of the export file.

 2 
CICS configurations that refer to DFHCSDUP or BATCHREP export files are write-only. You can copy, migrate, or create and save resource definitions to these CICS configurations, but you cannot use CICS Configuration Manager to read their contents.

Use these export files to transfer resource definitions to systems that do not have CICS Configuration Manager. To import the resource definitions in these files, use the DFHCSDUP utility or the BATCHREP utility supplied with CICS Transaction Server for z/OS.

CICS Configuration Manager does not read these export file formats because, although the DFHCSDUP and BATCHREP export files created by CICS Configuration Manager are straightforward, the DFHCSDUP and BATCHREP utilities can read files that contain a variety of syntax. To provide full support for reading such files, CICS Configuration Manager would need to duplicate the complex parsing already provided by these utilities. Instead, CICS Configuration Manager provides its own readable export file format.


Information Information

Feedback


Timestamp icon Last updated: Friday, 7 February 2014


http://pic.dhe.ibm.com/infocenter/cicsts/v5r1/topic///ccv-export-with.htm