Event Management Service (EMS) Analyzer Manual Abstract The Event Management Service (EMS) Analyzer selects events from EMS log files. You specify parameters, such as subsystem ID, event number, text, start time and stop time, through EMS Analyzer's conversational interface. The audience for the manual includes system managers, system operators, and programmers. Product Version C30 Supported Releases This manual supports function added to C30.
Document History Part Number Product Version Published 068091 C30.08 January 1992 133700 C30 August 1997 New editions incorporate any updates issued since the previous edition. A plus sign (+) after a release ID indicates that this manual describes function added to the base release, either by an interim product modification (IPM) or by a new product version on a .99 site update tape (SUT). Ordering Information For manual ordering information: domestic U.S.
New and Changed Information This is the second edition of the Event Management Service (EMS) Analyzer Manual. This is only a revision of the format. No content has been changed.
New and Changed Information Event Management Service (EMS) Analyzer Manual–133700 iv
Contents New and Changed Information iii About This Manual ix Notation Conventions xiii 1. Introduction Architecture 1-2 Features 1-2 2.
4.
A. Event Data File Record Definition Contents ASSUME 5-17 CLEAR 5-18 COMMENT 5-19 CONFIRM 5-20 CPUS 5-20 DELAY 5-22 DETAIL ERROR 5-23 DISPLAYEXTCHAR 5-24 DUMPLOG 5-24 ENV 5-27 EXIT 5-27 FC 5-27 HELP 5-28 HISTORY 5-30 INFO 5-31 LOG 5-34 OBEY 5-35 OUT 5-36 PAGESIZE 5-37 PARAM 5-38 PAUSE 5-39 REPEAT 5-39 RUN 5-40 SETPROMPT 5-41 START 5-42 STATUS 5-43 STOP 5-47 SYSTEM 5-48 TIMEOUT 5-48 VERSION 5-49 VOLUME 5-50 A. Event Data File Record Definition Enscribe Database File CSV File A-3 A-1 B. EMSASSID File C.
E. Error Messages Contents E. Error Messages Warning Messages E-1 Error Messages E-2 Interprocess Communication Warning Messages E-34 Interprocess Communication Error Messages E-35 Index Figures Figure 1-1. Figure 3-1. EMS Analyzer Architecture 1-2 Flowchart on How to Use EMS Analyzer 3-1 Tables Table 2-1. Table 2-2. Table 3-1. Table 5-1. Table A-1. Table A-2. Table D-1.
About This Manual This manual describes the Event Management Service (EMS) Analyzer. You use EMS Analyzer to analyze Event Management Service (EMS) log files. You can define search parameters and select event messages and then have EMS Analyzer route the resulting events to a designated terminal, spooler, Enscribe database file, or Comma Separated Values (CSV) file. Analysis and reporting can then be achieved on those resulting files.
Manual Organization About This Manual Manual Organization This manual consists of the following sections and appendixes: Section Contents Section 1, Introduction Provides an introduction to EMS Analyzer with a description of EMS Analyzer architecture Section 2, Installation Describes how to install EMS Analyzer Section 3, Using EMS Analyzer Describes how to use EMS Analyzer Section 4, Command Components Describes the EMS Analyzer command components Section 5, Command Descriptions Provides EMS A
Your Comments Invited About This Manual name, company name, address, and phone number in your message. If your comments are specific to a particular manual, also include the part number and title of the manual. Many of the improvements you see in Tandem manuals are a result of suggestions from our customers. Please take this opportunity to help us improve future manuals.
Your Comments Invited About This Manual Event Management Service (EMS) Analyzer Manual–133700 xii
Notation Conventions General Syntax Notation The following list summarizes the notation conventions for syntax presentation in this manual. UPPERCASE LETTERS. Uppercase letters indicate keywords and reserved words; enter these items exactly as shown. Items not enclosed in brackets are required. For example: MAXATTACH lowercase italic letters. Lowercase italic letters indicate variable items that you supply. Items not enclosed in brackets are required. For example: file-name [ ] Brackets.
Notation for Messages Notation Conventions An ellipsis immediately following a single syntax item indicates that you can repeat that syntax item any number of times. For example: "s-char..." Punctuation. Parentheses, commas, semicolons, and other symbols not previously described must be entered as shown. For example: error := NEXTFILENAME ( file-name ) ; LISTOPENS SU $process-name.
Notation for Management Programming Interfaces Notation Conventions [ ] Brackets. Brackets enclose items that are sometimes, but not always, displayed. For example: Event number = number [ Subject = first-subject-value ] A group of items enclosed in brackets is a list of all possible items that can be displayed, of which one or none might actually be displayed.
Change Bar Notation Notation Conventions margin of changed portions of text, figures, tables, examples, and so on. Change bars highlight new or revised information. For example: The message types specified in the REPORT clause are different in the COBOL85 environment and the Common Run-Time Environment (CRE). The CRE has many new message types and some new message type codes for old message types. In the CRE, the message type SYSTEM includes all messages except LOGICAL-CLOSE and LOGICAL-OPEN.
1 Introduction Event Management Service (EMS) messages provide important information about devices, subsystems, and applications. Tandem subsystems, such as Expand, Transaction Monitoring Facility (TMF), Pathway, and NonStop SQL, as well as your own custom applications, can generate thousands of event messages. EMS Analyzer enables you to examine and analyze this information, which is saved in the EMS event log files.
Architecture Introduction Online Help is available for EMS Analyzer. Help provides general information about EMS Analyzer objects and commands and comes in menu mode or command mode. Architecture Figure 1-1 illustrates the EMS Analyzer architecture. Tandem subsystems or your own subsystems send event messages to a collector, for example $0 or an alternate collector. These messages are logged in EMS log files.
2 Installation This section describes how to install EMS Analyzer. EMS Analyzer is designed to be used with the Event Management Service (EMS). EMS Analyzer operation requires proper EMS operation. For additional information about event management, refer to the EMS Manual. EMS Analyzer System Requirements EMS Analyzer requires the Tandem NonStop operating system, release C30 or later. There are no additional system dependencies. The EMS Analyzer ISV subvolume uses about 600 kilobytes of disk space.
Creating EMS Analyzer Installation Subvolume (ISV) Installation Creating EMS Analyzer Installation Subvolume (ISV) EMS Analyzer is installed at your site using the INSTALL program documented in the System Generation Manual. This is normally done by the system manager. Install EMS Analyzer software files from the Site Update Tape (SUT). The INSTALL program restores EMS Analyzer files from the SUT onto the Distribution Subvolume (DSV) and then copies them to the ISV during the installation process.
Before You Install EMS Analyzer Installation Before You Install EMS Analyzer Before you run the EMS Analyzer installation TACL macro (INSTEMSA), you should know the following: • • • • The installation macro does not alter the installation subvolume. A new subvolume is created when needed by the installation macro. This safeguard prevents undesirable installation results. If the installation of EMS Analyzer is unsatisfactory, purge the subvolumes and restart the installation procedures.
Sample EMS Analyzer Installation Installation Table 2-2. EMS Analyzer Installation Parameter Values (page 2 of 2) Number Name Value Description 5 EMSA-EMSDISTNAME emsdist-name Specifies the name of the consumer distributor used by EMS Analyzer. Each EMS Analyzer user should use a different name. If you do not want to specify the name of a distributor, you can specify SYSTEM-GENERATED as the value for this parameter and EMS Analyzer will assign a system generated name.
Installation Script Installation To help clarify the EMS Analyzer installation process, the sample EMS Analyzer installation is divided into steps. Each step has a brief explanation. Sample screens follow the command entries.
Installation Script Installation Step 1: Defining a File This step checks to see if a define file exists and creates one if it does not. At its creation, this file is filled with default values. EMS Analyzer - T9671C30 - (01NOV91) Copyright Tandem Computers Incorporated 1991 Installation Procedure. This procedure will install the EMS Analyzer product on your system. Defaults are displayed in square brackets and may be selected by pressing RETURN.
Installation Script Installation Step 2: Selecting and Defining the Parameters This step provides parameter or default parameters selection during EMS Analyzer installation. STEP #2: Please modify or accept the installation parameters. 1. ISV $SYSTEM.ZEMSA 2. EMSA-PROGRAM-SUBVOL $SYSTEM.SYSTEM 3. EMSACSTM-USER-SUBVOL $SYSTEM.STARTUP 4. EMSA-DDL-DEFAULT-SUBVOL $SYSTEM.SYSTEM 5. EMSA-EMSDIST-NAME SYSTEM-GENERATED 6. EMSA-EMSDIST-PRIORITY 100 7.
File-Specific Installation Considerations Installation Step 5: Installing EMS Analyzer Program EMS Analyzer INSTEMSA routine moves all the program and help text to the subvolume specified by EMSA-PROGRAM-SUBVOL parameter. The following files are moved: EMSA, EMSADDL, EMSAFLTR, EMSASSID, and EMSATEXT. STEP #5: Moving program and data files from $SYSTEM.ZEMSA to $SYSTEM.SYSTEM. EMSA files duplicated in: $SYSTEM.SYSTEM.
EMS Analyzer Help and Error Text File Installation his/her own default subvolume. You can use an ASSIGN to tell EMS Analyzer to read the EMSACSTM file from another subvolume if desired. 1> ASSIGN EMSACSTM, $DATA.ZEMSA.EMSACSTM 2> 3> == You may now run EMSA and it will get EMSACSTM file 4> == from $DATA.ZEMSA.EMSACSTM This file can be used to pre-configure your session parameters. You can use the ALIAS command to create shortcut commands for frequently invoked commands.
Installation EMS Analyzer CSV file Record Definition During the generation of the CSV file, EMS Analyzer looks through each event that matches the selection criteria and adds it to the file on a per event basis. If EMS Analyzer does not find a value for a token in the event, it uses a default value for the corresponding field in the CSV file. All fields are separated by commas. For a complete description of the CSV file record, see Appendix A, Event Data File Record Definition.
3 Using EMS Analyzer This section describes how to use EMS Analyzer. Figure 3-1 shows a flowchart on how to use EMS Analyzer. Figure 3-1.
Using EMS Analyzer These steps are explained in the following subsections: • • • • • • Running EMS Analyzer • • • • • • • • Running EMS Analyzer in Background Mode for a Batch Environment Exiting EMS Analyzer Entering EMS Analyzer Commands Configuring Function Keys Setting Detail Error Display Modifying Timeout Editing the EMS Analyzer Custom Configuration File Using Online Help Starting the Distributor • • • Stopping a Distributor Modifying the EMS Analyzer Distributor Priority Getting Status In
Running EMS Analyzer Using EMS Analyzer • • Starting the Search • • Altering the DUMPLOG STATUS Attribute Removing the More Text Question Examining Results • • Making Enform Reports Downloading Files to a Workstation Running EMS Analyzer EMS Analyzer follows the conventions of Tandem conversational interfaces, such as the Subsystem Control Facility (SCF). If you have used other Tandem products with a conversational interface, you will find EMS Analyzer easy to use and understand.
Running EMS Analyzer Using EMS Analyzer EMSA - T9671C30 - (01NOV91) (15DEC91) - 11/20/91 18:22:33 System \MTL Copyright Tandem Computers Incorporated 1991 (Invoking $SYSTEM.STARTUP.EMSACSTM) Confirm....... ON EMSA CONSUMER DISTRIBUTOR $Z902 started EMSA DISTRIBUTOR $Z902 altered: EMSLOG attribute EMSA DISTRIBUTOR $Z902 altered: FILTER attribute DISTRIBUTOR $Z902 1-> The EMS Analyzer prompt is the arrow (->), but you can modify the prompt by using the SETPROMPT command.
Running EMS Analyzer in Background Mode for a Batch Environment Using EMS Analyzer which must be a letter. (For network access, the name must be no more than four characters.) If you omit this parameter, the EMS Analyzer process is not named and has only a CPU number and process ID. NOWAIT specifies that TACL does not wait while the program runs. TACL returns a command input prompt after sending the startup message to the new process. If you omit this option, TACL pauses while EMS Analyzer runs.
Exiting EMS Analyzer Using EMS Analyzer • • • • • The EMSACSTM file is not executed. The abbreviation facility is not available. Make sure you specify full commands and attributes. These commands are not allowed: FC, HISTORY, PAUSE, exclamation point (!), question mark (?), and HELP (menu-mode). For the SETPROMPT command, the DIM and REVERSE parameters are not valid. You should use the ALLOW command to specify how many warnings and how many errors are allowed before stopping EMS Analyzer.
Entering EMS Analyzer Commands Using EMS Analyzer Entering Multiple Commands on a Line You can enter multiple EMS Analyzer commands at a single prompt (->) by separating the commands with semicolons.
Entering EMS Analyzer Commands Using EMS Analyzer is equivalent to the following series of commands: -> start, cpu 1, pri 100 -> alter, filter emsafltr -> info -> alter, starttime 1w -> info -> alter, stoptime eof -> info -> dumplog Entering a Comment Line You can enter a comment following the comment characters (==) at the beginning of a line or within a line. Any text on the line following the == is not processed: -> == This is a comment. Also, a comment can be entered using the COMMENT command.
Configuring Function Keys Using EMS Analyzer F16 while entering an EMS Analyzer command returns a message indicating the expected input. Configuring Function Keys You can use the ALIAS command to set up function keys. The EMS Analyzer default custom file already contains a set of function key configuration commands. To view the EMS Analyzer default custom file, see Appendix C, EMSACSTM File. Setting up Function Keys You can use function keys as predefined keywords or commands by using the ALIAS command.
Setting Detail Error Display Using EMS Analyzer Avoiding the Comma After the ALTER in the ALTER Command To use a function key to avoid having to type a comma after the ALTER command each time an attribute is modified, type the following at the prompt: -> alias F15 alter, -> ssid "tandem.expand" Press F15. The first command associates the function key F15 with the ALTER, command.
Modifying Timeout Using EMS Analyzer Modifying Timeout The timeout value is used when communicating with any distributor. Using the ALTER, INFO, or STATUS commands, for example, imply communications with a distributor. The timeout is the maximum time that EMS Analyzer waits to receive a response from a distributor. This timeout value is considered the global timeout value and should not be confused with the DUMPLOG STATUS attribute (see Note). The default timeout is 1 minute and 30 seconds.
Editing the EMS Analyzer Custom Configuration File Using EMS Analyzer Editing the EMS Analyzer Custom Configuration File From the installation of EMS Analyzer, a custom configuration file (EMSACSTM) is created. If this file is located in your default subvolume, it will be read each time you execute EMS Analyzer program command, EMSA. This file can be used to preconfigure your session parameters. Use the ALIAS facility of EMS Analyzer to create shortcut commands for often invoked commands as desired.
Using Online Help Using EMS Analyzer Example -> help version The VERSION command displays the version level of the specified object or objects. VERSION [ /OUT / ] [ ] [ , DETAIL ] /OUT / causes any EMSA output generated for this command to be directed to the specified file. is the name of the object or objects whose version level is to be displayed.
Using Online Help Using EMS Analyzer The HELP menu appears and prompts you for a basic component, subsystem, device name or option. Welcome to EMSA menu mode.
Using Online Help Using EMS Analyzer To get a list of EMS Analyzer commands and to get help on using HELP, enter ALL at the HELP prompt: HELP : all EMSA supports the following commands: -------------------------- COMMANDS-----------------------------------The following are EMSA commands: ALIAS ASSUME CPUS ENV HISTORY OUT REPEAT STATUS VERSION ALLOW CLEAR DELAY EXIT INFO PAGESIZE RUN STOP VOLUME ALTER COMMENT DETAIL FC LOG PARAM SETPROMPT SYSTEM ! ASSIGN CONFIRM DUMPLOG HELP OBEY PAUSE START TIMEOUT ?
Using Online Help Using EMS Analyzer If you want EMS Analyzer command information, enter EMSA at the HELP prompt.
Starting the Distributor Using EMS Analyzer If you want specific command information, enter the name of the command at the HELP EMSA prompt, for example VERSION. HELP EMSA : VERSION The VERSION command displays the version level of the specified object or objects. VERSION [ /OUT / ] [ ] [ , DETAIL ] /OUT / causes any EMSA output generated for this command to be directed to the specified file.
Stopping a Distributor Using EMS Analyzer For more information on the ASSUME, SETPROMPT, and START commands, see Section 5, Command Descriptions. Guidelines • • The default EMSACSTM file includes a START command to start a distributor. If the EMSACSTM file is located in your default subvolume, a distributor will be started automatically for you. For a sample of the default EMSACSTM file, refer to Appendix C, EMSACSTM File.
Getting Status Information About a Distributor Using EMS Analyzer Example DISTRIBUTOR $Y202 -> 5> altpri $y202, 80 6> pause DISTRIBUTOR $Y202 -> ! BREAK-KEY is pressed here. Getting Status Information About a Distributor To retrieve status information about a distributor, type the following at the prompt: -> status This command retrieves status information about the assumed distributor since a distributor name was not specified.
Setting up Filter Search Parameters Using EMS Analyzer This command is included in the default EMS Analyzer custom file (EMSACSTM) and is generally automatically invoked. The EMS Analyzer default filter (EMSAFLTR) is installed on the same subvolume as the EMS Analyzer program (refer to Section 2, Installation). You might have to specify the complete location (volume and subvolume) of the EMSAFLTR file, depending on your current subvolume.
Setting the Input Source Using EMS Analyzer Table 3-1. Filter Parameters Parameter Description SYSTEM This specifies the name of a system (node) from which events were generated. LDEV This identifies a particular device name or number. TEXT This specifies a particular text string to be searched. Setting the Input Source To set the input source for the events, use the ALTER command with the EMSLOG attribute, for example: -> alter, emslog $data.appl.
Resetting a Filter Parameter to its Default Value Using EMS Analyzer Example DISTRIBUTOR $Y197 -> info EMSA INFO DISTRIBUTOR $Y197 Distributor type. CONSUMER *Filter.......... $DATA.EMSA.EMSAFLTR *Emslog.......... $0.#ZSPI Coll log......... $SYSTEM.ZLOG00.ZZEV0004 Current log...... $SYSTEM.ZLOG00.ZZEV0004 *EventDB......... *EventDB type.... *EventDB extents. (20,100,16) *Format.......... TEXT *Dumplog Status.. 5 seconds Search criteria *Starttime... 91SEP16, 00:00:00 *Eventnumber. *Processid... *System...
Examples of Selecting Events Using EMS Analyzer Example DISTRIBUTOR $Y197 -> alter, emsafltr reset EMSA DISTRIBUTOR $Y197 altered: EVENTNUMBER attribute EMSA DISTRIBUTOR $Y197 altered: EVENTTYPE attribute EMSA DISTRIBUTOR $Y197 altered: PROCESSID attribute EMSA DISTRIBUTOR $Y197 altered: SSID attribute EMSA DISTRIBUTOR $Y197 altered: SYSTEM attribute EMSA DISTRIBUTOR $Y197 altered: LDEV attribute EMSA DISTRIBUTOR $Y197 altered: TEXT attribute DISTRIBUTOR $Y197 -> Guidelines When you use the ALTER, EMSAFL
Examples of Selecting Events Using EMS Analyzer Example DISTRIBUTOR $Y197 -> alter, starttime 1w, stoptime eof, ssid "tandem.pathway", text "timeout" EMSA DISTRIBUTOR $Y197 altered: STARTTIME attribute EMSA DISTRIBUTOR $Y197 altered: STOPTIME attribute EMSA DISTRIBUTOR $Y197 altered: SSID attribute EMSA DISTRIBUTOR $Y197 altered: TEXT attribute DISTRIBUTOR $Y197 -> dumplog Searching events...
Examples of Selecting Events Using EMS Analyzer The DUMPLOG command starts the search. Note. When you specify the null value for the stop time parameter, the search continues until the BREAK key is pressed. If the EMS source is a log file and you specify the stop time as the null value, the search continues until the end of file. Example DISTRIBUTOR $Y197 -> alter, starttime now, stoptime, ssid "tandem.
Defining the Output Destination Using EMS Analyzer Example DISTRIBUTOR $Y197 -> alter, emslog $system.zlog00.zzev0008 EMSA DISTRIBUTOR $Y197 altered: EMSLOG attribute DISTRIBUTOR $Y197 -> alter, starttime bof, stoptime eof, ssid "tandem.
Dumping Events into a File Using EMS Analyzer EMS Analyzer also allows you to specify an output destination for a single command, leaving the output destination for the session unchanged. To change the output destination for a single command, use /OUT file-spec/ following the command keyword.
Dumping Events into a File Using EMS Analyzer Dumping Events Into a CSV File To set the EMS Analyzer environment so that all selected EMS event messages are written to a CSV file, type the following at the prompt: -> alter, eventdb csv $data.emsacsv.emsadb1 purge -> dumplog This command sets the event database attribute to the desired CSV file name, which is purged (if it exists) and created. EMS Analyzer replaces the commas within fields with spaces before writing the record to the CSV file.
Defining the Format of the Output Using EMS Analyzer Defining the Format of the Output This subsection describes three ways to view the selected events: text, token, and token without header tokens. It also explains how you can use EMS Analyzer as a debugging tool by using the token display facility.
Viewing Events in Token Format—All Tokens Using EMS Analyzer Example DISTRIBUTOR $Y200 -> alter, format text EMSA DISTRIBUTOR $Y200 altered: FORMAT attribute DISTRIBUTOR $Y200 -> dumplog Searching events...
Viewing Events in Token Format—No Header Tokens Using EMS Analyzer Example DISTRIBUTOR $Y200 -> alter, format token detail EMSA DISTRIBUTOR $Y200 altered: FORMAT attribute DISTRIBUTOR $Y200 -> dumplog Searching events... -----------------------------------------------------------------------------Header Type: 1 Checksum: F Last Error: no error (0) Last Error Tkncode: (0,0,0) Max Field Version: 0 SSID: TANDEM.127.
Using EMS Analyzer as a Debugging Tool Using EMS Analyzer Example DISTRIBUTOR $Y200 -> alter, format token EMSA DISTRIBUTOR $Y200 altered: FORMAT attribute DISTRIBUTOR $Y200 -> dumplog Searching events... -----------------------------------------------------------------------------Subject Mark: * (2,2,500): 0 TANDEM.EMS.0 Text: "OMF: CPU 00, Current State = OVER THRESHOLD, Prev" "ious State = UP, Current Usage = 96, Configured T" "threshold = 90, Sampling Interval = 1 minutes.
Altering the DUMPLOG STATUS Attribute Using EMS Analyzer Altering the DUMPLOG STATUS Attribute The DUMPLOG STATUS attribute specifies the maximum time period in which you will receive feedback from EMS Analyzer when it is searching for events. The feedback is either an event message found or a status line indicating the current position, how many events passed the filter and how many events were read. In this example, a DUMPLOG command is invoked.
Examining Results Using EMS Analyzer Example DISTRIBUTOR $Y200 -> pagesize -1 terminal Pagesize............... -1 TERMINAL DISTRIBUTOR $Y205 -> env EMSA - T9671C30 - (01NOV91) (15DEC91) - 09/19/91 14:54:41 System \POLLUX Copyright Tandem Computers Incorporated 1991 Allow.............. ALL ERRORS Allow.............. ALL WARNINGS Assume............. DISTRIBUTOR $Y205 Confirm............ ON Detail Error....... OFF Log................ In................. $ASY00.#TERM02 Out................ $ASY00.
Making Enform Reports Using EMS Analyzer This command opens the database: > open event; This command runs a sample Enform query: > ?run emsaq1 Five samples are provided with EMS Analyzer: EMSAQ1, EMSAQ2, EMSAQ3, EMSAQ4, EMSAQ5. These are examples; any valid query can be performed.
Making Enform Reports Using EMS Analyzer Example The following example shows how to start Enform from an EMS Analyzer session, Event Management Service (EMS) Analyzer Manual–133700 3- 36
Making Enform Reports Using EMS Analyzer show events by ascending timestamp, and exit Enform: Event Management Service (EMS) Analyzer Manual–133700 3- 37
Using EMS Analyzer Making Enform Reports DISTRIBUTOR $Y205 -> enform Running the program file $SYSTEM.SYSTEM.ENFORM Enform - T9152C20 - (20APR90) DATE - TIME : 9/19/91 - 15:20:09 COPYRIGHT TANDEM COMPUTERS INCORPORATED 1979, 1983 >?dictionary $data.enform >?assign event to $data.emsaens.emsadb1 >open event; >?run $system.zemsa.emsaq1 1 * ! EMS Analyzer - ENFORM query example 1 1.01 * ! 1.1 * ! List all events by ascending timestamp 1.2 * ! Items shown are: time, 1.3 * ! system name, 1.
Making Enform Reports Using EMS Analyzer The following example shows the EMSAQ2 query: Event Management Service (EMS) Analyzer Manual–133700 3- 39
Making Enform Reports Using EMS Analyzer >?run $system.zemsa.emsaq2 2 * ! EMS Analyzer - ENFORM query example 2 2.01 * ! 2.02 * ! List all events by ascending timestamp 2.04 * ! Items shown are: time, 2.041 * ! subsystem id, 2.05 * ! crtpid, 2.07 * ! first 37 characters of text; 2.08 * ! 2.09 * !(file EMSADDL shows record definition for ENSCRIBE database files) 2.1 * ! 2.11 * LIST (HOUR * 3600 + MINUTE * 60 + SECOND) AS TIME "H2:M2:S2", 2.2 * ssid, 2.
Making Enform Reports Using EMS Analyzer The following example shows the EMSAQ3 query: Event Management Service (EMS) Analyzer Manual–133700 3- 41
Making Enform Reports Using EMS Analyzer >?run $system.zemsa.emsaq3 2 * ! EMS Analyzer - ENFORM query example 3 2.01 * ! 2.02 * ! List all events by timestamp 2.04 * ! Items shown are: date and time, 2.05 * ! system name, 2.051 * ! subsystem id in ascending order, 2.053 * ! crtpid, 2.07 * ! eventnumber, 2.071 * ! userid (group number), 2.074 * ! emphasis flag; 2.08 * ! 2.09 * !(file EMSADDL shows record definition for ENSCRIBE database files) 2.1 * ! 2.
Making Enform Reports Using EMS Analyzer The following example shows the EMSAQ4 query: >?run $system.zemsa.emsaq4 4 * ! EMS Analyzer - ENFORM query example 4 4.01 * ! 4.02 * ! List number of events per ssid by 4.021 * ! descending manager order 4.03 * ! Items shown are: manager, 4.04 * ! subsystem id for this manager, 4.05 * ! number of events for this ssid; 4.08 * ! 4.09 * !(file EMSADDL shows record definition for ENSCRIBE database files) 4.1 * ! 4.
Downloading Files to a Workstation Using EMS Analyzer Downloading Files to a Workstation You can use workstation tools on the Macintosh or PC to make presentation quality graphics of EMS Analyzer results. The size of the CSV file to be downloaded depends on the number of events selected and written to this file. Typically, an event in the CSV file takes around 400 bytes. For a Macintosh Type the following from the TACL prompt: 1> XMODEM S CSV-filename This downloads the file using XMODEM.
4 Command Components This section contains a description of the basic syntactic components used with EMS Analyzer. The command components that are described in this section are as follows: • • • • Objects and Object Lists Attributes and Attribute Values Strings, Integers, and Time Values Disk File Names Objects and Object Lists Objects are the entities that can be configured, controlled, and inquired about using EMS Analyzer.
Attributes and Attribute Values Command Components type, use the ASSUME command to always set the object-type to DISTRIBUTOR. The object-name format is as a single object name. The format of an object name is the same as the format of a NonStop Kernel process name. In EMS Analyzer, the object name represents a distributor process. The object name can be omitted if the ASSUME command is used to establish an appropriate object name.
Strings, Integers, and Time Values Command Components Strings, Integers, and Time Values EMS Analyzer requires a standard format for entering character strings, integers, and time values. The variables for these items are: • • • Char Integer Time Char The variable char is used for attributes that accept one or more 8-bit characters. The syntax of char is as follows: { "character-string" } { 'character-string' } character-string is any string of one or more printable ASCII characters.
Time Command Components • The range of a 64-bit integer is -2**63 through 2**64-1. Time The variable time is used for attributes that require a specified time interval. The syntax of time is as follows: [ [ hours : ] minutes : ] seconds [ . fraction ] hours is an integer, as defined in the subsection Integer above. minutes is an integer, as defined in the subsection Integer above. seconds is an integer, as defined in the subsection Integer above.
File Specification Command Components File Specification In the syntax descriptions for EMS Analyzer commands, the variable file-spec is used to denote a fully or partially qualified NonStop Kernel disk file name. A fully qualified file name has all four parts explicitly specified. A partially qualified file name has one or more optional parts missing. EMS Analyzer uses the appropriate default values to expand the file name to four parts. The syntax of file-spec is as follows: [ \system-name.
File Specification Command Components Event Management Service (EMS) Analyzer Manual–133700 4 -6
5 Command Descriptions This section describes the syntax of all commands available with EMS Analyzer. The information in this section is critical to understanding what commands are available, what they do and how they are entered. EMS Analyzer makes certain assumptions when various options are omitted. Table 5-1 gives an overview of the EMS Analyzer commands. A full description of each command follows. Table 5-1.
Exclamation Point (!) Command Descriptions Table 5-1.
Question Mark (?) Command Descriptions character-string is the first few characters of the command line to be re-executed. The most recent command line whose first characters match the string are re-executed. Considerations • If you use an exclamation point (!) alone, the previous command is re-executed. The exclamation point (!) alone is the same as ! -1. • If you specify a negative number and the associated command line is no longer in the history buffer, you get an error message.
ALIAS Command Descriptions number if positive, is the line number of the command line to be displayed. If negative, the current command-line number minus number is the line number of the command line to be displayed. character-string is the first few characters of the command line to be displayed. The most recent command line whose first characters match the string is displayed. Considerations • • • • • If you use a question mark (?) alone, the previous command is displayed.
ALIAS Command Descriptions /OUT file-spec/ causes any EMS Analyzer output generated for this command to be directed to the specified file. identifier is the name of the alias, consisting of an alphabetic character followed by 0 to 20 alphanumeric characters. If omitted, all previously defined aliases are displayed. text consists of any printable characters. This is the text that the alias name is expanded into. If omitted, the selected alias is displayed.
ALLOW Command Descriptions ALLOW The ALLOW command specifies the maximum number of warnings or errors allowed to occur during execution of an OBEY file, an IN file, or a command that refers to multiple objects. If any value is exceeded, EMS Analyzer halts execution of the OBEY file, IN file, or multiple object command. ALLOW affects only commands that issue multiple commands or refer to multiple objects.
ALTER Command Descriptions Examples -> ALLOW Execution of an OBEY file aborts with the detection of the first error. Warnings are ignored. -> ALLOW 5 ERRORS Execution of an OBEY file aborts when the sixth error is detected. Warnings are ignored. ALTER The ALTER command modifies the attribute values of the specified object or objects. ALTER [ /OUT file-spec/ ] [ object-spec ] [, attribute-spec ]...
ALTER Command Descriptions EMSAFLTR RESET resets all filter parameters values to original default values. The attributes modified by this command are: EVENTNUMBER, EVENTTYPE, LDEV, PROCESSID, SSID, SYSTEM and TEXT. EMSLOG [ collname | filename ] specifies in which source file to search for EMS events. When reset, the default value for this attribute is $0. collname collector name, in accordance with Tandem syntax. filename Tandem external file name. The specified file is an EMS events log file.
ALTER Command Descriptions 32767. If no value is specified, the actual Eventdb primary extent size value is assumed. sec-ext is the secondary extent size (units of 2048 bytes) of the specified data base or CSV file. The value is an integer in the range of 0 through 32767. If no value is specified, the primary extent size value is assumed. max-ext is the maximum number of extents to be created for the specified data base or CSV file. The value is an integer in the range of 0 through 978.
ALTER Command Descriptions FORMAT [ TEXT | TOKEN [detail] ] [ TEXT | TOKEN [detail] ] specifies in which format(s) the selected EMS events display on the screen. At most, two values can be specified. TEXT selected events display in text format. This is the default value. It can be combined with TOKEN value. TOKEN [detail] selected events display in token format. It can be combined with TEXT value. If present, the detail option indicates that all tokens are displayed.
ALTER Command Descriptions STARTTIME { BOF | NOW | TODAY | date time | time | offset { H | D | W } } specifies a start time for the search into logs. Any events before this time can not be selected. BOF start time is set to Beginning Of File. NOW start time is set to current time stamp. TODAY start time is set to today’s date, at 0:00:00 hour. date specific date. The following formats are valid: YYYY MM DD YYYY-MM-DD YYYY/MM/DD time specific time.
ALTER Command Descriptions STATUS [ OFF | 0..65535 ] when a value is set for STATUS, a status line is displayed every nn seconds when the distributor is searching and no events match the search criteria. OFF means no periodical status displays with the DUMPLOG command. Nevertheless, a status is forced every 5 minutes, but not shown to the user. This is to verify that the current position of the distributor has not passed the stop time attribute.
ALTER Command Descriptions time specific time. The following format is valid: HH [: MM [: SS] ] SYSTEM [ \system-name ] is the name of a system (node) from which events were generated. \system-name system name, in accordance with Tandem syntax. TEXT [ "text-string" ] is a particular text string. text-string any group of characters (max. 50). There is no case sensitivity. Considerations • • EMSAFLTR RESET attribute resets all filter attributes to their default values.
ASSIGN Command Descriptions ASSIGN The ASSIGN command changes, adds, and displays ASSIGN messages passed to a process initiated by the EMS Analyzer RUN command. ASSIGN [ logical-unit [, actual-file-name ] [, create-open-spec ] ] logical-unit name to which a file name or file attributes are assigned. The logical-unit requires one of the following: *.logical-file program-unit.
ASSIGN Command Descriptions pri-extent-size size of the first file extent to be allocated to the file (primary extent). The value is an integer in the range 1 through 65535. sec-extent-size size of the extents allocated to the file after the primary extent is allocated. The value is an integer in the range from 1 through 65535. exclusion-spec exclusion mode for logical-unit. It determines the circumstances in which other processes can access the file.
ASSIGN Command Descriptions CODE file-code assigns a file code to logical-unit. Specify file-code as an integer in the range 0 through 65535. If file-code is omitted, the file code is set to 0. REC record-size sets the length of records in logical-unit. Specify record-size a s an integer in the range 1 through 65535. BLOCK block-size sets the size of the data blocks used by logical-unit. Specify block-size as an integer in the range 1 through 65535.
ASSUME Command Descriptions ASSUME The ASSUME command sets the default object type, object name, or both for subsequent commands. The default object type is used when the object type is omitted from a command. The default object name is used when the object name is omitted from a command. If no default object name has been established and the object name is omitted from a command, a syntax error message occurs. A remote object name cannot be assumed.
CLEAR Command Descriptions If entered after the ASSUME command above, the following ASSUME command replaces the object-name part of the assumed object. The INFO command that follows displays information about the new assumed process. -> ASSUME $PASA -> INFO Object: $PASA (Appropriate Information) . . . CLEAR The CLEAR command clears the logical-file assignments made with the ASSIGN command, parameters set with the PARAM command, and alias names assigned with the ALIAS command.
COMMENT Command Descriptions Considerations • • During EMS Analyzer startup as the TACL parameter values and ASSIGN messages are read, use this CLEAR command to remove logical file assignments set with the ASSIGN command, the PARAM command, and the ALIAS command. This command does not affect TACL parameter values and ASSIGN messages after exiting from EMS Analyzer. Examples -> CLEAR ASSIGN SSV0 -> CLEAR ALL COMMENT Use the COMMENT command to add descriptive text to OBEY files.
CPUS Command Descriptions ON enables the display of confirmation messages. OFF disables the display of confirmation messages. Considerations Initially, confirmation messages are not displayed. Example The following example shows confirmation messages that are returned as a result of the CONFIRM ON command. -> CONFIRM ON CONFIRM ..... ON -> ALTER DISTRIBUTOR $DIS1, EVENTNUMBER 234 EMSA DISTRIBUTOR $DIS1 altered: EVENTNUMBER attribute -> PAGESIZE PAGESIZE .....
CPUS Command Descriptions . . . Summary Information Total Systems aaaaa Connected Systems bbbbb Total CPUs ccccc Up CPUs ddddd Explanation of Symbols sss system is the number and name of one of the systems that are now or were once connected to the network. nnnn,nnnn,nnnn,nnnn is the status of each processor in a system. 1 indicates that the processor is active. 0 indicates it is inactive. Period (.) represents a nonexistent processor.
DELAY Command Descriptions Examples -> CPUS displays summary information about all systems on the network. -> CPUS \C2 displays summary information about the system \C2. -> CPUS DETAIL displays both detailed and summary information about all systems on the network. DELAY The DELAY command suspends the EMS Analyzer process for a specified time interval. DELAY [ /OUT file-spec/ ] time /OUT file-spec/ causes any EMS Analyzer output generated for this command to be directed to specified file.
DETAIL ERROR Command Descriptions DETAIL ERROR The DETAIL ERROR command enables or disables the display of a full error description and suggested recovery action when an error is detected. DETAIL ERROR [ ON | OFF ] ON causes the display of detailed error information. OFF disables the display of detailed error information. Examples -> DETAIL ERROR ON -> start, cpu 1, pri 3738 EMSA E20331 The priority value must be in the range [1..199] Probable Cause The value specified for priority is not valid.
DISPLAYEXTCHAR Command Descriptions DISPLAYEXTCHAR The DISPLAYEXTCHAR command enables or disables the display of extended characters. DISPLAYEXTCHAR [ ON | OFF ] ON causes the display of extended characters. OFF disables the display of extended characters. This is the default. DUMPLOG The DUMPLOG command starts the search for the EMS events. DUMPLOG [ /OUT file-spec/ ] [ object-spec ] /OUT file-spec/ directs any EMS Analyzer output generated for this command to the specified file.
DUMPLOG Command Descriptions Examples -> DUMPLOG DISTRIBUTOR $dist -> DUMPLOG /OUT OutDump/ DISTRIBUTOR $dist The following is a sample of output format text. -> DUMPLOG DISTRIBUTOR $DIST Searching events...
DUMPLOG Command Descriptions The following is a sample of output format token detail. -> DUMPLOG DISTRIBUTOR $DIST Searching events... -----------------------------------------------------------------------------Header Type: 1 Checksum: F Last Error: no error (0) Last Error Tkncode: (0,0,0) Max Field Version: 0 SSID: TANDEM.127.
ENV Command Descriptions ENV The ENV (environment) command displays the EMS Analyzer startup banner and the current settings of the program environment parameters. These parameters are set by other EMS Analyzer commands. ENV [ /OUT file-spec/ ] /OUT file-spec/ causes any EMS Analyzer output generated for this command to be directed to the specified file. Example -> ENV EMSA - T9671C30 - (01NOV91) (15DEC91) - 01/08/88 13:10:49 System \MTL Copyright Tandem Computers Incorporated 1991 Allow.............
FC Command Descriptions number if positive, is the line number of the command line to be fixed. If negative, the current command line number minus number is the line number of the command line to be fixed. character-string is the first few characters of the command line to be fixed. The most recent command line whose first characters match the string are fixed. Considerations • • • • • • If you use FC alone, the previous command is fixed (FC alone is the same as FC 1).
HELP Command Descriptions Examples -> FC ..STARFUS DISTRIBUTOR 4 .. DDIT inserting == deleting the letters RF and == the letter T ..STATUS DISTRIBUTOR 4 .. R$DIST $DIST ..STATUS DISTRIBUTOR $DIST .. is == replacing the 4 and spaces with == finally, just a carriage return == entered, and the command is executed HELP The HELP command displays the syntax and meaning of EMS Analyzer commands.
HISTORY Command Descriptions object-type is a valid object type. object-name is an existing EMS Analyzer supported object name. Considerations • • • • • If HELP is entered by itself, EMS Analyzer enters a menu-driven help mode that displays the available help options. Enter CTRL/Y to exit the menu-driven mode. HELP EMSA displays information about commands and objects supported by EMSA. HELP ALL gives same results. HELP [EMSA] command displays specific information about the specified command.
INFO Command Descriptions number is the number of command lines to be displayed. If omitted, the 10 most recently entered commands display. Considerations • EMS Analyzer history buffer is 1024 bytes in memory. The exact number of retrievable command lines depends on the length of the commands. • The command lines are saved in the history buffer exactly as they were entered, with the exception of the FC and ! commands.
INFO Command Descriptions Examples -> INFO DISTRIBUTOR $dist -> INFO /OUT OutInfo/ DISTRIBUTOR $dist The following is a sample of output of the INFO command used on EMS Analyzer’s own distributor with the default filter (EMSAFLTR). -> INFO DISTRIBUTOR $Z464 EMSA INFO DISTRIBUTOR $Z464 Distributor type. CONSUMER *Filter.......... $STING.EMSA.EMSAFLTR *Emslog.......... $0.#ZSPI Coll log......... $SYSTEM.ZLOG00.ZZEV0004 Current log...... $SYSTEM.ZLOG00.ZZEV0004 *EventDB......... *EventDB type....
INFO Command Descriptions • • • • • • • Dumplog Status is the number of seconds between each display of a status line showing information about current search, for example: Current position, Events passed, Events read. If the Dumplog Status is set to OFF, no status lines are displayed. Starttime is the time after which the events can be selected if they correspond to filter parameters. No events are selected before this time. Stoptime is the time after which no events are selected.
INFO Command Descriptions This is a sample of output for a consumer distributor that is not the EMS Analyzer distributor: DISTRIBUTOR $Z683 -> INFO DISTRIBUTOR $z681 EMSA INFO DISTRIBUTOR $Z681 Distributor type. CONSUMER *Filter.......... $SYSTEM.SYSTEM.EMSAFLTR *Emslog.......... $0.#ZSPI Coll log......... $SYSTEM.ZLOG00.ZZEV0174 Current log...... $SYSTEM.ZLOG00.ZZEV0174 Search criteria *Starttime... *Stoptime..
LOG Command Descriptions LOG The LOG command directs a copy of the input commands and the output generated by EMS Analyzer to a file. LOG [ logfile-spec [ ! ] ] logfile-spec if present, specifies the file to which the commands and output are written. If the logfile-spec has the form of a disk file name and the file does not exist, an EDIT file is created. If the named file is an existing disk file, the information is appended to the file.
OUT Command Descriptions /OUT file-spec/ causes any EMS Analyzer output generated for this command to be directed to the specified file. file-spec specifies the file commands are to be read from. NOECHO suppresses the echo of each line executed in the OBEY file. Use this option when speed is important. Considerations • If the file-spec is not fully qualified, the name is expanded using the default values supplied by the SYSTEM and VOLUME commands.
PAGESIZE Command Descriptions file-spec is the file to which the output listing is written to. If the file-spec has the form of a disk file name and the file does not exist, an EDIT file is created. If the named file is an existing disk file, the output is appended to the file. If file-spec is omitted, the output destination is restored to the setting it had at startup time. ! purges the specified file and creates a new file of the same name.
PAGESIZE Command Descriptions Consideration If both TERMINAL and PRINTER are omitted, TERMINAL is assumed.
PARAM Command Descriptions PARAM The PARAM command is used to change, add, and display PARAM values that are passed to a process initiated by the EMS Analyzer RUN command. PARAM [ param-name [ param-value ] ] param-name is a user defined name to be assigned a value. The name contains from 1 to 31 alphanumeric characters, including hyphen (-) and circumflex (^). param-value is the value assigned to param-name. Considerations • • Leading and trailing blanks are deleted in the param-value.
PAUSE Command Descriptions Examples -> PARAM EMSA^DEBUG^ENABLE ON -> PARAM PARAM EMSA^DEBUG^ENABLE .ON. PAUSE The PAUSE command suspends EMS Analyzer and allows the terminal to be used by another process. When you invoke a process during an EMS Analyzer session through the RUN command, you can use the Break key to suspend the process and reactivate EMS Analyzer. Once in EMS Analyzer, you can use the PAUSE command to return control of the terminal to the other process.
RUN Command Descriptions Examples -> REPEAT 5 STATUS DISTRIBUTOR $DIST; DELAY 2:00 -> ALIAS DUMP DUMPLOG DISTRIBUTOR $DIST -> REPEAT DELAY 5:00 -DUMP RUN The RUN command initiates the execution of other programs from EMS Analyzer. Many programs can be run from EMS Analyzer, including EDIT, PUP, CUP, FUP, ERROR, NETMON, and DIAG6100. EMS Analyzer is suspended while the other program runs, and reactivates when the other program terminates.
SETPROMPT Command Descriptions (for VERSION) causes the program file VER to be run rather than execution of the VERSION command. Examples -> -> -> -> RUN MYPROG /NOWAIT/ CUP /IN INFILE, OUT $S.#LP1/ EDIT FILE1;XVS F ERROR 48 SETPROMPT The SETPROMPT command allows you to chose the prompt setting. SETPROMPT [ /OUT file-spec/ ] { [ NO ] prompt-option [, [ NO ] prompt-option ] ... } { ALL [, [ NO ] prompt-option ] ... } { NONE [, prompt-option ] ...
START Command Descriptions REVERSE displays the prompt in reverse video. SYSTEM displays the current system name. VOLUME displays the default volume and subvolume names. ALL enables all prompt-options. NONE disables all prompt-options. Considerations • The REVERSE and DIM options can be used only on a Tandem 6530 or 6520 terminal or a device operating as a 6530 emulator.
STATUS Command Descriptions object-spec designates the object to be started. If object-type is omitted, DISTRIBUTOR is assumed. If object-name is omitted, EMS Analyzer provides a name to the DISTRIBUTOR process. An ASSUME command is automatically done to assume the object-type DISTRIBUTOR and the new object-name. PRI pri-number indicates the priority at which the distributor is going to run. If omitted, the distributor will run at the same priority as EMS Analyzer.
STATUS Command Descriptions Considerations Information provided by this command is similar to what EMSDINFO provides at the TACL prompt. Examples -> STATUS DISTRIBUTOR $DIST -> STATUS /OUT OutStus/ DISTRIBUTOR $DIST This is a sample of output for a consumer distributor (collector mode). -> STATUS DISTRIBUTOR $Z467 EMSA STATUS DISTRIBUTOR $Z467 Distributor type. PPID............. Priority......... Current position. CONSUMER Filter..... $STING.EMSA.EMSAFLTR 02,074 BPID.......
STATUS Command Descriptions • • • • • • • • Coll log is the name of the current active EMS log file. This is displayed only if the distributor is in collector mode. Current log is the name of the EMS log file in which the distributor is currently positioned. Coll state is one of the following distributor states, which are associated with the named source collector: UNUSED, IDLE, FETCHING EVENT, PERFORMING STATUS or POSITIONING. This displays only if the distributor is in collector mode.
STATUS Command Descriptions This is a sample of output for a consumer distributor (file mode). -> STATUS DISTRIBUTOR $Z467 EMSA STATUS DISTRIBUTOR $Z467 Distributor type. PPID............. Priority......... Current position. CONSUMER Filter..... $STING.EMSA.EMSAFLTR 02,074 BPID....... NOT CONFIGURED 149 Last error. 0 91JUL25, 09:12:28 Emslog.............. $0.#ZSPI Event filtered...... 2 Event total......... 16 Event processing.... ACTIVATED This is a sample of output for a forwarding distributor.
STOP Command Descriptions This is a sample of output for a printing distributor. -> STATUS DISTRIBUTOR $Z123 EMSA STATUS DISTRIBUTOR $Z123 Distributor type. PRINTING PPID............. 01,066 Priority......... 148 Emslog.............. Coll log............ Current log......... Coll state.......... Coll IO status...... Record address...... Coll event filtered. Coll event total.... Coll event logging.. Filter..... BPID....... NOT CONFIGURED Last error. 0 $0.#ZSPI $SYSTEM.ZLOG00.ZZEV0004 $SYSTEM.ZLOG00.
SYSTEM Command Descriptions Examples -> STOP DISTRIBUTOR $dist -> STOP /OUT OutStop/ DISTRIBUTOR $dist SYSTEM The SYSTEM command designates the default system name for all file name and object name expansion. SYSTEM [ /OUT file-spec/ ] [ \system-name ] /OUT file-spec/ causes any EMS Analyzer output generated for this command to be directed to the specified file. \system-name is the system name that is to become the default system name.
VERSION Command Descriptions amount of time that can be specified is 5965:13:56:47. The smallest amount of time that can be specified is 1.00 seconds. For more detail about the time value, type HELP TIME. Consideration TIMEOUT functions in the same manner as pressing the Break key: it cancels any outstanding operation. Use this command with caution. Examples -> -> -> -> TIMEOUT 5 TIMEOUT 11:22.31 TIMEOUT 22:31.50 TIMEOUT ! ! ! ! 5 seconds 11 hours, 22 minutes and 31 seconds 22 minutes, 31.
VOLUME Command Descriptions Examples -> VERSION DISTRIBUTOR $dist -> VERSION /OUT OutVers/ DISTRIBUTOR $dist, DETAIL This is a sample of output format without detail. -> VERSION DISTRIBUTOR $Z860 VERSION \SUPPORT.$Z860 : EMSDIST - T9632C20 - 24JUN91 - EMS Distributor • • • EMSDIST is the product name of the specified distributor. T9632C20 is the product number. 24JUN91 is the product release date. This is a sample of output format with detail.
VOLUME Command Descriptions • • If volume-name is omitted and subvolume name is specified, the current default volume remains unchanged. Similarly, if volume-name is specified and subvolume-name is omitted, the current default subvolume remains unchanged. If both are omitted, the default volume and subvolume are restored to their initial settings from the beginning of EMS Analyzer session. A system name cannot be specified in the VOLUME command. Examples -> VOLUME $MKT -> VOLUME $MKT.
A Event Data File Record Definition Enscribe Database File Table A-1 shows the DDL record definition of event data files created by EMS Analyzer. Table A-1. EMS Analyzer Event Data File Record Definition - Enscribe Database (page 1 of 2) Field Name Data Type Description gentime BINARY 64 Corresponds to the generation time from the event. It corresponds to the ZEMS-TKNGENTIME token of the event buffer. There is no default value.
Enscribe Database File Event Data File Record Definition Table A-1. EMS Analyzer Event Data File Record Definition - Enscribe Database (page 2 of 2) Field Name Data Type Description console-print CHARACTER 1 Corresponds to the ZEMS-TKN-CONSOLEPRINT token of the EMS Analyzer event buffer. The default value is space. emphasis CHARACTER 1 Corresponds to the ZEMS-TKN-EMPHASIS token of the EMS Analyzer event buffer. It will have the value “T” if this is a critical; otherwise, it is “F”.
CSV File Event Data File Record Definition CSV File Table A-2 shows the CSV record definition of event data files created by EMS Analyzer. Table A-2. EMS Analyzer Event Data File Record Definition - CSV File (page 1 of 2) Field Name Data Type Description year BINARY 16 The year of gentime field. There is no default value. month BINARY 16 The month of gentime field. There is no default value. day BINARY 16 The day of gentime field. There is no default value.
CSV File Event Data File Record Definition Table A-2. EMS Analyzer Event Data File Record Definition - CSV File (page 2 of 2) Field Name Data Type Description console-print CHARACTER 1 Corresponds to the ZEMS-TKN-CONSOLEPRINT token of the EMS Analyzer event buffer. The default value is space. emphasis CHARACTER 1 Corresponds to the ZEMS-TKN-EMPHASIS token of the EMS Analyzer event buffer. It will have the value “T” if this is a critical; otherwise, it is “F”. The default value is space.
B EMSASSID File You can use this file as a reference to look up the subsystem IDs (SSIDs) for the most common Tandem subsystems and to include your own customer subsystem IDs. This file is installed on the same subvolume as the EMS Analyzer program (refer to Section 2, Installation). If you are running EMS Analyzer, you can access this file by issuing an OBEY command: -> OBEY $vol.subvol.
EMSASSID File Event Management Service (EMS) Analyzer Manual–133700 B- 2
C EMSACSTM File COMMENT COMMENT EMS Analyzer custom file COMMENT SETPROMPT all, no volume allow all errors detail error on alias F1 Info alias F2 Status alias F3 Dumplog alias F5 Alter, text alias SF5 Alter, text alias F7 enform alias F9 Alter, eventtype critical alias SF9 Alter, eventtype alias F10 Alter, eventdb enscribe emsadbe purge alias SF10 Alter, eventdb alias F11 Alter, format token alias SF11 Alter, format alias F15 Alter, confirm on start distributor , cpu 0, pri 100 alter, emslog $0 alter, fil
EMSACSTM File Event Management Service (EMS) Analyzer Manual–133700 C- 2
D Command Summary Table D-1.
Command Summary Table D-1. EMS Analyzer Command Summary (page 2 of 2) Commands Description OUT Redirects EMS Analyzer displays to a designated location, such as terminal, spooler, or out file PAGESIZE Sets the terminal screen size and printer page size PARAM Changes, adds, and displays PARAM values that are passed to a process initiated by EMS Analyzer RUN command PAUSE Suspends EMS Analyzer and releases the terminal for use by another process.
E Error Messages This section lists warnings and error messages. NonStop Kernel file system messages are described in the Guardian Procedure Errors and Messages Manual. System-supplied Values In the warning and error messages, system-supplied values are shown in one of these ways: • • • Angle brackets and an italicized value A series of slashes (\\\\\\\\\\\) A slash and an asterisk (\*) Warning Messages The following listing defines the warnings you might encounter when using EMS Analyzer.
Error Messages Error Messages EMSA 30501 End of file was reached on EMS source file Cause. The distributor reached an end-of-file position before another event message passed the filter. Recovery. This is a warning. No specific action is required. Error Messages The following listing defines the errors encountered and displayed when using EMS Analyzer. EMSA 20001 Maximum number of nested OBEY files () exceeded Cause. When an OBEY file invokes another OBEY file this is called nesting.
Error Messages Error Messages EMSA 20004 No more than numbers are allowed in this list Cause. Too many comma-separated values have been specified in a list of numbers. Recovery. Remove the extra values from the list. EMSA 20006 This command is only valid with a terminal for an infile Cause. The specified command will not function properly unless the EMSA input file is a terminal. Recovery. Remove the command from the OBEY file or do not use the command while communicating with EMSA via a process.
Error Messages Error Messages EMSA 20034 Input string is too long Cause. You typed in too much text for one command line. Recovery. Put separate commands on separate command lines or issue one command for each object name. EMSA 20035 Command line does not exist Cause. The command issued attempted to refer to a command that either no longer exists or never existed in the history buffer. Recovery. Correct the command to refer to a command in the history buffer.
Error Messages Error Messages EMSA 20049 CPU is unavailable Cause. The specified CPU is currently unavailable. Recovery. Use the CPUS command to determine which CPUs are currently available for a given system. EMSA 20050 System is unavailable Cause. The specified system is currently unavailable. Recovery. Use the CPUS DETAIL command to determine which systems are currently available. EMSA 20051 Subsystem is not supported Cause.
Error Messages Error Messages EMSA 20054 NEWPROCESS error 2: No process control block available Cause. Too many processes are running on the system right now. Recovery. Consult your system manager. EMSA 20055 NEWPROCESS error 4: Unable to allocate map Cause. System resources are currently unavailable. Recovery. Consult your system manager. EMSA 20056 NEWPROCESS error 6: File format error on Cause. The program file is invalid. Recovery. If the program resides on $SYSTEM.SYSTEM or $SYSTEM.
Error Messages Error Messages EMSA 20060 NEWPROCESS error 10: Unable to communicate with system monitor process Cause. The system monitor process is currently unavailable. Recovery. Usually no recovery is necessary. If further problems exist, then consult your system manager. EMSA 20061 NEWPROCESS error 12: Program file and library file cannot be the same Cause. The program and library files are identical. Recovery. Reissue the command with the correct library name.
Error Messages Error Messages EMSA 20069 Invalid help command combination specified Cause. The combination of parameters to the HELP command are invalid. Either the subsystem does not support the command or the object type is not applicable to the command. Recovery. Type the command HELP to determine valid subsystem/command combinations or HELP to determine the valid subsystem/command/object-type combinations. EMSA 20080 EMSA subsystem has no object type Cause.
Error Messages Error Messages EMSA 20084 Quoted string can be no more than characters long Cause. This instance of a quoted string can contain only characters. Recovery. Retype the command with a shorter quoted string length. The FC command can be used to accomplish this. EMSA 20085 - can be no more than characters long Cause. The expected
- is too long. Recovery. Shorten the
- to be within the required length limit.
Error Messages Error Messages EMSA 20090 value must be from to Cause. The specified value is out of range. Recovery. Specify a value within range. EMSA 20091 This command is not allowed when a repeat command has been issued. Cause. A REPEAT command was specified prior to the execution of this command. Recovery. Do not specify the REPEAT command in conjunction with this command. EMSA 20092 Repeat command stack overflow, command not available. Cause.
Error Messages Error Messages EMSA 20096 NEWPROCESS error 5: File error on swap file Cause. The swap file location is invalid. The file error number details the cause of the error. Recovery. Select a valid swap file location. Determine the appropriate action from the file-system error number. EMSA 20097 Duplicate command modifier Cause. The modifier is a duplicate of one already specified on the command line. Recovery. Contact your Tandem representative.
Error Messages Error Messages EMSA 20104 A recursive alias has been detected Cause. An alias that refers to itself directly or via other aliases has been invoked. Recovery. Use the CLEAR ALIAS command to delete the alias that causes the recursive loop. EMSA 20105 Alias expansion has overflowed the input buffer Cause. Expanding the aliases contained on this line will produce more text than will fit into the input buffer. This can be caused by a recursive alias. Recovery.
Error Messages Error Messages EMSA 20112 Maximum number of allowable errors exceeded Cause. This message informs the user that processing has been terminated because the maximum number of errors set by the ALLOW command has been exceeded. Recovery. Either correct the conditions that cause the errors or increase the number of allowable errors with the ALLOW command. EMSA 20113 Maximum number of allowable warnings exceeded Cause.
Error Messages Error Messages EMSA 20118 NEWPROCESS error 18: Process/device subtype is illegal Cause. A specified device was of the wrong type. Recovery. Consult documentation on the program you are trying to run to determine which devices are legal. EMSA 20119 NEWPROCESS error 19: Process/device subtype is not the same as its existing sibling Cause. There is a subtype mismatch. Recovery. Consult your system manager. EMSA 20200 did not expand to any EMSA supported object names Cause.
Error Messages Error Messages EMSA 20203 INTERNAL ERROR: Illegal value: Call: Param: Cause. An illegal value was supplied as a parameter to a procedure. Recovery. Contact your Tandem representative. EMSA 20204 Object name is too long Cause. The specified object name is too long. Recovery. Re-enter the object name. EMSA 20205 INTERNAL ERROR: A call to PUTPOOL failed Cause. A call to the NonStop Kernel procedure PUTPOOL failed. Recovery. Contact your Tandem representative.
Error Messages Error Messages EMSA 20209 The must be positive Cause. The specified unit must be a positive number. Recovery. Use the FC command to change the number to a positive value. EMSA 20210 Invalid terminal type for REVERSE and/or DIM option Cause. The SETPROMPT command with REVERSE and/or DIM option was specified for a terminal other than a 6530 or 6520. Recovery. Use the FC command to remove the REVERSE and/or DIM option and reissue the command.
Error Messages Error Messages EMSA 20214 Exceeded max number of chars allowed on the RUN command line Cause. The number of characters following the name of a program file exceeds the maximum number allowable. Recovery. Do not include more than two lines of text on the RUN command line. EMSA 20215 Expecting a blank Cause. A blank character was expected at this point in the command. Recovery. Use the FC command to fix the command to include a blank.
Error Messages Error Messages EMSA 20301 Error occurred in Guardian proc Cause. There was a major error in calling one of the Guardian procedures. Recovery. Contact your Tandem representative. EMSA 20302 File system error occurred while trying to purge file Cause. The file could not be purged because of a file-system error. Recovery. Use the ERROR program for an explanation of the file-system error.
Error Messages Error Messages EMSA 20307 File system error occurred while trying to cancel a request Cause. The attempt to cancel an I/O pending operation on the distributor failed. Recovery. Try to perform other commands on this distributor. If there is some errors, stop the distributor (see STOP command) and restart (see START command) another one. EMSA 20308 This is not a collector device Cause. The specified device is not a collector. Recovery. Specify a collector device.
Error Messages Error Messages EMSA 20312 Invalid SSID Cause. The specified SSID is not valid. All the following attributes on the command line, if there is some, are not altered. Recovery. At the command prompt, type “OBEY EMSASSID”. This will give you all valid SSIDs (owner.subsystem number). EMSA 20313 Sequence problem with start and stop time Cause. The start time and stop time attributes are not sequenced properly, that is the start time is after the stop time. Recovery.
Error Messages Error Messages EMSA 20317 Event messages for this timestamp are not available yet Cause. You specified a start time for which EMS events have not been generated yet. Recovery. Specify an earlier start time value. EMSA 20319 There must be an EMSLOG to do this command Cause. A source file (EMSLOG attribute) has to be specified before actually searching for particular events. Recovery. Specify a value for EMSLOG attribute (collector or EMS log file).
Error Messages Error Messages EMSA 20323 Event messages for this timestamp are not in this log file Cause. The specified start time is too late for the currently specified EMS log file. That is, the last record of the file is before the specified start time. Recovery. Specify an earlier start time. EMSA 20324 This command can be used only with EMSA current distributor Cause. The specified command can be applied only on current EMSA distributor. Recovery.
Error Messages Error Messages EMSA 20328 The maximum extent value must be in the range [0..978] Cause. The specified maximum extent value is not valid. Recovery. Specify a value in the range [0..978]. EMSA 20329 SPI error occurred while trying to get Cause. The event could not be decoded because of an SPI error. Recovery. Contact your Tandem representative. EMSA 20330 Same option specified twice in input command line Cause. There was an option that was specified twice in the command.
Error Messages Error Messages EMSA 30301 The configuration was not sent to the distributor because it is already configured that way Cause. The distributor is already configured the way you specified it. Recovery. No specific action required. EMSA 30302 The EMSDIST program file name was not found Cause. The distributor cannot be started since the program file name EMSDIST cannot be found. Recovery. Report this problem to your System Manager. EMSA 30303 Invalid FNB Cause. The FNB is not valid.
Error Messages Error Messages EMSA 30307 Filter parameter was not found in configuration Cause. The filter parameter was not removed or replaced from configuration because it was not there. Recovery. Contact your Tandem representative. EMSA 30310 The list of EMS source collector is full Cause. The maximum number of EMS source collectors loaded in configuration is reached. Recovery. EMS Analyzer allows only one EMS source collector at a time.
Error Messages Error Messages EMSA 30315 The specified process is not a distributor process Cause. This process does not have EMSDIST as program file name. Recovery. No specific action required. EMSA 30316 The distributor could not be started Cause. There was a problem while creating the new distributor. Recovery. Contact your Tandem representative. EMSA 30317 The system cannot be accessed Cause. There was a problem in accessing the system for information. Recovery.
Error Messages Error Messages EMSA 30502 Event messages for this timestamp are not available anymore Cause. You specified a start time for which EMS events have not been kept in EMS log files. They are not available anymore. Recovery. The distributor is now positioned by default at BOF. You can do research from BOF, or specify a later start time value. EMSA 30503 Event messages for this timestamp are not available yet Cause. You specified a start time for which EMS events have not been generated yet.
Error Messages Error Messages EMSA 31004 Invalid token in command message Cause. The distributor has received a command message with an unneeded or unrecognized token. Recovery. Try the command again and if the problem persists, contact your Tandem representative. EMSA 31005 Invalid token value in command message Cause. The distributor has received a command message with a bad token: the token value is invalid. Recovery.
Error Messages Error Messages EMSA 31014 Command message not allowed in this context Cause. The distributor has received a command message that is not allowed in this context. Recovery. Contact your Tandem representative. EMSA 31015 Required token missing in command message Cause. The distributor has received a command message that lacks a required token. Recovery. Try the command again and if the problem persists, contact your Tandem representative.
Error Messages Error Messages EMSA 31020 Filter could not be loaded by distributor Cause. The distributor could not load the filter. Recovery. Make sure the FILTER attribute is a valid filter file. If the problem persists, contact your Tandem representative. EMSA 31022 Filter parameter missing Cause. One or more filter parameter tokens are missing. Recovery. Try the command again and if the problem persists, contact your Tandem representative.
Error Messages Error Messages EMSA 31027 The collector is not associated with the distributor Cause. The collector is not associated with the distributor and cannot be disconnected. Recovery. Contact your Tandem representative. EMSA 31031 Event log (EMSLOG) cannot be accessed Cause. The distributor cannot access the event log. Recovery. Make sure the EMSLOG attribute is a valid EMS log file. EMSA 31032 Event messages for this timestamp are not in this log file Cause.
Error Messages Error Messages EMSA 31036 TEXTOUT or target cannot be accessed Cause. Either a printing distributor cannot access a TEXTOUT destination or a forwarding distributor cannot access a target collector. Recovery. Make sure the TEXTOUT or target destination is valid and can be reached. EMSA 31037 TEXTOUT destination already configured Cause. The TEXT destination is already in the list of print destinations for this printing distributor and cannot be added. Recovery.
Error Messages Error Messages EMSA 31043 Pool space for additional collector unavailable Cause. Another collector cannot be added: there is no pool space available. Recovery. Contact your Tandem representative. EMSA 31044 No event source (EMSLOG) specified Cause. The distributor has no event-message source collector or log-file source. Recovery. Specify a valid EMSLOG attribute value (collector or EMS log file). EMSA 31045 The collector (EMSLOG) is invalid Cause.
Interprocess Communication Warning Messages Error Messages EMSA 31051 Next log file unavailable or inaccessible Cause. The log file that should be next is unavailable or inaccessible. The distributor is using the file whose name is next in the queue of log-file names. Recovery. Report this problem to your System Manager. Interprocess Communication Warning Messages The following listing defines the interprocess communication warning messages you might encounter when using EMS Analyzer.
Interprocess Communication Error Messages Error Messages -00025 Object has no subordinates Cause. A command using the SUB modifier was issued but, no subordinate objects were found. This error is applicable only when the SUB modifier contains the SUBONLY value, or the value of a specific object type. Recovery. This is a warning. No action is necessary.
Interprocess Communication Error Messages Error Messages -00006 Command sequence invalid for Cause. The command sequence is invalid. A command was issued and cannot be executed because of the current activity or state of the target object. Recovery. This can be a warning or an error. Refer to the subsystem specific reference manual for the subsystem with which you are communicating for information about how that subsystem handles this error condition.
Interprocess Communication Error Messages Error Messages -00012 Maximum Limit Exceeded: for Cause. A fixed limit or configuration limit was exceeded. Generally, this error is used to report any overrun of a limit, including internal control blocks or tables. Recovery. The recovery action is dependent on the limit exceeded. Refer to the subsystem specific reference manual for the subsystem with which you are communicating for information about recovery from this error.
Interprocess Communication Error Messages Error Messages -00018 Object type is not supported by this subsystem Cause. This object type is not supported. An invalid, unknown, or unsupported object type was encountered. Recovery. Refer to the subsystem specific reference manual for the subsystem with which you are communicating for information about the object types supported by that subsystem. -00019 Invalid object name: Cause. An invalid object name template was found in the command buffer.
Interprocess Communication Error Messages Error Messages -00023 Internal Error: SPI error on (Tnm: ) Cause. An error having to do with a call to an SPI procedure occurred. Recovery. Contact your Tandem representative. -00024 Internal Error: Invalid subsystem ID: Owner: Number: Version: Cause. The subsystem ID specified (using a call to SSINIT) in the request is invalid. Recovery. Contact your Tandem representative.
Interprocess Communication Error Messages Error Messages -00029 Internal Error: Required token Missing: Token Code: (tnm:) Cause. A command was issued in which a required token is missing. Recovery. Contact your Tandem representative. -00030 Internal Error: Invalid Value: (tnm:, Offset: ) for Cause. An illegal value was encountered in a supported token. Recovery. Recovery action is dependent on the token in error and on the value specified in that token.
Interprocess Communication Error Messages Error Messages -00033 Internal Error: Empty SPI response Cause. There was no more data to display in response to a continuation request from EMS Analyzer to the subsystem. Recovery. Contact your TANDEM representative. -00034 Attribute is required in conjunction with for
Interprocess Communication Error Messages Error Messages -00038 Command power level too weak for the condition of object
Interprocess Communication Error Messages Error Messages -00993 No TLE was available for command timeout Cause. No TLE available for command timeout. Recovery. Contact your system manager. -00994 SIGNALTIMEOUT error; could not set command timeout Cause. The command timeout could not be set. Recovery. Contact your Tandem representative.
Interprocess Communication Error Messages Error Messages -00995 Internal Error: invalid name specified in MANAGER or OBJNAME token Cause. The subsystem’s manager process could not be accessed; invalid server name specified in MANAGER or OBJNAME token. Recovery. Contact your Tandem representative. -00998 Internal Error: Server version could not be obtained from subsystem Cause. The server version is not valid. Recovery. Contact your Tandem representative.
Index A ALIAS command 5-4 ALLOW command 5-6 ALTER command 5-7 Architecture 1-2 ASSIGN command 5-14 ASSUME command 5-17 Attributes and attribute values 4-2 Audience ix B Background mode 3-5 Batch mode 3-5 Break key 3-8 C CLEAR command 5-18 Commands abbreviating 5-4 abbreviations 3-8 ALIAS 5-4 ALLOW 5-6 ALTER 5-7 ASSIGN 5-14 ASSUME 5-17 CLEAR 5-18 COMMENT 5-19 components 4-1 CONFIRM 5-20 CPUS 5-20 DELAY 5-22 DETAIL ERROR 5-23 DISPLAYEXTCHAR 5-24 displaying again 5-3 DUMPLOG 5-24 ENV 5-27 exclamation point
D Index Custom configuration file editing 3-12 example C-1 reading 2-8 Customer subsystem IDs B-1 D Data file record definition A-1 DDL default dictionary 2-8 Debugging with EMS Analyzer 3-30 Default filter 3-19 DELAY command 5-22 DETAIL ERROR command 5-23, 5-24 Disk file names 4-4 DISPLAYEXTCHAR command 5-24 Distributor assuming 5-17 getting status 3-18 modifying priority 3-18 starting 3-17 stopping 3-17 Downloading files to a workstation 3-38 DUMPLOG command 5-24 DUMPLOG STATUS attribute 3-30 E EMS An
H Index Files (continued) downloading 3-38 EMSACSTM C-1 EMSASSID 5-10, B-1 Enscribe database A-1 help and error text location 2-8 installation 2-2 log 5-34 names 4-4 output 3-26 subsystem ID reference file 5-10 using ASSIGNs 5-14 Filter parameters, resetting 3-21 parameters, setting 3-20 parameters, viewing 3-21 Filter, default 3-19 Function keys configuring 3-9 setting 5-4 H HELP online, command mode 3-12 online, menu mode 3-13 HELP command 5-28 Help key 3-8 HISTORY command 5-30 I INFO command 5-31 INS
S Index RUN command 5-40 S Searching for events, command for 5-24 SETPROMPT command 5-41 START command 5-42 STATUS attribute 3-30 distributor 3-18 STATUS command 5-43 STOP command 5-47 Strings 4-3 Subsystem ID reference file 5-10 Subsystem IDs B-1 SYSTEM command 5-48 System requirements 2-1 T Time 4-4 TIMEOUT command 5-48 Timeout, modifying 3-11 V VERSION command 5-49 VOLUME command 5-50 W Warning messages lists of E-1 setting number to allow 5-6 Workstation, downloading to 3-38 Event Management Serv
