Αποτελέσματα Αναζήτησης
COBOL FILE STATUS CODES: File status Codes beginning with a '0' are considered Successful Execution. Codes beginning with a '1' are considered "At End" messages, those beginning with a '2' are considered "Invalid Key" messages, File Status Codes beginning with a '3' are considered "Permanent Errors", keys like '4x' are "Logical Errors" and '9x ...
Invalid or incomplete file information (1) Duplicate keys specified in COBOL program. The file has been successfully opened, but indexed database file created with unique key; or (2) Duplicate keys not specified in COBOL program, and indexed database file created allowing duplicate keys.
COBOL file status codes provide information about the result of each file operation executed. They're mainly useful for error handling, giving programmers a straightforward way to identify issues with file operations.
RM/COBOL file status codes are either ANSI'74 file status codes or can be mapped onto extended file status codes, as shown below. The first table of RM/COBOL file status codes is for DOS, Windows and OS/2, the second for UNIX.
If the key you're doing the START on has a larger value than any key in the VSAM file, you will get a 23 file status code. Adding a higher-valued key (such as HIGH-VALUES or all 9's) puts a record in the file with a key value higher than what you do the START on, and VSAM will return this record.
15 Απρ 2015 · The reason I'm stumped is that I'm using a START to navigate to the record inside of my .DAT file, and when I execute a READ just after the START has positioned my file pointer, I get the file status 23. Here is my code: 900-GET-INST-ID. OPEN INPUT INST-MST. MOVE FALL-IN-INST TO INST-NAME-REC.
23 Indicates no record found. An attempt has been made to access a record, identified by a key, and that record does not exist in the file. Alternatively a START or READ operation has been tried on an optional input file that is not present. 24
