M204.1767: Difference between revisions

From m204wiki
Jump to navigation Jump to search
(Automatically generated page update)
 
m (add <var>'s)
 
Line 1: Line 1:
{{Template:M204.1767 skeleton}}
{{Template:M204.1767 skeleton}}
<P>A CALL, DECLARE, or SUBROUTINE statement was found to have a null parameter list  (empty parentheses: <code>()</code>). If no parameters are required for a subroutine, the parameter list should be omitted completely. For example, <code>CALL S1</code>,
<P>
A <var>Call</var>, <var>Declare</var>, or <var>Subroutine</var> statement was found to have a null parameter list  (empty parentheses: <code>()</code>). If no parameters are required for a subroutine, the parameter list should be omitted completely. For example, <code>CALL S1</code>,
<b><i>not</i></b> CALL S1 (), is the correct way to call a subroutine that has no parameters. </P>
<b><i>not</i></b> CALL S1 (), is the correct way to call a subroutine that has no parameters. </P>
<p><b>Response:</b> Correct the statement and retry. </p>
<p>
<b>Response:</b> Correct the statement, and retry.  
</p>
{{Template:M204.1767 footer}}
{{Template:M204.1767 footer}}
<!-- skeleton as it was in pdf/NULL PARAMETER LIST IS ILLEGAL /-->
<!-- skeleton as it was in pdf/NULL PARAMETER LIST IS ILLEGAL /-->

Latest revision as of 18:46, 12 March 2018

M204.1767  Null parameter list is illegal

A Call, Declare, or Subroutine statement was found to have a null parameter list (empty parentheses: ()). If no parameters are required for a subroutine, the parameter list should be omitted completely. For example, CALL S1, not CALL S1 (), is the correct way to call a subroutine that has no parameters.

Response: Correct the statement, and retry.

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
COMPILECompilation error

Back to list of messages