OSI/MHS Configuration and Management Manual

Troubleshooting Your OSI/MHS Subsystem
OSI/MHS Configuration and Management Manual—424827-003
9-66
Problem Example
*Numeric-user-ID.. *
*Common-name...... *
*Terminal-type.... *
*Org-Name......... MTA1
*Org-Unit-1....... MSUSERS
*Org-Unit-2....... *
*Org-Unit-3....... *
*Org-Unit-4....... *
*Sur-name......... UAMS19
*Given-name....... *
*Initials......... *
*Generation....... *
*Dom-Type-1....... *
*Dom-Value-1...... *
*Dom-Type-2....... *
*Dom-Value-2...... *
*Dom-Type-3....... *
*Dom-Value-3...... *
*Dom-Type-4....... *
*Dom-Value-4...... *
...
If all O/R attributes are correct, then the problem is a password mismatch. The
following commands reset the password to the expected value and start the trace
again:
-> stop appl $zk1.#uams19
-> alter appl $zk1.#uams19,user-password UAMS11
-> start appl $zk1.#uams19
-> trace process
$zk1.#ok11,select(mhsencode,mhsdecode,mhsdpduman,mhsepduman,&
-> mhsrts),recsize 600, to trok11a
-> trace process $zk1.#ok11,stop
After asking the user to try logging on again, check the statistics counters. The display
shows that an association is now open, so you can stop the trace.
-> stats process $zk1.#ok11
MHS stats PROCESS RS \CS7.$OK11:
Reset-time........ 15 Dec 1994, 16:12:56.269
Sample-time....... 15 Dec 1994, 16:40:31.820
CPU............... 2 Protocol-errors... 0
Msgs-sent......... 1 Msg-bytes-sent.... 0
Msgs-received..... 1 Msg-bytes-received 0
Inc-assocs-open... 1 Inc-assocs-closed. 1
Inc-assocs-rej.... 1
-> log
-> ==
-> == Stop the trace
-> ==
-> trace process $zk1.#ok11,stop
-> log