Acucobol Error Codes
Contents |
otherwise specified, each file status code can be received for operations on any file organizations in any access mode. cobol error codes The ANSI'74, ANSI'85 and Extended File Status codes are given in your fortran error codes Error Messages. The following sections contain the RM/COBOL file status codes and the Microsoft V2 file status codes. mainframe error codes In addition to the above file status conventions you can produce more detailed extended file status codes. Extended file status codes have the following format: 9/nnn where nnn is java error codes a binary (COMP-X) number, equivalent to a run-time error number. Run-time errors are documented in the chapter Run-time System Messages in your Error Messages. For example, if you are writing a file to disk and the disk runs out of space, the ANSI'74 file status would be "30", which translates into a "Permanent error - no other information is
C++ Error Codes
available" error message. That error message is very general; a "permanent error" could mean that the disk has failed, or that the disk drive door is open. So, rather than return a generic file status, this COBOL system returns an extended file status of 9/007. When using ANSI'74 or ANSI'85 file status codes, the run-time system returns extended status codes if the extended file status is more specific than what would normally be returned. Unless otherwise specified, each file status code can be received for operations on any file organizations in any access mode. 15.1 List of Messages '74 '85 Meaning 00 00 Successful completion 02 02 Indexed files only. One of two possibilities: For a READ statement, the key value for the current key is equal to the value of that same key in the next record in the current key of reference. For a WRITE or REWRITE statement, the record just written created a duplicate key value for at least one alternate record key for which duplicates are allowed. 00 04 The length of
code starting with a "2" is considered to be an "invalid key" condition. 85 74 Vax DG IBM Condition 00 00 00 00 00 Operation successful. 02 02 00 00 00 The
Cics Error Codes
current key of reference in the record just read is duplicated in the next db2 error codes record. (read next) 02 02 02 00 00 The operation added a duplicate key to the file where duplicates were allowed. (write, visual basic error codes rewrite) 05 00 05 00 10 Optional file missing. If the open mode is I-O or EXTEND, then the file has been created. This is also returned by DELETE FILE if the file is not found. (open, https://supportline.microfocus.com/documentation/books/sx20books/fhscod.htm delete file) 07 00 07 00 00 A CLOSE UNIT/REEL statement was executed for a file on a non-reel medium. The operation is successful. 0M 0M 0M 0M 00 The operation was successful, but some optional feature was not used. For example, if you opened a file that specified an alternate collating sequence, but the host file system did not support that feature, then the open would succeed, but it would return this status. https://supportline.microfocus.com/Documentation/AcucorpProducts/docs/v6_online_doc/runtime/run63.htm 10 10 13 10 10 End of file. (read next) 14 00 14 00 00 A sequential READ statement was attempted for a relative file, and the number of digits in the relative record number is larger than the size of the relative key data item. (read next) 21 21 21 21 21 Primary key was written out of sequence, or the primary key on a rewrite does not match the last record read. This error occurs only for an indexed file open with the sequential access mode. (write, rewrite) 22 22 22 22 22 Duplicate key found but not allowed. (write, rewrite) 23 23 23 23 23 Record not found. 24 24 24 24 24 Disk full for relative or indexed file. (write) 24, 01 00 24, 01 00 24 A sequential WRITE statement was executed for a relative file, and the number of digits in the relative record number was larger than the size of the relative key data item. (write) 30, xx 30, xx 30, xx 30, xx 30 Permanent error. This is any error not otherwise described. The secondary code value is set to the host system's status value that caused the error. See your operating system user manual for an explanation, and C$RERR in Appendix I. 34 34 34 34 34 Disk full fo
PowerBSORT. Although these error codes are similar to the appendix "I-O Status List" of the "NetCOBOL User's Guide", there are differences and these codes are not returned in the FILE STATUS item.TableC.1 COBOL file system runtime error codesCode(Hexadecimal Number)ExplanationProgrammer http://software.fujitsu.com/jp/manual/manualfiles/m140007/b1wd3305/01enz200/b3305-c-00-00.html ResponseHighLow10Requested to make an entry after the end of a file or before the beginning of a file.Check whether the number of input character items are correct.21An error was found in the order of a primary key.Correct the program so that the key values are written in ascending order, or so that the record key values read by the preceding READ statement are not changed.22A new record key was duplicated in a error codes file in which the duplicate keys are not allowed.Correct the program so that the key is not duplicated.23The specified record does not exist.Change the logic so that no attempt is made to operate on a record that does not exist.24Insufficient disk space.Add more disk space and try again.2401The record number specified for writing a relative record file was invalid (zero).Specify a value for the relative record number.2402Writing a record caused the maximum file cobol error codes size to be exceeded.Split the file so that the file does not exceed the maximum file size.3001 mm nn02 mm nnThe COBOL file system encountered an operating system error.Correct the error returned from OS specified in nn mm.3001 01Memory acquisition failed.Increase the available memory or virtual memory (swap).3003 0ANo single record exists.Store at least one record.3004 0AMore files than accepted exist.Contact NetCOBOL Support. (*)3005 0AHandle name error.Contact NetCOBOL Support. (*)35A file with the specified file name does not exist.Confirm if the specified file name or path name exists.37Access was mismatched against the file property.Contact NetCOBOL Support. (*)3707Issued an open output or I-O instruction against a read-only file.Confirm the file attribute.38Cannot open a file closed with a lock.Do not operate on a file after it is closed with a lock.39Cannot open a file because of a mismatch of file properties.The file property specified in a parameter or option must match with that of the physical file.3901Mismatched file organization.The file organization specified in a parameter or option must match with that of the physical file. 3902Mismatched minimum record length.The minimum record length specified in a parameter or option must match with that of the physical file.3903Mismatched maximum record length.The maximum record length specified in a parameter or option must match with that of the physical file.3904Mismatched minimum block leng