M204.2684
M204.2684 Checkpoint configuration conflict - token token2
The possible token and token2 reasons cited for the conflict include the following:
- CHKPNTS is open so CPTIME must be non-zero
- CHKPNTS is open so DKUPDTWT must be zero
- A non-TBO file which pre-images but does not journal has been opened for update, sub-transaction CP is not allowed
- CHKPNTS is not open and CPTYPE = 1
- CHKPNTS is not open and CPTS is non-zero
- {CHKPOINT | CHKPNTS} contains a ring definition
- {CHKPOINT | CHKPNTS} has more than 16 levels of stream definition recursion
- {CHKPOINT | CHKPNTS} contains a CMS formatted file
- CHKPNTS is open and journalling not active
- CPTYPE = 1 is incompatible with NUSERS = 1
Parameters associated with checkpointing are consistency checked when checkpoint streams are opened, at the beginning of Online processing, and also during the processing of a RESET command. The error indicated in this message was found, and the result is that the Online failed to come up, or the RESET command was rejected.
Note: If CPTYPE is 1, neither CHKPOINT nor CHKPNTS can be defined as a ring stream or a CMS formatted data set.
System manager response: If the Online failed, change the appropriate CCAIN parameter line entries, the CHKPOINT/CHKPNTS stream definitions, or both. If the RESET command failed, take appropriate action.
Message attributes:
| RETCODEO=0 | Sets online return code |
|---|---|
| RETCODEB=0 | Sets batch (single user) return code |
| CLASS=I | Information class; the message can be suppressed with the X'02' bit setting of the MSGCTL parameter |
| AUDITMS | Writes the message with line type MS to the audit trail |
| NOCOUNT | Does not increment the error count (ERCNT) parameter |