M204.2565: Difference between revisions
Jump to navigation
Jump to search
(Automatically generated page update) |
m (add link) |
||
| Line 2: | Line 2: | ||
<P> | <P> | ||
A file can be rolled back only when using the checkpoint data set (RESTART) from the <em>last</em> job that updated the file. This message, which follows [[M204.0146]] (Roll Back information is obsolete), is issued when the RESTART data set is not from the last job that updated the file.</P> | A file can be rolled back only when using the checkpoint data set (<var>[[System and media recovery#Recovery data sets and job control|RESTART]]</var>) from the <em>last</em> job that updated the file. This message, which follows [[M204.0146]] (Roll Back information is obsolete), is issued when the <var>RESTART</var> data set is not from the last job that updated the file.</P> | ||
<P> | <P> | ||
There are two possible causes for this error:</P> | There are two possible causes for this error:</P> | ||
| Line 8: | Line 8: | ||
<LI>The file was updated by another job after the run that you are trying to roll back.</LI> | <LI>The file was updated by another job after the run that you are trying to roll back.</LI> | ||
<LI>The <var>RESTART | <LI>The <var>RESTART</var> command points to the wrong checkpoint data set (DD, DLBL, or FILEDEF).</LI> | ||
</ul> | </ul> | ||
| Line 16: | Line 16: | ||
job does not use checkpointing, the timestamp is created at the first update of the job only. </P> | job does not use checkpointing, the timestamp is created at the first update of the job only. </P> | ||
<P> | <P> | ||
The timestamp is written to both the checkpoint data set, if checkpointing is active, and the file itself. During ROLL BACK processing, Model 204 checks that the most recent timestamp from the RESTART data set is the same | The timestamp is written to both the checkpoint data set, if checkpointing is active, and the file itself. During <var>ROLL BACK</var> processing, Model 204 checks that the most recent timestamp from the <var>RESTART</var> data set is the same | ||
as that in the file. If they are different, message M204.0146 and this message are issued.</P> | as that in the file. If they are different, message M204.0146 and this message are issued. | ||
</P> | |||
<P class="note"><b>Note:</b> This is <em>not</em> a Model 204 internal error.</P> | <P class="note"><b>Note:</b> This is <em>not</em> a Model 204 internal error.</P> | ||
<P> | <P> | ||
If the timestamp from the file is:</P> | If the timestamp from the file is:</P> | ||
<ul> | <ul> | ||
<LI>Later than the timestamp from the RESTART data set, then the file was updated by another job after the run that you are trying to roll back. The timestamp from the file may assist you to identify the other job. Remember that the timestamp represents the time of the first update after the last checkpoint in that job, or the first update of the job, if not checkpointing.</LI> | <LI>Later than the timestamp from the <var>RESTART</var> data set, then the file was updated by another job after the run that you are trying to roll back. The timestamp from the file may assist you to identify the other job. Remember that the timestamp represents the time of the first update after the last checkpoint in that job, or the first update of the job, if not checkpointing.</LI> | ||
<LI>Earlier than the timestamp from the RESTART data set, then you are using the wrong checkpoint data set for RESTART, or (less likely) you restored the file from an old backup before attempting to run recovery.</LI> | <LI>Earlier than the timestamp from the <var>RESTART</var> data set, then you are using the wrong checkpoint data set for <var>RESTART</var>, or (less likely) you restored the file from an old backup before attempting to run recovery.</LI> | ||
</ul> | </ul> | ||
<p> | <p> | ||
Revision as of 19:43, 20 March 2018
M204.2565 token=token2, restart=token3
A file can be rolled back only when using the checkpoint data set (RESTART) from the last job that updated the file. This message, which follows M204.0146 (Roll Back information is obsolete), is issued when the RESTART data set is not from the last job that updated the file.
There are two possible causes for this error:
- The file was updated by another job after the run that you are trying to roll back.
- The RESTART command points to the wrong checkpoint data set (DD, DLBL, or FILEDEF).
Comparing timestamps
The timestamps in this message may assist in identifying the reason for the "Roll Back information is obsolete" message. Model 204 creates a file-specific timestamp at the first update to a file after each checkpoint. If a job does not use checkpointing, the timestamp is created at the first update of the job only.
The timestamp is written to both the checkpoint data set, if checkpointing is active, and the file itself. During ROLL BACK processing, Model 204 checks that the most recent timestamp from the RESTART data set is the same as that in the file. If they are different, message M204.0146 and this message are issued.
Note: This is not a Model 204 internal error.
If the timestamp from the file is:
- Later than the timestamp from the RESTART data set, then the file was updated by another job after the run that you are trying to roll back. The timestamp from the file may assist you to identify the other job. Remember that the timestamp represents the time of the first update after the last checkpoint in that job, or the first update of the job, if not checkpointing.
- Earlier than the timestamp from the RESTART data set, then you are using the wrong checkpoint data set for RESTART, or (less likely) you restored the file from an old backup before attempting to run recovery.
System manager response: Correct the error, and rerun Model 204 recovery.
Operator response: Contact your system manager.
Message attributes:
| RETCODEO=0 | Sets online return code |
|---|---|
| RETCODEB=4 | Sets batch (single user) return code |
| CLASS=E | Error class; the message can be suppressed with the X'04' 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 |
| OPR | Writes the message to the (operator) console |