Chapter 24 DMP (TFDS) Messages

Cause  TFDS received a CPU DOWN message, and the AUTODUMP flag is set to OFF.

Effect  A dump is not generated. The processor status for TFDS is CPU DOWN, NO DUMP.

Recovery  Either force the dump through TFDSCOM (set the AUTODUMP flag to ON and use the ANALYZE command) or reload the processor manually.

	NOTE: Leaving the AUTODUMP flag set to ON on completion of the ANALYZE command enables TFDS to automatically initiate a dump the next time it receives a CPU DOWN message. Exceptions: Neither setting the AUTODUMP flag to ON nor using the ANALYZE command generates a dump if TFDS determines that the cause of the CPU DOWN message is a recurrence of an incident already known to the TFDS incidents database. You can override this default and force a dump by using the INCIDENT DUMPOVERRIDE command (for one specific occurrence) or setting the DUMPOVERRIDE configuration parameter to ON (for all future occurrences).

Cause  TFDS generated a dump for a downed processor, and the AUTORELOAD flag is set to OFF.

Effect  An automatic reload is not enabled. The processor remains down, pending operator intervention.

Recovery  Generate a manual request of the RELOAD command, not a TFDSCOM command. It usually takes the form: RELOAD n, PRIME.

Cause  TFDS started a backup operation, but the tape drive is not ready.

Effect  The dump files cannot be saved on tape. The backup is waiting for a device.

Recovery  Mount a tape (on the tape drive specified through the TFDSCOM TAPE command) and put the tape drive online, or issue a CANCELBACKUP command.

Cause  The backup operation requires more tapes.

Effect  The backup is waiting for the next tape.

Recovery  Mount a tape and put the tape drive online.

Cause  A new incident was stored in the Incident Database.

Effect  A new register was stored in the incident table. The affected processors are dumped and reloaded automatically.

Recovery  Informational message only; no corrective action is needed.

Cause  An incident has already been defined in the database.

Effect  The number of occurrences is tabulated. The affected processors are dumped and reloaded automatically.

Recovery  Informational message only; no corrective action is needed.

Cause  Either a dump was requested through TFDSCOM or a CPU DOWN message arrived.

Effect  A dump is started by RCVDUMP. (Dumping a processor can take several minutes and can slow system performance during this time.) TFDS attempts to automatically reload the processor and get a processor dump according to your RETRY‑DUMP, RELOAD-ON-FAILURE, AUTORELOAD, AUTODUMP and RETRY-RELOAD configuration settings.

Recovery  Informational message only; no corrective action is needed.

Cause  A reload process has been started.

Effect  If followed by TFDS event message #10, Successful RELOAD, the processor is operational. If not, TFDS continues attempts to reload the processor according to your RETRY-RELOAD configuration setting.

Recovery  Informational message only; no corrective action is needed.

Cause  The RCVDUMP ended successfully.

Effect  A dump file was created.

Recovery  Informational message only; no corrective action is needed.

Cause  The reload process ended successfully.

Effect   The processor is operational.

Recovery  Informational message only; no corrective action is needed.

Cause   Not enough disk space is available on the specified volume, and TFDS has not been configured to search for and use an alternate volume. (Both the default volume and alternate volume capability are specified with the TFDSCOM DUMPVOLUME command.)

Effect  A dump file is not created. TFDS retries the dump, as specified by the RETRY-DUMP configuration setting. The RELOAD-ON-FAILURE option of the RETRY-DUMP command determines whether TFDS automatically reloads the processor after exhausting the specified number of retries, or the processor remains down (which allows you to find disk space and request the dump through TFDSCOM).

Recovery   If the RELOAD-ON-FAILURE option described previously has not been specified, you can enable more disk space and request the dump through TFDSCOM, or reload the processor manually.

Cause  The reload process failed.

Effect  The processor is down. TFDS continues attempts to reload the processor according to your RETRY-RELOAD configuration setting.

Recovery  If TFDS fails to automatically reload the processor, perform the reload manually.

Cause  TFDS has been started.

Effect  TFDS is starting up.

Recovery  Informational message only; no corrective action is needed.

Cause  A new incident is stored in the Incident Database.

Effect  Data collection is not performed on this problem again. The affected processors are dumped and reloaded automatically.

Recovery  Informational message only; no corrective action is needed.

Cause  A recurrent problem was discovered.

Effect  Data collection is not performed on this problem, and the number of occurrences of this problem is tabulated. The affected processors are reloaded automatically.

Recovery  Informational message only; no corrective action is needed.

Cause  A RCVDUMP process that TFDS started failed to finish.

Effect  A new RCVDUMP process is started. TFDS continues attempts to get a successful dump according to your RETRY-DUMP configuration settings.

Recovery  Informational message only; no corrective action is needed.

Cause  A reload process that TFDS started failed to finish.

Effect  A new reload process is started. TFDS continues attempts to reload the processor according to your RETRY-RELOAD configuration setting.

Recovery  If TFDS fails to automatically reload the processor after the retries specified by RETRY-RELOAD, the processor remains down until it is manually reloaded.

Cause  The number of processor failures is greater than the number of concurrent dumps allowed by the current TFDSCOM MAXCONDUMPS configuration setting.

Effect  A reload process is started for the specified processor. It is not dumped. If the reload is successful, the processor is operational.

Recovery  Informational message only; no corrective action is needed.

Cause  Internal error was detected in TFDS.

Effect  The effect depends on the error that occurred. In general, this message does not indicate a problem for your system.

Recovery  Report this message to your service provider and provide all relevant information:

If your local operating procedures require contacting your service provider, supply your system number and the numbers and product versions of all related products as well.

Cause  An error was detected in the TFDS configuration file during TFDS initialization. The line number and specific error are displayed.

Effect  A default value is assigned to the configuration option not properly specified.

Recovery  Use the TFDSCOM CONFIG command to view the TFDS configuration file, and use TFDSCOM commands to edit the TFDS configuration file as needed.

Cause  A noncritical error occurred during TFDS processing. For example, if a RELOAD command is issued while TFDS is analyzing a halted processor, an error results.

Effect  Normally, TFDS terminates incident processing at the point the error is encountered.

Recovery  Determine the cause of the error and correct it.

Cause  This message indicates routine TFDS operational status.

Effect  You can view these messages in the event log to determine the current status of TFDS (or use the TFDSCOM HISTORY command).

Recovery  Informational message only; no corrective action is needed.

Cause  A RCVDUMP process started by TFDS has returned a routine status message.

Effect  To determine the current status of the dump, view these messages in the EMS event log.

Recovery  Informational message only; no corrective action is needed.

Cause  A RELOAD process started by TFDS has returned a message.

Effect  To determine the current status of the reload, view these messages in the EMS event log.

Recovery  Informational message only; no corrective action is needed.

Cause  TFDS is in the process of duplicating files for a incident.

Effect  To determine the current status of this process, view these messages in the event log.

Recovery  Informational message only; no corrective action is needed.

Cause  A TFDS STOP command was received from TFDSCOM.

Effect  TFDS terminates.

Recovery  Informational message only; no corrective action is needed.

Cause  TFDS sent a status message related to the PRDUMP process that it started.

Effect  To determine the current status of the processor dump, view the status messages in the EMS log.

Recovery  Informational message only; no corrective action is needed.

Cause  TFDS sent a status message related to the DUMPUTIL process that it started.

Effect  To determine the current status of the DUMPUTIL, view the status messages in the EMS log.

Recovery   Informational message only; no corrective action is needed.

Cause  Reserved for future use.

Effect  N.A.

Recovery  Informational message only; no corrective action is needed.

Cause  As TFDS starts, it reads the configuration file and communicates with the Non-stop Kernel to determine information about the hardware environment.

Effect  To determine the current status of the TFDS configuration, view these messages in the EMS log.

Recovery   Informational message only; no corrective action is needed.

Cause  TFDS sent a status message related to the Garth process that it started.

Effect  To determine the current status of the Garth process, view the status messages in the EMS log.

Recovery  Informational message only; no corrective action is needed.

Cause  TFDS sent an error message related to the Garth process that it started.

Effect  To determine the current status of the Garth process, view the status messages in the EMS log.

Recovery  Informational message only; no corrective action is needed.

Cause  A TFDS Helper process has started.

Effect  The TFDS Helper process starts.

Recovery  Informational message only; no corrective action is needed.

Cause  The TFDS Helper process is stopping.

Effect  The TFDS Helper process stops.

Recovery  If the TFDS Helper process is not restarted automatically in the same processor, start this process manually. See the Tandem Failure Data System (TFDS) Manual for more information.

Cause  Failure incident processing was interrupted.

Effect  Failure incident processing resumes when the TFDS Helper process is restarted.

Recovery  Informational message only; no corrective action is needed.

Cause  The TFDS Helper process was unable to purge a snapshot file because it found one already in existence where it needed to create a new one.

Effect  The snapshot file is unneeded by TFDS. It is now wasting disk space, and its presence on the system can cause confusion.

Recovery  Check whether or not the file security caused the problem. Check whether or not someone has the file open and close it if necessary. Purge the snapshot file manually.

Cause  The TFDS Helper process was unable to pass control to the Visual Inspect Snapshot Server (INSPSNAP).

Effect  An Inspect Snapshot file is not captured. All other processing for this incident should proceed normally.

Recovery  Ensure that the INSPSNAP program is running in each processor.

Cause  The version of the TFDS Helper process is older than the version of the trigger interface.

Effect  The TFDS Helper will nevertheless handle the call from the Client using the common set of interface parameters.

Recovery  Install the latest versions of TFDS, TFDSHLP and TFDSCOM.

Cause  The TFDS Helper does not recognize data in the trigger interface. This may be due to a new TFDS client being run on a system with an older version of TFDSHLP, or it can be caused by an improperly written client.

Effect  Failure incident processing is interrupted.

Recovery  Ensure that the proper version of TFDSHLP is installed. Contact your service provider to report that the program file has called TFDS improperly.

Cause  The TFDS Helper process has determined that the version of the TFDS Monitor is not compatible with the version of the TFDS Helper.

Effect  TFDSHLP sends this message directly to $ZLOG. Rediscovery is not performed and this incident is not recorded in the TFDS database.

Recovery  Check for version inconsistencies between the TFDS Monitor and the TFDS Helper. Reinstall TFDS if necessary.

Cause  The TFDS Helper process has determined that the version of TFDSCOM is not compatible with the version of the TFDS Helper.

Effect  TFDSHLP will not respond to commands issued from TFDSCOM. Incident processing will continue as normal.

Recovery  Check for version inconsistencies between the TFDS Helper and TFDSCOM. Reinstall TFDS if necessary.

Cause  The TFDS Helper process was unable to send an EMS message to the TFDS Monitor.

Effect  TFDSHLP sends this message directly to $ZLOG. Rediscovery is not performed and this incident is not recorded in the TFDS database.

Recovery  Ensure that $ZDMP is running.

Cause  Tracing has been turned on for the TFDS Helper.

Effect  TFDS Helper process tracing begins.

Recovery  Informational message only; no corrective action is needed.

Cause  Tracing of the TFDS Helper process has been turned off.

Effect  TFDS Helper process tracing stops.

Recovery  Informational message only; no corrective action is needed.

Cause  The level of tracing for the TFDS Helper process has been changed.

Effect  Tracing continues at the new trace level.

Recovery  Informational message only; no corrective action is needed.

Cause  The TFDS Helper process has determined that the specified trace file name is too long for a Guardian file name.

Effect  The TFDS Helper process trace attempt fails.

Recovery  Restart the trace and specify a valid Guardian file name for the trace file. Note that TFDSHLP appends the processor number as the last two characters of the specified file name, so the trace file name you specify must not exceed six characters in length.

Cause  The TFDS Helper process has encountered an error when it attempted to open the indicated trace file.

Effect  The TFDS Helper process trace attempt fails.

Recovery  Check whether or not the specified file already exists on the system. Restart the trace and specify a different Guardian file name for the trace file.

Cause  The TFDS Helper process has determined that the specified trace file name is not a valid Guardian file name.

Effect  The TFDS Helper process trace attempt fails.

Recovery  Restart the trace and specify a valid Guardian file name for the trace file. Note that TFDSHLP appends the processor number as the last two characters of the specified file name, so the trace file name you specify must not exceed six characters in length.

Cause  An incorrectly formatted trace command was specified.

Effect  Tracing does not start.

Recovery  Use the TFDSCOM TRACEHELPER command to start tracing.

Cause  The TFDS Helper process encountered an unexpected internal error.

Effect  The TFDS Helper process continues to execute if the error is recoverable, or it stops if the error is unrecoverable.

Recovery  If the TFDS Helper process is not restarted automatically in the same processor, start this process manually. See Tandem Failure Data System (TFDS) Manual for more information.

Cause  The TFDS Helper process was unable to save the snapshot file to the requested location.

Effect  The snapshot file is saved to the indicated location instead.

Recovery  Informational message only; no corrective action is needed.

Cause  The TFDS Helper process encountered an error from the Visual Inspect snapshot server.

Effect  The snapshot file is not saved but other failure incident data processing is performed.

Recovery  Informational message only; no corrective action is needed.

Cause  The TFDS Helper process approached a time-out threshold waiting for an action to complete.

Effect  The TFDS Helper process continues waiting for a response.

Recovery  Informational message only; no corrective action is needed.

Cause  The TFDS Helper process encountered time-outs twice while waiting for an action to complete.

Effect  TFDSHLP sends the EMS message directly to $ZLOG and finishes processing the incident. The incident may not be recorded in the TFDS Incident Database.

Recovery  Informational message only; no corrective action is needed.

Cause  The TFDS Helper process did not receive a completion indication from the Visual Inspect Snapshot Server (INSPSNAP) within the required period of time.

Effect  The TFDS Helper process continues to wait for a response from the INSPSNAP. The TFDS client process remains in a debug state until INSPSNAP completes.

Recovery  If you need to free the TFDS client, stop the INSPSNAP process in the CPU where the client is running. (This causes the session to be given back to the TFDS Helper process so that the incident can complete its processing.)

Cause  An internal error occurred in TFDS.

Effect  The effect depends on the error that occurred. In general, this message does not indicate a problem for your system.

Recovery  Report this message to your service provider and provide all relevant information as follows:

If your local operating procedures require contacting your service provider, supply your system number and the numbers and product versions of all related products as well.

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
           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 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.

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
           bit 4 = TFDS_PROCESS_STOP
           bit 3 = TFDS_PROCESS_CONTINUE
           bit 2 = TFDS_CAPTURE_ALL
           bit 1 = TFDS_CAPTURE_STACK_TRACE - unused - always get stack trace
           bit 0 = TFDS_CAPTURE_SELECTIVE 

Cause  For G-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.

Cause  TFDS issues this event to document the analysis of an internal software error within the NonStop system. TFDS could generate this event through use of the TFDSCOM ANALYZE command or by any NSK subsystem instrumented with the TFDS APIs, triggering a TFDS instrument with a severity of INFORMATIVE.

Effect  Depends on the specific problem and severity.

Recovery  Informational message only; no corrective action is needed.