OSI/AS Configuration and Management Manual

Troubleshooting Guide
OSI/AS Configuration and Management Manual—424119-001
8-21
Troubleshooting Example
Troubleshooting Example
The following is a Session Layer TAPS process problem that you may encounter. The
steps in this example illustrate the logic you might follow when using a top-down
problem-solving approach. (Problems in the Presentation Layer and ACSE are
diagnosed and corrected in a similar manner.)
Symptoms
The application is waiting to accept a session connection. Connect requests are coming
into the subsystem, but for some reason the application continues to wait in
APS_EVENT_RECEIVE_ (the call does not complete). There are no errors returned,
either to the application or to the console log.
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-23
•
Step 4: Collect Trace Information Using SCF on page 8-30
•
Step 5: Analyze the Trace Using PTrace on page 8-30
•
Step 6: Correct the Problem on page 8-33
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
The first call to APS_ASSOC_ATTACH_ readies the TAPS process to accept the
session connection. Before the following typical line of code
ret := aps_assoc_attach_ ( cepi1, env, local1 );
the Inspect command
display LOCAL1.ZAPPL^NAME.ZC in ascii for 6
displays the following:
LOCAL1.ZAPPL^NAME.ZC = "LOCALX"