M204.0232: Difference between revisions

From m204wiki
Jump to navigation Jump to search
(Automatically generated page update)
 
m (minor word change)
 
Line 10: Line 10:
</ul>
</ul>
<p>
<p>
<b>Response:</b> In the first case, no response is required. In the second case, make sure that all files accessed in the <var>IN</var> clause are open or eliminate those which are not open from the <var>IN</var> clause and retry. For the third case, open the file.  
<b>Response:</b> In the first case, no response is required. In the second case, make sure that all files accessed in the <var>IN</var> clause are open, or eliminate from the <var>IN</var> clause those files that are not open, and retry. For the third case, open the file.  
</p>
</p>
{{Template:M204.0232 footer}}
{{Template:M204.0232 footer}}
<!-- skeleton as it was in pdf/FILE OR GROUP ISN'T OPEN - name/-->
<!-- skeleton as it was in pdf/FILE OR GROUP ISN'T OPEN - name/-->

Latest revision as of 23:24, 21 February 2018

M204.0232  File or group isn't open - name

This message can be generated for any of these reasons:

  • A CLOSE command for a file or group not currently open was issued.
  • An IN filename clause or IN groupname clause was issued as part of a SOUL statement. The specified file or group was not currently open. The compilation continues, but the request is not evaluated.
  • The OUTPUT file context specified for the COPY PROC command was a file or group not currently open.

Response: In the first case, no response is required. In the second case, make sure that all files accessed in the IN clause are open, or eliminate from the IN clause those files that are not open, and retry. For the third case, open the file.

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
ECHODisplays the line that caused the error

Back to list of messages