OSI/FTAM Programming Reference Manual

NonStop FTAM Initiator Error Messages
HP NonStop OSI/FTAM Programming Reference Manual—528611-001
B-15
APS Error Codes
Recovery. Check the calling sequence used in your application. If you have issued an
APS_EVENT_RECEIVE_, for example, make sure that you have first called the
desired FTM request or response procedure that will cause a confirm or indication. If
you have issued an MFM_AWAITIOX_ call, you should have first issued the
appropriate FTM request or response nowaited procedure and that procedure should
have returned a status value of ZAPS-VAL-STATUS-OK (0). Before calling an FTM
confirm or indication procedure to map the desired information into your application,
you must first call APS_EVENT_RECEIVE_ to receive the confirm or indication and
APS_STATUS_ to determine the type of event.
-136
Cause. One or more mandatory parameters were missing. This code corresponds to
file-system error 29 (missing parameter). This error might be returned during program
debugging but is unlikely to be returned during program run time.
Subcodes. For FTM-procedure parameters, see Table B-4 on page B-16, and for
APS-procedure parameters, see the OSI/AS Programming Manual.
Recovery. Add the missing parameter(s) to your procedure call, rebuild the
application, and then retry the operation.
-137
Cause. Either the parameter that the application passed to an FTM procedure call did
not address the runtime data (or stack) space reserved for the parameters of that
procedure, or an internal error occurred when the FTAM initiator passed a value to the
OSI/AS API. This code corresponds to file-system error 22 (application parameter out
of bounds).
Subcodes. For FTM-procedure parameters, see Table B-4 on page B-16, and for
APS-procedure parameters, the OSI/AS Programming Manual.
Recovery. Correct your use of parameters, rebuild the application, and then retry the
operation.
ZAPS-ERR-PARAM-MISSING
ZAPS-ERR-PARAM-BOUNDS