OSI/AS Configuration and Management Manual

Troubleshooting Guide
OSI/AS Configuration and Management Manual—424119-001
8-12
API Troubleshooting Example
The Inspect command
L5HALFO-d local_appl_1.zappl^name
displays the following:
The next step is to call APS_STATUS_ to find out why the operation failed. After the
following typical line of code
error := APS_STATUS_( cepi_1
, event_code
, device_name
, error_code
, error_subcode
, service_id
, diagnostic_buffer
, original_error_info
, transport_state
, transport_substate
);
the Inspect command
L5HALFO-d service_id
displays the following:
This screen tells you that the service ID is 1 (ZAPS-VAL-SERVICE-APS), and that the
error is returned by the API. Since the error is returned by the API, you need to find out
the type of error.
The Inspect command
L5HALFO-d error_code
displays the following:
In this case, the error returned is -126 (ZAPS-ERR-MGR-ERROR). This means that the
API failed to establish a connection because the OSI manager process detected an error.
The type of error is ZAPS-ERR-MGR subcode.
ZAPPL^NAME=
ZLEN= 6
ZC=
BYTE[0]= "LOCALZ"
SERVICE_ID= 1
ERROR_CODE= -126