Space announcement We are no longer updating this space, and you cannot comment on this space. The IMAGE COPY PLUS component is now documented in BMC AMI Backup and Recovery for IMS.

Using the Subsystem Data Set Interface (ICPSSDSI)


When you create image copy data sets with a BMC Image Copy utility compression option or by merging the individual copies of a VOLCOPY operation, the resultant image copy data sets are considered to be non-standard.

To read such a non-standard image copy data set with a non-BMC program, such as the IMS Data Base Recovery utility, DFSURDB0, you should use the Subsystem Data Set Interface (ICPSSDSI).

The ICPSSDSI reformats the non-standard image copy records and passes them to the non-BMC program, eliminating a need for a preprocessing step. BMC products can read the non-standard image copy data sets without invoking the ICPSSDSI.

To use the ICPSSDSI, do the following:

  1. Make sure the BMC Database Utilities Subsystem (DBUSS) is active on the same CPU during the program’s execution. For more information about the DBUSS, see Database Products for IMS Customization documentation.
  2. Concatenate the BMC product load library at the end of the STEPLIB concatenation.
  3. dd the following two DD statements to the program’s JCL:

    • dd1

      Describes the real non-standard image copy data set. The ddname can be any name you want to use.

    • dd2

      Describes the data set the program thinks it is reading. The DBUSS interprets this data set to the program.

      • The ddname should be the ddname that the program reading the image copy expects to find.
      • The DSN parameter should refer to the ddname of the dd1 statement.
      • The disposition (DISP) should be OLD.
      • Specify a SUBSYS parameter with the subparameters DBUZ (or the name of the alternate subsystem), ICPEX, and dd1 (the ddname you specified for the real, non-standard image copy).

        Note

        Do not use the SUBSYS parameter for an SMS-managed data set (one with an assigned storage class). Refer to the SUBSYS Parameter restrictions in the operating system documentation from IBM.

    For cataloged image copies that have DBRC(N) or DBRC(Y) with CATDS, use the subsystem interface as follows:

    //DD1      DD  DSN=COMPRESS.IMAGE.COPY,DISP=OLD
    //DD2      DD  DSN=*.DD1,DISP=OLD,
    //             SUBSYS=(DBUZ,ICPEX,DD1)

    For IMS users with NOCATDS and DBRC(Y), use the following JCL:

    //DD1     DD  DSN=COMPRESS.IMAGE.COPY,DISP=OLD
    //DD2     DD  DSN=*.DD1,DISP=OLD,VOL=REF=*.DD1,
    //            SUBSYS=(DBUZ,ICPEX,DD1)

    Refer to JCL-considerations for addition information.

    If you do not catalog the image copy data sets and specify DBRC(Y), use the following JCL:

    //DD1     DD  DSN=COMPRESS.IMAGE.COPIES,DISP=OLD,
    //            UNIT=TAPE,VOL=SER=123456
    //DD2     DD  DSN=*.DD1,DISP=OLD,
    //            VOL=REF=*.DD1,
    //            SUBSYS=(DBUZ,ICPEX,DD1)

    Refer to JCL-considerations for additional information

    If you do not catalog the image copy data sets and specify DBRC(N), use the following JCL:

    //DD1     DD  DSN=COMPRESS.IMAGE.COPIES,DISP=OLD,
    //            UNIT=TAPE,VOL=SER=123456
    //DD2     DD  DSN=*.DD1,DISP=OLD,
    //            SUBSYS=(DBUZ,ICPEX,DD1)

Refer to JCL-considerations for additional information.

Using-GENJCL contains example JCL for recovery using the subsystem data set interface with DBRC GENJCL.

The BMC Image Copy utility and Recovery utility can automatically read a non-standard image copy data set without these additional statements. You need them only for the ICPSSDSI.

This section contains the following topics:

Related topic

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*