HP Tandem Failure Data System (TFDS) Manual Abstract This manual describes the HP Tandem Failure Data System (TFDS), including operating procedures, interface commands, messages, and automation of most tasks associated with failure data collection and resource recovery in the event of software, subsystem, or processor failure. Product Version TFDS H02 Supported Release Version Updates (RVUs) This manual supports J06.03 and all subsequent J-series RVUs and H06.
Document History Part Number Product Version Published 540122-001 TFDS H02 July 2005 540122-002 TFDS H02 November 2005 540122-003 TFDS H02 August 2010
Legal Notices © Copyright 2010 Hewlett-Packard Development Company L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
HP Tandem Failure Data System (TFDS) Manual Glossary Index Figures Tables Legal Notices What’s New in This Manual v Manual Information v New and Changed Information About This Manual vii Notation Conventions viii HP Encourages Your Comments v xi 1.
2. Managing and Configuring TFDS (continued) Contents 2. Managing and Configuring TFDS (continued) Default Configuration Settings 2-8 TFDS Configuration File Example 2-9 Viewing the Current TFDS Configuration Settings Changing the TFDS Configuration 2-12 TFDS Configuration-File-Only Commands 2-14 2-10 3. Using TFDSCOM Starting TFDSCOM 3-1 Using Online Help 3-1 TFDSCOM Commands 3-2 A. EMS Messages and Templates Overview of TFDS EMS Event Messages EMS Messages A-2 Templates for EMS Support A-18 A-1 B.
D. Best Practices (continued) Contents D. Best Practices (continued) Use Default Values for Key Attributes D-2 E. Troubleshooting Processor Was Not Dumped Automatically E-1 Processor Was Not Reloaded Automatically E-1 TFDS Process Execution Error E-1 Database Version Mismatch Error E-2 On Startup: E-2 When DB-SUBVOL Is Specified in TFDSCOM: Availability of TFDS During System Startup E-3 E-2 Glossary Index Figures Figure 1-1. TFDS Organization and Architecture 1-2 Tables Table 3-1.
Contents HP Tandem Failure Data System (TFDS) Manual—540122-003 iv
What’s New in This Manual Manual Information HP Tandem Failure Data System (TFDS) Manual Abstract This manual describes the HP Tandem Failure Data System (TFDS), including operating procedures, interface commands, messages, and automation of most tasks associated with failure data collection and resource recovery in the event of software, subsystem, or processor failure. Product Version TFDS H02 Supported Release Version Updates (RVUs) This manual supports J06.03 and all subsequent J-series RVUs and H06.
What’s New in This Manual Changes to the H06.03 Manual (540122-002 Edition) Changes to the H06.03 Manual (540122-002 Edition) • • • • Revised EMS Event Messages 6001 and 7000. Updated the SNAPSHOTTODUMP configuration command guidelines. Added new guidelines to the AUTORELOAD and BURSTNOTIFY commands. Updated the REPORT command sample output.
About This Manual TFDS, a component of the HP NonStop™ operating system, is a software isolation tool that automates most tasks associated with failure data collection and resource recovery in the event of software, subsystem or processor failure.
Notation Conventions About This Manual Notation Conventions Hypertext Links Blue underline is used to indicate a hypertext link within text. By clicking a passage of text with a blue underline, you are taken to the location described. For example: This requirement is described under Backup DAM Volumes and Physical Disk Drives on page 3-2. General Syntax Notation This list summarizes the notation conventions for syntax presentation in this manual. UPPERCASE LETTERS.
General Syntax Notation About This Manual { } Braces. A group of items enclosed in braces is a list from which you are required to choose one item. The items in the list can be arranged either vertically, with aligned braces on each side of the list, or horizontally, enclosed in a pair of braces and separated by vertical lines. For example: LISTOPENS PROCESS { $appl-mgr-name } { $process-name } ALLOWSU { ON | OFF } | Vertical Line.
Notation for Messages About This Manual Line Spacing. If the syntax of a command is too long to fit on a single line, each continuation line is indented three spaces and is separated from the preceding line by a blank line. This spacing distinguishes items in a continuation line from items in a vertical list of selections.
Change Bar Notation About This Manual { } Braces. A group of items enclosed in braces is a list of all possible items that can be displayed, of which one is actually displayed. The items in the list can be arranged either vertically, with aligned braces on each side of the list, or horizontally, enclosed in a pair of braces and separated by vertical lines.
About This Manual HP Encourages Your Comments HP Tandem Failure Data System (TFDS) Manual—540122-003 xii
1 Introduction to TFDS First Failure Data Capture (FFDC) is an industry wide concept for capturing information at the first instance of a particular failure, and avoiding redundant failure data collection and problem-solving efforts. Tandem Failure Data System (TFDS) is the implementation of FFDC on HP Integrity NonStop™ NS-series servers.
Key Features Introduction to TFDS Key Features • • • • • • • Responds to both hardware-based and software-based processor failures. Maintains a database of unique failure incidents. Captures information only for new, unique failure incidents. Avoids responding to repeated failure incidents. Reloads and dumps processors automatically. Collects key system files required for failure analysis. Forwards collected information to service providers.
Components Introduction to TFDS Components These key components are represented in Figure 1-1: Component Description (page 1 of 2) Client A program instrumented to report failures to TFDS Debug services The central broker for all debug events eGarth A program used for processor failure analysis EMS logs Files to which events are written by both applications and subsystems GCSC Global Customer Support Center, the HP support organization for HP NonStop customers Incident DB The TFDS incident da
Functionality Introduction to TFDS Component Description (page 2 of 2) Snapshot file An image of a process’s environment that contains all of the data, the stack trace, and register states at a given point in time Snapshot server A program that accepts requests from Debug Services to save Snapshot Files of a process under debug control. TFDSCONF A file containing TFDS configuration information that is read by the TFDS monitor at startup.
Responding to Processor Down Messages Introduction to TFDS DMR and TMR Processors In response to a Processor Down messages for a DMR or TMR processor, the TFDS monitor: 1. Reloads the affected processor, leaving one NSBE in the STOPPED state. 2. Takes a dump of the STOPPED NSBE. 3. Reintegrates the STOPPED NSBE into the processor. 4. Analyzes the dump to build a failure signature. 5. Determines whether the failure is unique or redundant: a.
Responding to Software Failure Reports Introduction to TFDS 1. Takes the dump and copies the dump file and various other files to a subvolume for further analysis by the support organization. (For more information, see Files Included in Failure Data Collection on page 1-7.) 2. Records the failure signature as a new incident record in the incident database. 3. Sends a software failure event to the Event Management Service. b.
Files Included in Failure Data Collection Introduction to TFDS Files Included in Failure Data Collection Failure incident numbers are used to create names for subvolumes to which files that might be helpful in resolving problems are copied. These subvolume names have the form ZDMPnnnn, where nnnn is the incident number. The set of files that is collected depends on the type of incident that has occurred and whether or not the incident is a rediscovery.
Installation Introduction to TFDS Installation TFDS is composed of two standard software products, T6523 (TFDS) and T6520 (TFDS Instrumentation). These products are delivered in every RVU, and occasionally between RVUs as software product revisions (SPRs). Both RVUs and SPRs are installed by DSM/SCM. (For more information, see the DSM/SCM User’s Guide and the H06.nn Software Installation and Upgrade Guide.) DSM/SCM installs these TFDS product components to $SYSTEM.
2 Managing and Configuring TFDS This section discusses managing and configuring TFDS, and presents these topics: • • • • Monitoring TFDS Activity on page 2-1 Managing TFDS Processes on page 2-4 Managing Disk Space Usage on page 2-6 Configuring TFDS on page 2-7 Monitoring TFDS Activity You should monitor TFDS activity for any indication of a failure in your system, including a processor halt.
Common Tasks Managing and Configuring TFDS Viewing Processor Status To view processor status and reload states, use the TFDSCOM STATUS command.
Managing and Configuring TFDS Common Tasks Viewing Processing History To view recent TFDS activity, use the TFDSCOM HISTORY command. For example: tfdscom> history 08Jun 13:47 Started at 08Jun2005 13:47:02 08Jun 13:47 Starting TFDS Primary in cpu 0 08Jun 13:47 Starting TFDS Backup in cpu 1 08Jun 13:47 config file \DRP09.$DATA.MPTST.tfdsconf opened 08Jun 13:47 Tape assigned is - config file needs to be saved 08Jun 13:47 Using Incident DB subvol '\DRP09.$DATA.
Managing and Configuring TFDS Managing TFDS Processes Managing TFDS Processes By default, both the TFDS monitor and TFDS helper processes start automatically whenever you start your system They are preconfigured in SCF under the Kernel subsystem ($zzkrn) and are managed by the Persistence Manager ($zpm). Occasionally you might need to stop and restart these processes manually, however (for example, when you are installing a new version of TFDS).
Managing and Configuring TFDS Starting TFDS Processes Manually Starting TFDS Processes Manually Starting the TFDS monitor Process To start the TFDS monitor process manually, use the SCF START PROCESS command: SCF 1> start process $zzkrn.#tfds Starting TFDS helper Processes To start the TFDS helper processes, use the SCF START command: SCF 1> start process $zzkrn.#tfdshlp Stopping TFDS Processes Manually To stop TFDS processes manually, you use the SCF ABORT command.
Managing and Configuring TFDS Managing Disk Space Usage Managing Disk Space Usage Due to the large amount of disk space required by incident files related to processor dumps, disk space utilization is an important consideration when you use TFDS: • • • An incident captured by the TFDS monitor might require incident files to be collected into a subvolume to be used by your service provider for failure analysis. (For more information, see Files Included in Failure Data Collection on page 1-7.
Managing and Configuring TFDS Configuring TFDS 3. The TFDS monitor considers other volumes on the system that are not present in the list of DISALLOWED-VOLUMES. If a virtual disk is found, space-checking is not performed, and the virtual disk is automatically selected. If a virtual disk is not found, the largest volume that has sufficient space for the incident files is selected. TFDS does not spread files from a single incident across disk volumes or subvolumes.
Default Configuration Settings Managing and Configuring TFDS Default Configuration Settings Configuration Attributes Default Settings (page 1 of 2) ACQUIREFILES (none) ALTERNATE-VOLUMES (none) ANALYZEPRIORITY One less than the priority of the TFDS monitor process AUTOBACKUP OFF AUTODUMP ON AUTOREINTEGRATE ON AUTORELOAD ON AUTOSTIFLE 03 times, 24 hours BACKUPDELAY 1 minute BURSTINTERVAL 336 hours BURSTNOTIFY 15 times, 7200 minutes BURSTSUPPRESSION ON DB-SUBVOL $SYSTEM.
TFDS Configuration File Example Managing and Configuring TFDS Configuration Attributes Default Settings (page 2 of 2) SNAPSHOTFROMDUMP ON TAPE (none) TRACE-FILE $SYSTEM.ZTFDS.TRACEFIL TFDS Configuration File Example This TFDS configuration file shows the default settings used when the file is created initially: ! TFDS config file updated 05/07/06 05:25 ! ACQUIREFILES $vol.subvol.
Viewing the Current TFDS Configuration Settings Managing and Configuring TFDS Viewing the Current TFDS Configuration Settings To view the current settings of the TFDS configuration attributes, use the TFDSCOM CONFIG command. (For additional information, see CONFIG on page 3-15).
Viewing the Current TFDS Configuration Settings Managing and Configuring TFDS CONFIG DETAIL Command Example You can view additional TFDS configuration options by specifying the DETAIL option in the CONFIG command: tfdscom> config detail TFDS current configuration detail: AnalyzePriority 145 BackupDelay 1 minutes DumpAllSlices OFF Garth-File \YOSQA23.$SYSTEM.SYS00.
Managing and Configuring TFDS Changing the TFDS Configuration Changing the TFDS Configuration Making Changes Interactively You can make changes interactively to the TFDS configuration by using these TFDSCOM commands: Note. You can make interactive configuration changes permanent with the TFDSCOM SAVE command. (See SAVE on page 3-34.) If you do not save changes you make interactively, they are lost the next time TFDS is restarted.
Managing and Configuring TFDS Changing the TFDS Configuration Editing the TFDS Configuration File You can make changes to your TFDS configuration by editing your TFDS configuration file, which is located in the TFDS execution subvolume (usually $SYSTEM.ZTFDS). Note. When you insert commands into the TFDS configuration file, the changes do not take effect until you stop and then restart TFDS.
Managing and Configuring TFDS TFDS Configuration-File-Only Commands TFDS Configuration-File-Only Commands This section describes those TFDS commands that are valid only in the TFDS configuration file. (TFDSCOM will not recognize these commands.) For a list of all TFDS commands that you can use in the TFDS configuration file, see Editing the TFDS Configuration File on page 2-13.
Managing and Configuring TFDS TFDS Configuration-File-Only Commands Guidelines • • • • • • A maximum of twenty symptom strings or program file names can be configured. Added symptom strings or program file names are displayed by the CONFIG DETAIL command. (For more information, see CONFIG on page 3-15.) The SEVERITY and SEVERITYLIMIT attributes are mutually exclusive. Specifying an asterisk (*) as progname establishes default values for all programs.
Managing and Configuring TFDS TFDS Configuration-File-Only Commands These examples show the addition of halt codes to the halt code list: ADD HaltCode %103472 ADD HaltRange %0102000 - %0102777 ALTERNATE-VOLUMES The ALTERNATE-VOLUMES specifies additional volumes to be used for incident files when DUMPVOLUME becomes full. The additional volumes are used only if the ALTERNATE VOLUMES ALLOWED option was specified in a DUMPVOLUME command. The volumes are used in the order specified.
Managing and Configuring TFDS TFDS Configuration-File-Only Commands Guideline $SYSTEM is automatically disallowed by TFDS. Example DISALLOWED-VOLUMES $KERBEY GARTH-FILE The GARTH-FILE command specifies the file that TFDS will use to run the GARTH process. GARTH-FILE filename filename specifies a Guardian file name. Guidelines • • This command is intended for use only by development or support groups or under their direction.
Managing and Configuring TFDS TFDS Configuration-File-Only Commands MAXWAITFORRELOAD The MAXWAITFORRELOAD command specifies how many seconds TFDS should wait for a processor reload to complete before proceeding with a dump. MAXWAITFORRELOAD seconds seconds specifies is the number of seconds to wait. The minimum value is 1 second. The maximum value is 1800 (30 minutes). The default value is 300 (5 minutes). Guidelines • • This command is intended for only by HP support personnel or at their request.
Managing and Configuring TFDS TFDS Configuration-File-Only Commands Examples OSMDELAY 300 SNAPSHOTFROMDUMP The SNAPSHOTFROMDUMP command creates a file from a snapshot of a process that has caused a processor halt. The snapshot file is — small far smaller than a processor dump — and its contents are easily dialed-out to a service provider for analysis. SNAPSHOTFROMDUMP { ON | OFF } ON instructs TFDS to create a snapshot file of the process that has caused the halt. The default value is ON.
Managing and Configuring TFDS TFDS Configuration-File-Only Commands HP Tandem Failure Data System (TFDS) Manual—540122-003 2- 20
3 Using TFDSCOM This section explains the TFDSCOM user interface and describes each of the TFDSCOM commands.
TFDSCOM Commands Using TFDSCOM TFDSCOM Commands Table 3-1.
TFDSCOM Commands Using TFDSCOM Table 3-1.
TFDSCOM Commands Using TFDSCOM ACQUIREFILES The ACQUIREFILES command instructs TFDS to include specific additional files (files not automatically copied) when collecting failure data, either on disk when the incident occurs or on tape when using the BACKUP program. (For more information, see Files Included in Failure Data Collection on page 1-7.) ACQUIREFILES filename [ TEMP | OFF ] filename specifies the additional file or files to include.
TFDSCOM Commands Using TFDSCOM • This example specifies a file ($ALPHA.TFDS.DMPDTAIL) to be included in the next failure data collection only: ACQUIREFILES $ALPHA.TFDS.DMPDTAIL TEMP • This example specifies all files in a volume ($ALPHA) and subvolume (BETA) that begin with TFD00 are always to be included when collecting failure data: ACQUIREFILES $ALPHA.BETA.TFD00* ANALYZE The ANALYZE command requests a processor dump when the processor is down.
TFDSCOM Commands Using TFDSCOM ANALYZEPRIORITY The ANALYZEPRIORITY command sets the process priority assigned to the program that will analyze a halted processor to determine if a processor dump should be initiated. (See AUTODUMP on page 3-7.) ANALYZEPRIORITY priority priority specifies a priority for the program that will analyze the halted processor. The minimum value is 1, the maximum value is 190, and the default value is one less than the priority of the TFDS monitor process.
TFDSCOM Commands Using TFDSCOM • If AUTOBACKUP is set to ON, TFDS backs up dump information to a specified tape drive (or one found to be suitable on your system if none is specified). For information about specifying a tape drive, see TAPE on page 3-37. Review your backup procedures to prevent TFDS from using a mounted tape that is not write protected or protected with labeled-tape software. • If the AUTOBACKUP is set to OFF, you can still back up the files with the BACKUP command.
TFDSCOM Commands Using TFDSCOM AUTOREINTEGRATE The AUTOREINTEGRATE command specifies whether or not TFDS reintegrates NSBEs automatically. AUTOREINTEGRATE { ON | OFF } ON instructs TFDS to reintegrate NSBEs automatically. This value is not related to the AUTODUMP value. If TFDS takes a dump or not, AUTOREINTEGRATE is verified by TFDS to determine if the NSBE should be reintegrated or not. The default AUTOREINTEGRATE setting is ON. OFF instructs TFDS to not reintegrate the NSBE automatically.
TFDSCOM Commands Using TFDSCOM Guidelines • • • • • You can use the abbreviation ar in place of AUTORELOAD. In an SMR processor, there is already a fixed time-out value of 45 seconds after a dump has been taken, but before the first attempt at reloading the processor. The larger of the TIMEOUT value specified in this command and the fixed time-out value of 45 seconds will be used. In DMR and TMR processors, the time-out is not used on the first reload attempt.
TFDSCOM Commands Using TFDSCOM dumping and reloading (for SMR processors) when the processors fail num-times within num-hours. • The AUTOSTIFLE setting remains in effect until a processor remains stable for num-hours, the TFDS monitor process is restarted, or a new AUTOSTIFLE command is issued (implicit reset).
TFDSCOM Commands Using TFDSCOM • • • The time directive supersedes the current default set by the BACKUPDELAY command. When performing a RESTORE operation (see the Backup and Restore 2.0 Manual), use the OPEN option. Failure to do so results in an error message because the incident database files are open at the time the backup is performed. When you specify an incident number, you initiate the backup of files related to the incident in the incident database.
TFDSCOM Commands Using TFDSCOM Example BACKUPDELAY 20 BURSTINTERVAL The BURSTINTERVAL command sets the number of hours that a rediscovery incident will be part of a burst. With BURSTSUPPRESSION enabled, no entry is created in the incident database, and no event is sent to the maintenance log ($ZLOG). BURSTINTERVAL hours hours is the number of hours a rediscovery incident will be part of a burst. The hour range is 0 through 600. The default value is 336 hours.
TFDSCOM Commands Using TFDSCOM Guidelines • • • You can use the abbreviation bn in place of BURSTNOTIFY. You must set BURSTSUPPRESSION to ON for BURSTNOTIFY to start. BURSTNOTIFY controls notification of processes that send redundant error information. Disabling this feature forces TFDS to add duplicate incidents to the incident database and issue an internal error event for each recurrent problem. HP does not recommend disabling this option.
TFDSCOM Commands Using TFDSCOM Example BURSTSUPPRESSION OFF CANCELBACKUP The CANCELBACKUP command cancels a specific backup request. CANCELBACKUP bkup-req bkup-req represents an active backup request number. (The backup request number is the same as the number of the incident record.) Guidelines • • You can use the abbreviation ca in place of CANCELBACKUP. Use the BACKUP STATUS command to determine the number of the active backup requests that you want to cancel.
TFDSCOM Commands Using TFDSCOM • You are not prompted for authorization to purge associated files of an incident, so use caution. Example CLOSE 101 CONFIG The CONFIG command displays the current TFDS configuration settings set as defaults in the TFDS configuration file or altered through TFDSCOM commands. If you save the configuration file, changes made to settings by TFDSCOM commands remain in effect after you stop and restart TFDS. CONFIG [DETAIL] Caution.
TFDSCOM Commands Using TFDSCOM EXCLUDEFILES TEMP option. These file names are cleared when the next dump is done or if TFDS is stopped. (For more information, see EXCLUDEFILES on page 3-21.) • Because you can change configuration file settings by using TFDSCOM commands and then saving the file, you are not required to use other means to edit the configuration file. If you edit the file and want to add notes to it, use the comment character (!).
TFDSCOM Commands Using TFDSCOM Example This example changes the location of the incident database to $DATA.TFDSDB: DB-SUBVOL $DATA.TFDSDB DETAIL The DETAIL command retrieves the specified detail record from the incident database. DETAIL rec-num rec-num is the record number in the incident database, obtained using the REPORT command. Guidelines • • You can use the abbreviation d in place of DETAIL. For information about the format of the detail record, see REPORT on page 3-31.
TFDSCOM Commands Using TFDSCOM Examples • This example disables dumping and reloading for processor 0: DISABLECPUS 0 • This example disables dumping and reloading for processor 1, 3 and 5: DISABLECPUS 1 3 5 • This example disables dumping and reloading for all processors in the system: DISABLECPUS ALL DUMPALLSLICES The DUMPALLSLICES command controls whether or not TFDS performs parallel dumping (reloading a processor before dumping it) for processor halt codes that have been specified by the ADD co
TFDSCOM Commands Using TFDSCOM DUMPOVERRIDE The DUMPOVERRIDE command instructs TFDS always to collect a processor dump after a processor has halted, overriding the normal TFDS operation that suppresses processor dumps for duplicate incidents. DUMPOVERRIDE { ON | OFF } ON instructs TFDS to collect a processor dump after a processor has halted. OFF instructs TFDS not to collect a processor dump after a processor has halted. The default DUMPOVERRIDE setting is OFF.
TFDSCOM Commands Using TFDSCOM ALTERNATE VOLUMES ALLOWED instructs TFDS to select another volume if the first one does not have the specified amount of free space. (TFDS looks to see if ALTERNATE-VOLUMES has any volumes specified. If alternate volumes are specified, the dump is taken on an alternate volume. If no alternate volumes are specified, TFDS selects the disk drive with the largest amount of free space and generates the dump.
TFDSCOM Commands Using TFDSCOM ENABLECPUS The ENABLECPUS command enables the dumping and reloading of specific processors if a Processor Down event occurs. ENABLECPUS { n [, n, ... ] | ALL } n specifies a valid processor number. Processor numbers range from 0 through 15. ALL specifies all processors. Caution.
TFDSCOM Commands Using TFDSCOM Guidelines • • • • You can use the abbreviation exc in place of EXCLUDEFILES. $SYSTEM.SYSnn.OSDIR contains a list of critical system fils. By default TFDS automatically collects all files listed in the OSDIR file. The excluded files list is lost when the TFDS monitor process ($ZDMP) is stopped unless you use the SAVE command to preserve it. When you use this command in a TFDS configuration file, the OFF and TEMP options are not valid and should not be used.
TFDSCOM Commands Using TFDSCOM The subcommand begins its operation at the character positioned directly above it. To stop editing the line, press Enter. Specify more than one subcommand on a line by separating each subcommand with a double slash (//). Example This example uses the FC command and the d and i subcommands to get help on the AUTOBACKUP command: TFDSCOM> fc TFDSCOM> HELP AUTODUMP tfdscom...........ddddiBACKUP TFDSCOM> HELP AUTOBACKUP tfdscom......
TFDSCOM Commands Using TFDSCOM HELP displays a list of all TFDS commands. HELP command displays a brief description of all TFDS commands. HELP command_name displays information for the specified command. You can also enter an abbreviation instead of the entire command name. HELP document displays detailed information for all TFDS commands. HELP events displays information for all TFDS events. HELP revisions displays the revision history of the TFDS products.
TFDSCOM Commands Using TFDSCOM Example Sample HISTORY output: 14Apr 09:23 14Apr 09:23 14Apr 09:23 14Apr 09:23 ********End Instrumented subsystem triggered TFDS instrument (17) No Saveabend Requested (17) --Closing Incident-(17) --Processing Completed for incident-of data******** HP Tandem Failure Data System (TFDS) Manual—540122-003 3- 25
TFDSCOM Commands Using TFDSCOM IGNORECPUS The IGNORECPUS command specifies that a processor be unavailable for processing Processor Down messages. IGNORECPUS [ OFF ] { 1 [ 2 3 ...n ] | [ ALL ] } OFF clears the status of IGNORECPUS for any processor from a previous IGNORECPUS command, making it available for processing Processor Down messages. n specifies the processors to be ignored by TFDS. Valid processor numbers range from 0 through 15. ALL specifies all processors.
TFDSCOM Commands Using TFDSCOM IGNOREOPERATORHALTS The IGNOREOPERATORHALTS command instructs TFDS either to start or to stop ignoring operator halts. IGNOREOPERATORHALTS { ON | OFF } ON directs TFDS to ignore operator halts. The default setting is ON, which means that no incident is put in the incident database and no 600x software error event is generated. OFF causes a processor dump (if AUTODUMP is enabled) and reload (if AUTORELOAD is enabled) when tools that cause intentional halts are used. Caution.
TFDSCOM Commands Using TFDSCOM Example INCIDENT DUMPOVERRIDE 150 MAXCONDUMPS The MAXCONDUMPS command specifies the number of concurrent processor dumps that TFDS should be allowed to initiate. MAXCONDUMPS num-condumps num-condumps is the maximum number of concurrent dumps that TFDS attempts to perform. The dump range is 1 through 4. The default value is 3. Guidelines • • You can use the abbreviation mcd in place of MAXCONDUMPS.
TFDSCOM Commands Using TFDSCOM PROCESSINGDELAY The PROCESSINGDELAY command instructs TFDS to wait a specific number of seconds before it starts the analysis and possible dump of a down processor. PROCESSINGDELAY time time is the delay in seconds. Seconds can range from 0 through 86400. The default value is 1. Guidelines • • • You can use the abbreviation pd in place of PROCESINGDELAY. PROCESSINGDELAY is valid only for SMR processors. (It is ignored in DMR and TMR processors.
TFDSCOM Commands Using TFDSCOM REM The REM command insert comments into the current trace file. REM tracefilecomment tracefilecomment specifies either an integer or a quoted string. Example REM "Further investigation required." REMOTENOTIFY The REMOTENOTIFY command causes TFDS to create a zero-length file on the specified remote system. REMOTENOTIFY is useful if you are managing multiple systems from one workstation.
TFDSCOM Commands Using TFDSCOM • • If this flag is set to ON, TFDS creates a file for each incident under the specified system.volume.subvolume. This name indicates the subvolume in which information related with each incident is located (for example, ZDMP00xx). If a network file transfer is invoked, a link to the target system must be operational because remote passwords are required. Example This example defines the target location of dump information under \GRANDE.$SIST.DUMP: REMOTENOTIFY ON \GRANDE.
TFDSCOM Commands Using TFDSCOM If the date option is provided, it overrides the rec-num option, and records based on that date are displayed. If neither is specified, the report starts with the first record. If STATUS is specified, only records specified by inc-stat are displayed. Guidelines • • • You can use the abbreviation r in place of REPORT. Records are displayed in a chronological format. If date is provided, records are displayed in chronological order.
TFDSCOM Commands Using TFDSCOM Rec. incident database record number. Date Time Incident occurrence date and time. # Number of recurrences (displayed only for initial incidents). Root Record number of the initial occurrence of this type of incident. If blank, this is the root or initial incident. Halt Processor halt code. Product Product number; available only for TFDS instrumented programs (NA if not available).
TFDSCOM Commands Using TFDSCOM If the TFDS dump fails and the REINTEGRATE-ON-FAILURE option is not specified, the NSBE is be reintegrated for approximately 1 hour. This delay enables you to continue efforts to obtain a valid processor dump by trying to dump the NSBE left in the stopped state. See AUTOREINTEGRATE on page 3-8. • In all processor configurations (SMR, DMR and TMR), there is a 45-second delay between each attempts at taking a dump.
TFDSCOM Commands Using TFDSCOM Guidelines • • • • • If no file name is specified, the current configuration file name is used. To display the configuration file name, use the CONFIG command. All configuration file attributes are written to the save file, whether the attributes have default or assigned values. The filename variable has to be a type 101 EDIT file. If this file does not exist, it is generated. If the file already exists, the contents are overwritten.
TFDSCOM Commands Using TFDSCOM Error text specifying interface problem with TFDS helper. Error text returned from TFDS helper. Example STATS HELPERS STATUS The STATUS command returns a TFDS view of either the processors or the TFDS helper processes. It shows the processor status and reload states. STATUS [HELPERS] HELPERS requests TFDS helper process information.
TFDSCOM Commands Using TFDSCOM h is the number of hours that a processor must survive in order for its successive reloads counter to be reset. If the number of successive reloads passes t, reloads are stifled for h hours. c is the processor number. tfdsst is the state of TFDS. It can be: Analyzing Not configured Reloading Dumped Not dumped Takeover Dumping Not reloaded Up cpust is the processor state.
TFDSCOM Commands Using TFDSCOM tape-unit represents the name of a local or remote tape drive. If tape-unit is not specified, the tape drive selection is set to “Not Assigned.” Guidelines • • You can use the abbreviation ta in place of TAPE. When TFDS starts up, if a tape drive is not specified, the system is scanned for a tape unit: ° If a suitable tape drive is found, this message appears in the TFDSCOM history display: Tape assigned is $tape-unit—config file needs to be saved.
TFDSCOM Commands Using TFDSCOM • • • The BURST SUPPRESSION task 'started' the timer (see BN command) for this incident. (For more information, see BURSTNOTIFY on page 3-12.) The BURST SUPPRESSION task detected the 'last' duplicate incident for this symptom string. The counts include ° ° • The number of incidents in the burst (see BN command) The total number of incidents for this symptom string since this burst task started. There could be more than one entry in the list.
TFDSCOM Commands Using TFDSCOM Command accepted indicates the termination request was accepted by the TFDS helper process. Helper not running indicates the TFDS helper process is not running on this processor. Helper not responding indicates a time-out occurred when attempting to communicate with the TFDS helper process. Helper on wrong CPU indicates the TFDS helper process for this processor is running on a different processor. CPU down indicates the processor is down.
TFDSCOM Commands Using TFDSCOM • • • • • • • • • • • • • • debug toggles the debug flag (abend/saveabend/close). flags displays the status of continuous capture, time and trace level. flush flushes tables and the trace buffer to the file tracefil. flushc flushes the trace buffer to the file tracecom. flush0 flushes the trace buffer to file tracefil. flush1 flushes and clears the history buffer to the file tracefi1. init sets trace 3, conton, timeon, flush0, and clr0.
TFDSCOM Commands Using TFDSCOM Guidelines • • • filename must be a 101 type Edit file. If filename does not already exist, it is created. If filename already exists, then the new trace data is appended to the end of the file. Example TRACE-FILE $DATA02.TRACEDAT.
TFDSCOM Commands Using TFDSCOM • • • 0x00000100 specifies that TFDSCOM-related tasks are to be traced in greater detail. 0x00000200 specifies that TFDS helper statistics are to be traced. 0x00000400 specifies that hash values calculated by TFDS helper processes are to be traced. tracefile specifies is a Guardian filename where the TFDS helper trace data is stored. Valid input for tracefile is [system.]vol.subvol.file-prefix. The file prefix is used as the prefix of the trace file name.
TFDSCOM Commands Using TFDSCOM Helper not running indicates TFDS helper is not running on this processor. Helper not responding indicates a time-out occurred when communicating with the TFDS helper. Helper on wrong CPU indicates TFDS helper process name for this processor is running on the wrong processor. CPU down indicates the associated processor is down. Error text specifying an interface problem with TFDS helper. Error text returned from TFDS helper.
TFDSCOM Commands Using TFDSCOM Helper on wrong CPU indicates the TFDS helper process name for this processor is running on the wrong processor. CPU down indicates the processor is down. Error text specifying interface problem with TFDS helper. Error text returned from TFDS helper.
TFDSCOM Commands Using TFDSCOM HP Tandem Failure Data System (TFDS) Manual—540122-003 3- 46
A EMS Messages and Templates The Event Management Service (EMS) receives and logs information about important events that occur in TFDS and the TFDSCOM user interface. This appendix defines each EMS message that TFDS can send, and provides templates for customizing operator messages.
EMS Messages and Templates EMS Messages EMS Messages 3 TFDS *0003* $ZDMP : BACKUP Waiting for Device : $yyyyy Cause. TFDS started a backup operation, but the tape unit 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. 7 TFDS *0007* $ZDMP : DUMP; Starting a Dump for CPU : nn Cause.
EMS Messages and Templates EMS Messages 13 TFDS *0013* $ZDMP : TFDS Starting in CPU : nn Cause. An operator has started TFDS. Effect. TFDS is starting up. Recovery. Informational message only; no corrective action is needed. 16 TFDS *0016* $ZDMP: RCVDUMP of CPU nn Failed. Attempting Retry Number: nn Cause. A RCVDUMP process that TFDS started failed to finish. Effect. A new RCVDUMP process is started.
EMS Messages and Templates EMS Messages 21 TFDS *0021* Processing Anomoly: xxxxxxxx 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. 22 TFDS *0022* Processing Status: xxxxxxxx Cause. This message indicates routine TFDS operational status.
EMS Messages and Templates EMS Messages 25 TFDS *0025* Fup Processing Status: xxxxxxxx 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. 26 TFDS *0026* Stop message from Tfdscom: TFDS stopping Cause. A TFDS STOP command was received from TFDSCOM. Effect. TFDS terminates. Recovery.
EMS Messages and Templates EMS Messages 42 TFDS $ZDMP : TFDSHLP stopping, CPU : nn 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. 43 TFDS $ZDMP : TFDSHLP continuing the processing of event for client process xxxxxxxx. Program file: xxxxxxxx Cause. Failure incident processing was interrupted. Effect.
EMS Messages and Templates EMS Messages Recovery. Ensure that the INSPSNAP program is running in each processor. 46 TFDS $ZDMP : Client process xxxxxxxx used a newer trigger value than is supported by the currently running TFDSHLP. Please ensure the proper version of TFDS is installed. Cause. The version of the TFDS helper process is older than the version of the trigger interface. Effect. Failure incident processing is interrupted. Recovery. Install the latest versions of TFDS, TFDSHLP and TFDSCOM.
EMS Messages and Templates EMS Messages 49 TFDS $ZDMP : TFDSHLP is incompatible with TFDSCOM. TFDSHLP version: xxxxxxxx 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.
EMS Messages and Templates EMS Messages 53 TFDS $ZDMP : TFDSHLP trace level changed. New level: nn 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. 54 TFDS $ZDMP : TFDSHLP Trace filename too long. Filename specified: xxxxxxxx Cause. The TFDS helper process has determined that the specified trace file name is too long for a Guardian file name. Effect.
EMS Messages and Templates EMS Messages specified file name, so the trace file name you specify must not exceed six characters in length. 57 TFDS $ZDMP : TFDSHLP invalid trace command Command specified: xxxxxxxx Cause. An incorrectly formatted trace command was specified. Effect. Tracing does not start. Recovery. Retype the TRACE-HELPER command using correct syntax. 58 TFDS $ZDMP : TFDSHLP internal error. Summary: xxxxxxxx. Source file: xxxxxxxx Line number: nn Cause.
EMS Messages and Templates EMS Messages Recovery. Informational message only; no corrective action is needed. 61 TFDS $ZDMP : TFDSHLP Incident processing timeout warning. Incident age: hh:mm:ss 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. Recovery. start this process manually.
EMS Messages and Templates EMS Messages 6001 Software Error *6001* : Incident Symptom String, Severity n, Product Number, Program Name, File Name, Error Location Following are the descriptions of the possible tokens in a failure event. name is the display heading for the token in the event detail. ZDMP-TKN-CPU-NUM CPU is the processor number that failed in a processor down incident. ZDMP-TKN-INCIDENT-NUM DB Incident Record # is the record number of the incident in the TFDS Incident Database.
EMS Messages and Templates EMS Messages Additional-text-n is the message text supplied by the caller for an instrument incident. For a processor down incident, these fields contain: TFDS VPROC, TFDS CONFIGURATION options, trace filename, whether an operator halt occurred, and time metrics. ZDMP-TKN-DIPID DIPID-Error-Location is either: • • For an instrument incident, the unique identifier of the failure specified by the caller.
EMS Messages and Templates EMS Messages ZDMP-TKN-FILENAME Filename is either: • • For an instrument incident, the source file name reported by the caller. For a processor down incident, the source file name reported by the program that halted the processor. ZDMP-TKN-OPTIONS Options is the options specified by the caller for an instrument incident.
EMS Messages EMS Messages and Templates ZDMP-TKN-RTLVPROC RTL Version is the VPROC of the RTL being used for a Legacy API instrument or the Trigger API's VPROC. ZDMP-TKN-PERCEIVED-SEVERITY Severity is the severity of the instrument or processor down incident. For an instrument, the severity is assigned by the caller or overridden by the ADD command.
EMS Messages EMS Messages and Templates ZDMP-TKN-CLIENT-OSS-PATHNAME Client-program-OSS-pathname is the OSS pathname for an OSS process calling an instrument. This token is only for an instrument incident. ZDMP-TKN-CLIENT-PROCESS-NAME Client-process-name is the caller's process name. This token is only for an instrument incident. ZDMP-TKN-CLIENT-PROC-SEQ-NUM Client-process-sequence-number is the caller's sequence number. This token is only for an instrument incident.
EMS Messages and Templates EMS Messages 7000 Data Capture Informative *7000* : Incident Symptom String, Severity n, Product Number, Program Name, File Name, Error Location See message 6001 on page A-12 for the descriptions of the possible tokens in a failure event. Cause. TFDS issues this event to document the analysis of an internal software error within the NonStop operating system.
EMS Messages and Templates Templates for EMS Support Templates for EMS Support Use these TFDS templates if you are developing or customizing operator messages for TFDS events.
EMS Messages and Templates Templates for EMS Support MSG: ZEMS-TKN-EVENTNUMBER, ZDMP-EVT-INCIDENT-RECURRENT "TFDS *0006* <1>: " " Product #<2>, Halt Code %<3>" " Recurrent Problem Logged, " " Symptom String : <4>" 1: 2: 3: 4: ZDMP-TKN-CRTPIDN, FILE ZDMP-TKN-PRODUCT-NUM ZDMP-TKN-HALT-CODE, 06 ZDMP-TKN-SYMPTOM-STRING MSG: ZEMS-TKN-EVENTNUMBER, ZDMP-EVT-RCVDUMP-STARTING "TFDS *0007* <1>: DUMP; Starting" " a ReceiveDump for CPU: <2>" 1: ZDMP-TKN-CRTPIDN, FILE 2: ZDMP-TKN-CPU-NUM, ZI2 MSG: ZEMS-TKN-EVENTNUM
EMS Messages and Templates Templates for EMS Support MSG: ZEMS-TKN-EVENTNUMBER, ZDMP-EVT-HALT-INC-NEW "TFDS *0014* <1>:" " Product #<2>, Halt Code %<3> CPU #<4>" " New Problem Logged, File(s) Located at <5>" " Symptom String : <6>" " Version Info : <7>" " Resource Name : <8>" " Source File Name : <9>" " Company Name : <10>" 1: 2: 3: 4: 5: 6: 7: 8: 9: 10: ZDMP-TKN-CRTPIDN, FILE ZDMP-TKN-PRODUCT-NUM,A10 ZDMP-TKN-HALT-CODE, 06 ZDMP-TKN-CPU-NUM, ZI2 ZDMP-TKN-INCIDENT-FILENAME, FILE ZDMP-TKN-SYMPTOM-STRING,A4
EMS Messages and Templates Templates for EMS Support MSG: ZEMS-TKN-EVENTNUMBER, ZDMP-EVT-TOO-MANY-DUMPS "TFDS *0018* <1>: Too many concurrent CPU dumps. " "Reloading CPU <2>." 1: ZDMP-TKN-CRTPIDN, FILE 2: ZDMP-TKN-CPU-NUM, ZI2 MSG: ZEMS-TKN-EVENTNUMBER, ZDMP-EVT-TEXT "TFDS *0019* TEXT: <1>." 1: ZDMP-TKN-JUST-TEXT, FILE MSG: ZEMS-TKN-EVENTNUMBER, ZDMP-EVT-CONFIG-ERROR "TFDS *0020* Configuration Error: <1>.
EMS Messages and Templates Templates for EMS Support MSG: ZEMS-TKN-EVENTNUMBER, ZDMP-EVT-GARTH-STAT "TFDS *0031* Garth Status: <1>." 1: ZDMP-TKN-JUST-TEXT, FILE MSG: ZEMS-TKN-EVENTNUMBER, ZDMP-EVT-GARTH-ERROR "TFDS *0032* TFDS Garth Error: <1>.
EMS Messages and Templates Templates for EMS Support MSG: ZEMS-TKN-EVENTNUMBER, ZDMP-EVT-HLP-TRIGGER-TOO-NEW "TFDS <1>: Client process " "<*IF 2><3><*ENDIF> used a newer trigger value than" " is supported by the currently running TFDSHLP." " Please ensure the proper version of TFDS is installed.
EMS Messages and Templates Templates for EMS Support MSG: ZEMS-TKN-EVENTNUMBER, ZDMP-EVT-HLP-TRC-LEVELCHANGE "TFDS <1>: TFDSHLP trace level changed." " New level: <2>" 1: ZDMP-TKN-CRTPIDN, FILE 2: ZDMP-TKN-HLP-TRACE-LEVEL, ZI2 MSG: ZEMS-TKN-EVENTNUMBER, ZDMP-EVT-HLP-TRC-NAME-TOO-LONG "TFDS <1>: TFDSHLP Trace filename too long.
EMS Messages and Templates Templates for EMS Support MSG: ZEMS-TKN-EVENTNUMBER, ZDMP-EVT-HLP-SNAPSHOT-ERR "TFDS <1>: TFDSHLP Snapshot Server Error." " <*IF 2> <3><*ENDIF>" " Snapshot file not saved: <4>" 1: 2: 3: 4: ZDMP-TKN-CRTPIDN, FILE TOKENPRESENT(zdmp-tkn-hlp-error-text) zdmp-tkn-hlp-error-text, A60 zdmp-tkn-dump-file-name, A60 MSG: ZEMS-TKN-EVENTNUMBER, ZDMP-EVT-HLP-CLEANUP-TIMER "TFDS <1>: TFDSHLP Incident processing timeout warning.
EMS Messages and Templates Templates for EMS Support HP Tandem Failure Data System (TFDS) Manual—540122-003 A -26
B Dependencies and Compatibility This appendix discusses compatibility issues and dependencies associated with TFDS and presents these topics: • • Compatibility Issues on page B-1 TFDS Product Dependencies on page B-3 Compatibility Issues In general, rule-based products that can interfere with TFDS functions should be disabled.
Dependencies and Compatibility Rule Management Services (RMS) Rule Management Services (RMS) To disable the processor dump and reload capabilities within RMS: 1. If you are not already in NonStop NET/MASTER NARS, log on to it. After a successful logon, a primary menu panel lets you select Rule Maintenance within RMS. 2. Select Rule Maintenance by typing R.6 (at any => prompt) and press Enter. The RMS: Rule Maintenance Panel appears. 3.
Dependencies and Compatibility TFDS Product Dependencies TFDS Product Dependencies TFDS has these dependencies: • • • • • • • • • • • • • TFDS process dumps depend on the Inspect subsystem (IMON and INSPSNAP). TFDS uses the Persistence Manager ($ZPM) to start or restart the TFDS monitor and TFDS helpers, which are defined under the Kernel subsystem. TFDS uses the Visual Inspect snapshot server services to create snapshot files. TFDS uses eGarth to gather information about processor software failures.
Dependencies and Compatibility TFDS Product Dependencies HP Tandem Failure Data System (TFDS) Manual—540122-003 B- 4
C TFDS Changes for H-Series RVUs This section indicates TFDS features and options that are new or obsolete in H-series RVUs and addresses these topics: • • • • New Features in H-Series RVUs on page C-1 New Commands in H-Series RVUs on page C-2 Obsolete Features in H-Series RVUs on page C-3 Obsolete Commands in H-Series RVUs on page C-3 New Features in H-Series RVUs Support for Hardware Failures TFDS supports processor failures caused by both hardware and software faults.
TFDS Changes for H-Series RVUs New Commands in H-Series RVUs New Commands in H-Series RVUs TFDSCOM Commands These TFDSCOM commands are new in H-series RVUs: • • • • • AUTOREINTEGRATE on page 3-8 EXCLUDEFILES on page 3-21 STATS HELPERS on page 3-35 TRACEHELPER on page 3-42 VERSION on page 3-44 For a list and descriptions of all current TFDSCOM commands, see TFDSCOM Commands on page 3-2.
TFDS Changes for H-Series RVUs Obsolete Features in H-Series RVUs Obsolete Features in H-Series RVUs In G-series RVUs, the NonStop S-series Fast Memory Dump (FMD) concept of capturing the first 2 GB of memory, reloading the processor, and then capture the remaining memory does not exist in H-series RVUs.
TFDS Changes for H-Series RVUs Obsolete Commands in H-Series RVUs HP Tandem Failure Data System (TFDS) Manual—540122-003 C- 4
D Best Practices This section provides guidelines for how best to configure, use, and manage TFDS. These topics are addressed: • • • • • Keep All TFDS Processes Running on page D-1 Designate a Dump Volume on page D-1 Designate an Alternate Volume Set on page D-1 Designate a Disallowed Volume Set on page D-1 Use Default Values for Key Attributes on page D-2 Keep All TFDS Processes Running TFDS monitor ($zdmp) and TFDS helpers ($zthnn) should always be running.
Best Practices Use Default Values for Key Attributes Use Default Values for Key Attributes You should use these default values for key TFDS configuration attributes: • • • • BURSTSUPPRESSION ON (For more information, see BURSTSUPPRESSION on page 3-13.) AUTODUMP ON (For more information, see AUTODUMP on page 3-7.) AUTOREINTEGRATE ON (For more information, see AUTOREINTEGRATE on page 3-8.) AUTORELOAD ON (For more information, see AUTORELOAD on page 3-8.
E Troubleshooting This appendix provides information that can be useful when troubleshooting these situations: • • • • Processor Was Not Dumped Automatically on page E-1 Processor Was Not Reloaded Automatically on page E-1 TFDS Process Execution Error on page E-1 Database Version Mismatch Error on page E-2 Processor Was Not Dumped Automatically Use the TFDSCOM CONFIG command to verify that: • • AUTODUMP is set to ON. (For more information, see AUTODUMP on page 3-7.) The processor is enabled.
Database Version Mismatch Error Troubleshooting Database Version Mismatch Error In order to protect itself against potential access to older incident database formats, the TFDS monitor verifies the version by reading the incident database Control File, and follows these rules. On Startup: 1. If the incident database location specified in the TFDS configuration file contains incident database files with a different version, issue an EMS message and use the default incident database location ($SYSTEM.
Troubleshooting Availability of TFDS During System Startup Availability of TFDS During System Startup When the system is starting up, the TFDS processes are started in a long sequence of startup activities. Depending on the availability of these processes and what events occur during startup, you might encounter problems with: • • CPU dumping: The TFDS monitor is started by the Persistence Manager. The StartMode value is SYSTEM.
Troubleshooting Availability of TFDS During System Startup HP Tandem Failure Data System (TFDS) Manual—540122-003 E- 4
Glossary absolute pathname. An Open System Services (OSS) pathname that begins with a slash (/) character and is resolved beginning with the root directory. Contrast with relative pathname. ASSIGN. An HP Tandem Advanced Command Language (TACL) command you can use to associate a file name with a logical file of a program or to assign a physical device to logical entities that an application uses. assign message. Within Subsystem Control Facility (SCF), a message created by SCF for each ASSIGN command.
cold load Glossary cold load. A synonym for system load or load (in the case of single processor load). System load or load is the preferred term in HP NonStop™ system publications. command file. An EDIT file that contains a series of commands and serves as a source of command input. console message. See operator message. DEFINE. An HP Tandem Advanced Command Language (TACL) command you can use to specify a named set of attributes and values to pass to a process. DEFINES paragraph.
Event Management Service (EMS) Glossary Event Management Service (EMS). A Distributed Systems Management (DSM) product that provides event collection, event logging, and event distribution facilities. EMS provides different event descriptions for interactive and programmatic interfaces, lets an operator or an application select specific event-message data, and allows for flexible distribution of event messages within a system or network. event message.
firmware Glossary On an HP NonStop™ system, the Guardian file system for an Expand node is a subset of the OSS virtual file system. Traditionally, the API for file access in the Guardian environment is referred to as the Guardian file system. In some UNIX and NFS implementations, the term file system means the same thing as fileset. That is, a file system is a logical grouping of files that, except for the root of the file system, can be contained only by directories within the file system.
Glossary HP NonStop™ Blade Complex (NSBC) HP NonStop™ Blade Complex (NSBC). The set of one, two, or three NonStop Blade Elements and their associated LSUs. For the first release of NonStop servers, a NonStop Blade Complex contains one to four logical processors. Also called a Blade Complex. HP NonStop™ Blade Element (NSBE). A portion of one or more logical processors and one part of a NonStop Blade Complex.
Kernel subsystem Glossary Kernel subsystem. In G-series and H-series release version updates (RVUs), the subsystem for configuration and management of the Subsystem Control Facility (SCF) subsystem managers that are generic processes, some system attributes, and the ServerNet X and Y fabrics. Kernel subsystem manager process. The generic process that starts and manages other generic processes, some system attributes, and the ServerNet X and Y fabrics in G-series release version updates (RVUs).
NonStop™ NS-series servers Glossary NonStop™ NS-series servers. See HP Integrity NonStop™ NS-series servers. NonStop™ Series TNS/E. See TNS/E. NonStop Technical Library. See HP NonStop™ Technical Library (NTL). NSAA. See HP NonStop™ advanced architecture (NSAA). NSBC. See NonStop™ Blade Complex (NSBC). NSBE. See NonStop™ Blade Element (NSBE) NSE-A processor. See HP NonStop™ System EPIC Model A processor (NSE-A processor). object code file.
OSS Glossary OSS. See Open System Services (OSS). OSS environment. See Open System Services (OSS) environment. OSS Monitor. See Open System Services (OSS) Monitor. parallel dumping. For DMR and TMR processors, the TFDS method of reloading a halted processor before dumping the affected NSBE. pathname. In the Open System Services (OSS) file system and Network File System (NFS), the string of characters that uniquely identifies a file within its file system. A pathname can be either relative or absolute.
reintegration Glossary reintegration. When a processor element has diverged or has been added or replaced, memory is copied from a functioning NonStop Blade Element to the replaced or added NonStop Blade Element, and the processor element is reintegrated into the logical processor. relative pathname. In the Open System Services (OSS) file system and Network File System (NFS), a pathname that does not begin with a slash (/) character.
SCF Glossary SCF. See Subsystem Control Facility (SCF). server. (1) An implementation of a system used as a stand-alone system or as a node in an Expand network. (2) A combination of hardware and software designed to provide services in response to requests received from clients across a network. For example, HP NonStop™ servers provide transaction processing, database access, and other services. (3) A process or program that provides services to a client or a requester.
Subsystem Control Facility (SCF) Glossary Each subsystem has a manager through which applications can request services by issuing commands defined by that subsystem. See also subsystem manager. Subsystem Control Facility (SCF). An interactive interface for configuring, controlling, and collecting information from a subsystem and its objects. SCF enables you to configure and reconfigure devices, processes, and some system variables while your HP NonStop™ server is online. subsystem manager.
TNS/E Glossary TNS/E. Refers to fault-tolerant HP computers that support the HP NonStop™ operating system and are based on the Intel® Itanium® processor. TNS/E systems run the Itanium instruction set and can run TNS object files by interpretation or after acceleration. TNS/E systems include all HP NonStop™ systems that use NSE-x processors. Contrast with TNS/E and TNS/R. TNS/R.
Index A Abort process (SCF command) 2-5 ACQUIREFILES command 1-7, 2-12, 2-13, 3-2, 3-4 ADD command 2-13, 2-14, C-2 ALTERNATE-VOLUMES command 2-13, 2-16, D-1 ANALYZE command 3-2, 3-5 ANALYZEPRIORITY command 2-12, 2-13, 3-2, 3-6 AUTOBACKUP command 2-12, 2-13, 3-2, 3-6 AUTODUMP command 2-12, 2-13, 3-2, 3-7, D-2, E-1 AUTOREINTEGRATE command 2-12, 2-13, 3-2, 3-8, C-2, D-2 AUTORELOAD command 2-12, 2-13, 3-2, 3-8, D-2 AUTOSTIFLE command 2-12, 2-13, 3-2, 3-9 B BACKUP command 3-2, 3-10 BACKUPDELAY command 2-12, 2-1
D Index Configuration file (continued) SNAPSHOTFROMDUMP 2-13, 2-19 TAPE 2-13, 3-37 TRACEHELPER 3-42 TRACE-FILE 2-13, 3-41 VERSION 3-44 Editing 2-13 Configuration options ACQUIREFILES 2-8 ALTERNATE-VOLUMES 2-6, 2-8 ANALYZEPRIORITY 2-8 AUTOBACKUP 2-8 AUTODUMP 2-8 AUTOREINTEGRATE 2-8 AUTORELOAD 2-8 AUTOSTIFLE 2-8 BACKUPDELAY 2-8 BURSTINTERVAL 2-8 BURSTNOTIFY 2-8 BURSTSUPPRESSION 2-8 DB-SUBVOL 2-8 Default settings 2-8 DISABLECPUS 2-8 DISALLOWED-VOLUMES 2-8 DUMPALLSLICES 2-6, 2-8 DUMPOVERRIDE 2-8 DUMPVOLUME 2-
F Index F MAX-DB-ENTRIES command 2-12, 2-13, 3-3, 3-28 Failure analysis 2-6 Failure data 1-6 Failure data collection 1-7, 2-4 Failure events 2-1 Failure signature 1-5, 1-6 FC command 3-2, 3-22 FMD commands C-3 FULLANDEXTRACTED command 2-13, 3-23 G GARTH-FILE command 2-13, 2-17 GCSC 1-3 H HELP command 3-2, 3-23 HISTORY command 3-2, 3-24 HP NonStop™ Blade Element (NSBE) 1-4 H-series RVU 1-8 I IGNORECPUS command 2-12, 2-13, 3-3, 3-26 IGNOREOPERATORHALTS command 2-12, 2-13, 3-3, 3-27 INCIDENT command 3-3
R Index R T RcvDump 1-3 Rediscovery 1-5, 1-6, 2-7 Rediscovery analysis 1-5, 1-6, 2-7 REINTEGRATE-ON-FAILURE 3-33 Reload 1-3 RELOAD-ON-FAILURE 3-33 REM command 3-3, 3-30 REMOTENOTIFY command 2-12, 2-13, 3-3, 3-30 REPORT command 3-3, 3-31 RETRY-DUMP command 2-12, 2-13, 3-3, 3-33, C-2 RETRY-RELOAD command 2-12, 2-13, 3-3, 3-34 Rule Management Services B-2 Rule Management Utility Program B-1 T6520 1-8 T6523 1-8 TAPE command 2-12, 2-13, 3-3, 3-37 TASKS command 3-3, 3-38 TFDS Architecture 1-2 Availability, a
T Index TFDS (continued) event messages A-1/A-17 Events 2-1 Features 1-2 Helper process 1-4, 1-6, 1-8 Adding 2-4 Starting 2-5 Stopping 2-5 Incident database E-2 Installation 1-8 Installing 2-4 Instruments 1-4 Introduction 1-1 Managing 2-1 Disk space 2-6, 2-7 Migration considerations 1-8 Monitor process 1-4, 1-5, 1-6, 1-7, 1-8, 2-6, 2-7, E-1, E-2 Adding 2-4 Starting 2-5 Stopping 2-5 Monitoring 2-1 Overview 1-1 Process configuration 2-4 TFDSCOM 3-1 commands 3-2 Troubleshooting E-1 TFDS helper 1-4, 1-6, 1-8,
V Index TFDSCOM (continued) TAPE 3-3, 3-37 TASKS 3-3, 3-38 TFDS STOP 3-3, 3-39 TRACE 3-3, 3-40 TRACEHELPER 3-3, 3-42 TRACE-FILE 3-3, 3-41 VERSION 3-3, 3-44 Online help 3-1 Starting 3-1 Using 3-1 TFDSCONF 1-4 TFDSHLP 1-8 TMR 1-4, 1-5, 2-7 TRACE command 3-3, 3-40 TRACEHELPER command 3-3, 3-42, C-2 TRACE-FILE command 2-12, 2-13, 3-3, 3-41 V VER command C-3 VERSION command 3-3, 3-44, C-2 Virtual disk, Selecting 2-6 Z ZDMPTEMP 1-7 Special Characters $0 1-7 $ZDMP 1-8, 2-1, D-1 $ZLOG 1-7 $ZPH 2-4 $ZTHnn 1-8 $
