OSI/AS Configuration and Management Manual

Troubleshooting Guide
OSI/AS Configuration and Management Manual—424119-001
8-33
Troubleshooting Example
Step 6: Correct the Problem
Now that you know what the problem is, you need to correct it. Since the local SSEL
fields don't match, you need to reconfigure so they do match.
Use the INFO ENTRY #APPL command to check on the application entry LOCALX.
The SCF command
info entry $omgr.#appl.localx
displays the following:
This screen shows the SSEL identifier as 555501. However, from trace record #147, you
know that the identifier requested by the CN-SPDU (the called SSEL) is 555503. One of
these SSEL identifiers must be corrected. In this example, the APPL ENTRY object
needs to be corrected. Therefore, you need to change the SSEL field in the
#APPL.LOCALX entry, using the following SCF command:
alter entry $omgr.#appl.localx, ssel 555503
Now, perhaps, the TAPS process will accept the connect request. You might take another
trace to check it. First stop the application and then start the trace using the SCF
command:
trace process $tap1, to tracefil, recsize 1000, pages 64
Retry the connection from the remote application, and then stop the trace using the SCF
command:
trace process $tap1,stop
Use PTrace to analyze the trace. This time you need to look only at the SPDUs, filtering
for Layer 5 L5PROV CONNECT. The SCF command
ptrace from tracefil
OSIAS Info ENTRY \MARS.$OMGR.#APPL.LOCALX
*AEQualifier.......
*APTitle...........
*PSEL..............
*SSEL.............. 555501
*TSEL.............. 4444444401
*NSAP.............. 408333111101
*Loopback.......... OFF
*Deletetime........ -1 (static SU)
*L5Profile......... \MARS.$OSIM.#L5.prof5
*L4Profile......... \MARS.$OSIM.#L4.prof4
*L3Profile......... \MARS.$OSIM.#L3.prof3
*L5Server.......... \MARS.$OSIM.#TAPS.TAPS1
*L4Server.......... \MARS.$OSIM.#TSP.TSP1
*L3Server.......... \MARS.$OSIM.#NSP.x25a