OSI/AS Configuration and Management Manual

Troubleshooting Guide
OSI/AS Configuration and Management Manual—424119-001
8-50
Troubleshooting Example
The SCF command
INFO PROFILE $OMGR.#L4.PROF1,DETAIL
displays the following:
Finally, you can clearly see the problem. The SENDSECURITY is set to include the
string password when sending CR-TPDUs, but the RECVSECURITY is set to validate
incoming CR-TPDUs for the string password.
The following SCF command changes the password in the profile:
ALTER PROFILE $OMGR.#L4.PROF1, RECVSECURITY "password"
Now the TSP process should accept the connect request. You might take another trace to
check it out. First stop the application and then start the trace using the SCF command:
TRACE PROCESS $TSP2, TO TR1
While the trace is on, rerun the application. You can see that the session connection is
successful.
Stop the trace. The following SCF command stops the trace:
TRACE PROCESS $TSP2, STOP
Use PTrace to analyze the trace. This time you only need to look at the TPDUs, filtering
for Layer 4.
The SCF command
PTrace FROM TR4; SELECT L4
displays the following:
OSIAS Detailed Info PROFILE \MARS.$OMGR.#L4.PROF1
*AltClass ........ 2 *Checksum.......... ON
*Class............ 2 *ConnectTimeout.... 0:02:00.00
*DisconnTimeout... 0:02:00.00
*Expedited........ OFF *ExtendedFormat.... OFF
*InactiveTimeout.. 0:00:30.00 *L4Window.......... 4
*MaxRexmit........ 3 *Multiplex......... ON
*NetType.......... B
*RecvSecurity..... PASSWART
*RefTimeout....... 0:01:40.00
*RexmitTimeout.... 0:00:10.00
*SendSecurity..... PASSWORD
*TConPri.......... 0 *TPDUSize......... 512
*TTRTimeout....... 0:01:30.00 *TWRTimeout....... 0:02:00.00
*WindowTimeout.... 0:00:10.00
Trace of: \MARS.$TSP2, Type (55,4).
Ptrace Data File: $OSI.DIAG.TR4
Trace started: 10/16/91 04:38:29.23
First trace entry: 10/16/91 04:38:29.24
Last trace entry: 10/16/91 18:04:22.72
Trace entry size limit: 520