OSI/AS Configuration and Management Manual

Troubleshooting Guide
OSI/AS Configuration and Management Manual—424119-001
8-11
API Troubleshooting Example
The following steps are used to solve this problem:
•
Step 1: Reset the Statistics Counters and Rerun the Application on this page
•
Step 2: Analyze the Application Using Inspect on this page
•
Step 3: Review the Statistics Using SCF on page 8-13
•
Step 4: Correct the Problem on page 8-14
•
Step 5: Return to the Inspect Session Log on page 8-14
Step 1: Reset the Statistics Counters and Rerun the Application
Reset all the statistics counters. (See Command File for Resetting Statistics Counters on
page 8-68.)
Rerun the application. This ensures that the statistics screens are as free from irrelevant
information as possible, and makes it easier to identify information pertaining to the
particular problem you are trying to diagnose.
Step 2: Analyze the Application Using Inspect
When troubleshooting problems at this level, you should look at your application code
using Inspect. The following are entries from the Inspect log, along with explanatory
comments:
The application posts a session attach, using an application name LOCALZ. After the
following typical line of code
status := APS_ASSOC_ATTACH_ ( cepi_1,
, api_environment
, local_appl_1
);
the Inspect command
L5HALFO-d status
displays the following:
This screen tells you that the return status is 2 (ZAPS-VAL-STATUS-NO-RETRY); the
operation failed.
The Inspect command
L5HALFO-d api_environment.zend^system^name
displays the following:
STATUS= 2
ZEND^SYSTEM^NAME=
ZC=
BYTE[0]= "$OMGR"