The automatic-recovery-control statement
Each automatic-recovery-control statement describes an error situation and the recovery actions for it.
Use these rules to code RECOVER statements:
- Each statement must begin on a new 80-byte logical record.
The symbols
//*%OPC
must appear in bytes 1 to 7 and be followed by at least one blank.//*%OPC RECOVER
- Identifies a RECOVER statement
//*%OPC
- Identifies a RECOVER continuation statement
The automatic recovery function also inserts informational statements in the JCL://* OPC
- Identifies a message statement
//*>OPC
- Identifies a comment statement
See Message and comment statements for more information.
- You cannot use variables anywhere in the RECOVER statement.
- The parameters are optional; you can code them in any sequence.
- Each parameter consists of a keyword followed by an equals sign and variable information.
- Parameters are separated by commas.
- You cannot code the same keyword more than once on the same statement.
- If you code only one parameter value, you do not need to enclose
it in parentheses; for example,
JOBCODE=PCHK
. - Bytes 72 to 80 are ignored by the automatic recovery function.
- When the total length of fields on a control statement exceeds
71 bytes, continue the statement using the following continuation
conventions:
- Interrupt the field after a complete or partial parameter, including the comma that follows it, before byte 72.
- Code the identifying continuation characters
//*%OPC
followed by at least one blank in bytes 1 to 7 of the statement that follows. - Continue the interrupted operand in any position from bytes 9 to 16.
- When automatic recovery is related to non-z/OS trackers, limit the RECOVER statement to one card (avoid continuation).