OSI/FTAM Programming Reference Manual

NonStop FTAM Initiator Error Messages
HP NonStop OSI/FTAM Programming Reference Manual—528611-001
B-8
APS Error Codes
-107
Cause. Cause. Your application attempted to invoke a primitive that was not valid in
the current state.
Subcodes. The possible subcodes are ZAPS-ERR-SM-BAD-STATE and ZAPS-ERR-
SM-BAD-EVENT. For more information, see the OSI/AS Programming Manual.
Recovery. Check your application’s calling sequence against the situation you are
encountering. For example, an abort might have occurred, the responding system
might have gone down, you might have opened a file in an unknown state, and so on.
If the calling sequence is incorrect for the situation—for example, the application is still
issuing requests although either the NonStop initiator or remote responder has
aborted—adjust your sequence of procedures to the encountered situation.
If the calling sequence is correct for the situation, trace the initiator and TAPS
processes and follow the standard procedures at your site for contacting the
appropriate support personnel. These procedures might involve contacting your local
HP support analyst.
-108
Cause. The operation you tried to initiate is not supported or not available. For
example, you could have called an FTM confirm or indication procedure that does not
correspond to the primitive that you received. The call is ignored.
Subcodes. None.
Recovery. Recovery. Check your application calling sequence for errors.
-109
Cause. The FTAM API does not recognize the CEPI you have specified. This causes
the procedure you have called to fail.
Subcodes. None.
Recovery. Recall the procedure using the correct CEPI.
ZAPS-ERR-STATE-MACHINE
ZAPS-ERR-INVALID-OPERATION
ZAPS-ERR-UNKNOWN-CEPI