Chapter 9: Error Handling

Fileshare error messages are listed in the chapter Fileshare Server Messages.

This chapter details:

Fileshare-specific causes of run-time status codes returned by the COBOL system
Communications errors generated by CCI
Transaction processing errors

9.1 COBOL Run-time Errors

Status Code	Meaning
9/037	Access is denied. In addition to the normal situations where this error occurs, Fileshare generates this error when: An invalid user-ID and/or password is passed to a Fileshare Server and Fileshare Password Security is active A Fileshare Client attempts to access a particular data file and access is denied See the chapter Security for more information.
9/100	A CLOSE operation is tried on a data file that is participating in an active transaction. See the section Transaction Processing in the chapter Database Integrity for more information.
9/124	A communications error occurred between the Fileshare Client and the Fileshare Server. You can call `fs_status` to determine the cause of the error. For details of this call see the section Communications Errors.
9/125	Caused by one of these conditions: A transaction or record lock timed out. (See the section Automatic Record Lock Timeout in the chapter Database Integrity.) The Fileshare Client has been forced to log off from the Fileshare Server If you are using the Micro Focus File Handler interface, an invalid Fileshare session ID was passed on the call to the File Handling Redirector module. Check that the six bytes of the FCD from offset 79 have not been changed. A previous access to this open file returned a 9/124 status, so further operations cannot be made
9/126	The record size used on the I/O operation is too large to be handled by the Fileshare Server. See the description of the `/m` option in the section Server Configuration in the chapter Configuration.
9/173	When using the virtual file interface, the program-name specified in the database reference file is not found. See the section Virtual File Handler Interface in the chapter Advanced Operation.

9.2 Communications Errors

Error status 9/124 on an I/O operation indicates that a communications error has occurred between the Fileshare Client and the Fileshare Server.

The most common time for error 9/124 to occur is on the very first I/O request that your program makes. It is then that the Fileshare Client tries to contact the Fileshare Server. If the Fileshare Client is unable to do this, it returns error 9/124. If you receive this error, examine the configuration of Fileshare and check that:

The Fileshare Server is started and operational
You have specified the correct Fileshare Server name. The name that you specify must exactly match the name specified when the Fileshare Server was started.
The Fileshare Client and Fileshare Server are configured to use the same CCI communications protocol
You have a working network connection between the Fileshare Client and the Fileshare Server and the correct network driver and software is loaded

Once you have made a successful connection and the Fileshare Server is servicing the request from the Fileshare Client, the request is visible if trace is active at the Fileshare Server. See the section Monitoring Fileshare in the chapter Advanced Operation for more information. Any further communications errors are returned to the program using the error code 9/124. This is a fatal error and the Fileshare Client drops the connection to the Server. To determine the cause of the error, call the entry point fs_status in the the File Handling Redirector module. The format of the call is:

call "fs_status" returning cci-status

where the parameter is defined as:

01 cci-status pic x(2) comp-x.

On return, cci-status contains the CCI error code returned to the File Handling Redirector module from the CCI module. For details of CCI error codes, please refer to your book, Configuring CCI.

You can make an additional call after error 9/124 to obtain an extended error message. This message is in the form of a text string that indicates a CCI-specific error as well as some additional information. The format of the call is:

call "fs_commserr" using by reference buffer
                         by value maxlen
                         by reference actual-len

where the parameters are defined as:

01 buffer     pic x(n).
01 maxlen     pic x(4) comp-5 value length of buffer.
01 actual-len pic x(4) comp-5.

On return, buffer contains the extended error message and actual-len contains the length of this message. The additional information in the returned message includes:

The date and time that the last error 9/124 was returned
Last return code from the CCI module (a 4-digit number)
Message code (for the File Handling Redirector module's internal use, a 2-digit number)
The CCI error message text

In addition, the File Handling Redirector module automatically logs communications errors in a local file called fhneterr.log. Each entry in the log file has the same format as the buffer returned from the fs_commserr call.

If you do not have a call to fs_commserr in your application, you can check this file for more detailed information following a 9/124 error.

This log file is not deleted by the Fileshare Client. You can, however, delete it if its contents are of no interest.

9.3 Transaction Processing Errors

The COMMIT and ROLLBACK operations work across many data files. You cannot check the file status of any one data file to see if the COMMIT or ROLLBACK operation was successful. Instead, call the entry point fs_status to determine the status of the COMMIT or ROLLBACK operation.

The format of the call is:

call "fs_status" returning t-status

where the parameter is defined as:

01 t-status pic x(2) comp-x.

A non-zero status indicates that the COMMIT or ROLLBACK operation failed. Fileshare cannot provide definitive information on transaction processing errors because of the complexity of multiple file transactions across networks.

Communications

Fileshare Server Messages