Cobol I/o Error 90 05
Contents |
Errores de salida (00 - 99) Martes, 17 de Enero de 2012 17:20 administrador Output Errors Input/output errors include all errors that can occur during file access. The format is as follows: COBOL I/O error number on cobol error codes COBOL-fllename f i le file-access-name The numerically ordered list presentes below shows the values cobol error codes mainframe that can appear as number in the 110 error messages, and a description of each error. The list is presentes in file error codes in cobol numerical order. The 110 error number has the form: mm, nn mm is a two-digit decimal number indicating the general class of error that occurred. lt is also the value stored into the file
Cobol Db2 Error Codes
status data ¡tem if such an ¡tem has been specified for the associated file. Thus, this value is available to the program. nn is a two-digit code that provides more specific information on the nature of the error. This value is available to the program only if you call the subprograrn C$RERR (describes in the discussion that begins on page F-22). When the 1/0 error is 30, the file status 90 in cobol 110 error number has the form: 30, OS error nnnnn OS is the operating system that generated the error and indicates how the nnnnn code should be interpretad. nnnnn is the operating system error code that was retumed when the error occurred. This value is available to the program only if you call the subprogram C$RERR (describes in the discussion that begins on page F-22). The phrase " 1 985 mode" indicates that the error message description applies oral to ANSI COBOL 1985. The phrase "1974 mode" indicates that the ertor message description applies only to ANSI COBOL 1974. Messages not marked with either phrase indicate that the description applies to both ANSI COBOL 1985 and 1974. Number Description O0 The operation was successful. O2 The operation was successful but a duplicate key was detected. For a READ statement, the key value for the current key of reference is equal to the value of that same key in the next logical record within the current key of reference. For a REWRITE or "ITE statement, the record just written created a duplicate key value for at least one altemate record key for which duplicates are allowed. 04,05 The record read from the file is sho
otherwise specified, each file status code can be received for operations on any file organizations in any access mode. The ANSI'74, ANSI'85 and Extended File Status codes microfocus cobol file status codes are given in your Error Messages. The following sections contain the RM/COBOL file
Cobol Abend Codes
status codes and the Microsoft V2 file status codes. In addition to the above file status conventions you can produce
File Status 90 In Cobol While Writing
more detailed extended file status codes. Extended file status codes have the following format: 9/nnn where nnn is a binary (COMP-X) number, equivalent to a run-time error number. Run-time errors are documented in http://interdata.d2g.com/index.php/component/content/article/45-recursos-cobol/52-errores-de-salida-00-99 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 available" error message. That error message is very general; a "permanent error" could mean that the disk has failed, or that the disk https://supportline.microfocus.com/documentation/books/sx20books/fhscod.htm 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 the record being processed does not conform to the fixed file attributes for that file. 00 05 The referenced optional file is not present at the time the OPEN statement is executed. 00 07 Sequential files only. For an OPEN or CLOSE statement with the REEL/UN
Low Order Digit Meaning 0 Successful Completion 0 Nofurther information 2 The READ statement was successfully executed, but a duplicate key was detected. That http://publib.boulder.ibm.com/iseries/v5r1/ic2924/books/c0925392642.htm is, the key value for the current key of reference was equal to the value of the key in the next record. For information about enabling file status 02 see the http://www.simotime.com/vsmfsk01.htm accompanying notes under the READ statement. 4 An attempt was made to read a record that is larger than the largest, or smaller than the smallest record allowed by the error codes RECORD IS VARYING clause of the associated file-name. 5 An OPEN statement is successfully executed, but the referenced optional file is not present at the time the OPEN statement is executed. If the open mode is I-O or EXTEND, the file has been created. CPF4101, CPF4102, CPF4103, CPF4207, CPF9812. 7 For a CLOSE statement with the NO REWIND, REEL/UNIT, or FOR REMOVAL cobol error codes phrase or for an OPEN statement with the NO REWIND phrase, the referenced file was on a non-reel/unit medium. A Job ended in a controlled manner by CL command ENDJOB, PWRDWNSYS, ENDSYS, or ENDSBS CPF4741. Escape message sent during an accept input operation, READ from invited program device (multiple device listings only). M Last record written to a subfile. CPF5003 P The file has been opened successfully, but it contains null-capable fields and the ASSIGN clause does not specify ALWNULL and device-type DATABASE. Q A CLOSE statement for a sequentially-processed relative file was successfully executed. The file was created with the *INZDLT and *NOMAX options, so its boundary has been set to the number of records written. 1 At end conditions 0 A sequential READ statement was attempted and no next logical record existed in the file because the end of the file had been reached (no invites outstanding) CPF4740, CPF5001, CPF5025. 2 +-------------------------------IBM Extension--------------------------------+ No modified subfile record found. CPF5037+----------------------------End of IBM Extension----------------------------+ 4 A sequential READ statement was attempted for a relative file and the number of significant digits
040-28 065-41 070-46 081-51 090-5A 100-64 124-7C 135-87 141-8D 150-96 161-A1 173-AD 180-B4 193-C1 210-D2 Summary Software Agreement and Disclaimer Downloads & Links Current Server or Internet Access Internet Access Required Glossary of Terms Comments or Feedback Company Overview Quick Link or Search Assembler Language CICS Information COBOL Language Java, JSP and Beans JCL Job Control Numbers Formating Relational Data Base Non-Relational Data An Enterprise System Model ASCII/EBCDIC Tables Data Management Series File Status Codes File Transfer Protocol (FTP) SIMOPATH Learn/Reference Glossary of Terms Home Page Help Desk for Simotime Introduction This document provides a summary of the two-byte File-Status-Key (sometimes referred to as file return code or file status code) with a brief narrative for each code. For the COBOL environment if the FILE STATUS clause is specified in the FILE-CONTROL entry, a value is placed in the specified status key (the 2-character data item named in the FILE STATUS clause) during execution of any request on that file. The value indicates the status of that request. The value is placed in the status key before execution of any EXCEPTION/ERROR declarative or INVALID KEY/AT END phrase associated with the request. The following tables contain file-status-key content that may be set by Micro Focus COBOL (Mainframe Express or Net Express) or an IBM Mainframe System (MVS, OS/390 or ZOS). We have made a significant effort to ensure the documents and software technologies are correct and accurate. We reserve the right to make changes without notice at any time. The function delivered in this version is based upon the enhancement requests from a specific group of users. The intent is to provide changes as the need arises and in a timeframe that is dependent upon the availability of resources. Copyright © 1987-2016SimoTime TechnologiesAll Rights Reserved File Status Key Overview The ANS/85 standard provides for a two-byte File-Status-Key. The first character of the File-Status-Key is known as status-key-1 and defines a group or category. The second character is known as status-key-2 additional