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:
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:
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.