Explanation
In the message text:
One of the following
two lines then appears:
CHECKPOINT SUCCESSFUL WITH POSSIBLE
SPECIAL REQUIREMENTS.
Then the following line appears:
[MODULE = module-name]
A
CHKPT macro instruction was run successfully. However:
- Your program could be enqueued upon resources. The ENQ macro instruction
was issued by either the problem program, the BDAM READ macro instruction
with exclusive control, the RESERVE macro instruction, or the BDAM
WRITE macro instruction with variable-length (V) or undefined (U)
record format. Note that the enqueues will not be reestablished if
restart occurs.
- Or checkpoint was unable to complete the check for enqueued resources,
due to insufficient storage or due to an error detected by the QSCAN
service.
In the message text:
- jjj
- The jobname.
- sss
- The stepname.
- ppp
- The procedure step name.
- ddname
- The data definition name of the checkpoint data set.
- devnum
- The device number.
- volser
- The serial number of the volume containing the data set.
- checkid
- The checkpoint identification.
- xxx
- The reason code giving more specific information about the condition.
- module-name
- The module in which an error was detected.
System action
A valid checkpoint entry was written and is eligible
for a deferred or automatic restart.
Programmer response
See z/OS DFSMSdfp Checkpoint/Restart for
the reason codes for the IHJ messages. Find the value of xxx under
the heading 'Reason Codes for IHJ Messages,' and follow the programmer
response for that reason code. Ensure that the program reestablished
the enqueues upon restart, provide more storage for checkpoints, or
determine what the problem is with GQSCAN service. After correcting
the problem, resubmit the job.
Source
Data Facility Product (DFP)
Routing code
Descriptor code