Exporting resource definitions to another site

To send copies of resource definitions from your system to remote sites that might or might not have CICSĀ® Configuration Manager:

  1. Use CICS Configuration Manager to write the resource definitions to a CICS configuration that refers to an export file.

    To define a CICS configuration that refers to an export file:

    1. Select primary menu option 1.2 CICS Configurations.
    2. On the command line, enter DEF.

      For details, see Defining CICS configurations that refer to export files.

    There are several ways to write resource definitions to a CICS configuration (these apply to any CICS configuration, not just those that refer to export files):

    • Edit or view a resource definition, and then enter SAVEAS on the command line, and specify the CICS configuration that refers to the export file.
    • Display a list panel of resource definitions, and then enter C (Copy) next to the resource definitions that you want to write to the export file, and specify the CICS configuration that refers to the export file.
    • Package resource definitions into a change package, and then migrate the change package to the CICS configuration that refers to the export file.
  2. Use your preferred method to transfer the export file to the remote site.

    The method that you use to transfer export files to remote sites depends on your network environment: CICS Configuration Manager does not transfer the export file for you. Here is an example scenario for transferring an export file to a remote site using a combination of file transfer protocol (FTP) and e-mail:

    1. Transfer the export file from your z/OSĀ® host to your PC as a binary file.
    2. Zip the file on your PC.
    3. Attach the zipped file to an e-mail message.
    4. Send the e-mail to the remote site.

    Now suppose that you are the person at the remote site who receives this e-mail:

    1. Detach the zipped file from the e-mail.
    2. Unzip the export file.
    3. Transfer the export file to your z/OS host as a binary file with a fixed-blocked (FB) record format and a logical record length of either 80 bytes (for a BATCHREP or DFHCSDUP export file) or 1500 bytes (for a CICS Configuration Manager export file).

      For example, if you are using a standard FTP command-line utility, enter the following FTP commands after logging on:

      binary
      quote site recfm=fb lrecl=1500
      put file_path data_set_name

For details on importing the resource definitions at the remote site, see Importing resource definitions from an export file.


Information Information

Feedback


Timestamp icon Last updated: Friday, 1 November 2013


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