OSI/AS Configuration and Management Manual

Troubleshooting Guide
OSI/AS Configuration and Management Manual—424119-001
8-31
Troubleshooting Example
The following PTrace commands set up the trace filters:
filter l5prov
filter l5user
The PTrace command
find "Attach"
displays the following:
This screen shows that record #47 of the trace is the API request from the user's
application to the TAPS process. The addresses all seem to match, and the subdevice
was correctly added by the OSI manager process.
Note that PTrace FIND commands are case-sensitive; you might want to include
lowercase and uppercase options for your search string.
Pressing the N key, for “next” (or using the F1, F2, F3, and so on, function keys)
continues the search and displays the following:
This screen shows that record #63 of the trace is the conclusion of the
APS_ASSOC_ATTACH_ primitive, with no error reported.
10/16/91 13:39:14:430 >000.000 #47 TAPS L5 USER
L5 Request Su Name #Z00000P Session ID 14
Request Addr %H000A36E8 Request Tag %H0001F8D4
Request Code -32767 (Attach Req)
local^addr:
zappl^name.zlen = 6 zappl^name.zc =
000: 4C4F 4341 4C58 LOCALX
zpsap.zssel.zlen = 3 zpsap.zssel.zc =
000: 5555 0100 UU.
zpsap.ztsel.zlen = 5 zpsap.ztsel.zc =
000: 4444 4444 0100 DDDD.
zpsap.znsap.zlen = 6 zpsap.znsap.zc =
000: 4083 3311 1101 @.3...
filename = \249.TSP1 #Z00000P
10/16/91 13:39:14:480 >000.050 #63 TAPS L5 USER
L5 Reply Su Name #Z00000P Session ID 14
Reply Addr %H000A36E8 Request Tag %H0001F8D4
Status Code = ZAPS^Val^Status^Ok (0)
Error = ZAPS^Err^Ok(0), Error Subcode = (0).