COBOL Manual for TNS/E Programs (H06.08+, J06.03+)

Cause
One of:
• The source text from which the indicated COBOL program was compiled included the
NONSTOP directive, but the current source text does not.
• The current source text includes a NONSTOP directive, but the source text from which the
indicated COBOL program was compiled did not.
• The program searched an import library that includes a COBOL program that was compiled
with the directive NONSTOP (page 558).
The compiler assumes that programs in an import library were compiled without the
NONSTOP directive. If this is not true, the compiler issues warning 369, which you can
ignore.
Run-time problems might occur if proper operation of the program depends on the run unit’s
executing as a process pair.
370 (Error)
Inconsistent parameter attributes
Cause
One of:
• Different CALL statements referencing the same COBOL program specify a different number
of parameters in their USING phrases.
• The number of parameters defined in the Procedure Division of a COBOL program differs
from the number of parameters expected by the callers.
• For one or more parameters of a COBOL program, the access mode (STANDARD or
EXTENDED-STORAGE) defined in the program differs from the access mode expected by
the callers.
371 (Error)
Formal parameter not a variable
Cause
The formal parameter of the called routine is neither a data variable nor the word OMITTED.
372 (Error)
Actual parameter is a file, so formal parameter must be a struct
Cause
The actual parameter of an ENTER statement is a file name (FD or SD), but it does not correspond
to a formal parameter that expects a struct.
373 (Warning)
Potential odd byte address converted to even byte address
Cause
The compiler cannot determine if a problem exists. Verify that the correct address is passed to
the routine.
Most COBOL data items are referenced internally by byte addresses. When one of these appears
as the actual parameter corresponding to the formal parameter of a routine that expects a 2-byte
address, the compiler must convert the item’s byte address to a 2-byte address. If the data item
begins on an odd-byte boundary, that information is lost by the conversion operation (thus the
value space of the item appears, to the called routine, to begin one byte before it actually does).
If the data item begins on an even-byte boundary, there is no problem.
Message List 1159