Compaq OSI/FTAM D43, OSI/APLMGR D43 manual 5001, 5003, 5004

Compaq FTAM Responder Diagnostic Messages Access-Related Diagnostic Messages

5001

Bad FADU - size error

Cause. The application or FTAM user tried to access a nonexistent column in an SQL table.

Effect. The responder cancels the service, and the association is left in a data-transfer idle state.

Recovery. The application or FTAM user should issue a cancel response and then reissue the request, verifying that the number of data elements in the FADU sent is less than or equal to the number of columns in the table.

5003

Bad FADU - poorly specified

Cause. The responder has received an erase request for an FTAM-2 document type and the FADU-ID parameter was not begin, or in the case of an FTAM-1 or FTAM-3 document type, the FADU-ID parameter was not first. The responder can also return this diagnostic message if an invalid data type was specified for the data to be written to an SQL table, or if an attempt was made to write to an SQL table using the UA access context instead of the FA access context.

Effect. The responder cancels the service, the association is left in the file-open regime, and the file is left in an unknown state.

Recovery. The application or FTAM user should issue a cancel response, close the file, and reissue the erase request with the valid FADU ID.

5004

Bad FADU - bad location

Cause. The responder has received a read or write request with an invalid FADU-ID parameter. The responder returns this diagnostic message when the application or FTAM user attempts to access an empty file or locate a FADU corresponding to a record before the beginning or after the end of the file; or when, while reading a file, the responder receives an unexpected end-of-file message (specific to SQL tables and Enscribe relative files). The responder can also generate this diagnostic message if it receives an SQL error of -5 or if, while attempting to locate the current position in the file, it receives a file-system error.

Effect. The responder cancels the service, and the association is left in a data-transfer idle state.

Recovery. The application or FTAM user should issue a cancel response, and then reissue the read or write request with a valid FADU ID.

OSI/FTAM Responder Manual—425199-001

A-19