M204.2099: Difference between revisions
Jump to navigation
Jump to search
(Automatically generated page update) |
No edit summary |
||
Line 5: | Line 5: | ||
<p> | <p> | ||
<b>File manager response:</b> To re-activate TBO, first issue <code>RESET FOPT</code> to turn off the X'02' option, then issue <code>RESET FRCVOPT X'00'</code>. </p> | <b>File manager response:</b> To re-activate TBO, first issue <code>RESET FOPT</code> to turn off the X'02' option, then issue <code>RESET FRCVOPT X'00'</code>. </p> | ||
{{Template:M204.2099 | {{Template:M204.2099 footer}} | ||
<!-- skeleton as it was in pdf/FRCVOPT FORCED TO 'NO TRANSACTION BACKOUT' /--> | <!-- skeleton as it was in pdf/FRCVOPT FORCED TO 'NO TRANSACTION BACKOUT' /--> |
Latest revision as of 19:32, 15 March 2018
M204.2099 FRCVOPT forced to 'no transaction backout'
The message accompanies a RESET of FOPT to x'02', "Don't lock pending updates," and is for informational purposes. It is a reminder to the File Manager that the reset of FOPT had the indirect result of disabling Transaction back out (TBO) for the file.
File manager response: To re-activate TBO, first issue RESET FOPT
to turn off the X'02' option, then issue RESET FRCVOPT X'00'
.
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 |