NOTIFYMODE keyword

The NOTIFYMODE keyword specifies the condition for registering image copy record to RECON.

Functions that support this keyword
Image Copy function
Statements that support this keyword
GLOBAL statement
Site default option
Supported
Related keyword
Format
Read syntax diagramSkip visual syntax diagramNOTIFYMODE=FORCECOND
FORCE
Registers the image copy record to DBRC RECON regardless of how the image copy processing ended.
COND
Conditionally registers the image copy record to DBRC RECON based on the result of image copy processing.
If image copy processing ends in one of the following conditions, the Image Copy function does not register the image copy record to DBRC RECON:
  • Errors in the image copy processing, such as I/O errors or invalid input data format
  • Errors in HASH pointer check processing (enabled by HDPC=Y or DEDBPC=Y)
  • If a DL/I database, HALDB partition, or DEDB area is to be reprocessed in the next run by the Checkpoint Restart function (enabled by RESTART=Y). For considerations on IC registration of DEDB areas, see Timing of image copy registration.
If more than two image copy data sets are created for a database data set or area data set, and if the third or the fourth image copy data set is in error, the Image Copy function continues the process and registers the primary and secondary image copy data sets to the DBRC RECON data set.
If NOTIFYMODE=COND is specified, image copy registration is done by the units of databases instead of units of database data sets. For example, if a database consists of multiple database data sets, all image copies are registered to RECON after all the database data sets are successfully processed. This means, if an error is encountered when processing a database data set, no image copies are registered to RECON.
Default value
NOTIFYMODE=FORCE

Combination of NOTIFYMODE=COND and RESTART=value

If NOTIFYMODE=COND, RESTART=value, and HDPC=Y or DEDBPC=Y are specified, the behavior of IMS HP Image Copy varies based on the value that is specified in the RESTART keyword and the result of HASH pointer check.

The following table shows the behavior of IMS HP Image Copy for each condition.

Table 1. Behavior of IMS HP Image Copy for NOTIFYMODE=COND, RESTART, and HDPC=Y or DEDBPC=Y combination
Condition Actions taken
RESTART specification HASH error Image copy registered to RECON? Reprocessed in the next run by the Checkpoint restart function?
(Y,HASH) No error Yes No
(Y,HASH) Unidentified error No Yes
(Y,HASH) Severe error No No
Y No error Yes No
Y Unidentified error Yes No
Y Severe error No No
N No error Yes No
N Unidentified error Yes No
N Severe error No No
Note: For the meanings of HASH errors, see Types of errors detected by HASH Check option.

Timing of image copy registration

The timing that an image copy is registered to RECON varies based on the database type and the value that is specified in the NOTIFYCOND keyword.

If NOTIFYMODE=FORCE is specified, the timing that an image copy is registered does not vary by database type. All image copies are registered after image copies are created for each DBDS. For example, if you use the IC statement, all DBDSs are processed serially and each image copy is registered soon after the image copy is created.

If NOTIFYMODE=COND is specified, the timing that an image copy is registered varies by database type.

  • For a DEDB, the timing of image copy registration is the same as the timing for NOTIFYMODE=FORCE if no error is detected in the image copy creation processing.
  • For DL/I database and HALDB, all image copies are registered at the end of image copy job step. This is because DL/I database and HALDB might have logical relationships between databases, and that registering image copies at the end of job step avoids unnecessary image copies to be registered.

If a database group, such as CA group or DBDS group in DBRC, consists of both DEDB and DL/I database or DEDB and HALDB, the registration timing differs within that database group.

If you specify to take image copies for a database group that includes DEDB, and if you enable the Checkpoint Restart function for all the members of the group with the RSTTYPE=1 option, the registration of IC records are processed as follows:
  • For DEDB areas, the IC records of successfully processed DBDSs will be registered to RECON and IC records of DBDSs that have errors will not be registered to RECON.
  • For DL/I databases and HALDBs, no IC records are registered to RECON when an error is encountered while processing the members of the group.
However, in the restart processing, all the members will be reprocessed. This means that the registered IC records in the first run remain in the RECON as unnecessary records even when NOTIFYMODE=COND is specified.

The following table shows the difference in the timing of image copy registration to DBRC by NOTIFYCOND keyword and by database type.

Table 2. Difference in the timing of image copy registration
NOTIFYMODE value Database type Timing of the image copy registration to RECON
NOTIFYMODE=FORCE DL/I, HALDB At the end of the image copy process for the DBDS
NOTIFYMODE=FORCE DEDB At the end of the image copy process for the DBDS
NOTIFYMODE=COND DL/I, HALDB (see note) At the end of the image copy job step (if no error is detected)
NOTIFYMODE=COND DEDB At the end of the image copy process for the DBDS (if no error is detected)
Note: When processing a data set group, that is, when database consists of multiple database data sets, image copy is registered after the last database data set is processed.