OSI/AS Configuration and Management Manual

Troubleshooting Guide
OSI/AS Configuration and Management Manual—424119-001
8-9
Concentrate on the Layer Exhibiting the Problem
If your application receives errors from the API, you can assume that the error is
occurring between the TAPS process and the API. If the error reported is a connection
error (for example, error 140), then you would check the Transport Layer to see if it
returned an error. If the Transport Layer also reports an error, then you would check for
errors in the subordinate Network Layer, and so on, until you eventually arrive at the
original source of the error.
As with many data communications problems, you will find that most of your problems
can be tracked to your initial OSI/AS configuration, regardless of what layer you are
starting from. Using the CHECK ENTRY command can help you verify your
configuration. Once you've overcome the difficulties of the initial setup stages, you'll
find that adding OSI processes, entries, and profiles is relatively easy. You can overcome
almost all OSI errors either by changing your configuration or by changing the sequence
of the APS procedure calls in your application.
Concentrate on the Layer Exhibiting the Problem
It is very important to know what an application was trying to do when a problem
occurred. Was the application trying to establish a connection, or waiting for an
incoming connection request? Was the application trying to send data or respond to the
session protocol, or was the application receiving an incoming message? Did the
application request that a connection be released, or did a connection release request
come from the remote partner or from the OSI network? Knowing the answers to these
questions helps you understand the cause of a problem.
In this section, problem-solving information for each of the major interfaces is broken
down into the following categories:
•
Using SCF commands to analyze symptoms
•
Using PTrace to scan and analyze traces
•
A working example
Application Program Interface (API)
The API is the interface between an application and the TAPS process. When
troubleshooting API problems, you can generally get useful information from the error
codes and subcodes returned from the APS procedure calls.
SCF Commands
Errors in APS procedure calls often can be diagnosed by looking at the statistics. The
following command returns statistics information on the OSI manager process $OMGR:
STATS SUBSYS $OMGR
The statistics screen returned shows that the OSI manager process received 13 register
requests, and that all 13 requests were successfully processed by the OSI manager
process: