NonStop NS-Series Operations Guide (H06.12+)

Table 9-2 Additional Processor Dump Information for Your Service Provider (continued)
__________________________________________The processor numbers of the processors that were
dumped, along with the letter designation of the PEs
dumped.
__________________________________________The date that the processor dump was done
__________________________________________The RVU you are using
You should also provide:
A list of any software product revisions (SPRs) you have installed since installing the RVU.
A list of any customer-written privileged programs running on your system and explanations
of what they do.
The reason for the processor dump. If you performed a processor dump because a processor
halted, include the halt code and the frequency of the halts. The halt code and other
information is displayed in the Processor Status dialog box of the OSM Low-Level Link.
Any particular circumstances that you think contributed to the problem. A brief description
of the problem in an EDIT file and a short program that duplicates or illustrates the problem
(if possible) would be helpful.
Any OSM status messages reported.
Related Reading
For more information about tools used to monitor and perform recovery operations on processors,
refer to the documentation listed in the following table.
Table 9-3 Related Reading for Monitoring and Recovery Operations on Processors
SeeToolFor Information About
Guardian User’s Guide
TACL Reference Manual
TACLRecovery operations for processes
OSM online help
OSM Service Connection User’s Guide
OSMMonitoring or recovery operations on
processors
Replace Blade Element Procedure
(Available in the OSM Service
Connection, accessed by performing
the Blade Element Replace action.)
Usually requires service providerReplacing a memory unit
ViewSys User’s GuideViewSysMonitoring processor performance
Tandem Failure Data System (TFDS)
Manual
TFDSRecovery operations for processor
halt
120 Processors and Components: Monitoring and Recovery