M204.1409: Difference between revisions

From m204wiki
Jump to navigation Jump to search
(Automatically generated page update)
 
m (add <var>'s)
 
Line 4: Line 4:
other files in the regeneration run. </P>
other files in the regeneration run. </P>
<p>
<p>
<b>File manager response:</b> Make sure you specified the correct stopping point on the REGENERATE command. If specifying an exact stopping point, match the date and time against the date and time of the end of the desired update unit as shown in
<b>File manager response:</b> Make sure you specified the correct stopping point on the <var>REGENERATE</var> command. If specifying an exact stopping point, match the date and time against the date and time of the end of the desired update unit as shown in
the audit trail from the original run. If no audit trail is available, create one by running AUDIT204 against the corresponding journal, or specify an inexact stopping point using the <code>LAST UPDATE/CHECKPOINT BEFORE <i>date time</i></code> syntax of the REGENERATE command. Also, verify that the journal containing the desired stopping point is included as part of CCAGEN.  
the audit trail from the original run. If no audit trail is available, create one by running AUDIT204 against the corresponding journal, or specify an inexact stopping point using the <code>LAST UPDATE/CHECKPOINT BEFORE <i>date time</i></code> syntax of the <var>REGENERATE</var> command. Also, verify that the journal containing the desired stopping point is included as part of CCAGEN.  
</p>
</p>
{{Template:M204.1409 footer}}
{{Template:M204.1409 footer}}
<!-- skeleton as it was in pdf/MISSING STOPPING POINT FOR FILE filename /-->
<!-- skeleton as it was in pdf/MISSING STOPPING POINT FOR FILE filename /-->

Latest revision as of 00:50, 7 March 2018

M204.1409  Missing stopping point for file token

This message applies only to a media recovery run. The stopping point for recovering the specified file is missing from the journal data set(s). Model 204 will deactivate the file and attempt to continue processing any other files in the regeneration run.

File manager response: Make sure you specified the correct stopping point on the REGENERATE command. If specifying an exact stopping point, match the date and time against the date and time of the end of the desired update unit as shown in the audit trail from the original run. If no audit trail is available, create one by running AUDIT204 against the corresponding journal, or specify an inexact stopping point using the LAST UPDATE/CHECKPOINT BEFORE date time syntax of the REGENERATE command. Also, verify that the journal containing the desired stopping point is included as part of CCAGEN.

Message attributes:

RETCODEO=0Sets online return code
RETCODEB=4Sets batch (single user) return code
CLASS=EError class; the message can be suppressed with the X'04' bit setting of the MSGCTL parameter
AUDITERWrites the message with line type ER to the audit trail
COUNTIncrements the error count (ERCNT) parameter

Back to list of messages