OSI/FTAM Programming Reference Manual

NonStop FTAM Initiator Error Messages
HP NonStop OSI/FTAM Programming Reference Manual—528611-001
B-14
APS Error Codes
-129
Cause. You set a time limit of 0D when calling APS_EVENT_RECEIVE_, but no event
was received.
Subcodes. None.
Recovery. Continue with other processing.
-131
Cause. No association exists.
Subcodes. None.
Recovery. Call APS_DISCARD_ to discard the association context and release the
CEPI. Then call FTM_INITIALIZE_REQ_ to reinitiate the association.
-134
Cause. The FTAM initiator process has reported a file-system error in communicating
with the TAPS process. The current operation fails.
Subcodes. The subcode indicates the file-system error. For descriptions of the
file-system errors, refer to the Guardian Procedure Errors and Messages Manual.
Recovery. Recovery depends on the subcode received.
-135
Cause. A request failed because no operation was pending on the association. This
error can be returned under these conditions:
•
The application called APS_EVENT_RECEIVE_, MFM_AWAITIOX_, or an FTM
confirm or indication procedure out of sequence. For example, the application
might call MFM_AWAITIOX_ to wait for completion of an I/O operation, but no I/O
operation is pending.
•
The application called MFM_CANCEL_REQ_ to cancel an operation that no longer
exists.
Subcodes. None.
ZAPS-ERR-NO-EVENT
ZAPS-ERR-NO-CONNECTION
ZAPS-ERR-TAPS-FS-ERROR
ZAPS-ERR-NONE-PENDING