TFDS Manual

EMS Messages and Templates
Tandem Failure Data System (TFDS) Manual—520628-003
D-11
EMS Messages
•
Descriptions of the problem and accompanying symptoms
•
Details from the message or messages generated
•
Supporting documentation such as Event Management Service (EMS) logs, trace
files, and a processor dump, if applicable
If your local operating procedures require contacting the Global Customer Support
Center (GCSC), supply your system number and the numbers and product versions of
all related products as well.
6000
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:
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
bit 4 = TFDS_PROCESS_STOP
bit 3 = TFDS_PROCESS_CONTINUE
bit 2 = TFDS_CAPTURE_ALL
Software Data Capture *6000* : Company Name,
Product Tnnnn,
Program Name, File name xxxxxxxx, DIPID nn,
Severity n, VPROC xxxxxxxx,
Stack Trace
xxxxxxxx
xxxxxxxx
xxxxxxxx