|
Dieses Gerät hat auch andere Anweisungen:
Anleitung Zusammenfassung
EMS Messages and Templates
EMS Messages
bit 1 = TFDS_CAPTURE_STACK_TRACE - unused - always get stack trace
bit 0 = TFDS_CAPTURE_SELECTIVE
Cause. For D-series RVUs, TFDS and the TFDS run-time library issue this event to
notify you about an internal software error within the NonStop system. TFDS could
generate this event as a result of a halted processor or any NonStop Kernel subsystem
instrumented with the TFDS run-time library. The event detail should specify the actual
program that caused the event to be generated.
Effect. Depends on the specific problem and severity. This event is dialed out to your
service provider if the system is so configured.
Recovery. Determine the cause of the failure and take appropriate action.
6001
Software Error *6001* : Incident Symptom String,
Severity n,
Tnnnn, Product Name, File Name, Error Location
In addition to this event message, you can choose Event Detail in event viewers such
as WebViewPoint to get more information. This example includes the Event Detail
fields and an explanation of what the fields represent:
TFDS-Symptom-String - collection representing Company, Tnumber, Process,
source code filename, and Instrument ID number - used
for incident rediscovery.
halt example - Tandem?.NA.TSYSDP2.NA.011705
instrumented subsystem example - Tandem.T8336.FFDC_RD.XXXTESTC.00002
Incident-Filename - program name and location that triggered the incident.
Severity - problem severity as assigned by the developer.
CPU - processor that incident occurred in.
Code-VPROC - only available for instrumented subsystems.
Stack-trace - stack trace extracted from failing program.
Dump-Filename - saveabend or cpudump filename and location (if a dump
was instigated).
DB Incident Record # - record # of incident in TFDS incident Database
(see TFDSCOM report and detail commands).
Additional-text-1: Vproc of the TFDS that processed the incident.
Additional-text-2: TFDS Configuration data at the time of the incident:
BDONR/00000 AS3 ASH24 ARD1 RD2 MCD1 RR2 TNS D45T6523 G05_12JAN2000_TFDS
where BDONR = state of the autoBackup, autoDump, Override, remoteNotify,
and autoReload flags at the time of the incident
AS = AutoStifle time, ASH = AutoStifle Hours
RD = Reload Delay, MCD = Max Concurrent Dumps, RR = Reload Retrys
TNS = Tandem Non Stop Base OS version, and the TFDS Vproc.
Additional-text-5: Garth or Crunch metrics - ie for development use only.
Text: General Usage
relays data about previous duplicate incidents:
Dup incident of #21, 00/01/12 10:14
information indicating that this could be a rediscovery or reanalyze:
REANALYZE of CPU OR CPUDUMP - POSSIBLE DUP
AND for INSTRUMENTED Subsystem calls:
data about 'TFDS not Running' at the time the incident was encountered
Options: are the action parameters specified by the programmer
%B00001000 bit positions numbered 76543210 from left to right
bit 7 = TFDS_VD_BYPASS
bit 6 = TFDS_CPU_HALT - currently unused
bit 5 = TFDS_PROCESS_ABEND
Tandem Failure Data System (TFDS) Manual — 520628-003
D -12
...Dieses Handbuch ist für folgende Modelle:
PC Desktops - HP NonStop L-Series (329.83 kb)