COBOL Invokes the VAX-11 COBOL compiler to compile a COBOL source program. See the VAX-11 COBOL User's Guide for additional information. This optional software product is available under separate license. Format: COBOL file-spec[,...] COBOL can also be used to: o Invoke the VAX-11 COBOL-74 compiler (COBOL/C74) Additional information available: Other_compiler /C74 Errors Parameters Qualifiers /ANSI_FORMAT /AUDIT /CHECK /CONDITIONALS /COPY_LIST /CROSS_REFERENCE /DEBUG /LIST /MACHINE_CODE /MAP /OBJECT /SEQUENCE_CHECK /TRUNCATE /VERB_LOCATION /WARNINGS COBOL Parameters file-spec[,...] Specifies one or more COBOL source programs to be compiled. If a file specification does not contain a file type, the compiler uses the default file type of COB. You can specify more than one input file but you must use separators. Each file is compiled separately when you separate the file specifications with a comma. Files separated by plus signs are concatenated in a single compilation. No wild card characters are allowed in the file specification. COBOL Qualifiers /ANSI_FORMAT /ANSI_FORMAT /NOANSI_FORMAT (D) Indicates that the source program is in conventional ANSI format. The compiler then expects 80-character card image records with optional sequence numbers in character positions 1 through 6, indicators in position 7, Area A beginning in position 8, Area B beginning in position 12, and the identification area in positions 73 through 80. The default is /NOANSI_FORMAT; that is, the compiler assumes that the source program is in DIGITAL's terminal format, where Area A begins in position 1, Area B begins in position 5, and the source program records do not have line numbers. Valid for COBOL and COBOL/C74. /AUDIT /AUDIT[=("string",...)] /NOAUDIT (D) Controls whether user-supplied text is to be included in a Common Data Dictionary (CDD) history list entry if a compilation accesses the CDD. You can specify from 1 to 64 strings with the /AUDIT qualifier. If you specify more than one string, separate them with commas and enclose the list in parentheses. If you specify /AUDIT without a string, a standard history list entry is created with no additional text. Valid for COBOL. Not supported by COBOL/C74. /CHECK /CHECK[=(option[,...])] /NOCHECK (D) Specifies conditions to be checked at execution time. Controls whether the system checks PERFORM statements, indexes, subscripts, reference modifications, and the depending-item for specific run-time errors. You can select one or more of the following options: [NO]PERFORM Verifies that PERFORM statement rules are met. The default is NOPERFORM. [NO]BOUNDS Verifies the range of subscripts and reference modifiers. The default is NOBOUNDS. ALL Same as /CHECK without any options. NONE Same as /NOCHECK. Default if /CHECK is not used. Valid for COBOL. Not supported by COBOL/C74. /CONDITIONALS /CONDITIONALS[=(character,...)] /NOCONDITIONALS (D) Indicates which conditional compilation lines are to be compiled. The characters A-Z specify the conditional compilation lines to be complied. If no characters are specified, all conditional compilation lines are compiled. Valid for COBOL. Not supported by COBOL/C74. /COPY_LIST /COPY_LIST /NOCOPY_LIST (D) Controls whether text copied from library files is printed in the listing file. If /NOCOPY_LIST is specified, only the COPY statement appears in the listing. Valid for COBOL and COBOL/C74. /CROSS_REFERENCE /CROSS_REFERENCE[=(option[,...])] /NOCROSS_REFERENCE (D) Controls whether the compiler creates a cross-reference listing as part of the listing file. You can select one or both of the following options: ALPHABETICAL The compiler sorts user-defined names in alphabetical order and lists them with the source program line numbers. DECLARED Produces a listing of user-defined names in order of declaration. If you specify /CROSS_REFERENCE without specifying an option, an alphabetical listing of user-defined names is produced. COBOL/C74 does not allow the options, data- and procedure-names are listed in ascending order with the source program line numbers on which they appear. Valid for COBOL and COBOL/C74. /DEBUG /DEBUG[=(option[,...])] /NODEBUG Controls whether the compiler produces traceback and local symbol table information for the VAX-11 Symbolic Debugger. You can select one or more of the following options: [NO]SYMBOLS Produces a local symbol table that allows you to refer to data items by data-name. NOSYMBOLS is the default. [NO]TRACEBACK Produces traceback information only to provide the debugger with compiler-generated line numbers and names. TRACEBACK is the default. ALL Provides traceback and local symbol table information. Equivalent to /DEBUG without any options or /DEBUG=(TRACEBACK,SYMBOLS). NONE Omits traceback and local symbol table information. /DEBUG=NONE is equivalent to /NODEBUG. If you specify a qualifier parameter, the default options do not change unless individually modified. Valid for COBOL and COBOL/C74. /LIST /LIST[=file-spec] /NOLIST Controls whether the compiler names and produces an output listing file. If you issue the COBOL command from the interactive mode, the compiler does not create a listing file; the default is /NOLIST. If you issue the COBOL command from batch mode, the default is /LIST: the compiler gives a listing file the same file name as the input source file. The output file type defaults to LIS. The listing file always contains a listing of the source program. Other portions of the listing file are optionally produced under the control of the /MACHINE_CODE, /MAP, and /CROSS_REFERENCE qualifiers. Valid for COBOL and COBOL/C74. /MACHINE_CODE /MACHINE_CODE /NOMACHINE_CODE (D) Controls whether the listing file contains a list of the generated machine code. Valid for COBOL. Not supported by COBOL/C74. /MAP /MAP[=option] /NOMAP (D) Controls whether the compiler produces the following maps in the listing file: o data-names, procedure-names, and file-names o external references o subschema objects You can control the format of the data-name, procedure-name, and file-name maps in the listing file by specifying one or both of the following options: ALPHABETICAL Produces an alphabetical list of map items DECLARED Produces a list of map items in the order they were declared If you specify /MAP without specifying an option, an alphabetical list of map items is produced. COBOL/C74 does not allow the use of the option with /MAP. Valid for COBOL and COBOL/C74. /OBJECT /OBJECT[=file-spec] (D) /NOOBJECT Controls whether the compiler creates an output object module. By default, the compiler produces an object module with the same file name as the source file and a file type of OBJ. Valid for COBOL and COBOL/C74. /SEQUENCE_CHECK /SEQUENCE_CHECK /NOSEQUENCE_CHECK (D) Controls whether the compiler produces a sequence check on the line numbers in columns 1 through 6 of the source program. Valid for COBOL. Not supported by COBOL/C74. /TRUNCATE /TRUNCATE /NOTRUNCATE (D) Controls how the compiler stores values in COMPUTATIONAL receiving items if high-order truncation is necessary. If you specify /NOTRUNCATE, the compiler truncates values according to the VAX-11 hardware storage unit (word, longword, or quadword) allocated to the receiving item. If you specify /TRUNCATE, the compiler truncates values according to the number of decimal digits specified by the PICTURE size. Specifying /TRUNCATE increases program execution time. Valid for COBOL. Not supported by COBOL/C74. /VERB_LOCATION /VERB_LOCATION /NOVERB_LOCATION (D) Controls whether the compiler lists the object location for each verb in the source program. If you specify /VERB_LOCATION, the location appears on the line before the source line in which the verb is used. Valid for COBOL/C74 only. /WARNINGS /WARNINGS[=(option[,...])] /NOWARNINGS Controls whether the compiler prints warning or informational diagnostics as well as error and severe error diagnostic messages. You can select one or more of the following options: [NO]STANDARD Produces/does not produce informational diagnostics on language features that are DIGITAL extensions. NOSTANDARD is the default. [NO]INFORMATION Produces/does not produce informational diagnostics. NOINFORMATION is the default. [NO]OTHER Produces/does not produce warning diagnostics. OTHER is the default. ALL Provides the diagnostics produced by STANDARD, INFORMATION, and OTHER. /WARNINGS=ALL is the equivalent of /WARNINGS. NONE Omits the listing of all diagnostics. /WARNINGS=NONE is the equivalent of /NOWARNINGS. If you specify an option, defaults for other options do not change (unless individually modified). COBOL/C74 does not allow the use of the option, only /WARNINGS and /NOWARNINGS are permitted. Valid for COBOL and COBOL/C74. COBOL Errors CALFAI CALL failed on routine Explanation: Failure to CALL the specified routine. This may be due to one of several possible conditions: a. The routine name is too long (greater than 31 characters). b. The routine name is too short (for example, all blanks). c. The routine name contains invalid characters. d. The named routine is not in the linked image. User Action: Either code the routine name to conform to the syntax rules for proper routine name formation or relink the image to include the missing routine. COBOL Errors CANFAIL CANCEL failed on routine Explanation: Failure to CANCEL the specified routine. This may be due to a number of problems including: a. The routine name is too long (greater than 31 characters). b. The routine name is too short (for example, all blanks) c. The routine name contains invalid characters. d. The named routine is not in the linked image. User Action: Either code the routine name to conform to the syntax rules for proper routine name formation or relink the image to include the missing routine. COBOL Errors DELINCOPE DELETE on file incompatible with OPEN mode Explanation: The DELETE operation is not compatible with the open mode of the file. The file status variable, if present, has been set to 94. No applicable USE procedure was found. User Action: Examine the mode in which the file is opened (prior to the attempted DELETE operation) and make the open mode consistent with the DELETE operation. COBOL Errors DELNO_R_S attempting DELETE on file without previous READ or START Explanation: Attempting to perform a DELETE on this file without having previously performed a READ or START operation. The file status variable, if present, has been set to 93. No applicable USE procedure was found. User Action: Your program must execute a READ or START operation (in sequential access mode) immediately before executing the DELETE operation. This must occur for each execution of the DELETE operation. COBOL Errors DELUNOFIL attempting DELETE on unopened file Explanation: Attempting to perform a DELETE before the file is opened. The file status variable, if present, has been set to 94. No applicable USE procedure was found. User Action: Your program must execute an appropriate OPEN operation before attempting to perform a DELETE operation on the file. COBOL Errors EOFON_ACC end-of-file detected on ACCEPT from file Explanation: An end-of-file condition was detected in executing an ACCEPT statement. User Action: You typed a CNTRL/Z, which caused an end-of-file condition for an ACCEPT statement. If you wish to use CNTRL/Z as an end-of-file indicator, you should code the input operations using an ACCEPT AT END statement. COBOL Errors ERRDURACC error during ACCEPT from file Explanation: An error condition was detected by RMS in executing the ACCEPT operation. The subsequent error message is the RMS error code associated with this error. User Action: You typed an illegal character (such as BREAK key). If you wish to trap such illegal input characters, code the input operation using a COBOL READ statement and declare an appropriate USE procedure to handle the error. COBOL Errors ERRDURDIS error during DISPLAY on file Explanation: An error condition was detected by RMS in executing the DISPLAY operation. The subsequent error message is the RMS error code associated with this error. User Action: Examine the logical name assignment and/or the type of device to which the DISPLAY statement is attempting to write output information. COBOL Errors ERRDURSOR error during SORT or MERGE Explanation: An error has occurred during a SORT or MERGE operation. The subsequent error message is the associated SORT or MERGE error code. User Action: Examine the logic of the program to determine why an error is occurring during a SORT or MERGE. In particular, if the program contains input procedures for the SORT or MERGE operation, ensure that at least one RELEASE operation is executed in the input procedure. Failure to do so can cause this error condition. COBOL Errors ERRON_FIL error on file Explanation: An error status has been returned by RMS that is not recognized by the VAX-11 COBOL I/O error handler. The subsequent error message is the associated RMS error code. The file status variable, if present, has been set to 30 (except for a CLOSE operation -- file status = 98). No applicable USE procedure has been found. User Action: Examine the subsequent error message issued by RMS and respond accordingly, or code an applicable USE procedure to handle the I/O error. COBOL Errors EXPDBOVER expression value in database argument list overflows longword Explanation: The value of an offset or relative position integer expression in a database record selection expression cannot be contained in a longword. User Action: Determine why the value is too large and correct the program to use a value that is representable in a longword. COBOL Errors FAIGET_EF failure to get event flag Explanation: An internal operation associated with execution of the CANCEL operation requires an event flag number. The attempt to allocate the event flag number has failed. User Action: The process associated with your COBOL program has allocated a number of event flags. The execution of the CANCEL operation has requested one more event flag than is available to the process. Deallocate some event flag before executing the COBOL program containing the CANCEL operation. COBOL Errors FAIGET_VM failure to get virtual memory Explanation: An internal operation associated with the execution of an ACCEPT or DISPLAY statement requires the allocation of dynamic virtual memory. The attempt to allocate this space has failed. User Action: The executable image containing the COBOL ACCEPT or DISPLAY operation is using a large quantity of virtual memory. The execution of the ACCEPT or DISPLAY statement has requested more dynamic memory than is available to the executable image. Your program must use less virtual memory if the COBOL ACCEPT or DISPLAY operation is to work successfully. COBOL Errors FATINTERR fatal internal error Explanation: An internal consistency check has failed. This represents an internal error in the Run-Time Library and should be reported to Digital Equipment Corporation by software performance report. User Action: Either discuss this error with your local software support specialist or submit a software performance report with supporting documentation, including the system traceback listing. COBOL Errors FILALRCLO file already closed Explanation: Attempting to CLOSE a file that is already closed. The file status variable, if present, has been set to 94. No applicable USE procedure has been found. User Action: Examine the logic of your program and eliminate the redundant CLOSE operation. Alternatively, you may discover the inadvertent omission of performing an OPEN on this file. COBOL Errors FILALRLOC file is already locked Explanation: In the file sharing environment, attempting to open a file for which another process has exclusive access. The file status variable, if present, has been set to 91. No applicable USE procedure has been found. User Action: Declare an applicable USE procedure for this file to handle this I/O condition. COBOL Errors FILALROPE file is already open Explanation: Attempting to open a file that is already open. The file status variable, if present, has been set to 94. No applicable USE procedure has been found. User Action: Examine the logic of the program and eliminate the redundant OPEN operation. Alternatively, you may declare an applicable USE procedure to handle this error. COBOL Errors FILCLOLOC file is closed with LOCK Explanation: Attempting to open a file that is already closed with LOCK. The file status variable, if present, has been set to 94. No applicable USE procedure has been found. User Action: Examine the logic of the program and eliminate the attempted OPEN operation on the file. Alternatively, you may declare an applicable USE procedure to handle the error. COBOL Errors FILNOTFOU file not found on OPEN Explanation: The named file was not found during the execution of the OPEN statement. The file status variable, if present, has been set to 97. No applicable USE procedure has been found. User Action: Examine the referenced directory to check for the existence of the named file. Another common source of this error is a mistake in spelling the file specification for the file. COBOL Errors GOTO_ALT GO TO with no preceding ALTER Explanation: Attempting to perform a GO TO that has no preceding ALTER. User Action: Examine the logic of the program to ensure that the execution of an ALTER statement precedes the execution of the referenced GO TO statement. COBOL Errors INTDIVZER intermediate divide by zero Explanation: Attempting to divide by COBOL Intermediate Temporary that has a value of zero. User Action: Examine the referenced expression in which a division operation occurs and determine why the divisor has a zero value. COBOL Errors INTEXPOVE intermediate exponent overflow Explanation: A COBOL Intermediate Temporary is created that has an exponent greater than +99. User Action: Examine the referenced line of the source program containing an arithmetic operation and determine what is causing a COBOL Intermediate Temporary to be created with too large an exponent. COBOL Errors INTEXPUND intermediate exponent underflow Explanation: A COBOL Intermediate Temporary is created that has an exponent less than -99. User Action: Examine the referenced line of the source program containing an arithmetic operation and determine what is causing a COBOL Intermediate Temporary to be created with too small an exponent. COBOL Errors INTRESOPE intermediate reserved operand Explanation: Encountering a reference to a previously created COBOL Intermediate Temporary whose exponent is greater than +99 or less than -99. User Action: Examine the referenced line of the source program containing an arithmetic operation and determine what is causing a COBOL Intermediate Temporary to be created with too large or too small an exponent in a previously executed statement. COBOL Errors INVARG invalid argument Explanation: Internal consistency checking has detected an invalid argument being passed to a routine in the COBOL Run-Time Library. This represents an internal error and should be reported to Digital Equipment Corporation. User Action: Submit a software performance report with the appropriate supporting documentation, including the system traceback listing. COBOL Errors INVDECDAT invalid decimal data Explanation: Invalid decimal data has been encountered in the course of converting a numeric DISPLAY data item into a packed number. One or more of the following problems may exist: a. The length of the source string is outside of the range 0 through 31. b. The length of the destination packed decimal string is outside of the range 0 through 31. c. The source string contains an invalid byte. An invalid byte is: - Any character other than ASCII "0" through "9" in a digit byte or an ASCII "+" or a space or a hyphen in the sign byte of a leading separate numeric data item. - Any character other than ASCII "0" through "9" in any high-order byte (that is, any byte except the least significant byte) in a trailing numeric data item. d. In the case of trailing numeric input, the translation of the least significant digit produces an invalid decimal digit or sign nibble. User Action: This error usually occurs when space characters are used in lieu of insignificant, leading, zero digit positions for numeric fields. These fields are commonly found within records on a file. Examine such numeric fields on the file and replace all insignificant leading spaces in these fields with numeric zero characters. Alternatively, before referencing these fields in arithmetic operations, use the INSPECT statement to change insignificant space characters to zeros in these fields. Another alternative is the NUMERIC class test to determine if numeric data items contain numeric characters only. This class test should be executed before these numeric data items are referenced in arithmetic operations. COBOL Errors INVDECDIG invalid decimal digit Explanation: An invalid decimal digit has been encountered in the course of converting a packed decimal number. User Action: Examine the logic of the program to determine why illegal data is being discovered in converting the packed decimal number. COBOL Errors INVLINVAL invalid LINAGE value on file Explanation: An invalid value has been encountered in one of the data names associated with the LINAGE clause for this file. User Action: Examine the logic of the program and determine why a data name value associated with the LINAGE clause does not fall within the range of values as prescribed in the COBOL rules for the LINAGE clause. COBOL Errors KEYNOTMAT attempting to open indexed file whose actual keys do not match those declared Explanation: An OPEN was attempted on an indexed file whose keys (as described in the program) do not have the same data-type, size, and position within the record as when the file was created. The file status data item, if specified, has been set to 94. No applicable USE procedure has been found. User Action: Run SYS$SYSTEM:DSP to determine the actual keys within the file and change the program to describe the keys correctly. COBOL Errors LSTHNDLDB lost handler for database exception - environment corrupted Explanation: The default COBOL handler COB$$HANDLER was deleted, or a new handler was established that did not call COB$$HANDLER when a program was attempting to execute a GLOBAL USE procedure for a DB-EXCEPTION. User Action: Do not establish a new handler or include in the new handler a call to COB$$HANDLER for unrecognized conditions. COBOL Errors LSTHNDUSE lost handler for a USE procedure - environment corrupted Explanation: The default COBOL handler COB$$HANDLER was deleted, or a new handler was established that did not call COB$$HANDLER when a program was attempting to execute a GLOBAL USE procedure for an I/O statement. User Action: Do not establish a new handler or include in the new handler a call to COB$$HANDLER for unrecognized conditions. COBOL Errors NESERRPER nesting error for PERFORM Explanation: A logic error has been encountered in the order in which the nesting of PERFORM ranges are exited. User Action: PERFORM ranges must be exited in reverse order from which these PERFORM ranges are activated. Examine the logic of the PERFORM range nesting to discover why these PERFORM ranges are not exited in reverse order of their activation. COBOL Errors NO_SPACE no file space on device for file Explanation: During the course of an OPEN, a failure to find additional space on a particular device has been detected. The file status variable, if present, has been set to 95. No applicable USE procedure has been found. User Action: Most likely, you have many outdated and/or transient files on the device. Examine the directories on the particular device and free-up sufficient space by purging or deleting unused files, then resubmit the program for execution. COBOL Errors OCCDEPOVE OCCURS DEPENDING value overflows longword Explanation: The value of the data name associated with an OCCURS DEPENDING phrase cannot be contained in a longword. User Action: Examine the referenced line in the source program containing an implicit reference to the data name associated with an OCCURS DEPENDING phrase to determine why this value has overflowed a longword value. COBOL Errors ORGNOTMAT attempting to open file whose actual organization does not match that declared Explanation: There is a mismatch between the organization of the file as declared in the program and the organization of the file as it was created. This mismatch is encountered on the OPEN operation. The file status variable, if present, has been set to 94. No applicable USE procedure has been found. User Action: Examine the program and change the declaration of the file's organization to match the file organization attributes (sequential, relative, or indexed) when the file was initially created. COBOL Errors REAINCOPE READ on file incompatible with OPEN mode Explanation: The file was opened in a mode that is incompatible with a READ operation (that is, an open mode for which READ operations are disallowed). This error usually represents bad logic in the user program. The file status variable, if present, has been set to 94. No applicable USE procedure has been found. User Action: Examine the logic of the program to determine why a READ operation that is incompatible with the open mode is being attempted. Change the open mode to allow the READ operation or eliminate the READ operation. COBOL Errors REASMAMIN attempting READ of variable length smaller than minimum allowed from file Explanation: Attempting to READ a record that is smaller than the minimum length record declared in the program for this file. The file status variable, if present, has been set to 94. No applicable USE procedure has been found. User Action: Examine the length of the record on the file being read and then change the minimum record length declared in the program for this file to allow a successful READ operation on the record. COBOL Errors REAUNOFIL attempting READ on unopened file Explanation: Attempting a READ operation on a file that is not open at this time. This error usually represents a logic error in the user program. The file status variable, if present, has been set to 94. No applicable USE procedure has been found. User Action: Examine the logic of the program to determine why a READ operation is attempted on an unopened file. Change the logic of the program by opening the file or by eliminating the READ operation. COBOL Errors RECACTPER recursive activation of PERFORM Explanation: Attempting to PERFORM a paragraph or section that is already activated due to a previous PERFORM statement. This constitutes an attempted recursive activation of the paragraph or section and is illegal in the COBOL language. The program must execute an EXIT statement from the paragraph or section before this paragraph or section can be the subject of a subsequent PERFORM. User Action: Examine the logic of the program to determine why an EXIT from the paragraph or section is not being executed before the subsequent PERFORM of the same paragraph or section. COBOL Errors RECACTUSE recursive activation of USE procedure Explanation: Attempting to activate (enter) a USE procedure while that USE procedure is already active. USE procedures are activated (or entered) in response to an error or condition associated with an I/O operation. Within that USE procedure, another I/O operation has been attempted that caused this USE procedure to be entered recursively before exiting from the initial entry to the USE procedure. This recursive activation of the USE procedure is illegal in the COBOL language. User Action: Examine the logic of the program to ascertain the condition causing the recursive activation of the USE procedure and eliminate that condition. COBOL Errors RECLOCDEL record on file is already locked (DELETE attempt) Explanation: In the file sharing environment, attempting to DELETE a record that is already locked by another, contending process. The file status variable, if present, has been set to 92. No applicable USE procedure has been found. User Action: Code an applicable USE procedure in which the problem of record contention may be handled properly by your own program. Using USE procedures is important in the file sharing environment. COBOL Errors RECLOCREA record on file is already locked (READ attempt) Explanation: In the file sharing environment, attempting to READ a record that is already locked by another, contending process. The file status variable, if present, has been set to 92. No applicable USE procedure has been found. User Action: Code an applicable USE procedure in which the problem of record contention may be handled properly by your own program. Using USE procedures is important in the file sharing environment. COBOL Errors RECLOCREW record on file is already locked (REWRITE attempt) Explanation: In the file sharing environment, attempting to REWRITE a record that is already locked by another, contending process. The file status variable, if present, has been set to 92. No applicable USE procedure has been found. User Action: Code an applicable USE procedure in which the problem of record contention may be handled properly by your own program. Using USE procedures is important in the file sharing environment. COBOL Errors RECLOCSTA record on file is already locked (START attempt) Explanation: In the file sharing environment, attempting to perform a START operation on a record already locked by another, contending process. The file status variable, if present, has been set to 92. No applicable USE procedure has been found. User Action: Code an applicable USE procedure in which the problem of record contention may be handled properly by your own program. Using USE procedures is important in the file sharing environment. COBOL Errors RECLOCWRI record on file is already locked (WRITE attempt) Explanation: In the file sharing environment, attempting to WRITE a record that is already locked by another, contending process. The file status variable, if present, has been set to 92. No applicable USE procedure has been found. User Action: Code an applicable USE procedure in which the problem of record contention may be handled properly by your own program. Using USE procedures is important in the file sharing environment. COBOL Errors REWINCOPE REWRITE on file incompatible with OPEN mode Explanation: The REWRITE operation is not compatible with the open mode of the file. The file status variable, if present, has been set to 94. No applicable USE procedure has been found. User Action: Examine the mode in which the file was opened prior to the attempted REWRITE operation and change the open mode to allow the successful completion of the REWRITE operation. Alternatively, change the logic of the program to bypass the attempted REWRITE operation. COBOL Errors REWNO_R_S attempting REWRITE on file with no previous READ or START Explanation: Attempting to perform a REWRITE on this file without having previously performed a READ or START operation. The file status variable, if present, has been set to 93. No applicable USE procedure has been found. User Action: Your program must execute a READ or START operation (that is, sequential access mode) immediately before executing the REWRITE operation. This must occur for each execution of the REWRITE operation. COBOL Errors REWSMAMIN attempting REWRITE of variable length smaller than minimum allowed on file Explanation: Attempting to REWRITE a record that is smaller than the minimum record length declared in the program for this file. The file status variable, if present, has been set to 94. No applicable USE procedure has been found. User Action: Examine the length of the record on the file being rewritten and then change the minimum record length attribute in the program for the file to allow the successful REWRITE operation for this record. COBOL Errors REWUNOFIL attempting REWRITE on unopened file Explanation: Attempting to perform a REWRITE operation on this file before the file is opened. The file status variable, if present, has been set to 94. No applicable USE procedure has been found. User Action: Examine the logic of the program to determine why a REWRITE operation is attempted before the file is opened. Change the logic of the program to open the file or, alternatively, eliminate the REWRITE operation. COBOL Errors STAINCOPE START on file incompatible with OPEN mode Explanation: The START operation is not compatible with the current open mode of the file. The file status variable, if present, has been set to 94. No applicable USE procedure has been found. User Action: Examine the mode in which the file was opened prior to the attempted START operation and change the open mode to allow the successful completion of the start operation. COBOL Errors STAUNOFIL attempting START on unopened file Explanation: Attempting to perform a START operation on this file before the file is opened. The file status variable, if present, has been set to 94. No applicable USE procedure has been found. User Action: Examine the logic of the program to determine why a START operation is attempted before the file is opened. Change the logic of the program to open the file or, alternatively, eliminate the START operation before executing the OPEN. COBOL Errors SUBOVELON subscript or reference modifier overflows longword Explanation: The evaluation of a subscript or reference modifier has produced a value that cannot be contained in a longword quantity. User Action: Examine the referenced line of the source program containing the subscripting operation or reference modifier to determine why the value produced overflows a longword quantity. COBOL Errors TIMOVELON TIMES value overflows longword Explanation: The evaluation of the TIMES operand associated with the PERFORM statement has produced a value that cannot be contained in a longword quantity. User Action: Examine the referenced line of the source program to determine why the evaluation of the TIMES operand produces a value that overflows a longword quantity. COBOL Errors UNDEF_EXP attempting undefined exponentiation -- negative base raised to fractional exponent Explanation: Attempting an illegal exponentiation operation in COBOL in which a negative base is taken to a fractional power. User Action: Examine the logic of the source program to determine why this illegal operation is being attempted. COBOL Errors UNEINSCON INSPECT CONVERTING lengths unequal Explanation: The lengths of the search and replacement strings are not equal in the INSPECT CONVERTING statement. User Action: Examine the referenced INSPECT CONVERTING statement to determine why the lengths of the search and replacement strings are not equal. These lengths must be the same according to the rules of the COBOL language. COBOL Errors UNLNO_CUR attempting UNLOCK on file with no current record Explanation: Attempting to perform an UNLOCK RECORD statement without having established a current record. The file status variable, if present, is set to 93. No applicable USE procedure has been found. User Action: Execute a record operation that locks a record, and therefore establishes a current record before executing an UNLOCK RECORD statement. COBOL Errors UNLUNOFIL attempting UNLOCK on unopened file Explanation: Attempting an UNLOCK operation on a file that is not open. This error usually represents a logic error in the program. The file status data item, if present, has been set to 94. No applicable USE procedure has been found. User Action: Determine why an UNLOCK operation is attempted on an unopened file. Change the program to open the file or eliminate the UNLOCK operation. COBOL Errors WRIBEYBOU attempting WRITE beyond boundaries of file Explanation: Attempting to WRITE a record at a logical position that is outside of the bounds of this file. If a sequential WRITE has been attempted on a sequentially organized file, the file status variable has been set to 34 and no applicable USE procedure was found. User Action: This error usually occurs when your program attempts to write records to a volume that does not have sufficient free space to contain the file. Delete or purge as many files as possible to free-up sufficient space to contain the file being written. COBOL Errors WRIINCOPE WRITE on file incompatible with OPEN mode Explanation: The WRITE operation is not compatible with the current open mode of the file. The file status variable, if present, has been set to 94. No applicable USE procedure has been found. User Action: Examine the mode in which the file was opened prior to the attempted WRITE operation. Alternatively, change the logic of the program to bypass the attempted WRITE operation. COBOL Errors WRINOTASC attempting to WRITE non-ascending ISAM key on file Explanation: Attempting to perform a sequential WRITE operation to an indexed file in which the primary key is not in ascending sequence value. The file status variable, if present, has been set to 21. No applicable exception label or USE procedure was found. User Action: Examine the logic of the program to determine why the primary key values are not written in ascending key value. COBOL Errors WRISMAMIN attempting WRITE of variable length smaller than minimum allowed on file Explanation: Attempting to WRITE a record that is smaller than the minimum length record declared in the program for this file. The file status variable, if present, has been set to 94. No applicable USE procedure has been found. User Action: Examine the logic of the program to determine why it is shorter than the minimum length declared for this file in the program. COBOL Errors WRIUNOFIL attempting WRITE on unopened file Explanation: Attempting to perform a WRITE operation on this file before the file is opened. The file status variable, if present, has been set to 94. No applicable USE procedure has been found. User Action: Examine the logic of the program to determine why the WRITE operation is attempted before the file is opened. Change the logic of the program to open the file before executing the WRITE. Alternatively, eliminate the WRITE operation.