OSI/FTAM Programming Reference Manual

NonStop FTAM Initiator Error Messages
HP NonStop OSI/FTAM Programming Reference Manual528611-001
B-12
APS Error Codes
-124
Cause. You specified an invalid APLMGR process name in a call to the
FTM_INITIALIZE_REQ_ procedure, or that the process specified is not an APLMGR
process of the correct version.
Subcodes. None.
Recovery. Specify a valid APLMGR process name.
-125
Cause. The FTAM API encountered a file-system error while communicating with the
APLMGR process. This error indicates that the connect sequence has failed.
Subcodes. The error subcode specifies the file-system error encountered. For
descriptions of file-system errors, refer to the Guardian Procedure Errors and
Messages Manual.
Recovery. Check the subcode to discover the precise error, and correct as indicated.
-126
Cause. The FTAM API has failed to establish an association because the APLMGR
process detected an error.
Subcodes. If APLMGR returns a positive subcode, the error is an APLMGR error.
Table B-3
lists the error subcodes that APLMGR returns if it detects an error when you
use the FTM_INITIALIZE_REQ_ procedure to establish an association. If a negative
subcode is returned, the error is a communications management error; for descriptions
of communications management errors, refer to the Communications Management
Programming Manual.
ZAPS-ERR-BAD-MGR
ZAPS-ERR-MGR-FS-ERROR
ZAPS-ERR-MGR-ERROR
Table B-3. APLMGR Subcodes (page1of2)
Constant
(ZFTM-ERR-MGR-) Value Meaning
BOUNDS-ERR 7000 Bounds error- internal error
SUBTYPE-BAD 7001 Bad subtype - internal error
REGREQ-TBL 7002 Register-request table - internal error
ASE-FS-ERR 7003 FTAM file-system error