IBM VS Cobol II Run Time Messages

The following messages pertain to COBOL. Each message is followed by an explanation describing the condition that caused the message, a programmer response suggesting how you might prevent the message from occurring again, and a system action indicating how the system responds to the condition that caused the message.

The messages also contain a symbolic feedback code, which represents the first 8 bytes of a 12-byte condition token. You can think of the symbolic feedback code as the nickname for a condition. As such, the symbolic feedback code can be used in user-written condition handlers to screen for a given condition, even if it occurs at different locations in an application.

The messages in this section contain alphabetic suffixes that have the following meaning:
I Informational message
W Warning message
E Error message
S Severe error message
C Critical error message

IGZ0002S IGZ0003W IGZ0005S IGZ0006S IGZ0007S IGZ0009C IGZ0011C IGZ0012S IGZ0013S IGZ0014W IGZ0015S IGZ0016W IGZ0017S IGZ0018S IGZ0019W IGZ0020S IGZ0021C IGZ0022W IGZ0023S IGZ0024S IGZ0026W IGZ0027W IGZ0028S IGZ0029S IGZ0030S IGZ0031S IGZ0032S IGZ0033S IGZ0034W IGZ0035S IGZ0036W IGZ0037S IGZ0038S IGZ0039S IGZ0040S IGZ0041W IGZ0042C IGZ0044S IGZ0045S IGZ0046W IGZ0047S IGZ0048W IGZ0049W IGZ0050S IGZ0051S IGZ0052C IGZ0053S IGZ0054W IGZ0055W IGZ0056W IGZ0057S IGZ0058S IGZ0059W IGZ0060W IGZ0061S IGZ0063S IGZ0064S IGZ0065S IGZ0066S IGZ0067S IGZ0068S IGZ0069S IGZ0070S IGZ0071S IGZ0072S IGZ0073S IGZ0074S IGZ0075S IGZ0076W IGZ0077W IGZ0078S IGZ0079S IGZ0080S IGZ0096C IGZ0097S IGZ0098C IGZ0099C IGZ0100S IGZ0108S IGZ0151S IGZ0152S IGZ0154S IGZ0155S IGZ0156S IGZ0157S IGZ0158S IGZ0159S IGZ0160S IGZ0161S IGZ0162S IGZ0163S IGZ0164C IGZ0165S IGZ0166S IGZ0167S IGZ0168S IGZ0169W IGZ0170S IGZ0172W IGZ0200W IGZ0201W IGZ0202W IGZ0203W IGZ0204W IGZ0205W IGZ0206W IGZ0207W IGZ0210S IGZ0211S
IGZ0002S
IGZ0002S debugging-information

Explanation: A SYNAD error has occurred on a QSAM file. The text was supplied by the system SYNADAF routine. Since the debugging information supplied in this message is system specific, the message format differs between CMS and MVS environments. The message issued under MVS consists of the following: IGZ0002S job name, step name, unit address, device type, ddname, operation attempted, error description, actual track address and block number, access method. The message issued under CMS is as follows: IGZ0002S 120S operation type ERROR nnn ON ddname, Definitions requiring further explanation for the above message formats are: 120S is the CMS message number for SYNAD errors operation type INPUT or OUTPUT device type UR for unit record device TA for magnetic tape device DA for direct access device nnn is the associated error code ddname is the DDNAME of the related file operation attempted actual operation Programmer Response: For more information regarding the CMS message number 120S and related error codes, see VM/SP System Messages and Codes, SC19-6204. For information on the MVS text of this SYNAD message, see Data Administration: Macro Instruction Reference, GC26-4057, and Data Administration Guide, GC26-4058.

System Action: The application was terminated.

IGZ0003W
IGZ0003W A logic error occurred for file file-name in program program-name at relative location relative-location.

Explanation: This error is usually caused by an I/O operation request that is not valid for the file--for example, a WRITE into a file opened for INPUT, or a START to a VSAM ESDS.

A file status clause was specified or an error declarative statement was active for the file.

Programmer Response: Check the operation request and modify the program.

System Action: No system action was taken.

IGZ0005S
IGZ0005S OS/VS COBOL programs in the application were found in multiple enclaves.

Explanation: OS/VS COBOL programs are restricted to one enclave within an application.

Programmer Response: Modify the application so that the OS/VS COBOL programs appear in one enclave only.

System Action: The application was terminated.

IGZ0006S
IGZ0006S The reference to table table-name by verb number verb-number on line line-number addressed an area outside the region of the table.

Explanation: When the SSRANGE option is in effect, this message is issued to indicate that a fixed-length table has been subscripted in a way that exceeds the defined size of the table, or, for variable-length tables, the maximum size of the table.

The range check was performed on the composite of the subscripts and resulted in an address outside the region of the table. For variable-length tables, the address is outside the region of the table defined when all OCCURS DEPENDING ON objects are at their maximum values; the ODO object's current value is not considered. The check was not performed on individual subscripts.

Programmer Response: Ensure that the value of literal subscripts and/or the value of variable subscripts as evaluated at run-time do not exceed the subscripted dimensions for subscripted data in the failing statement.

System Action: The application was terminated.

IGZ0007S
IGZ0007S The reference to variable length group group-name by verb number verb-number on line line-number addressed an area outside the maximum defined length of the group.

Explanation: When the SSRANGE option is in effect, this message is issued to indicate that a variable-length group generated by OCCURS DEPENDING ON has a length that is less than zero, or is greater than the limits defined in the OCCURS DEPENDING ON clauses.

The range check was performed on the composite length of the group, and not on the individual OCCURS DEPENDING ON objects.

Programmer Response: Ensure that OCCURS DEPENDING ON objects as evaluated at run-time do not exceed the maximum number of occurrences of the dimension for tables within the referenced group item.

System Action: The application was terminated.

IGZ0009C
IGZ0009C A delete of module module-name was unsuccessful.

Explanation: An attempt to delete a module failed.

Programmer Response: See your IBM service representative.

System Action: The application was terminated.

IGZ0011C
IGZ0011C module-name was not a proper module for this system environment.

Explanation: A library subroutine that is system sensitive is inappropriate for the current system environment. For example, an OS environment specific module has been loaded under CICS. The likely causes are:

Programmer Response: Check for the conditions stated above, and modify the environment or the application as needed.

System Action: The application was terminated.

IGZ0012S
IGZ0012S There was an invalid attempt to end a sort or merge.

Explanation: A sort or merge initiated by a COBOL program was in progress and one of the following was attempted:
  1. A STOP RUN was issued.
  2. A GOBACK or an EXIT PROGRAM was issued within the input procedure or the output procedure of the COBOL program that initiated the sort or merge. Note that the GOBACK and EXIT PROGRAM statements are allowed in a program called by an input procedure or an output procedure.
  3. A user handler associated with the program that initiated the sort or merge moved the condition handler resume cursor and resumed the application.

Programmer Response: Change the application so that it does not use one of the above methods to end the sort or merge.

System Action: The application was terminated.

IGZ0013S
IGZ0013S An error return code return-code came from a CICS command CICS-command issued by library subroutine library-subroutine.

Explanation: An error was encountered when a run-time routine issued a CICS command. The error return code is from the field EIBRESP in the CICS EIB. For more information about the values for the field EIBRESP, see the CICS/ESA Application Programmer's Reference.

Programmer Response: Modify your application as required.

System Action: The application was terminated.

IGZ0014W
IGZ0014W module-name is no longer supported. Its content was ignored.

Explanation: This message is issued when the run-time detects that IGZETUN or IGZEOPT is linked with the application. IGZETUN and IGZEOPT are ignored when running with LE/370. CEEUOPT may be used in place of IGZETUN and IGZEOPT.

Programmer Response: Remove the explicit INCLUDE of IGZEOPT or IGZETUN during the link-edit step.

System Action: No system action was taken.

IGZ0015S
IGZ0015S A recursive call was attempted to a program that was already active. The program name is program-name.

Explanation: An illegal recursive entry to an active program is detected. For example, Program A has CALLed Program B, and Program B is CALLing Program A.

Programmer Response: Remove the recursive call to program-name or specify the IS RECURSIVE phrase on the PROGRAM-ID statement for the recursively CALLed program. Additionally, if the recursive program is called dynamically, link-edit it with REUS.

System Action: The application was terminated.

IGZ0016W
IGZ0016W Program program-name could not be deactivated by non-return exit of a routine. Subsequent reentry is not supported.

Explanation: A COBOL program cannot normally be recursively entered. When non-return style procedure collapse processing is being performed for a COBOL program, an attempt is made to reset the program to a state where it can be recursively entered. This is not supported for certain combinations of function used within the program. After this message is issued, any attempt to reenter the program will result in message IGZ0015S and termination of the enclave.

Programmer Response: Do not reenter the program or modify the program to allow it to be successfully reset.

System Action: No system action was taken.

IGZ0017S
IGZ0017S The open of DISPLAY or ACCEPT file with environment name environment-name was unsuccessful.

Explanation: An error occurred while opening the DISPLAY/ACCEPT file.

Programmer Response: Check to make sure a ddname has been defined for the file.

System Action: The application was terminated.

IGZ0018S
IGZ0018S On CICS, an attempt was made to run a COBOL program which is not reentrant. The program name is program-name.

Explanation: COBOL programs running on CICS must be reentrant.

Programmer Response: In order to make a COBOL program reentrant, compile the COBOL program with the RENT compile-time option.

System Action: The application was terminated.

IGZ0019W
IGZ0019W A FUNCTION result used as a DELIMITED BY operand is larger than the UNSTRING object in program program-name at displacement displacement. The DELIMITED BY phrase is ignored.

Explanation: A FUNCTION used as a DELIMITED BY operand was larger than the UNSTRING object.

Programmer Response: Check the FUNCTION arguments to ensure that they are not larger than the UNSTRING object.

System Action: No system action was taken.

IGZ0020S
IGZ0020S A logic error occurred. Neither FILE STATUS nor a declarative was specified for file file-name in program program-name at relative location relative-location. The status code was status-code.

Explanation: This error is an I/O error, usually caused by an operation request that is not valid for the file, for example, a WRITE into a file opened for INPUT, or a START to a VSAM ESDS.

No file status clause was specified, and no error declarative was in effect.

Programmer Response: Check operation request for the file.

System Action: The application was terminated.

IGZ0021C
IGZ0021C macro-name was unsuccessful for file file-name.

Explanation: The execution of an ENDREQ, GENCB, MODCB, SHOWCB, or TESTCB macro failed. This is the result of system or VSAM problems.

Programmer Response: See your IBM service representative.

System Action: The application was terminated.

IGZ0022W
IGZ0022W File file-name in program program-name will return the maximum record length when read.

Explanation: A VSAM RRDS with a varying record length has been opened for input. The maximum record length will be returned.

Programmer Response: None

System Action: No system action was taken.

IGZ0023S
IGZ0023S The dynamic allocation of file file-name was unsuccessful. The return code was return-code. The reason code was reason-code.

Explanation: An attempt to dynamically allocate a file using DYNALLOC failed, resulting in the indicated return and reason codes.

Programmer Response: Review the job stream or filedef to see if any DDNAMES are missing or misspelled. If you can not find any errors, resubmitt the job with the CBLQDA(OFF) run-time option and check for any access method messages.

System Action: The application was terminated.

IGZ0024S
IGZ0024S An invalid separate sign character was detected in program-name at displacement displacement.

Explanation: An operation was attempted on data defined with a separate sign. The value in the sign position was not a plus (+) or a minus (-).

Programmer Response: This error might have occurred because of a REDEFINES clause involving the sign position or a group move involving the sign position, or the position was never initialized. Check for these cases. The compiler formatting option TEST(), or equivalent, along with the ABTERMENC() runtime option, can be used to generate a formatted dump of the user data. This dump can then be used to identify the unacceptable data item contents.

System Action: The application was terminated.

IGZ0026W
IGZ0026W The SORT-RETURN special register was never referenced, but the current content indicated the sort or merge operation in program program-name on line number line-number was unsuccessful.

Explanation: The COBOL source does not contain any references to the sort-return register. The compiler generates a test after each sort or merge verb. A nonzero return code has been passed back to the program by Sort/Merge.

Programmer Response: Determine why the Sort/Merge was unsuccessful and fix the problem. Possible reasons why the Sort/Merge was unsuccessful include:

System Action: No system action was taken.

IGZ0027W
IGZ0027W The sort control file could not be opened.

Explanation: An attempt to open the sort control file has failed. Possible reasons for the open failure include:

When the sort control file cannot be opened, user-supplied sort control cards will not be passed to Sort/Merge.

The sort control file is optional. On MVS, if you did not provide a ddname for the sort control file (the sort control file name is IGZSRTCD unless it is overridden by changing the value of the SORT-CONTROL special register) you will also get this message: IEC130I 'IGZSRTCD DD STATEMENT MISSING'. This message is informational only.

Programmer Response: If you want to pass in sort control cards from the sort control file, verify that the ddname is specified and the file is available.

System Action: No system action was taken.

IGZ0028S
IGZ0028S An I/O error occurred in sort control file file-name.

Explanation: An I/O error was encountered while trying to read the sort control file. Some or all of the user-supplied sort control cards will not be passed to Sort/Merge.

Programmer Response: For more information, look at the previous system message you received relating to this I/O error.

System Action: The application was terminated.

IGZ0029S
IGZ0029S Argument-1 for function function-name in program program-name at line line-number was less than zero.

Explanation: An illegal value for argument-1 was used.

Programmer Response: Ensure that argument-1 is greater than or equal to zero.

System Action: The application was terminated.

IGZ0030S
IGZ0030S Argument-2 for function function-namein program program at line line-number was not a positive integer.

Explanation: An illegal value for argument-1 was used.

Programmer Response: Ensure that argument-2 is a positive integer.

System Action: The application was terminated.

IGZ0031S
IGZ0031S A restart was not possible since the checkpoint record record-name was taken while a sort or merge was in progress.

Explanation: An attempt was made to use the restart facility of checkpoint/restart to resume execution of a job from a checkpoint taken by a COBOL program because of a rerun clause during a Sort/Merge operation. Only checkpoints taken by the sort product can be used to restart from a point within the Sort/Merge operation.

The checkpoint record cannot be used for restart.

Programmer Response: Use a different checkpoint record. If no other checkpoint records exist, the job cannot be restarted.

System Action: The application was terminated.

IGZ0032S
IGZ0032S A CANCEL was attempted on active program program-name.

Explanation: An attempt was made to cancel an active program. For example, program A called program B; program B is trying to cancel program A.

Programmer Response: Remove the failing CANCEL statement. In order to locate the failing CANCEL statement, rerun the application with TERMTHDACT(TRACE) or (ABEND). Review the traceback information to identify the program that issued the CANCEL.

System Action: The application was terminated.

IGZ0033S
IGZ0033S An attempt was made to pass a parameter address above 16 megabytes to AMODE(24) program program-name.

Explanation: An attempt was made to pass a parameter located above the 16-megabyte storage line to a program in AMODE(24). The called program will not be able to address the parameter.

Programmer Response: If the calling program is compiled with the RENT option, the DATA(24) option may be used in the calling program to make sure that its data is located in storage accessible to an AMODE(24) program. If the calling program is compiled with the NORENT option, the RMODE(24) option may be used in the calling program to make sure that its data is located in storage accessible to an AMODE(24) program. Verify that no linkedit, binder or genmod overrides are responsible for this error.

System Action: The application was terminated.

IGZ0034W
IGZ0034W The file with system-name system-name could not be extended. Secondary extents were not specified or were not available. The last WRITE was at offset offset in program program-name.

Explanation: There is insufficient space available for an output file. There is no invalid key clause, file status, or user error declarative. This corresponds to the MVS X37 ABEND.

Programmer Response: Check the file attributes and if necessary, reallocate the file. Also check dataset allocations.

System Action: No system action was taken.

IGZ0035S
IGZ0035S There was an unsuccessful OPEN or CLOSE of file file-name in program program-name at relative location location. Neither FILE STATUS nor an ERROR declarative were specified. The status code was status-code.

Explanation: An error has occurred while opening or closing the named file. No file status or user error declarative was specified.

Programmer Response: Check to make sure there is a ddname defined for the indicated file.

System Action: The application was terminated.

IGZ0036W
IGZ0036W Truncation of high order digit positions occurred in program program-name on line number line-number.

Explanation: The generated code has truncated an intermediate result (that is, temporary storage used during an arithmetic calculation) to 30 digits; some of the truncated digits were not 0.

Programmer Response: See COBOL/370 Programming Guide for a description of intermediate results.

System Action: No system action was taken.

IGZ0037S
IGZ0037S The flow of control in program program-name proceeded beyond the last line of the program.

Explanation: The program did not have a terminator (STOP, GOBACK, or EXIT), and control fell through the last instruction.

Programmer Response: Check the logic of the program. Sometimes this error occurs because of one of the following logic errors:

System Action: The application was terminated.

IGZ0038S
IGZ0038S A reference modification length value of reference-modification-value on line line-number which was not equal to 1 was found in a reference to data item data-item which was passed by value.

Explanation: The length value in a reference modification specification was not equal to 1. The length value must be equal to 1.

Programmer Response: Check the indicated line number in the program to ensure that any reference modified length values are (or will resolve to) 1.

System Action: The application was terminated.

IGZ0039S
IGZ0039S An invalid overpunched sign was detected in program program-name on line line-number.

Explanation: An operation was attempted on data defined with an overpunched sign. The value in the sign was not valid.

Programmer Response: This error might have occurred because of a REDEFINES clause involving the sign position or a group move involving the sign position, or the position was never initialized. Check for the above cases.

System Action: The application was terminated.

IGZ0040S
IGZ0040S An invalid separate sign was detected in program program-name on line line-number.

Explanation: An operation was attempted on data defined with a separate sign. The value in the sign position was not a plus (+) or a minus (-).

Programmer Response: This error might have occurred because of a REDEFINES clause involving the sign position or a group move involving the sign position, or the position was never initialized. Check for the above cases.

System Action: The application was terminated.

IGZ0041W
IGZ0041W The warning message limit was exceeded. Further warning messages were suppressed.

Explanation: The limit on warning messages is 256. This constraint on the number of warning messages prevents a looping program from flooding the system buffers.

Programmer Response: Correct the situations causing the warning messages or correct the looping problem.

System Action: No system action was taken.

IGZ0042C
IGZ0042C There was an attempt to use the IGZBRDGE macro, but the calling program was not COBOL.

Explanation: A non-COBOL program attempted to call a COBOL program using the IGZBRDGE interface. COBOL/370 could not find a COBOL environment.

Programmer Response: Do not call an entry point specified via the IGZBRDGE macro from a non-COBOL program.

System Action: The application was terminated.

IGZ0044S
IGZ0044S There was an attempt to call the COBOL main program program-name that was not in initial state.

Explanation: You will receive this message if you attempt to enter a NONREENTRANT COBOL/370 or VS COBOL II main program more than once. This is a nonstandard entry attempt.

Programmer Response: Modify the application so that the non-reentrant COBOL main program won't be called more than once.

System Action: The application was terminated.

IGZ0045S
IGZ0045S Unable to invoke method method-name on line number line number in COBOL program program-name.

Explanation: The specific method is not supported for the class of the current object reference.

Programmer Response: Check the indicated line number in the program to ensure that the class of the current object reference supports the method being invoked.

System Action: The application was terminated.

IGZ0046W
IGZ0046W The value specified in the program for the special-register special register was overridden by the corresponding value in the sort control file.

Explanation: A nondefault value for the SORT special register specified in the message was used in a program, but a value in the SORT control file which corresponds to that SORT special register was found. The value in the SORT control file was used, and the value in the SORT special register was ignored.

Programmer Response: See COBOL/370 Programming Guide for a description of SORT special registers and the SORT control file.

System Action: No system action was taken.

IGZ0047S
IGZ0047S Unable to invoke method method-name on line number line number in COBOL class class-name.

Explanation: The specific method is not supported for the class of the current object reference.

Programmer Response: Check the indicated line number in the class to ensure that the class of the current object reference supports the method being invoked.

System Action: The application was terminated.

IGZ0048W
IGZ0048W A negative base was raised to a fractional power in an exponentiation expression in program program-name at displacement displacement. The absolute value of the base was used.

Explanation: A negative number raised to a fractional power occurred in a library routine.

The value of a negative number raised to a fractional power is undefined in COBOL. If a SIZE ERROR clause had appeared on the statement in question, the SIZE ERROR imperative would have been used. However, no SIZE ERROR clause was present, so the absolute value of the base was used in the exponentiation.

Programmer Response: Ensure that the program variables in the failing statement have been set correctly.

System Action: No system action was taken.

IGZ0049W
IGZ0049W A zero base was raised to a zero power in an exponentiation expression in program program-name at displacement displacement. The result was set to one.

Explanation: The value of zero raised to the power zero occurred in a library routine.

The value of zero raised to the power zero is undefined in COBOL. If a SIZE ERROR clause had appeared on the statement in question, the SIZE ERROR imperative would have been used. However, no SIZE ERROR clause was present, so the value returned was one.

Programmer Response: Ensure that the program variables in the failing statement have been set correctly.

System Action: No system action was taken.

IGZ0050S
IGZ0050S A zero base was raised to a negative power in an exponentiation expression in program program-name at displacement displacement.

Explanation: The value of zero raised to a negative power occurred in a library routine.

The value of zero raised to a negative number is not defined. If a SIZE ERROR clause had appeared on the statement in question, the SIZE ERROR imperative would have been used. However, no SIZE ERROR clause was present.

Programmer Response: Ensure that the program variables in the failing statement have been set correctly.

System Action: The application was terminated.

IGZ0051S
IGZ0051S An invalid EBCDIC digit string was detected on conversion to floating point in program-name at displacement displacement.

Explanation: The input to the conversion routine contained invalid EBCDIC data.

Programmer Response: Ensure that the program variables in the failing statement have been set correctly.

System Action: The application was terminated.

IGZ0052C
IGZ0052C An internal error or invalid parameters were detected in the floating point conversion routine called from program-name at displacement displacement.

Explanation: None

Programmer Response: See your IBM service representative.

System Action: The application was terminated.

IGZ0053S
IGZ0053S An overflow occurred on conversion to floating point in program-name at displacement displacement.

Explanation: A number was generated in the program that is too large to be represented in floating point.

Programmer Response: You need to modify the program appropriately to avoid an overflow.

System Action: The application was terminated.

IGZ0054W
IGZ0054W An overflow occurred on conversion from floating point to fixed point in program-name at displacement displacement. The result was truncated.

Explanation: The result of a conversion to fixed point from floating point contains more digits than will fit in the fixed point receiver. The high order digits were truncated.

Programmer Response: No action is necessary, although you may want to modify the program to avoid an overflow.

System Action: No system action was taken.

IGZ0055W
IGZ0055W An underflow occurred on conversion to floating point in program-name at displacement displacement. The result was set to zero.

Explanation: On conversion to floating point, the negative exponent exceeded the limit of the hardware. The floating point value was set to zero.

Programmer Response: No action is necessary, although you may want to modify the program to avoid an underflow.

System Action: No system action was taken.

IGZ0056W
IGZ0056W One or more files were not closed by program program-name prior to program termination.

Explanation: The specified program has finished but has not closed all of the files it opened. COBOL attempts to clean up storage and closes any open files.

Programmer Response: Check that all files are closed before the program terminates.

System Action: No system action was taken.

IGZ0057S
IGZ0057S There was an attempt to initialize a reusable environment through ILBOSTP0, but either the enclave was not the first enclave or COBOL was not the main program of the already established enclave.

Explanation: A request to establish a reusable environment through ILBOSTP0 can only occur at the beginning of the application. Examples when this error can occur:

Programmer Response: Only invoke ILBOSTP0 prior to calling any program within the application that brings up Language Environment.

System Action: The application was terminated.

IGZ0058S
IGZ0058S Exponent overflow occurred in program program-name at displacement displacement.

Explanation: Floating point exponent overflow occurred in a library routine.

Programmer Response: Ensure that the program variables in the failing statement have been set correctly.

System Action: The application was terminated.

IGZ0059W
IGZ0059W An exponent with more than nine digits was truncated in program program-nameat displacement displacement.

Explanation: Exponents in fixed point exponentiations may not contain more than nine digits. The exponent was truncated back to nine digits; some of the truncated digits were not 0.

Programmer Response: No action is necessary, although you may want to adjust the exponent in the failing statement.

System Action: No system action was taken.

IGZ0060W
IGZ0060W Truncation of high order digit positions occurred in program program-name at displacement displacement.

Explanation: Code in a library routine has truncated an intermediate result (that is, temporary storage used during an arithmetic calculation) back to 30 digits; some of the truncated digits were not 0.

Programmer Response: See COBOL/370 Programming Guide for a description of intermediate results.

System Action: No system action was taken.

IGZ0061S
IGZ0061S Division by zero occurred in program program-name at displacement displacement.

Explanation: Division by zero occurred in a library routine. Division by zero is not defined. If a SIZE ERROR clause had appeared on the statement in question, the SIZE ERROR imperative would have been used. However, no SIZE ERROR clause was present.

Programmer Response: Ensure that the program variables in the failing statement have been set correctly.

System Action: The application was terminated.

IGZ0063S
IGZ0063S An invalid sign was detected in a numeric edited sending field in program-name on line number line-number.

Explanation: An attempt has been made to move a signed numeric edited field to a signed numeric or numeric edited receiving field in a MOVE statement. However, the sign position in the sending field contained a character that was not a valid sign character for the corresponding PICTURE.

Programmer Response: Ensure that the program variables in the failing statement have been set correctly.

System Action: The application was terminated.

IGZ0064S
IGZ0064S A recursive call to active program program-name in compilation unit compilation-unit was attempted.

Explanation: COBOL does not allow reinvocation of an internal program which has begun execution, but has not yet terminated. For example, if internal programs A and B are siblings of a containing program, and A calls B and B calls A, this message will be issued.

Programmer Response: Examine your program to eliminate calls to active internal programs.

System Action: The application was terminated.

IGZ0065S
IGZ0065S A CANCEL of active program program-name in compilation unit compilation-unit was attempted.

Explanation: An attempt was made to cancel an active internal program. For example, if internal programs A and B are siblings in a containing program and A calls B and B cancels A, this message will be issued.

Programmer Response: Examine your program to eliminate cancellation of active internal programs.

System Action: The application was terminated.

IGZ0066S
IGZ0066S The length of external data record data-record in program program-name did not match the existing length of the record.

Explanation: While processing External data records during program initialization, it was determined that an External data record was previously defined in another program in the run-unit, and the length of the record as specified in the current program was not the same as the previously defined length.

Programmer Response: Examine the current file and ensure the External data records are specified correctly.

System Action: The application was terminated.

IGZ0067S
IGZ0067S The NOEQUALS keyword in the sort control file file-name conflicted with the specifications of the DUPLICATES phrase on the SORT statement.

Explanation: A sort control file with an OPTION card specifying the NOEQUALS keyword was used for a SORT which had the DUPLICATES IN ORDER phrase specified. The NOEQUALS keyword and the DUPLICATES phrase conflict.

Programmer Response: Either remove the NOEQUALS keyword from the sort control file or remove the DUPLICATES IN ORDER phrase from the SORT statement.

System Action: The application was terminated.

IGZ0068S
IGZ0068W Duplicate characters were ignored in an INSPECT CONVERTING statement in program program-name at displacement displacement.

Explanation: The same character appeared more than once in the identifier that contained the characters to be converted in an INSPECT CONVERTING statement. The first occurrence of the character, and the corresponding character in the replacement field, are used, and subsequent occurrences are not used.

Programmer Response: Duplicate characters in the indicated INSPECT statement may be deleted; programmer action is not required.

System Action: No system action was taken.

IGZ0069S
IGZ0069S On VM, file file-name in program program-name attempted to use VSAM in XA or ESA mode. Using VSAM while in XA or ESA mode is not supported under the installed level of VM. The program was terminated.

Explanation: VSAM can only operate in S/370 mode virtual machines on VM/SP XA and VM/ESA Release 1 ESA feature. The job was cancelled. Only on VM/ESA Release 1.1 (CMS8), and higher releases, can VSAM and VS COBOL II be used in XA-mode and XC-mode virtual machines.

Programmer Response: See your systems programmer for assistance.

System Action: The application was terminated.

IGZ0070S
IGZ0070S The FILEDEF command "FILEDEF ddname DISK FILE ddname A4" was unsuccessful.

Explanation: An attempt at dynamic allocation for CMS file ddname using the FILEDEF command has failed.

Programmer Response: See your systems programmer for assistance.

System Action: The application was terminated.

IGZ0071S
IGZ0071S ALL subscripted table reference to table table-name by verb number verb-number on line line-number had an ALL subscript specified for an OCCURS DEPENDING ON dimension, and the object was less than or equal to 0.

Explanation: When the SSRANGE option is in effect, this message is issued to indicate that there are 0 occurrences of dimension subscripted by ALL.

The check is performed against the current value of the OCCURS DEPENDING ON OBJECT.

Programmer Response: Ensure that ODO object(s) of ALL-subscripted dimensions of any subscripted items in the indicated statement are positive.

System Action: The application was terminated.

IGZ0072S
IGZ0072S A reference modification start position value of reference-modification-value on line line-number referenced an area outside the region of data item data-item.

Explanation: The value of the starting position in a reference modification specification was less than 1, or was greater than the current length of the data item that was being reference modified. The starting position value must be a positive integer less than or equal to the number of characters in the reference modified data item.

Programmer Response: Check the value of the starting position in the reference modification specification.

System Action: The application was terminated.

IGZ0073S
IGZ0073S A non-positive reference modification length value of reference-modification-value on line line-number was found in a reference to data item data-item.

Explanation: The length value in a reference modification specification was less than or equal to 0. The length value must be a positive integer.

Programmer Response: Check the indicated line number in the program to ensure that any reference modified length values are (or will resolve to) positive integers.

System Action: The application was terminated.

IGZ0074S
IGZ0074S A reference modification start position value of reference-modification-value and length value of length on line line-number caused reference to be made beyond the rightmost character of data item data-item.

Explanation: The starting position and length value in a reference modification specification combine to address an area beyond the end of the reference modified data item. The sum of the starting position and length value minus one must be less than or equal to the number of characters in the reference modified data item.

Programmer Response: Check the indicated line number in the program to ensure that any reference modified start and length values are set such that a reference is not made beyond the rightmost character of the data item.

System Action: The application was terminated.

IGZ0075S
IGZ0075S Inconsistencies were found in EXTERNAL file file-name in program program-name. The following file attributes did not match those of the established external file: attribute-1 attribute-2 attribute-3 attribute-4 attribute-5 attribute-6 attribute-7

Explanation: One or more attributes of an external file did not match between two programs that defined it.

Programmer Response: Correct the external file. For a summary of file attributes which must match between definitions of the same external file, see IBM COBOL Language Reference.

System Action: The application was terminated.

IGZ0076W
IGZ0076W The number of characters in the INSPECT REPLACING CHARACTERS BY data-name in program program-name at displacement displacement was not equal to one. The first character was used.

Explanation: A data item which appears in a CHARACTERS phrase within a REPLACING phrase in an INSPECT statement must be defined as being one character in length. Because of a reference modification specification for this data item, the resultant length value was not equal to one. The length value is assumed to be one.

Programmer Response: You may correct the reference modification specifications in the failing INSPECT statement to ensure that the reference modification length is (or will resolve to) 1; programmer action is not required.

System Action: No system action was taken.

IGZ0077W
IGZ0077W The lengths of the data-item items in program program-name at displacement displacement were not equal. The shorter length was used.

Explanation: The two data items which appear in a REPLACING or CONVERTING phrase in an INSPECT statement must have equal lengths, except when the second such item is a figurative constant. Because of the reference modification for one or both of these data items, the resultant length values were not equal. The shorter length value is applied to both items, and execution proceeds.

Programmer Response: You may adjust the operands of unequal length in the failing INSPECT statement; programmer action is not required.

System Action: No system action was taken.

IGZ0078S
IGZ0078S ALL subscripted table reference to table table-name by verb number verb-number on line line-number will exceed the upper bound of the table.

Explanation: When the SSRANGE option is in effect, this message is issued to indicate that a multi-dimension table with ALL specified as one or more of the subscripts will result in a reference beyond the upper limit of the table.

The range check was performed on the composite of the subscripts and the maximum occurrences for the ALL subscripted dimensions. For variable-length tables the address is outside the region of the table defined when all OCCURS DEPENDING ON objects are at their maximum values; the ODO object's current value is not considered. The check was not performed on individual subscripts.

Programmer Response: Ensure that OCCURS DEPENDING ON objects as evaluated at run-time do not exceed the maximum number of occurrences of the dimension for table items referenced in the failing statement.

System Action: The application was terminated.

IGZ0079S
IGZ0079S On CICS, program-lang program program-name attempted to call OS/VS COBOL program program-name.

Explanation: On CICS, a COBOL/370 or a VS COBOL II program attempted to call an OS/VS COBOL program with the CALL statement. Using the CALL statement to perform calls between the following are not not supported on CICS:

Programmer Response: If you need to invoke an OS/VS COBOL program from a COBOL/370 or VS COBOL II program, use EXEC CICS LINK.

System Action: The application was terminated.

IGZ0080S
IGZ0080S A dynamic call to module-name failed because the program entry name program-name does not match.

Explanation: If a program compiled with the PGMNAME(LONGUPPER) or the PGMNAME(LONGMIXED) option is dynamically called, the program name must be identical to the name of the module that contains it. If an alternate entry name is called, the entry name must be identical to the ALIAS name representing that entry point. Note that the program entry name can not exceed 8 bytes and must be entirely upper-case.

Programmer Response: The name of the program failing the dynamic call, must be modified to comply with the rules state aboved. Otherwise, only static calls to the program are permitted.

System Action: The application was terminated.

IGZ0096C
IGZ0096C A load of module module-name was unsuccessful.

Explanation: An attempt to load a module failed. The module was not available or a system load failure occurred.

Programmer Response: See your systems programmer for assistance.

System Action: The application was terminated.

IGZ0097S
IGZ0097S Argument-1 for function function-name in program program-name at displacement displacement contained no digits.

Explanation: Argument-1 for the indicated function must contain at least 1 digit.

Programmer Response: Adjust the number of digits in Argument-1 in the failing statement.

System Action: The application was terminated.

IGZ0098C
IGZ0098C The message text for message message-number was inaccessible to IGZCWTO.

Explanation: The message text module used by IGZCWTO did not contain message text for the indicated message number.

Programmer Response: See your IBM service representative.

System Action: The application was terminated.

IGZ0099C
IGZ0099C Internal error error-number was detected in module module-name.

Explanation: An unrecoverable error was detected in run-time module module-name.

When the module name in the message is IGZCXCC, the error-number indicates the error as described below:

Error-number Description 1 The COBOL environment is not initialized. The COBOL environment must be initialized before calling IGZCXCC. 2 An invalid function code was passed to IGZCXCC. 3 An invalid name length was passed to IGZCXCC. 4 IGZCXCC detected that a nested enclave should be created. 5 IGZCXCC cannot be called when running on CICS or VM.

When the module name in the message is IGZCLNC, IGZCLNK, or IGZCFCC, the error-number indicates the error as described below: Error-number Description 9 IGZCXCC is being used and an invalid cancel was attempted. Programmer Response: See your IBM service representative.

System Action: The application was terminated.

IGZ0100S
IGZ0100S Argument-1 for function function in program program at displacement displacement was less than or equal to -1.

Explanation: An illegal value was used for Argument-1.

Programmer Response: Ensure that argument-1 is greater than -1.

System Action: The application was terminated.

IGZ0108S
IGZ0108S The cancel of program program-name failed because the module load point address was not provided when the program was loaded.

Explanation: In an LE/370 preinitialized environment users may specify their own load service routine. If this routine fails to provide the module load point address as an output parameter when loading a COBOL program, that program can not be cancelled using COBOL'S CANCEL statement.

Programmer Response: Modify the user load service to provide the module load point address.

System Action: The application was terminated.

IGZ0151S
IGZ0151S Argument-1 for function function-name in program program-name at displacement displacement contained more than 18 digits.

Explanation: The total number of digits in argument-1 of the indicated function exceeded 18 digits.

Programmer Response: Adjust the number of digits in argument-1 in the failing statement.

System Action: The application was terminated.

IGZ0152S
IGZ0152S Invalid character character was found in column column-number in argument-1 for function function-name in program program-name at displacement program-displacement.

Explanation: A non-digit character other than a decimal point, comma, space or sign (+,-,CR,DB) was found in argument-1 for NUMVAL/NUMVAL-C function.

Programmer Response: Correct argument-1 for NUMVAL or NUMVAL-C in the indicated statement.

System Action: The application was terminated.

IGZ0154S
IGZ0154S A procedure pointer was set to nested program nested-program-name in program program-name at displacement displacement.

Explanation: Procedure pointers can not be set to a nested program.

Programmer Response: Make sure that the procedure program is set to an external program.

System Action: The application was terminated.

IGZ0155S
IGZ0155S Invalid character character was found in column column-number in argument-2 for function function-name in program program-name at displacement program-displacement.

Explanation: Illegal character was found in argument-2 for NUMVAL-C function.

Programmer Response: Check that the function argument does follow the syntax rules.

System Action: The application was terminated.

IGZ0156S
IGZ0156S Argument-1 for function function-name in program program-name at line line-number was less than zero or greater than 28.

Explanation: Input argument to function FACTORIAL is greater than 28 or less than 0.

Programmer Response: Check that the function argument is only one byte long.

System Action: The application was terminated.

IGZ0157S
IGZ0157S The length of Argument-1 for function function-name in program program-name at line line-number was not equal to 1.

Explanation: The length of input argument to ORD function is not 1.

Programmer Response: Check that the function argument is only one byte long.

System Action: The application was terminated.

IGZ0158S
IGZ0158S The length of Argument-1 for function function-name in program program-name at displacement displacement was zero.

Explanation: The length of the argument of the REVERSE, the UPPER-CASE or the LOWER-CASE function is zero.

Programmer Response: Make sure that the length of the argument is greater than zero.

System Action: The application was terminated.

IGZ0159S
IGZ0159S Argument-1 for function function-name in program program-name at line line-number was less than 1 or greater than 3067671.

Explanation: The input argument to DATE-OF-INTEGER or DAY-OF-INTEGER function is less than 1 or greater than 3067671.

Programmer Response: Check that the function argument is in the valid range.

System Action: The application was terminated.

IGZ0160S
IGZ0160S Argument-1 for function function-name in program program-name at line line-number was less than 16010101 or greater than 99991231.

Explanation: The input argument to function INTEGER-OF-DATE is less than 16010101 or greater than 99991231.

Programmer Response: Check that the function argument is in the valid range.

System Action: The application was terminated.

IGZ0161S
IGZ0161S Argument-1 for function function-name in program program-name at line line-number was less than 1601001 or greater than 9999365.

Explanation: The input argument to function INTEGER-OF-DAY is less than 1601001 or greater than 9999365.

Programmer Response: Check that the function argument is in the valid range.

System Action: The application was terminated.

IGZ0162S
IGZ0162S Argument-1 for function function-name in program program-name at line line-number was less than 1 or greater than the number of positions in the program collating sequence.

Explanation: The input argument to function CHAR is less than 1 or greater than the highest ordinal position in the program collating sequence.

Programmer Response: Check that the function argument is in the valid range.

System Action: The application was terminated.

IGZ0163S
IGZ0163S Argument-1 for function function-name in program program-name at line line-number was less than zero.

Explanation: The input argument to function RANDOM is less than 0.

Programmer Response: Correct the argument for function RANDOM in the failing statement.

System Action: The application was terminated.

IGZ0164C
IGZ0164C module-name was unable to get HEAP storage.

Explanation: The request made to obtain heap storage failed.

Programmer Response: See your IBM service representative.

System Action: The application was terminated.

IGZ0165S
IGZ0165S A reference modification start position value of start-position-value on line line referenced an area outside the region of the function result of function-result.

Explanation: The value of the starting position in a reference modification specification was less than 1, or was greater than the current length of the function result that was being reference modified. The starting position value must be a positive integer less than or equal to the number of characters in the reference modified function result.

Programmer Response: Check the value of the starting position in the reference modification specification and the length of the actual function result.

System Action: The application was terminated.

IGZ0166S
IGZ0166S A non-positive reference modification length value of length on line line-number was found in a reference to the function result of function-result.

Explanation: The length value in a reference modification specification for a function result was less than or equal to 0. The length value must be a positive integer.

Programmer Response: Check the length value and make appropriate correction.

System Action: The application was terminated.

IGZ0167S
IGZ0167S A reference modification start position value of start-position and length value of length on line line-number caused reference to be made beyond the rightmost character of the function result of function-result.

Explanation: The starting position and length value in a reference modification specification combine to address an area beyond the end of the reference modified function result. The sum of the starting position and length value minus one must be less than or equal to the number of characters in the reference modified function result.

Programmer Response: Check the length of the reference modification specification against the actual length of the function result and make appropriate corrections.

System Action: The application was terminated.

IGZ0168S
IGZ0168S The creation of a second enclave within a reusable environment was attempted. The first program of the second enclave was program-name.

Explanation: Reusable environment support is limited to a single enclave. The enclave must be the first enclave.

Programmer Response: Modify the application so that it can run within a single enclave with the COBOL reusable environment. If the program name printed is "????????" then the first program of the second enclave is not COBOL.

System Action: The application was terminated.

IGZ0169W
IGZ0169W External data data-record was allocated within the 31-bit address range. The called program program-name contained a definition for this external data, and it was compiled with the DATA(24) option.

Explanation: External data was allocated ANYWHERE within the 31-bit addressing range by a program. But a subsequently called program containing a definition for that same external data was compiled with the DATA(24) option. This was discovered while processing external data records during program initialization.

Programmer Response: Re-compile program with the DATA(31) option if appropriate. If the external data needs to be allocated below 16M, then the FIRST program in the rununit that contains a definition of the external data must be compiled with the DATA(24) option.

System Action: No system action was taken.

IGZ0170S
IGZ0170S One or more files were not closed by NORENT program program-name and the program cannot be found in storage.

Explanation: The specified NORENT program has not closed all of the files it opened and the program cannot be found in storage. COBOL is unable to close the files because the required control blocks which reside in the program are no longer available. Unpredictable results will occur when the system attempts to close the files. This error can occur if the application has an assembler program that loads and deletes the specified NORENT program.

Programmer Response: Ensure that all files are closed by the NORENT program.

System Action: The application was terminated.

IGZ0172W
IGZ0172W RTEREUS was specified, but ignored. A reusable run-time environment was not established because the first program in the application was not COBOL.

Explanation: A reusable environment can be established only when the main program of the first enclave is COBOL.

Programmer Response: Ensure that RTEREUS is off. The performance benefits of using RTEREUS are available without the run-time option when the application is running under Language Environment.

System Action: No system action is taken.

IGZ0200W
IGZ0200W A file attribute mismatch was detected. File file-name in program program-name was defined as a physical sequential file and the file specified in the ASSIGN clause was a VSAM data set.

Explanation: The program file description specified that the file was a physical sequential file and the data set associated with the ASSIGN clause was found to be a VSAM file. The OPEN statement failed.

Programmer Response: Check that the file description and the DD parameter associated with the ASSIGN clause are for the correct data set.

System Action: If a file status was specified, no system action is performed. If a file status field was not specified, the program is terminated and message IGZ0035S is generated.

IGZ0201W
IGZ0201W A file attribute mismatch was detected. File file-name in program program-name had a record length of record-length-1 and the file specified in the ASSIGN clause had a record length of record-length-2.

Explanation: The program file description specified a record length that did not match the record length of the data set associated with the ASSIGN clause. The OPEN statement failed.

Programmer Response: For Format-V and Format-S files the maximum record length specified in your program must be exactly 4 bytes smaller than the length attribute of the data set. For Format-F files, the record length specified in your program must exactly match the length attribute of the data set. For Format-U files, the maximum record length specified in your program must exactly match the length attribute of the data set. If your file is a printer file, the compiler may add one byte to the file description for carriage control character, depending on the ADV compiler option and the COBOL statements used in your program. In which case, the added byte must be included in the data set length attribute. For VSAM files, the record length must not be greater than the maximum length attribute of the data set. For VSAM simulated RRDS (SIMVRD run-time option) the record length specified in the ASSIGN clause is incremented by 4 bytes prior to comparison with the length attribute of the data set.

System Action: If a file status was specified, no system action is performed. If a file status field was not specified, the program is terminated and message IGZ0035S is generated.

IGZ0202W
IGZ0202W A file attribute mismatch was detected. File file-name in program program-name specified ASCII data and the file specified in the ASSIGN clause did not contain the ASCII data attribute.

Explanation: The CODE-SET clause was specified in the program file description and the data set associated with the ASSIGN clause did not contain ASCII data. The OPEN statement failed.

Programmer Response: Check that the data set associated with the ASSIGN clause is the correct one, and if it is, check the data set for the ASCII attribute.

System Action: If a file status was specified, no system action is performed. If a file status field was not specified, the program is terminated and message IGZ0035S is generated.

IGZ0203W
IGZ0203W A file attribute mismatch was detected. File file-name in program program-name specified non-ASCII data and the file specified in the ASSIGN clause contained the ASCII data attribute.

Explanation: The data set associated with the ASSIGN clause contained ASCII type data and the file description in the program did not contain ASCII data. The OPEN statement failed.

Programmer Response: Check that the data set associated with the ASSIGN clause is the correct one, and if it is, check the data set for the ASCII attribute.

System Action: If a file status was specified, no system action is performed. If a file status field was not specified, the program is terminated and message IGZ0035S is generated.

IGZ0204W
IGZ0204W A file attribute mismatch was detected. File file-name in program program-name was defined as RECORDING MODE recording-mode and the file specified in the ASSIGN clause did not contain the same attribute.

Explanation: The RECORDING MODE specified in the program file description did not match the data control block fields of the data set associated with the ASSIGN clause. The OPEN statement failed.

Programmer Response: Check the data control block fields of the actual data set to verify that the RECORDING MODE matches. The most common cause of this error is conflicting fixed and variable record length data set attributes.

System Action: If a file status was specified, no system action is performed. If a file status field was not specified, the program is terminated and message IGZ0035S is generated.

IGZ0205W
IGZ0205W An OPEN failure occurred for file file-name in program program-name because the SMSVSAM server was not available. The file was closed.

Explanation: COBOL encountered a SMSVSAM server not available error return while performing OPEN, I/O, or control block testing of a VSAM data set in RLS mode. For this error condition VSAM requires that the file be closed, opened, and positioned prior to resubmitting requests. Look for possible VSAM error messages in the job log.

Programmer Response: COBOL only performs a close of the file. Resolve the SMSVSAM server not available condition and resubmit the run or remove the RLS keyword specification from the DD statement.

System Action: No system action is performed.

IGZ0206W
IGZ0206W The AIXBLD runtime option was invalid for file file-name in program program-name because the file was opened in RLS mode. The file was closed.

Explanation: The AIXBLD option is only supported for VSAM data sets opened without RLS mode. VSAM data sets opened in RLS mode can be empty, but upgrades to empty paths are not supported. The alternate index path must be built prior to using RLS mode. The alternate index was not built and the file was closed.

Programmer Response: If AIXBLD option is required, remove the RLS keyword specification from the DD statement for this file and resubmit the run.

System Action: No system action is performed.

IGZ0207W
IGZ0207W The SIMVRD runtime option was invalid for file file-name in program program-name because the file was opened in RLS mode. The file was closed.

Explanation: The SIMVRD option is not supported for VSAM data sets in RLS mode. The file was closed.

Programmer Response: If SIMVRD option is required, remove the RLS keyword specification from the DD statement for this file and resubmit the run.

System Action: No system action is performed.

IGZ0210S
IGZ0210S There was an attempt to run an OS/VS COBOL program program-name in a non-initial thread.

Explanation: OS/VS COBOL programs can only run in the initial thread. For example, OS/VS COBOL programs can not run in a subtask created by a PL/I CALL statement with the TASK, EVENT, or PRIORITY option.

Programmer Response: Compile the COBOL program with the COBOL/370 compiler.

System Action: The application is terminated.

IGZ0211S
IGZ0211S There was an attempt to run COBOL programs in more than one thread. The name of the program that was invoked is program-name.

Explanation: COBOL/370 and VS COBOL II programs can only be run in one thread at a time. This condition can occur when PL/I multitasking is used or when POSIX(ON) is in effect.

If PLI multitasking is used, here are examples that can cause this condition:

If POSIX(ON) is in effect, here are examples that can cause this condition:

Programmer Response: Change the application so that COBOL programs are used in only one task at a time if they are running in the PL/I Multitasking environment or in one thread at a time if they are running with POSIX(ON).

System Action: The application is terminated.

If you experience a problem with this page, please send a message to JTate@JaTomes.Com including a description of the problem.

Last modified: Monday Jan-11-1999.