5.2.2 Output Message

If the CHECK function checks and detects an abnormality, it will generate a message. This message is usually output to the message box.

While the messages that are generated by the CHECK function normally have the severity code E, the severity code changes to U when the message output count equals a predetermined value. (For more information about severity codes, refer to “NetCOBOL Messages”.)

The CHECK(PRM) internal program call parameter produces a diagnostic message at compilation if it determines an error in the calling structure parameters, but it does not check the number of times specified (n,PRM) for runtime message output.

Checking parameters for calling a method

[PID:xxxxxxxx TID:xxxxxxxx] FAILURE IN USING (or RETURNING) PARAMETER OF THE 'method-name' METHOD. 'NUMBER' (or PARAMETER=parameter's sequence number ). PGM=program-name LINE=statement-number

Remedy: Modify your program so that the method referenced in the message is called with valid parameters and execute it again.

JMP08101-E/U

Checking Subscripts and Indexes

[PID:xxxxxxxx TID:xxxxxxxx] SUBSCRIPT/INDEX IS OUT OF RANGE. PGM=program-name. LINE=statement-number. OPD=data-name (dimension of data-name)

Remedy: Specify a correct value for the subscript or index indicated in the message, then re-execute.

JMP0820I-E/U

Checking Reference Modification

[PID:xxxxxxxx TID:xxxxxxxx] REFERENCE MODIFIER IS OUT OF RANGE. PGM=program-name. LINE=statement-number. OPD=data-name.

Remedy: Correct the program so that reference modification of the data item indicated in the message is performed within the specified range.

JMP0821I-E/U

Checking a Target Word of the OCCURS DEPENDING ON Clause

[PID:xxxxxxxx TID:xxxxxxxx] ODO OBJECT VALUE IS OUT OF RANGE. PGM=program-name. LINE=statement-number. OPD=data-name. ODO=name of target word of ODO clause.

Remedy: Specify a correct value for the object (in the OCCURS DEPENDING ON clause) indicated in the message, then re-execute.

JMP0822I-E/U

Checking numeric data exceptions

[PID:xxxxxxxx TID:xxxxxxxx] INVALID VALUE SPECIFIED. PGM=program-name. LINE=statement-number. OPD=data-name

Remedy: Set a valid value in the operand referenced by the message and re-execute.

JMP08281-E/U

Checking zero-divisor

[PID:xxxxxxxx TID:xxxxxxxx] DIVIDED BY ZERO. PGM=program-name. LINE=statement-number. OPD=data-name

Remedy: Change the divisor in the operand referenced by the message to any value other than zero and re-execute.

JMP08291-E/U

Checking the program calling conventions

[PID:xxxxxxxx TID:xxxxxxxx] FAILURE IN CALLING CONVENTIONS OR PARAMETERS OF THE 'called program name' PROGRAM. PGM=program-name. LINE=statement-number.

Remedy: Correct the programs so that the calling conventions and parameters match, then re-execute.

JMP0811I-E/U

Internal program call parameter investigation

THE NUMBER OF PARAMETERS SPECIFIED IN USING PHRASE OF CALL STATEMENT MUST BE THE SAME NUMBER OF PARAMETERS SPECIFIED IN USING PHRASE OF PROCEDURE DIVISION.

Remedy: Correct the program so that the number of parameters is the same.

JMN3334I-S

THE TYPE OF PARAMETER @2@ SPECIFIED IN USING PHRASE OR RETURNING PHRASE OF CALL STATEMENT MUST BE THE SAME TYPE OF PARAMETER @3@ SPECIFIED IN PROCEDURE DIVISION USING PHRASE OR RETURNING PHRASE OF PROGRAM @1@.

@1@: Program name

@2@: Identifier

@3@: Identifier

Remedy: Correct the program so that the class name, FACTORY, and ONLY that are specified in the USAGE OBJECT REFERENCE clause of the object specified in the parameter are the same.

JMN3335I-S

THE LENGTH OF PARAMETER @2@ SPECIFIED IN USING PHRASE OR RETURNING PHRASE OF CALL STATEMENT MUST BE THE SAME LENGTH OF PARAMETER @3@ SPECIFIED IN PROCEDURE DIVISION USING PHRASE OR RETURNING PHRASE OF PROGRAM @1@.

@1@: Program name

@2@: Identifier

@3@: Identifier

Remedy: Correct the program so that the parameter lengths are the same.

JMN3414I-S

RETURNING ITEM MUST BE SPECIFIED FOR CALL STATEMENT WHICH CALLS @1@. THERE IS RETURNING SPECIFICATION IN PROCEDURE DIVISION OF PROGRAM @1@.

@1@: Program name

Remedy: Correct the program so that the existence or non-existence of RETURNING phrase is matched.

JMN3508I-S

RETURNING ITEM MUST NOT BE SPECIFIED FOR CALL STATEMENT WHICH CALLS @1@. THERE IS NOT RETURNING SPECIFICATION IN PROCEDURE DIVISION OF PROGRAM @1@.

@1@: Program name

Remedy: Correct the program so that the existence or non-existence of RETURNING phrase is matched.

JMN3333I-S

External program call parameter investigation

[PID:xxxxxxxx TID:xxxxxxxx] FAILURE IN '$1' OF CALL STATEMENT. PGM=program-name. LINE=statement-number.

Remedy

Based on the content indicated by $1, perform operations presented in "Table 5.2 The contents of $1 of JMP0812I-E/U " then try again.

Table 5.2 The contents of $1 of JMP0812I-E/U
$1	Corrective action taken by the programmer
USING PARAMETER NUMBER	Match the number of USING phrase parameters
USING nTH PARAMETER (nTH = 1ST, 2ND, 3RD, 4TH...)	Match the size of nth USING phrase parameters
RETURNING PARAMETER	Match the size of RETURNING phrase parameters

JMP0812I-E/U

Message Output Count

Specify a message count in compiler option CHECK at compile time. If one run unit contains two or more COBOL programs, which had the CHECK option, specified, the number of messages specified with the compile option for the program that is activated first will be used. The message count can be changed at execution time by using execution time option c.

The CHECK function can also be suppressed by specifying execution time option. The following CHECK functions can be suppressed. Plurals can be specified.

noc : All the CHECK function
nocb : CHECK(BOUND)
noci : CHECK(ICONF)
nocl : CHECK(LINKAGE)
nocn : CHECK(NUMERIC)
nocp : CHECK(PRM)

Program execution is continued until the message count reaches the specified count. Refer to "Format of Runtime Options" in the "NetCOBOL User's Guide" for the detail.