OSI/AS Configuration and Management Manual

Troubleshooting Guide
OSI/AS Configuration and Management Manual—424119-001
8-16
TAPS Process
And now for one last check; the Inspect command
L5HALFO-d service_id
displays the following:
The service ID of 5 (ZAPS-VAL-SERVICE-SESSION) now fully verifies that TAPS is
configured for session service. (This is the default value resulting from the previous
APS_ASSOC_ATTACH_ call.)
TAPS Process
The TAPS process accepts primitives from the API, interacts with the OSI manager
process to create subdevices, and provides Session Layer, Presentation Layer, and ACSE
connections with remote peer entities. This discussion is focused primarily on the
Session Layer connections. (Troubleshooting Presentation Layer and ACSE connections
is similar to troubleshooting Session Layer connections.)
Events can be returned to TAPS as indication primitives or confirm primitives. In
addition, errors can be returned as status completions, such as error 140. Some of the
errors to particularly watch for are frequent occurrences of the following:
•
Connection refused indication primitives
•
Provider exception report indication primitives
•
Resynchronize indication primitives
SCF Commands
You can get a good idea of the quality of a session entity by using the STATS, STATUS,
and CHECK SU commands. The following command returns a good, overall look at the
session service provider for the TAPS process $TAP1:
STATS SERVICE $TAP1.#L5
The screen returned in this example shows that two abort SPDUs were sent, out of a
total of 100:
SERVICE_ID= 5