Compaq OSI/APLMGR D43, OSI/FTAM D43 manual 5026, 5027, Table A-9. Access Contexts by Document Typ

Compaq FTAM Responder Diagnostic Messages Access-Related Diagnostic Messages

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 request with the correct FADU operation. Make sure the document type opened supports the access context. Refer to Table A-9 for valid access contexts.

Table A-9. Access Contexts by Document Typ

Document	Access
Type	Context
FTAM-2	FA, UA
FTAM-1,	UA
FTAM-3,
and NBS-9

5026

Bad write (unspecific)

Cause. A local file-system error other than an end-of-file message has occurred on the write service.

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 retry the application. If the error persists, the file is probably corrupt and cannot be accessed. In this case, the Compaq problem solver should perform the file recovery operations normally used at the site; then the application or FTAM user can retry the application.

5027

Bad read (unspecific)

Cause. A local file-system error other than an end-of-file message has occurred on the read service. One possible cause of this error is that one of the records in an FTAM-3 file with a string-significance value of fixed contained a string whose length was smaller than the maximum-string-length value. This could occur because the file was created outside FTAM, because it was corrupted in some way, or because the wrong file was specified.

Effect. The responder cancels the service.

Recovery. The application or FTAM user should issue a cancel response. The application or FTAM user should ensure that the correct file is specified; the file must satisfy the string-length rules described under “Maximum-String-Length Checking of Data Values” in Section 4. If the application specified the correct file, the application or FTAM user should retry the application; if the error persists, the file is probably corrupt and cannot be accessed. In this case, the Compaq problem solver should perform the

OSI/FTAM Responder Manual—425199-001

A-22