DBRC IC record registration

The Create Image Copy function issues the NOTIFY.IC or the CHANGE.IC command under certain conditions. These commands register the primary output image copy data set to RECON.

NOTIFY.IC command and CHANGE.IC command

The NOTIFY.IC or the CHANGE.IC command for the primary output data set is issued when both NOTIFY=Y and DBRC=Y are specified in the ICEIN control statement. These commands register the primary output image copy data set to RECON when one of the following conditions is met:

  • If only the primary image copy data set is registered to RECON as an available IC record, the Create Image Copy function issues the CHANGE.IC command for the primary output data set and registers it to RECON as the secondary image copy data set.
  • If either the primary image copy data set or the secondary image copy data set is flagged as an error in RECON, the Create Image Copy function issues the CHANGE.IC command for the primary output data set and registers it to RECON rather than to the error IC record.
  • If an image copy data set that has the same runtime and the same type of input image copy data set is not registered to RECON, the Create Image Copy function issues the NOTIFY.IC command for the input image copy data set and the primary output image copy data set to:
    • Register the input image copy data set as the primary image copy data set.
    • Register the primary output data set to RECON as the secondary image copy data set.

The NOTIFY.IC command is supported only for batch image copy.

If both the primary and the image copy data sets are normally registered in RECON, the CHANGE.IC command is not issued.

The Create Image Copy function issues the CHANGE.IC command for the target IC record in RECON. It is strongly recommended that ICEDLIST DD is specified in runtime JCL and you take the DBRC command report.

NOTIFY.IC restrictions

If any of the following conditions is met, the Create Image Copy function ignores NOTIFY=Y:

  • Both the primary and the secondary image copy data sets are registered normally to RECON.
  • Neither the primary nor the secondary image copy data set is registered to RECON and the type of the input image copy data set is one of the following:
    • Concurrent image copy
    • Fast Recovery image copy
    • IC2 image copy
    • Online image copy
  • Both the primary and the secondary image copy data sets are flagged as an error in RECON and the input image copy data set is not specified in the JCL.
  • The type of the input image copy data set is one of the following, and the input data set is not dynamically allocated:
    • Online image copy
    • IC2 image copy
    • Concurrent image copy