OSI/AS Programming Manual

Error Codes
Status and Error Codes
B–14 056783 Tandem Computers Incorporated
-124: ZAPS-ERR-BAD-MGR
Cause. You specified an invalid name in the ZEND-SYSTEM-NAME field of
the API environment parameter in a call to APS_ASSOC_ CONNECTREQ_ or
APS_ASSOC_ATTACH_. The process specified is not an OSI manager process
of the correct version.
Subcodes. None.
Effect. The requested operation is not performed.
Recovery. Specify a valid OSI manager process name.
-125: ZAPS-ERR-MGR-FS-ERROR
Cause. The API encountered a file-system error while communicating with an OSI
manager process. For descriptions of the file-system errors, refer to the System
Procedure Errors and Messages Manual. This error indicates that the connect sequence
has failed.
Subcodes. The error subcode specifies the file-system error encountered.
Effect. The affected call is ignored.
Recovery. Normally, no recovery is possible. Check the subcode to determine the
precise error.
-126: ZAPS-ERR-MGR-ERROR
Cause. The API has failed to establish a connection because the OSI manager process
detected an error.
Subcodes. See Table B-9 and the discussion following that table. Note that the errors
listed in Table B-9 are subsystem programmatic interface (SPI) error codes and
therefore are not in the usual negative range for API error codes or subcodes. If a
negative subcode is returned, it is a communications management error; for
descriptions of communications management errors, refer to the Communications
Management Programming Manual.
Effect. The requested operation is not performed.
Recovery. Depends upon the subcode received.