Problem:
Could you tell me where I can locate the descriptions of the error codes that contain the special characters, as above?
Resolution:
When you get a file status returned and the first character is a "9" it means that the second character is actual a binary value representing a run-time error and these are called extended file status codes.
If you look in the Help under Extended file status you will find an example:
Example of Extended File Status Codes
The example code that follows illustrates how to redefine a standard file status so that it can be used as an extended file status. Assume for this example that the input file does not exist - when the OPEN INPUT statement is executed, a file status of 9/013 ("file not found") is returned.
select in-file
assign to "user.dat".
file status is file-status.
...
working-storage section.
01 file-status.
05 status-key-1 pic x.
05 status-key-2 pic x.
05 status-key-2-binary redefines status-key-2 pic 99 comp-x.
...
procedure division.
open input in-file
if file-status not = "00"
if status-key-1 = "9"
if status-key-2-binary = 13
display "File not found"
...
If you want to display the extended file status code, you need to move the second byte of the file status data item to a display field large enough to hold the maximum value 255:
select in-file
assign to "user.dat"
file status is file-status.
...
working-storage section.
01 ans74-file-status.
05 status-key-1 pic x.
05 status-key-2 pic x.
05 status-key-2-binary redefines status-key-2 pic 99 comp-x.
01 display-ext-status
05 filler pic xx value "9/"
05 display-key 2 pic 999
...
procedure division.
open input in-file
if file-status not = "00"
display "Error. File status =" with no advancing
if status-key-1 = "9"
move status-key-2-binary to display-key-2
display display-ext-status
else
display file-status
end-if
---------------------------------------------------------------------------
or you could look in an ASCII character chart to see what the decimal value of the character displayed is.
In this case an A with a ^ on it is equal to decimal 194.
If you then look in the Net Express Help under Reference->Error Messages->Run-time System errors you will see a page with links to the various run-time errors.
If you click on 194 you will see the following:
COBRT194 File size too large (Fatal)
A file which your program is accessing is too large for successful execution to continue.
Resolution:
When your program has terminated you should recode your program spreading the data over more than one file to ensure that no file becomes too large for your operating system to handle. Having recoded your program you can then rerun it.
--------------------------------------------------------------
This means that the file you are trying to create is too large.
If you look in the Net Express Help under Programming->File Handling->Reference-->Limits you will see the size limits for various file types.
Under sequential files you will see the following:
Sequential and Relative File Size Limits
The following file size limits affect sequential (including line sequential) and relative files:
Exclusive Shared FILEMAXSIZE set to
4 Gb 1 Gb 4
8 MTb 4 MTb 8
where FILEMAXSIZE is a File Handler configuration file setting that defaults to 4.
------------------------------------
This tells me that the FILEMAXSIZE option is either set to 4 explicitly or implicitly by default.
In order to create a sequential file > 4gb you will have to add the FILEMAXSIZE=8 option to the extfh.cfg file.
