OSI/MHS Configuration and Management Manual

ManualsBrandsHP ManualsServerHP NonStop G-Series

341

342

343

344

345

346

347

348

349

350

Troubleshooting Your OSI/MHS Subsystem

OSI/MHS Configuration and Management Manual—424827-003

9-59

Problem Example

This subsection provides an example of LO and RS process interface problems. The

method used to identify the problem includes:

1. Using SCF to display RS or LO process statistics

2. Using SCF to trace RS or LO process actions

3. Using PTrace to display the results of the SCF trace

This method is useful primarily if accounting events are disabled or if the events do not

completely explain the problem. In general, it is useful to turn on accounting events as

soon as you notice a problem in the STATS PROCESS display; information in the

event messages can help you decide how to search the trace records.

The example refers to the RS process in the subsystem whose statistics are listed

below; the RS process statistics are highlighted in boldface. The most important

statistics counters to monitor are Inc-assoc-rej and Protocol-errors. Any increase in

these counters indicates that a problem has occurred. (Note that the counts of

messages sent and received are counts of protocol messages, not X.400 messages.

For complete descriptions of the fields in these displays, see the OSI/MHS SCF

Reference Manual.)

-> stats process $zk1.*

MHS stats PROCESS MS \CS7.$IK11:

Reset-time........ 15 Dec 1994, 15:35:17.683

Sample-time....... 15 Dec 1994, 15:54:52.510

CPU............... 0

MTA-delivered..... 0 MTA-reports....... 0

UAs-logged-on..... 0 UAs-logged-off.... 0

UA-cancel......... 0 UA-delete......... 0

UA-fetch.......... 0 UA-list........... 0

UA-submitted...... 0 UA-probes......... 0

UA-summary........ 0

MHS stats PROCESS MS \CS7.$IK21:

Reset-time........ 15 Dec 1994, 15:35:17.780

Sample-time....... 15 Dec 1994, 15:54:52.603

CPU............... 1