Diagnosing checkpoint problems
Since each message can have several specific problems, reviewing the trace logs captured under the started task will provide more details on common problems dealing with the checkpoint functions. The following table shows the possible messages and their meaning.
| Symptoms | Problem/Cause | Action |
|---|---|---|
| EZD1835I | This message indicates that the CHKPOINT DD statement was missing or the data set name was 'NULLFILE'. The function is disabled. | For details and other messages, see the appropriate EZD1835I message in z/OS Communications Server: IP Messages Volume 2 (EZB, EZD). |
| EZD1836I | This message indicates that the checkpoint data set could not be opened. | For details and other messages, see the appropriate EZD1836I message in z/OS Communications Server: IP Messages Volume 2 (EZB, EZD). |
| EZD1849I | This message indicates that JES spool file could
not be allocated by the SAPI interface. The spool file may have been previously purged by an operator command. |
For details and other messages, see the appropriate EZD1849I message in z/OS Communications Server: IP Messages Volume 2 (EZB, EZD). |
| Abend S08B | This abend is issued by the MVS™ Data-In-Virtual component when accessing
the checkpoint data set. Reason code xxxx001D. The checkpoint data set is not a valid VSAM linear data set or an incorrect control interval size was used when the VSAM data set was defined. |
For details about the S08B abend, see z/OS MVS System Codes. |