HP NonStop ASAP Server Manual Abstract HP NonStop™ Availability Statistics and Performance (ASAP) is an availability, state, and performance statistics collection infrastructure for the HP NonStop operating system and application resources. Product Version ASAP SE30V2.8 Supported Release Version Updates (RVUs) This manual supports D42.00 and all subsequent D-series RVUs, G06.00 and all subsequent G-series RVUs, and H06.
Document History Part Number Product Version Published 522303-002 ASAP SE30V2 October 2003 522303-004 ASAP SE30V2 January 2004 522303-005 ASAP SE30V2.5 October 2004 522303-006 ASAP SE30V2.7 May 2006 522303-007 ASAP SE30V2.
HP NonStop ASAP Server Manual Glossary Index What’s New in This Manual vii Manual Information vii New and Changed Information Figures Tables vii About This Manual xv Audience xvi Manual Organization xvii Related Resources xvii Notation Conventions xvii 1.
1. Introduction to Availability Statistics and Performance (ASAP) (continued) Contents 1.
3. Running ASAP Contents 3.
4. Using Discrete Object Thresholds (DOTs) (continued) Contents 4. Using Discrete Object Thresholds (DOTs) (continued) TMF Entity-Supported Objective Attributes 4-28 5.
6. ASAP Conversational Interface Commands (continued) Contents 6.
B. ASAP Data Definitions (continued) Contents B.
Tables Contents Tables Table 3-1. Table 6-1. Table 6-2. Table 6-3. Table 6-4. Table 6-5. Table 6-6. Table 6-7. Table 6-8. Table 6-9. Table 6-10.
Contents HP NonStop ASAP Server Manual—522303-007 viii
What’s New in This Manual Manual Information HP NonStop ASAP Server Manual Abstract HP NonStop™ Availability Statistics and Performance (ASAP) is an availability, state, and performance statistics collection infrastructure for the HP NonStop operating system and application resources. Product Version ASAP SE30V2.8 Supported Release Version Updates (RVUs) This manual supports D42.00 and all subsequent D-series RVUs, G06.00 and all subsequent G-series RVUs, and H06.
New and Changed Information What’s New in This Manual • • • A new Query command was added. For more information, see the following sections: • • Query Statistics Gathering Process on page 1-13 QUERY Command on page 6-73 A new SET TCP ON|OFF option has been added to enable the TCP entity. For more information, see TCP entity-option on page 6-120. A new SET QUERY ON|OFF option was added to enable the Query entity.
New and Changed Information What’s New in This Manual • • • • • • • • • • • • You can now secure clients settings. A Set Password button has been added to the General tab of the ASAP Client Properties window. This button displays a dialog box that allows you to protect various property sheets with a password (and lock functions) in the ASAP environment. For more information, see the ASAP Client Manual. Client/Server EDL version checking is now performed automatically.
New and Changed Information What’s New in This Manual ° ° ° ° • Write only aggregate file records to the historical database. Use wild-card file names to specify files to be monitored. Monitor OSS files by specifying the OSS pathname. Specify custom event numbers for specific objectives using the RANK command. Custom event numbers in the range 6000 through 9999 are available for this purpose. The OSS Permissions attribute has been added to file records.
New and Changed Information What’s New in This Manual • • • Added GOAL and RANK Usage Considerations on page 4-7 to further explain how to use the RANK command. Added EMS Event Considerations on page 4-7 to explain the options you have in ASAP for working with EMS events. Added the STATUS and NOEMS options to the rankspec parameter of the RANK command.
New and Changed Information What’s New in This Manual ° PROCESS Command on page 6-66 Note. The PROCESS command in ASAP Release 1 has become PROCESSBUSY in ASAP Release 2. The Selected Process function that PROCESS now performs is new to ASAP Release 2.
New and Changed Information What’s New in This Manual • ° ° ° ° PROCESS SPOOLER TAPE TMF For File, Process, RDF, Spooler, Tape, TMF entities: ° ° Added statistics definitions in DDL Section Definitions on page B-1 Updated DDL Section Record Declarations on page B-28 HP NonStop ASAP Server Manual—522303-007 xv
New and Changed Information What’s New in This Manual HP NonStop ASAP Server Manual—522303-007 xvi
About This Manual This manual describes these Availability Statistics and Performance (ASAP) products: • The ASAP Server monitors, gathers, and analyzes system availability throughout a network of NonStop servers. System Entities are CPU, Comm, Disk, Expand, File, Hybrid1, Node, Process, Processbusy, Query, RDF, Spooler, System, Tape, TCP/IP, Telserv2, and TMF.
About This Manual Audience This manual also describes these important tools for your ASAP environment: • The Entity Definition Language (EDL) lets you describe an entity and its associated data attributes required for the ASAP Client, Server, and Extension. The system entities CPU, Disk, Expand, File, Hybrid, Node, Process, ProcessBusy, Query, RDF, Spooler, System, Tape, TCP/IP, Telserv, and TMF have entity definitions in the ASAP2SYS file. This file must not be altered.
About This Manual Manual Organization Manual Organization Section/Appendix Description 1 ASAP product overview 2 Installing ASAP on the server 3 Running the ASAP program 4 Using Discrete Object Thresholds (DOTs) 5 File and Process Monitoring 6 TCP and Telserv Monitoring 7 ASAP Conversational Interface commands A A sample standard Enform query and a sample ASAPCOL as an Enform Server B ASAP database data definitions and record layouts Related Resources This manual describes the ASAP Cli
About This Manual General Syntax Notation General Syntax Notation This list summarizes the notation conventions for syntax presentation in this manual. UPPERCASE LETTERS. Uppercase letters indicate keywords and reserved words. Type 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 computer type.
About This Manual General Syntax Notation | Vertical Line. A vertical line separates alternatives in a horizontal list that is enclosed in brackets or braces. For example: INSPECT { OFF | ON | SAVEABEND } … Ellipsis. An ellipsis immediately following a pair of brackets or braces indicates that you can repeat the enclosed sequence of syntax items any number of times.
About This Manual Notation for Messages !i,o. In procedure calls, the !i,o notation follows an input/output parameter (one that both passes data to the called procedure and returns data to the calling program). For example: error := COMPRESSEDIT ( filenum ) ; !i:i. !i,o In procedure calls, the !i:i notation follows an input string parameter that has a corresponding parameter specifying the length of the string in bytes.
About This Manual Notation for Management Programming Interfaces horizontally, enclosed in a pair of brackets and separated by vertical lines. For example: proc-name trapped [ in SQL | in SQL file system ] { } 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.
About This Manual !o. Notation for Management Programming Interfaces The !o notation following a token or field name indicates that the token or field is optional. For example: ZSPI-TKN-MANAGER token-type ZSPI-TYP-FNAME32.
1 Introduction to Availability Statistics and Performance (ASAP) The Availability Statistics and Performance (ASAP) software product provides an availability monitoring infrastructure for monitoring the availability and performance of: • • System object information—operational status and performance of NonStop systems Application information—user-defined application domain availability statistics The Entity Definition Language (EDL) lets you describe an entity and its associated data attributes, which is
Introduction to Availability Statistics and Performance (ASAP) • • • • • • • • ASAP Server Features Automatic host communication using the Client Server Gateway Performance and State icons propagated upward through tree view Hierarchical tree view of nodes, entities, objects, and applications Context-sensitive menus on graphs and grids allow data mining Encapsulated interface to Open Enterprise Management (OEM) Gateway Reporting of App, CPU, Disk, Expand, File, Node, Process, ProcessBusy, RDF, Spooler, S
Introduction to Availability Statistics and Performance (ASAP) • • • • ASAP Extension Features Automatic archival of Object History Provides network-wide performance and state history Normalized, allowing fast, ad hoc, real-time queries Can partition database across multiple disk volumes ASAP Extension Features • • • • • • • Easy-to-use API Domains of service Availability monitoring Metric calculation and generation Alerts based on user-defined objectives Data normalized in the ASAP Server database Fu
Introduction to Availability Statistics and Performance (ASAP) • • • • • • ASAP Hybrid Features Domains of service Availability monitoring Metric calculation and generation Alerts based on user-defined objectives Data normalized in the ASAP Server database on a NonStop server Full integration with the ASAP Client and Server ASAP Hybrid Architecture • • • • • • Monitors and Statistics Gathering agent Non-messaging data collection Shared memory segment counters Application Programmer Interface Multileve
Introduction to Availability Statistics and Performance (ASAP) Data Collection and Monitoring Data Collection and Monitoring ASAP monitors and reports high-level, real-time network availability and user-defined application availability from one or more nodes. Availability information is sent to one or more collection nodes within the network.
Introduction to Availability Statistics and Performance (ASAP) Availability Overview Availability Overview The ASAP Server collects state and performance information for System and Application entities. ASAP entities that report on performance and state information include: • • • • • • • • • • • Application domain statistics (through the optional ASAPX and ASAPH products) track the productivity, performance, and availability of customer-developed applications.
Introduction to Availability Statistics and Performance (ASAP) • • • • • • • • • Components of ASAP User selected Processes collects process availability information, such as CPU, PIN Pri, Busy, Process state, Wait State, and Pages used. RDF statistics, such as relative delay times, relative byte address of the record being processed, and sequence number of the audit or image file. Spooler availability information, such as jobs, open, hold, and print.
Introduction to Availability Statistics and Performance (ASAP) Components of ASAP Figure 1-1.
Introduction to Availability Statistics and Performance (ASAP) Presentation Interfaces Presentation Interfaces The basic ASAP product includes the ASAP Client and Server, shipped on two CDs. Conversational Interface The ASAP Conversational Interface (CI) provides a command interpreter so you can work directly from the collection system. The CI also provides command and control of the ASAP components. See Section 6, ASAP Conversational Interface Commands.
Introduction to Availability Statistics and Performance (ASAP) Command and Control ASAP performance information is stored in a structured real-time availability database that user programs can easily access. The structure of this normalized database is documented in each release of ASAP. To generate DDL data structures that you can use in your program for accessing the ASAP database, refer to the released file ASPDDLDB.
Introduction to Availability Statistics and Performance (ASAP) Collection Collection The Database Collector is a process pair that collects application and system availability information from system nodes throughout the network. Availability information records from remote monitors and SGPs throughout the network are received by the ASAP Collector process, which stores the data in the normalized ASAP database. User-defined partitions let multiple volumes share the I/O workload.
Introduction to Availability Statistics and Performance (ASAP) CPU Statistics Gathering Process CPU Statistics Gathering Process The remote ASAP Monitor starts the CPU SGP in each CPU of the monitored node. CPU SGPs are responsible for gathering CPU-level statistics, including CPU performance metrics, Operational state, and information about the busiest processes in their CPU. The CPU SGPs reports CPU-level information to the ASAP Monitor process.
Introduction to Availability Statistics and Performance (ASAP) Node Statistics Gathering Process Node Statistics Gathering Process Node SGPs collect Expand end-to-end node statistics for the Node entity. These processes use the Subsystem Programmatic Interface (SPI) to collect path information and traffic statistics between two Expand end nodes. The Node SGP gathers availability information, bundles it in a single message, and forwards it to the ASAP Collect process.
Introduction to Availability Statistics and Performance (ASAP) Tape Statistics Gathering Process Tape Statistics Gathering Process Tape SGPs collect Tape availability information. Tape availability information is obtained from the Media Serve process using the Subsystem Programmatic Interface (SPI). The availability information gathered is performance utilization and operational state. The Tape SGP reports on objective thresholds when they do not meet the userdefined values.
Introduction to Availability Statistics and Performance (ASAP) COLLECT/ASAPDB COLLECT/ASAPDB The ASAP database includes current and historical information about system performance and the operational status of system objects. The ASAP database is automatically created when the ASAP Collect process is first started.
Introduction to Availability Statistics and Performance (ASAP) HP NonStop ASAP Server Manual—522303-007 1- 16 COLLECT/ASAPDB
2 Installing ASAP on the Server Topic Page Task 1: Ensure Your System Meets Requirements 2-1 Task 2: Install ASAP Server Product Files 2-2 Task 3: Set Up ASAP Server 2-3 Task 4: Configure ASAP Components 2-12 Starting and Stopping ASAP 2-23 Task 1: Ensure Your System Meets Requirements To install ASAP Server, your system must meet these requirements: Hardware HP NonStop server. For more information, see the ReadMe file included with your RVU or software product revision (SPR) for ASAP.
Installing ASAP on the Server Task 2: Install ASAP Server Product Files Task 2: Install ASAP Server Product Files To install ASAP product files on the system, use the IPSETUP program on the ASAP installation CD. For more information on IPSetup, see the IPSetup help on the CD. 1. Put the ASAP installation CD in your workstation. • • If AutoRun is enabled on your workstation, IPSETUP starts automatically after you insert the CD.
Installing ASAP on the Server • • Task 3: Set Up ASAP Server To view release documentation when IPSetup closes, click the View Release Documentation checkbox. The Launch DSM/SCM Planner Interface check box is checked if you indicated before that you will manage the product with DSM/SCM. If you do not want to launch DSM/SCM when IPSetup closes, uncheck the check box. 12. Click Finish.
Installing ASAP on the Server Full Install on This Node Figure 2-1. ASPSETUP Main Menu, AsapInstall VST002.vsd Full Install on This Node The Node installation copies object files and configuration files to the $SYSTEM.SYSTEM location. The install process secures the files for network access, and creates the database DDL dictionary. To fully install and configure ASAP on a data collection node: 1. From the AsapInstall menu, select Full Install on this node; then press Return.
Installing ASAP on the Server Full Install on This Node For context-sensitive help on any field in the ASAP Local Install Configuration panel, put the cursor on that field and press Shift-Return. Figure 2-3 shows the result of pressing Shift-Return with the cursor on the ASAP Install subvolume field. ASPSETUP displays default values in uppercase when it displays the configuration panel.
Installing ASAP on the Server Full Install on This Node Figure 2-4. First Page of Output From the START FULL INSTALL Function VST004.vsd ASPSETUP displays an Asap Tacl window so you can monitor the progress of the installation on the collection node. During the installation, ASPSETUP: • • • • • • Performs security checks. Checks for a previous version of ASAP. If a previous version is found, the older version is renamed to $volume.ZASAPOLD.*. Checks for the existence of an ASAP database.
Installing ASAP on the Server Remote Monitor Install Figure 2-5. Completion Display From the START FULL INSTALL Function VST005.vsd 3. To confirm that the installation did not encounter any errors, scroll through the output in the Asap Tacl window. The Asap Tacl window is a SeeView window that scrolls automatically. To turn off the automatic scroll feature, press Delete-Line from a terminal or Ctrl-Delete from a workstation.
Installing ASAP on the Server Remote Monitor Install Figure 2-6. ASAP Help Text for Remote Monitor Install VST006.vsd Figure 2-7 shows a sample Remote Monitor Install page. Uppercase characters represent default values. Mixed case character entries are supplied by the user and have no default values. Figure 2-7. Remote Monitor Install Display With User Entries VST007.vsd You do not have to install both ASAP and the ASAP Extension (ASAPX) on remote nodes.
Installing ASAP on the Server Remote Monitor Install 2. Enter the ASAP installation location in the ASAP Install subvolume field. 3. Optionally, enter the ASAP Extension subvolume in the ASAPX Install subvolume field. 4. Enter a network user ID. 5. Enter the password for SUPER.SUPER. 6. Press Return to start the installation. ASPSETUP displays a menu of all the nodes in your network (Figure 2-8). 7.
Installing ASAP on the Server Remote Monitor Install ASPSETUP shuts down the remote monitors on the selected nodes, creates an installation OBEY file, and starts the remote installation process (Figure 2-9). Figure 2-9. Output From Remote Install VST009.vsd ASPSETUP displays an Asap Tacl window so you can monitor the progress of the installation on each node that you selected. The installation terminates if you exit SeeView while ASAP is being installed.
Installing ASAP on the Server Remote Monitor Install Figure 2-10. Sample Remote Install Completion Screen VST010.vsd 9. To confirm that the installation did not encounter any errors, scroll through the output in the Asap Tacl window. The Asap Tacl window is a SeeView window that scrolls automatically. To turn off the automatic scroll feature, press Delete-Line from a terminal or Ctrl-Delete from a workstation.
Installing ASAP on the Server Task 4: Configure ASAP Components Task 4: Configure ASAP Components To customize the ASAP configuration on your nodes, use this information about component configuration: • • • ASAP configuration file ASAP object files ASAP database Confirm ASAP Configuration Settings ASAPCONF, the ASAP configuration file, sets up configuration information specific to your and users’ sites.
Installing ASAP on the Server Confirm ASAP Configuration Settings You can use the ASAP configuration wizard, ASAPWIZ, as an alternative to manually creating an ASAPCONF file. To use the configuration wizard, change your volume to the ASAP installation subvolume and type RUN ASAPWIZ. The wizard determines the latest copy of ASAP installed on your system and prompts you with specific questions to properly configure ASAP in your environment.
Installing ASAP on the Server Confirm ASAP Configuration Settings You can also monitor database usage with the ASAP command interpreter DB command. If you do not allow ASAP to automatically retain data for a certain number of days, it is up to the user to manage the accumulated data so it doesn't fill up the disk drive.
Installing ASAP on the Server ASAP Object Files You may now run ASAP CI and enter MONITOR FILE and MONITOR PROCESS commands to configure the files and processes that ASAP will monitor. The ASAP Wizard has successfully completed. 2> ASAP Object Files The ASAP system consists of these files on $SYSTEM.SYSTEM: Object File Full Name Description ASAP ASAP Conversational Interface Starts and manages the Monitor and Collector programs, and displays the ASAP availability information.
Installing ASAP on the Server ASAP Object Files Object File Full Name Description ASAPTCP TCP Statistics Gathering Process (SGP) Gathers availability and statistics information for nine TCP/IP entities and three Telserv entities. ASAPTMF TMF Statistics Gathering Process (SGP) Gathers availability information for the TMF subsystem on the node. ASAPXSGP ASAP Statistics Gathering Process (SGP) Gathers service-level metrics about customer applications.
Installing ASAP on the Server ASAP Object Files period of time, or indefinitely. For more information about database maintenance options, see the SET RETAIN option on page 6-116. The ASAP Collect process is continuous. If a CPU fails, the backup Collect process automatically takes over so database access is always available. The ASAP database is a real-time normalized database and can be queried online.
Installing ASAP on the Server ASAP Object Files ASAPFIL Object File The ASAP Monitor starts the File SGP on its node if File is enabled. The ASAP Statistics Gathering (ASAPFIL) Process collects availability information for userselected files or subvolumes. The utilization counters gathered include percent file full, number of files in the subvolume, and number of partitions. For a complete list of file availability counters, see FILE Command on page 6-33.
Installing ASAP on the Server ASAP Object Files to-end node statistics. The statistics gathered are path information statistics and traffic statistics between two Expand nodes. ASAPNCP communicates directly with the Expand Manager process to obtain raw counters. For a complete list of node availability counters, see NODE Command on page 6-63. The Node SGP does not support monitoring or Discrete Objectives Thresholds (DOTs).
Installing ASAP on the Server ASAP Object Files Catalog MediaSRV server using the SPI interface to obtain the status and information about the tape devices and tape mount requests on the node. The utilization counters gathered include number of outstanding tape mounts and Label mode checks. For a complete list of Tape availability counters, see TAPE Command on page 6-136.
Installing ASAP on the Server Size the ASAP Database Subvolume ASAPXSGP is a standard ASAP SGP and is started and managed by ASAPMON. The ASAPX Library The optional ASAPX Library is made of four object files: Object File Description Installation ASAPXDLL A dynamic link library (DLL) containing the ASAPX API procedures Installed by the ASAPX installation process.
Installing ASAP on the Server Size the ASAP Database Subvolume To determine the approximate daily size of the database at a central location, use this formula: Bytes = + + + + + + + + + + + + + + + + + + + + + Cpus Nodes Apps Comm Disks Expand Files Ncpnodes Processes ProcessBusyEntries * Cpus Query + (Query2 RDFs Spoolers * 4 Tapes TCP TCPPort TCPRoute TCPSubnet Telserv TelservService TelservWindow TMFs * 4 Where: Cpus Nodes Apps Comm Disks Expand Files Ncpnodes Processes ProcessBusyEntries Query = =
Installing ASAP on the Server • • • • • • Recommended Sample Rates 10 nodes 100 disk volumes 30 Expand line-handlers 50 files 50 processes 3 ProcessBusyEntries per CPU The daily storage requirement for a five-minute sample interval requires approximately 32 megabytes of disk space: Bytes = = 80 10 100 30 50 50 3 * * * * * * * 128 128 222 400 212 312 80 * * * * * * * (1440/5) (1440/5) (1440/5) (1440/5) (1440/5) (1440/5) (1440/5) -------- CPU Node Disk Expand File Process ProcessBusy 2,949,120 +
Installing ASAP on the Server Starting ASAP Starting ASAP 1. Start ASAP by entering ASAP at a TACL prompt: TACL 1 > ASAP ASAP - Availability Stats and Performance - T0402V02.5 (15OCT2004) Copyright (C) 1999, 2001-2004 Hewlett-Packard Company Obey $SYSTEM.SYSTEM.ASAPCONF + 2. Verify the ASAP configuration by entering the SET command to display the current configuration values. For example: +SET ASAP Configuration Control settings: Version................. T0402V02.05 (15SEP2004) Action..................
Installing ASAP on the Server Starting ASAP Object................ Parameters............ CPU................... COMM.............ON Object................ Parameters............ CPU................... DISK.............ON Object................ Parameters............ CPU................... EXPAND...........ON Object................ Parameters............ CPU................... FILE.............ON Object................ Parameters............ CPU................... NODE.............ON Object...............
Installing ASAP on the Server Stopping ASAP 5. After successfully starting the ASAP Collector, start the Monitor processes on the nodes that are to report to the Collector that was just started. For example: +STARTUP !Starts Monitor on the local node +STARTUP \NY !Starts Monitor in New York +STARTUP \CHICAGO !Starts Monitor in Chicago 6. If you are using the ASAP Client, you can start it at this time. For more information, see the ASAP Client Manual.
Installing ASAP on the Server Using OBEY Files Using OBEY Files You can set up OBEY files using the editor of your choice. To execute the OBEY file using the ASAP CI, enter OBEY $vol.subvol.filename. The SHUTDOWN commands can be placed in Edit type file and then obeyed from within the ASAP CI. To create OBEY files while in the ASAP CI, use the SET LOGGING ON command and the SET LOGFILE $vol.subvol.filename.
Installing ASAP on the Server Using OBEY Files HP NonStop ASAP Server Manual—522303-007 2- 28
3 Running ASAP ASAP is started from a single START command, and is self-configuring in terms of what objects it automatically monitors when the configuration file is set up correctly and executed. It also includes options to modify their default configurations. For more information, see Section 6, ASAP Conversational Interface Commands. To start the ASAP Conversational Interface (CI): 1. Type ASAP at a TACL prompt. Whenever the ASAP CI is started, it automatically obeys the ASAPCONF configuration file.
Running ASAP Starting the ASAP Collector Starting the ASAP Collector Before you start the ASAP Collector, you must use the ASAP SET command to define the ASAP Collector options. You can set options through OBEY files, TACL macros, or interactively from the ASAP CI. For a complete list of SET options for the collector, see SET Command on page 6-87.
Running ASAP Starting the ASAP Monitors and SGPs From the same ASAP CI, another collector on \NY can be set up to collect on $Data2.asapdb, purge all records daily at 2:15 a.m., and not collect availability records between 10:00 p.m. and 2:30 a.m. +set db $data2.asapdb.db +set retain none +set sleeptime 2200, 0230 +set clean 0215 +STARTUP \NY COLLECT Starting the ASAP Monitors and SGPs Before you start the ASAP Monitors and SGPs, define the ASAP Monitor and SGP options using the ASAP SET command.
Running ASAP • • • • • • • • • • • • • • Starting the ASAP Monitors and SGPs SET PRIORITY SET PROCESS SET PROXY SET PROXYOBJECT SET PROXYPARAM SET QUERY SET RATE SET RDF SET SPOOLER SET SYNC SET SYNCSLOW SET TAPE SET TCP SET TMF For more information about these commands, see SET Command on page 6-87.
Running ASAP Starting the Monitor Processes Starting the Monitor Processes After you define the ASAP Monitor and SGP options, you can start the Monitor processes. This example sets up the ASAP subsystem to monitor two nodes. Disk and Expand objects are being monitored on both nodes, and application (APP) objects are being monitored on one of the nodes, with an availability rate of five minutes: +SET OBJECTIVESEVENTS ON +SET DISK ON, PARAMETERS “CPU 2 VOLUME $DATA” +SET APP ON, PARAMETERS “CONFIG $DATA2.
Running ASAP Getting Collector and Monitor Status Information Table 3-1.
Running ASAP Starting ASAP With the Default Configuration Starting ASAP With the Default Configuration When the Monitor starts, it starts the SGPs that were set to ON. The SGPs get the list of domains they should monitor from the Objectives Database. Each SGP configures some domains by default when no entity records are found in the Objectives Database. For more information, see MONITOR Usage Considerations on page 4-6.
Running ASAP Shutting Down the ASAP Collector and ASAP Monitors Shutting Down the ASAP Collector and ASAP Monitors The SHUTDOWN command stops the Collector or Monitor processes. The Monitor also shuts down all executing SGPs in each CPU. Stop the remote monitors first, then the collection node’s Monitor, and finally the Collector process.
Running ASAP Monitoring Different Sets of Network Nodes Monitoring Different Sets of Network Nodes You can configure multiple sets of ASAP Monitor and ASAP Collector processes to operate autonomously with different designated collection locations and options. This lets geographically separate operation groups monitor selectively different sets of network nodes. Figure 3-1 shows an example of such a configuration. Examples A and B illustrate two possible ASAP process configurations. Figure 3-1.
Running ASAP Viewing the ASAP Event Log Example B Example B defines a second set of processes that report statistics for a selected regional group of nodes to the LA node: SET SET SET SET SET COLLECT \LA DB $DATA2.ASAPDB.
Running ASAP ASAP Help These error messages indicate that Expand communication problems exist between the Remote node and the Collection node. ASAP Help The ASAP CI has online help for all of the ASAP commands. For a summary of the help available for all of the ASAP commands: +HELP ALL This output is produced: ASAP - Availability Stats and Performance - T0402V02.05 (15SEP2004) ALL ASAP commands are summarized below: ACTION Defines rules and lists actions. APP Reports on APPLICATION stats.
Running ASAP ASAP Help To obtain detailed help on any command: +HELP command To obtain help on ASAP error numbers: +HELP ERROR All of the ASAP error messages are output to your terminal or workstation.
4 Using Discrete Object Thresholds (DOTs) DOTs let users set discrete objectives and recovery actions against specific attributes for any domain within an ASAP entity. DOTs also let users selectively monitor specific objects (domains), and provide an event generation service.
Using Discrete Object Thresholds (DOTs) DOTs Overview domain, and turning it OFF in the objectives database, makes ASAP monitor no domains for the subsystem. For example, MONITOR CPU 1, ADD, OFF makes ASAP monitor no processors if it is the only CPU object specified in the database, or if all other CPU domains are also in the OFF state. • DOTs lets you set discrete thresholds on any attribute for any domain.
Using Discrete Object Thresholds (DOTs) <#LASTSTATE> The last state of the attribute <#VALUE> The value of the attribute <#GOAL> The objective value Specifying Domains and Objectives Action strings can also be stored as predefined rules by using the ASAP CI ACTION command. ASAP creates an initial set of predefined rules automatically, including one called RELOAD that executes the TACL RELOAD command.
Using Discrete Object Thresholds (DOTs) The Objectives Database The Objectives Database The objectives database stores a list of domain names to monitor. If names do not exist in the database, a default set of objects are autoconfigured for monitoring. The objectives database stores your objectives thresholds. ASAP produces states for attributes by comparing objectives from the objectives database with the computed interval value of the attribute.
Using Discrete Object Thresholds (DOTs) • • • • • • • • • • The Objectives Database TCPProcess (Optional) TCPQIO (Optional) TCPRoute (Optional) TCPRTE (Optional) TCPSubnet (Optional) TCPUDP (Optional) TelservProcess (Optional) TelservService (Optional) TelservWindow (Optional) TMF Once the monitored entities are loaded in the database, you can set individual userdefined objectives against entity domains by using the GOAL or RANK commands.
Using Discrete Object Thresholds (DOTs) MONITOR Usage Considerations MONITOR Usage Considerations This table shows the domains monitored by each ASAP if no objects are defined to monitor, and shows the default process names of the ASAP SGP processes and the database file name for each entity: Entity Default Process Name Database Filename APP $ZOOH DBAPP All application domains registered using the ASAP_REGISTER_ API COMM $ZOOU DBCOM All configured communication line types 7, 11, 13, 53, 5158, 60
Using Discrete Object Thresholds (DOTs) GOAL and RANK Usage Considerations GOAL and RANK Usage Considerations Use the GOAL and RANK commands to set discrete objectives on any attribute defined in EDL that has an associated state (StatePair Yes). For example, to set a global objective for all CPUs to less than 90% busy with a queue length less than 2, then override it with a specific objective on CPU 2 that its queue length must be less than 1: GOAL CPU, BUSY < 90, QUEUE < 2 GOAL CPU 2, QUEUE < 1 Note.
Using Discrete Object Thresholds (DOTs) • Status Change Events To turn on the corresponding up event (event 4001) when the domain or objective recovers, place the SET ObjectivesEventUp ON command in your ASAPCONF file. ASAP generates down events for a domain whenever the state for an attribute configured to generate events is greater than or equal to the state specified in the SET ObjectivesEventState command.
Using Discrete Object Thresholds (DOTs) Event Considerations Summary Therefore, RANK PROCESS, STATUS = “DOWN” is an invalid command because objectives cannot be set on the Status attribute. However, to control how ASAP generates events on Status changes, you can enter event control keywords using the Status attribute. By default, ASAP writes one critical EMS event when it finds a system object whose OpState passes the event generation test.
Using Discrete Object Thresholds (DOTs) • Event Considerations Summary To define the additional attributes for which you want events generated, issue RANK commands. For example, to generate a critical event if any CPU exceeds 89% busy, enter RANK CPU, BUSY < 90 CRITICAL.
Using Discrete Object Thresholds (DOTs) System Entity Specifics System Entity Specifics System entities that have one or more attributes with an associated StatePair attribute support DOTs. System entity attributes are defined in the file $SYSTEM.SYSTEM.ASAP2SYS. Any modifications to this file might cause incorrect entity objectives records to be written to the ASAP objectives database. To get help about which entity attributes can be ranked, use the SHOW command.
Using Discrete Object Thresholds (DOTs) COMM Entity-Supported Objective Attributes COMM Entity-Supported Objective Attributes Attribute Description Value CPU Primary CPU Comm Line configured to Integer BCPU Backup CPU Comm Line configured to Integer Requests IO Requests per second Integer32 Busy Percent time line busy reading and writing Integer ReadBusy Percent Time Line Busy Reading Integer WriteBusy Percent Time Line Busy Writing Integer InKB Kilobytes read per second Integer64
Using Discrete Object Thresholds (DOTs) DISK Entity-Supported Objective Attributes DISK Entity-Supported Objective Attributes Attribute Description Value P* Primary disk path in use, value = P or B Character 1 wide M ** Mirror disk path in use, value = P or B Character 1 wide CPU Primary CPU number of the Disk process for this volume Integer FULL Percentage of disk space currently used Integer REQUESTS Number of disk I/O requests per second Integer32 BUSY Percent time disk busy reading,
Using Discrete Object Thresholds (DOTs) EXPANDIP Entity-Supported Objective Attributes Attribute Description Value PktSnt Number of Level-4 packets sent Integer32 PktRvd Number of Level-4 packets received Integer32 PThruSnt Number of Level-4 PassThru packets sent Integer32 PThruRvd Number of Level-4 PassThru packets received Integer32 LnkSnt Number of requests sent Integer32 LnkRvd Number of requests received Integer32 CPU Primary Cpu number of the Expand Line Handler Process for thi
Using Discrete Object Thresholds (DOTs) HYBRID Entity-Supported Objective Attributes Attribute Description Value RWEP Read, Write, Execute, Purge security (Safe = Safeguard) Character 4 wide Open Yes = Open; No = Not open Character 3 wide TMF Yes = Audited by TMF; No = Not audited Character 3 wide Files Number of files in subvolume Integer32 Permissio n OSS permissions string Character 10 wide Progid Progid indicator (yes/no) Character 3 wide License License indicator (yes/no) Chara
Using Discrete Object Thresholds (DOTs) PROCESSBUSY Entity-Supported Objective Attributes Attribute Description Value WState Lsig/Lpipe(status), Pon(cpu pwr), Iopon (I/O pwr), Intr Character 8 wide MPages Memory pages in use Integer64 (implied decimal) MSent * Messages sent per second Integer64 (implied decimal) MRecvd * Messages received per second Integer64 (implied decimal) Qlen * Receive queue length Integer32 MQlen * Maximum receive queue length Integer32 PFaults * Page faults p
Using Discrete Object Thresholds (DOTs) SPOOLER Entity-Supported Objective Attributes SPOOLER Entity-Supported Objective Attributes Attribute Description Value Error Last error encountered Integer32 PCPU CPU of primary process Integer BCPU CPU of backup process Integer NumJobs Number of jobs defined for this entity Integer32 BatchJobs Number of batch jobs defined for this entity Integer32 OpenJobs Number of jobs not fully defined Integer32 PrintJobs Number of jobs currently printing
Using Discrete Object Thresholds (DOTs) TAPE Entity-Supported Objective Attributes TAPE Entity-Supported Objective Attributes Attribute Description Value PCPU CPU of the backup tape device process Integer BCPU CPU of the backup tape device process Integer MountReq Number mount requests outstanding for this tape drive or node Integer MountTime Amount of time since MountReq > 0 Integer TapeStatus Status of the tape currently loaded in the tape drive Character 8 wide TapeLabel Label type o
Using Discrete Object Thresholds (DOTs) TCP/IP and Telserv Entities-Supported Objective Attributes Attribute Description Value Xsum The number of packets received with bad checksum values Integer32 BadLen The number of packets that were shorter than the length specified in the ICMP header Integer32 Reflect The number of ICMP Reflect packets that were received Integer32 InEchoRply The number of Echo message input replies Integer32 InDstUnrch The number of Destination Unreachable messages in
Using Discrete Object Thresholds (DOTs) TCP/IP and Telserv Entities-Supported Objective Attributes Attribute Description Value FragTimeout The number of fragments whose TTL expired Integer32 Fwd The number of packets that were forwarded Interger32 CantFwd The number of packets received but could not be forwarded (no route available to the specified destination) Integer32 RedirSent The number of ICMP Redirects sent Integer32 OutPkts The number of output packets Interger32 Error Collectio
Using Discrete Object Thresholds (DOTs) TCP/IP and Telserv Entities-Supported Objective Attributes Attribute Description Value SockUDP Number of sockets open using UDP protocol Integer32 SockUnkn Number of sockets open using an unknown protocol Integer32 SockLstn The open sockets currently in a listening state Integer32 BadXsum The number of packets received with bad checksum values Integer32 BadOff The number of packets received with a bad data offset Integer32 BadHdrLen The number of
Using Discrete Object Thresholds (DOTs) TCP/IP and Telserv Entities-Supported Objective Attributes Attribute Description Value SndByte The total number of data bytes sent Integer32 SndRexmitByte The number of bytes retransmitted Integer32 SndAcks The number of ACK packets sent Integer32 SndProbe The number of window probes sent Integer32 SndUrg The number of packets sent with the URG bit set Integer32 SndWinUpdate The number of window update packets sent Integer32 SndCtrl The number
Using Discrete Object Thresholds (DOTs) TCP/IP and Telserv Entities-Supported Objective Attributes Attribute Description Value Droppedsyn The number of dropped SYNs because of sonewconn() failed Integer32 ScAdded The number of SYN cache entries added Integer32 ScCompleted The number of SYN cache connections completed Integer32 ScTimedOut The number of SYN cache entries timed out Integer32 ScOverflowed The number of SYN cache entries dropped due to overflow Integer32 ScReset The number o
Using Discrete Object Thresholds (DOTs) TCP/IP and Telserv Entities-Supported Objective Attributes Attribute Description Value MaxPoolSpc The maximum pool space used Integer32 PoolFails The number of times a pool space request failed Integer32 TotalMbufs The current number of MBUFs allocated Integer32 CurrMbufsUse The current number of MBUFs in use Integer32 MaxMbufsUse The maximum number of MBUFs to be used Integer32 MbufFails The number of times an MBUF was not available Integer32 D
Using Discrete Object Thresholds (DOTs) Attribute TCP/IP and Telserv Entities-Supported Objective Attributes Description Value Error Collection Error Integer64 Zusage The number of times the specific route has been used to send out IP datagrams Integer32 Error Collection Error Integer64 BadRedir The number of bad route redirect requests Integer32 Dyn The number dynamic redirects from smart gateways Integer32 NewGw The number redirects from new/unknown gateways Integer32 NotReach The
Using Discrete Object Thresholds (DOTs) Attribute TCP/IP and Telserv Entities-Supported Objective Attributes Description Value Error Collection Error Integer64 OutPkts The number of packets output on the subnet interface Integer32 InPkts The number of packets input on the subnet interface Integer32 OutErrs The number of errors detected while outputting packets on the subnet interface Integer32 InErrs The number of errors detected while inputting packets on the subnet interface Integer32
Using Discrete Object Thresholds (DOTs) TCP/IP and Telserv Entities-Supported Objective Attributes Attribute Description Value Avgactvterm The average number of terminals in the system in the last five minutes Integer32 Spireq The number of SPI requests processed Integer32 Userdata The number of bytes sent by the user to the network Integer32 Netreq The number of packets received from the network Integer32 Userreq The number of user requests Integer32 Error Collection Error Integer64
Using Discrete Object Thresholds (DOTs) TMF Entity-Supported Objective Attributes Attribute Description Value WinTyp Type of Window, Static or Dynamic Character 7 wide CAddr Caller's IP address IpAddr CPort Caller's Port Integer LAddr6 Local IP Address IpAddr6 FAddr6 Foreign IP Address IpAddr6 CAddr6 Caller's IP address IpAddr6 Openers Number of opens against the window Integer32 Processes Number of processes found running against the window Integer32 Active The number of proce
5 File and Process Monitoring ASAP provides various ways to monitor files and processes and to control the amount of data produced for those objects. The most common method of monitoring a file or process is to specify the Guardian file or process name using the ASAP MONITOR command. For example, the commands MONITOR FILE $DATA.SUBVOL.FILE and MONITOR PROCESS $ABC will configure ASAP to monitor file $DATA.SUBVOL.FILE and process $ABC.
File and Process Monitoring Monitoring Processes from an Object File aggregate-only domain. For more information on aggregate and aggregate-only domains, see the subsections on aggregation later in this section. Wild-card domains that are resolved at each interval are stored in a memory pool in the File and Process SGPs. The pool is allocated from extended memory and is controlled by KMSF. Excessive numbers of objects can deplete the pool space.
File and Process Monitoring Monitoring Files and Processes Using OSS Pathnames PROCESS, LIST, DETAIL command can be used to view pool usage and the MBYTES parameter to the ASAP Process SGP process is used to control the amount of space within the pool. For more information, see the MONITOR Command on page 6-53 and PROCESS option in the SET Command on page 6-87. To set an objective on a domain resolved from an object filename you must include the object filename specifier in the name.
File and Process Monitoring Logical Grouping Note. Resolving the processes running from an OSS pathname can result in excessive low-level messaging in the NonStop OS. This method should be used judiciously in extremely high-performance application environments. Logical Grouping ASAP lets you group files into hierarchical groups of files and processes into hierarchical groups of processes.
File and Process Monitoring Creating Specific Aggregate Domains (Recommended) Creating Specific Aggregate Domains (Recommended) To create an aggregate domain for hierarchically grouped files or processes, use the MONITOR command to add the aggregate domain to the ASAP configuration. For example, MONITOR PROCESS SALES\# causes ASAP to create the Sales\# domain and to aggregate all domains starting with Sales into that domain.
File and Process Monitoring Aggregation Defined Aggregation Defined The way attribute values are combined in the aggregate records varies by attribute and can be changed. Different users might want different behavior for a specific attribute. For example, consider the Process Busy, Pri and PFName attributes. (Busy represents process busy.) By default, ASAP sums all the process busy values in the group for the aggregate record, so you can see the total consumption of processor resources across the group.
File and Process Monitoring Aggregation Rules Aggregation Rules The EDL Attribute property MetricRule is used to define the aggregation property of a File or Process attribute.
File and Process Monitoring Attributes without States The state at which ASAP considers a file or process to be alerting is the Low Alert state 3, so if any attribute in the domain record has a state of 3 or higher, the domain is counted in the number of alerting domains shown in the Status text field. If you prefer a different alert level, you can change the state at which ASAP considers a process to be alerting. See the FILE and PROCESS options for the SET Command on page 6-87.
File and Process Monitoring Default Process MetricRule Settings behavior can be turned on with the RUL aggregate control and results in this priority ranking of the possible values, from low to high: PState WState UnAlloc None Starting Lreq Runnable Lpipe DebugBrk Pon DebugTrp Iopon DebugReq Intr InspMBrk Lcan InspBrk Ldone InspTrp Ltmf InspReq Linsp SaveAben Stopping XIOInit As an example, when RUL is specified, a process in the Stopping process state is considered to be worse than
File and Process Monitoring Modifying the Default Aggregation Settings Attribute Default Value QLen MAX MQLen MAX Pfaults SUM The Process Count attribute provides an automatic count of all domains in the group and is always one for a detail domain. The Process ACount attribute provides the number of attributes that are alerting when viewed in a detail process record and provides the number of domains that are alerting when viewed in an aggregate domain record.
6 ASAP Conversational Interface Commands The ASAP Conversational Interface (CI) provides the commands and options to start, stop, configure, and get the status of the ASAP system, as well as the commands to display object status and performance data. Use the CI to configure, start, stop, and get the status of the system resources Application (APP), CPU, DISK (DSK), Expand (LH), FILE(FIL), Node end-to-end (NCP), PROCESS(PRO), executing ProcessBusy (PCB), RDF(RDF), SPOOLER (SPL), TAPE(TAP), and TMF(TMF).
ASAP Conversational Interface Commands Table 6-1.
ASAP Conversational Interface Commands Considerations Table 6-1.
ASAP Conversational Interface Commands ACTION Command ACTION Command The ACTION command is used to list action strings for a specific domain or domains and to define, delete and list rules, or stored action strings that can be used in RANK commands to define actions for failed objectives. ACTION[/OUT file/][LIST] [\node][entity][domain][attribute [operator]] RULE [\node][rule][=string] |[, DELETE] LIST The LIST option is used to output information about all actions defined in the objectives database.
ASAP Conversational Interface Commands ACTION Command string An action string not enclosed in quotes, where the first word in the string represents the command interpreter the command should be sent to and the remainder of the string is the command to be sent to the CI. The string should be entered exactly as it will be sent to the command interpreter. Include any of the tokens below in the string, and ASAP will substitute actual names for the symbolic tokens.
ASAP Conversational Interface Commands ACTION Command To define a stored action to resecure files: ACTION RULE SECURE = FUP SECURE <#OBJECT>, "<#GOAL>" ACTION RULE RESECURE, DELETE deletes the RESECURE action. ACTION CPU 0 BUSY GT gets action/wait for CPU 0 BUSY GT. Default Rules ASAP automatically loads several rules into its database of Action Rules when it creates it for the first time. These may be used in any GOAL or RANK command.
ASAP Conversational Interface Commands APP Command APP Command The APP command displays customer application service-level metrics for the specified nodes. For customer-developed applications to participate in the ASAP system, ASAPX must be installed. Customer-developed applications must be ASAP enabled through calls to the ASAPX library. For more information, see the ASAP Extension Manual. For an explanation of APP performance statistics, enter HELP APPSTATS.
ASAP Conversational Interface Commands APP Command \* specifies that the performance and state information for all systems is to be displayed. node specifies the individual system for which statistical information is to be displayed. If you want information for all the systems, specify APP \*. If you do not specify a node or the wild-card character (*), the default is used. The default is the system where the ASAP program was started, or the system specified in the ASAP SYSTEM command.
ASAP Conversational Interface Commands APP Command CPU cpu-number specifies that the performance information for the APP domains executing in the specified CPU, cpu-number, are displayed. If you do not specify a CPU, statistics for all APPs in the current system are displayed. STATES displays the associated OEM state for each attribute where StatePair is true. These OEM states are reported, depending on the type of ranking used (see SET OBJECTIVESRANK on 6-104): Existence 1 Object exists.
ASAP Conversational Interface Commands APP Command AGGREGATEONLY specifies that only aggregate records are output in the command. AGGREGATEONLY is useful in large domain populations for controlling the amount of data sent to the ASAP Client. MINSTATE [AUTO|state] specifies that only records which have at least one attribute with a state greater than or equal to state are to be output. state must be a valid OEM state from 1 through 8.
ASAP Conversational Interface Commands APP Command Examples These examples show some available options along with the display output: +APP \CENTDIV ATM \CENTDIV Domain\Name\Hierarchy -------------------------------Atm\Guest\Chicago\$Jx00 Atm\Guest\Chicago\$Jx01 Atm\Guest\Chicago\$Jx20 Atm\Guest\Chicago\$Jx21 !DEFAULT OUTPUT Domain = ATM Status Date Time Ct Error --------------- ----- ----- -- ----Up 5/10 16:56 17 0 Up 5/10 16:56 17 0 Up 5/10 16:56 17 0 Up 5/10 16:56 17 0 +APP \CENTDIV MARKET \CENTDIV Do
ASAP Conversational Interface Commands APP Command AT Time GRID YES GRAPH YES GRAPHMAX 0 HELP "Time of Stats"; AT Valid GRID NO GRAPH NO GRAPHMAX 0 HELP "Validity Flag"; AT ET GRID NO GRAPH NO GRAPHMAX 0 HELP "Elapsed Time in Minutes"; AT CT GRID NO GRAPH NO GRAPHMAX 0 HELP "Count of Attributes"; AT Error GRID YES GRAPH NO GRAPHMAX 1 HELP "Collection Error" STATEPAIR YES STATERULE UseStateGraphState TypeData INT64 Format "I4"; AT ErrorState GRID NO GRAPH NO GRAPHMAX 9 HELP "State of Erro
ASAP Conversational Interface Commands -------------------------------- --------------- ----- ----Receive\$Jx50 Up 5/10 17:47 Receive\$Jx51 Up 5/10 17:47 APP Command -- ----4 0 4 0 continued... TransRate ErrCount Busy State --------- -------- ----- ----0.1500 2 0.04 3 0.6000 4 0.10 3 This example retrieves detail record information about the ATM application directly from ASAP memory instead of from the ASAP database.
ASAP Conversational Interface Commands CLEANUP Command CLEANUP Command The CLEANUP command invokes the database cleanup function. How the cleanup function works depends on the RETAIN option assigned to the Collect server. Caution. This command purges or releases statistics. This command can cause degradation in performance when the RETAIN option is set to a value greater than one. Only advanced ASAP users should use this command.
ASAP Conversational Interface Commands COMM Command \* specifies that the performance and state information for all systems is to be displayed. node specifies the individual system for which statistical information is to be displayed. If you want information for all the systems, specify COMM \*. If you do not specify a node or the wild-card character (*), the default is used. The default is the system where the ASAP program was started, or the system specified in the ASAP SYSTEM command.
ASAP Conversational Interface Commands COMM Command hh is the hour. mm is the minute. m/d/y is the month, day, and year. Valid m/d/y entries are mm/dd/yy, yyyy/mm/dd, or mm/dd/yyyy. CPU number lists the statistics for the communication line are currently operating in the specified CPU number, cpu-number. INFO lists the operational information for monitored communication lines. DATE displays the date of the sample converted to the database local civil time.
ASAP Conversational Interface Commands COMM Command Suspending G-series Communication line is entering a suspended state and is not operational. Serviced G-series Communication line is being serviced and is not operational. Special D-series Communication line is in the special state and is not operational. Exclusive D-series Communication line is in the exclusive state and is not operational. LDEV displays the logical device number of the communication line.
ASAP Conversational Interface Commands COMM Command PROGRAM displays the object file name of the communication lines. PERCENT is the default for the COMM command. This option displays communication utilization in requests per second, percentage busy, percentage reading, and percentage writing. Retry and transactions are displayed as per second, and Response time is displayed as average response time. For a description of the performance statistics, see Table 6-2 on page 6-18.
ASAP Conversational Interface Commands COMMIT Command Table 6-2. COMM Statistics and Descriptions Statistics Option/Description TXACTN Number of terminal transactions per second performed by the I/O processes for all the subdevices on the communication line. WRITE Number of writes per second. WRIT% Percent communication busy writing data.
ASAP Conversational Interface Commands CPU [/OUT file/] [ \* ] [ [.] * [ \node ] [ [.] cpu ] CPU Command ] [, [, [, [, [, [, [, [, [, [, SAMPLES count DETAIL PERCENT USE CONFIGURED HISTO AVG STATE TYPE TIME hh[:mm [m/d/y] ] ] ] ] ] ] ] ] ] ] OUT file specifies the spooler or line printer where the ASAP output is to be sent. When no output file is specified, the output is displayed on your terminal or workstation.
ASAP Conversational Interface Commands CPU Command DETAIL displays all statistics for the specified CPU or system. Displays high PIN PCB configuration and usage statistics for D-series and later systems. On C-series systems, the display heading is named LCB, on D-series systems and later, the display heading is named PCBX. PERCENT displays the percentage of the total resource values for Memory pages, Control blocks (PCB, PCBX, LCB, and TLE), System, and MapPool.
ASAP Conversational Interface Commands • • CPU Statistics A CPU is being reloaded. A CPU was configured but does not physically exist. When a “<” appears immediately after the timestamp, the statistics were received late by the Collector process. Late statistics are an indication of busy Expand lines. hh is the hour. mm is the minute. m/d/y is the month, day, and year. Valid m/d/y entries are mm/dd/yy, yyyy/mm/dd, or mm/dd/yyyy.
ASAP Conversational Interface Commands CPU Statistics Statistics Description/Option SBSY The average percentage CPU send busy for the sample SEG The number of virtual memory segments (Dxx and later) for USE/Conf SWAP The memory manager page fault rate in page swaps per second SYS The number of SysPoll words for USE/CONF TIME The time of the sample converted to database local civil time TLE The number of time list elements currently in use USE/CONF Options that control whether statistics are
ASAP Conversational Interface Commands DB Command ----------------------%---------------------------------------------------00 2/25 8:05 1 1 1 46 2 2 16384 255 544 600 32767 01 2/25 8:05 1 1 1 34 16384 255 1544 600 32767 02 2/25 8:05? 1 0 03 2/25 8:05? 1 0 In this example, the output for CPUs 2 and 3 has a ? after the time, indicating that the statistics are not valid. These CPUs were down.
ASAP Conversational Interface Commands DISK Command -------- - -------------- ------- ---- ---------------CPU Z0115CPU 04/01/16 00:00 255,255 NUNU 2004/01/15 17:28 Z0116CPU 04/01/17 00:00 255,255 NUNU 2004/01/16 00:01 Z0117CPU 04/01/18 00:00 255,255 NNNN 2004/01/17 00:01 Z0118CPU 04/01/19 00:00 255,255 NNNN 2004/01/18 00:01 Z0119CPU 04/01/20 00:00 255,255 NNNN 2004/01/19 00:01 • ---------------2004/01/16 2004/01/17 2004/01/18 2004/01/19 2004/01/20 00:00 00:00 00:00 00:00 00:00 If DETAIL is specified,
ASAP Conversational Interface Commands DISK Command where the ASAP program was started, or the system specified in the ASAP SYSTEM command. volume specifies the individual DISK volume for which performance and state information is to be displayed. All the disks from all the collected nodes can be output by specifying DISK \*.*. If you do not specify a DISK or the wild-card character (*), the default is used. The default is all the DISK devices on the current system.
ASAP Conversational Interface Commands DISK Command AVG displays the largest statistical values for the entire volume. Only one line of output is displayed. This can be used in conjunction with the CPU, RATE, PERCENT, and QUEUE options. CPU number lists the statistics for disk devices that IOPs are currently operating in the specified CPU number, cpu-number. INFO lists the operational information for primary disk devices and the mirror devices if they exist.
ASAP Conversational Interface Commands DISK Command GRP displays the group number. G-series. MOD displays the module number. G-series. SLT displays the slot number. G-series. STATE displays the operational state of the device. A device could be in these STATEs: Up device is operational. Down entire device is down. HDown entire device is in a Hard down state. -P HD primary path is Hard down. -P Dn primary path is Down. -B H backup path is Hard down. -B Dn backup path is Down. -M H mirror path is Hard down.
ASAP Conversational Interface Commands DISK Command -MB H mirror backup path is Hard down. -MB D mirror backup path is Down. Reviv device is being revived. Frmtg device is being formatted. Specl device is in the Special state. ERROR displays the Error reason when the disk statistics are invalid. CpuDn IOP switched to another CPU. The sample for the devices is invalid for one sample interval. Cpusw IOP for the disk volume switched to another CPU. The sample for the devices is invalid for one sample.
ASAP Conversational Interface Commands DISK Command Pthsw controller path switch occurred. The sample for the device is invalid for one sample interval. SteCh device state change. The sample for the device is invalid for one sample interval. UnAvl device configured but the disk process for the device has not started. PERCENT is the default for the DISK command. This option displays disk utilization in percentage busy, percentage reading, percentage used, and percentage writing.
ASAP Conversational Interface Commands DISK Command Table 6-5. DISK Statistics and Descriptions Statistics Option/Description BSPLT The block split total of 512 through 4096 block splits for the volume. BUSY% Total percentage disk busy during read, write, and seek operations. CHIT Cache hits. Total of 512 through 4096 blocks that occurred per second. DATE Date of the sample converted to the database local civil time. INPUTKB The number of kilobytes read per second from the disk.
ASAP Conversational Interface Commands $MC-M 14:50 $MM-P 4/28 14:50 $MM-M 14:50 $RTOOL-P 4/28 14:50 $SYSTEM-P 4/28 14:50 $SYSTEM-M 14:50 2 .93 3 .93 3 1 3 3 EDL Command 1.72 1.72 3 3 3 3 3 3 0.10 100.80 100.80 0.00 1.20 1.20 0 40 35 0 0 0 0 37 37 0 0 0 +DISK,RATE \CHITOWN Date Time State GBUsed Requests Rate Writes Reads Swap Qlen -----------------------------------------------------------------------$DSV-P 4/29 13:25 Up 1.57 0.00 $NSX-P 4/29 13:25 Up 0.58 23.00 23.5 11.3 12.2 .
ASAP Conversational Interface Commands EXIT Command EXIT Command The EXIT command stops the Conversational Interface. +EXIT FC Command +FC The FC command retrieves and displays the last ASAP command you entered so you can modify and re-execute it. The FC command uses the subcommands R, I, and D to replace, insert, or delete characters. For more information about this command, see the Guardian User’s Guide.
ASAP Conversational Interface Commands FILE Command node specifies the individual system for which statistical information is displayed. If you want information for all the systems, specify FILE \*. If you do not specify a node or the wild-card character (*), the default is used. The default is the system where the ASAP program was started or the system specified in the ASAP SYSTEM command. domain specifies the individual file domains for which performance and state information is displayed.
ASAP Conversational Interface Commands FILE Command STATES shows all attributes that have an associated state. DETAIL shows all available statistics attributes, without states. MINSTATE displays files from memory in a subvolume or aggregate domain, depending on the selected option: state shows files with an OEM-state greater than or equal to state. AUTO shows files with an OEM-state higher than 2, or else shows all files. EXACT shows statistics for only the specified domain.
ASAP Conversational Interface Commands FILE Command Examples For descriptions of the fields displayed in FILE command output, enter help filestats. • To display a list of file domains being monitored and a few attributes: +file \CENTDIV File Domains --------------------------$Mm.filework $Mm.xx.disk $System.system.
ASAP Conversational Interface Commands $Mm.xx.disk $System.system.asapmon FILE Command Up Up 2 2 9/19 10:00 9/19 10:00 0 1 0 1 0 2 49 2 continued... Eof ---------978944 0 1569704 Owner ------0,0 255,255 255,255 Rwep ---aaaa ncnc nunu Open ---No No Yes Tmf --No No No S Files S Code Format Type - ----- - ---- ------ -------1 25 1 - 1 - 1 0 1 Unstruct 1 - 1 100 1 Unstruct Parts ----0 0 continued...
ASAP Conversational Interface Commands GOAL Command GOAL Command The GOAL command controls the objectives used to produce alerts and spawn actions within ASAP. It controls the set of objectives and gets information about those objectives. GOAL [/OUT file/] [entity | *] [\node], COMMIT [.| ]][domain]], goal [,goal,...
ASAP Conversational Interface Commands GOAL Command domain is any form of an ASAP domain name. Domain names can represent physical devices ($Data) or abstract representations of applications (Funds\Transfer\Input.) Some command options support the asterisk wild-card character at the end of the domain name. COMMIT sends a commit request to all entities or a specific entity on a local or remote node. This request causes ASAP to reload its set of objectives for the entity or entities on the node.
ASAP Conversational Interface Commands GOAL Command event INFO | CRITICAL [REPEAT] [NODISPLAY] [down] [-up] INFO configures ASAP to generate an informational event when the objective is not met. CRITICAL configures ASAP to generate a critical event when the objective is not met. REPEAT causes ASAP to repeat the event for each interval where the objective is not met. NODISPLAY overrides any global settings to suppress display of the event on the operator console.
ASAP Conversational Interface Commands GOAL Command NOEMS Used only with the STATUS attribute. NOEMS turns off automatic event generation for status changes in ASAP system entities. action ACTION string | rule [WAIT wait] [NOREPEAT] string is an action string where the first word in the string is a command interpreter name such as TACL, SCF, or FUP, and the remainder of the string represents the command to be executed by that command interpreter.
ASAP Conversational Interface Commands GOAL Command WAIT wait indicates the number of minutes ASAP should wait before retrying an action string against a particular entity and domain. The wait time also depends on the ASAP rate setting because ASAP validates objectives only once per cycle. NOREPEAT indicates that ASAP should not continue to repeat the action until the condition is corrected. LIKE sets attributes in the new or modified domain that are currently active in the LIKE domain.
ASAP Conversational Interface Commands GOAL Command LIST retrieves a list from the active set of objectives for all entities or for a specific entity. The LIST command communicates directly with running ASAP components to retrieve objective information. entity must be specified when domain is specified; otherwise both are optional. Domain names can use the asterisk wild-card character as the last character in the name.
ASAP Conversational Interface Commands • HELP Command To commit all objectives changes: GOAL, COMMIT • To define an action to reload a CPU after it fails: GOAL CPU, STATUS ACTION "TACL RELOAD <#DOMAIN>, PRIME" WAIT 15 • To define a goal and action to secure the NonStop OS userid file to "OOOO": GOAL FILE $SYSTEM.SYSTEM.
ASAP Conversational Interface Commands HELP Command command specifies the command or keyword to display detailed help for. ALL provides a summary of all commands. ERROR lists all of the Monitor and Collect error messages by message number, description, and parameters. For a description of these messages, including suggested recovery actions, see the ASAP Messages Manual. SET option provides a description of a specific SET option. Example ASAP - Availability Stats and Performance - T0402V02.
ASAP Conversational Interface Commands LH Command LH Command The LH command collects Expand line-handler entity availability statistics for the specified node names and line names. The Expand line-handler services incoming and outgoing requests and responses to transfer data between processes. For an explanation of line-handler statistics, type HELP NETSTATS. LH [/OUT file/] [ \* ] [ \node ] [ [.]line ] [ [.
ASAP Conversational Interface Commands LH Command * specifies that availability information for all lines is to be displayed. If you do not specify a line or the wild-card character (*), ASAP uses the default, which is all Expand lines for the current system. INFO displays line attribute information. The information includes the logical device number (LDEV), the primary and backup processor identifiers, the line subtype, the NEXTSYS and time factor values, and any ASAP line collection errors.
ASAP Conversational Interface Commands LH Command IP displays the Expand statistics for Expand lines configured using either the IP transport or the ATM transport. Only lines configured using IP or ATM are displayed. Statistic counters reported are: DFrame Number of data frames sent and received.
ASAP Conversational Interface Commands LH Command PATH displays Expand statistics only for Expand Multiline Path process subtype 1. You can use this option with all other LH options. POOL displays pool use.
ASAP Conversational Interface Commands LH Command m/d/y is the month, day, and year. Valid m/d/y entries are mm/dd/yy, yyyy/mm/dd, or mm/dd/yyyy. USE displays statistics about current pool usage. For percentages, see the POOL option. RAW displays RATES data in a dense tabular format rather than the standard ASAP sparse format. LH Statistics Table 6-6 lists the LH statistics and options shown by the HELP NETSTATS command. Table 6-6.
ASAP Conversational Interface Commands Statistics Options TIME Statistics starting at a time other than the current time. USE Values in kilobytes rather than pool percentages (% is default). RAW Shows statistics in tabular format rather than standard display. LH Command Table 6-7. Statistic Counters (page 1 of 2) Counter Description ACK Number of Acknowledgments sent or received. BCC Total number of BCC errors in this sample. CAN Number of Cancel requests sent or received.
ASAP Conversational Interface Commands LH Command Table 6-7. Statistic Counters (page 2 of 2) Counter Description PkRcv Total number of Level 4 packets (local+passthru) received. POOL Combined buffer Pool usage = msg + oos in % or kilobytes. PtSn Total number of Level 4 packets (passthru only) sent. PtRv Total number of Level 4 packets (passthru only) received. QyCmd Number of IP or ATM Query commands sent or received. QyRsp Number of IP or ATM Query responses sent or received.
ASAP Conversational Interface Commands LOG Command LOG Command The LOG command displays the most recent ASAP disc log event records for ASAP in the specified node. LOG [\node] [ blocks ] blocks optionally specifies the display of additional history. It indicates the number of log event record blocks to display. Example LOG \NEWYORK 3 !display 3 blocks of ASAP event records in \NEWYORK MONITOR Command The MONITOR command controls monitored objects (domains) within ASAP.
ASAP Conversational Interface Commands MONITOR Command To manipulate or report on existing objects: MONITOR [ entity ] [ \node ] ,ON [\node.domain ] ,OFF [ domain ] ,DELETE ,INFO [ ,DETAIL ] [ ,OBEYFORM ] ,DETAIL ,OBEYFORM ,LIST [ ,DETAIL ] entity is the name of an ASAP entity as defined in EDL. node is the node name the command applies to. domain is a form of an ASAP domain name. Domain names can represent physical devices ($Data) or abstract representations of applications (Funds, Transfer, or Input).
ASAP Conversational Interface Commands MONITOR Command APP - application COMM - $line CPU - cpu DISK - $volume entity - application EXPAND - $line EXPANDIP - $line FILE - [logical\]$file | /pathname, ADD PROCESS - [logical\]$process | /pathname, ADD PROCESSBUSY - cpu RDF - primary->backup SPOOLER - $supervisor SYSTEM - \node TAPE - $tape TCPPROCESS - $tcpprocess TCPPORT - port TCPROUTE - $tcpprocess.#route TCPSUBNET - $tcpprocess.#subnet TELSERVPROCESS - $telservprocess TELSERVSERVICE - $telservprocess.
ASAP Conversational Interface Commands MONITOR Command domain name specified. For more information on using logical names, see Section 5, File and Process Monitoring. SALES\ is an example of a logical prefix. $file is a filename, subvolume name or filename pattern containing wild-card characters in the subvolume or file portions of the name. For example, $DATA.SUBVOL, $DATA.SUBVOL.FILE, $DATA.SUBVOL.F*, and $DATA.SUB*.F*. pathname is a process object file or OSS file specified as an OSS pathname.
ASAP Conversational Interface Commands MONITOR Command $tcpprocess is the process name of a TCP/IP process or a TCP/IPv6 SAM process. port is a valid TCP/IP port number. $tcpprocess.#route is the TCP/IP process name and route name of a TCP/IP route. $tcpprocess.#subnet is the TCP/IP process name and subnet name of a TCP/IP subnet. $telservprocess is the process name of a TELSERV process. $telservprocess.service is the TELSERV process name and service name of a TELSERV service. $telservprocess.
ASAP Conversational Interface Commands MONITOR Command ON turns monitoring on in the database for the specified domains in the specified entity. When domain is specified, entity must be specified, otherwise both are optional. Domain names can use the asterisk wildcard character as the last character in the name. For a domain to be turned on, it must first be added to the database using the ADD parameter. ON also outputs each domain turned on (INFO).
ASAP Conversational Interface Commands MONITOR Command otherwise both are optional. Domain names can use the asterisk wildcard character as the last character in the name. LIST, DETAIL retrieves a list of the active domains from a running ASAP Server component and includes entity detail information (if any) for all entities or for a specific entity. When domain is specified, entity must be specified, otherwise both are optional.
ASAP Conversational Interface Commands • MONITOR Command To turn on all domains on \REMOTE already in the database: MONITOR \REMOTE, ON • To add and turn on CPU 0 on \REMOTE: MONITOR CPU \REMOTE.
ASAP Conversational Interface Commands • MONITOR Command To monitor all files in subvolume $DATA.SUB that start with FIL: MONITOR FILE $DATA.SUB.FIL*, ADD • To monitor an OSS file: MONITOR FILE /home/dir/filename • To monitor a file as part of a logical group named SALES: MONITOR FILE SALES\DATA\$DATA.SUB.SALES • To dynamically monitor all processes running from an object file: MONITOR PROCESS $DATA.OBJECT.
ASAP Conversational Interface Commands MONITOR Command command MEMORY option. The single aggregate record written to the ASAP database can summarize 10, 100, or even 1000 or more individual processes. MONITOR PROCESS SALES\ORDERS\## • To monitor a TCP/IP Process entity and its sub-entities TCPICMP, TCPIP, TCPQIO, TCPRTE and TCPUDP: MONITOR TCPPROCESS $ZTCP01 • To monitor a specific TCP/IP route: MONITOR TCPROUTE $ZTCP01.
ASAP Conversational Interface Commands NODE Command Entity MONITOR Syntax TELSERV SERVICE MONITOR TELSERVSERVICE $telservprocess.service TELSERVWIND OW MONITOR TELSERVWINDOW $telservprocess.#window TAPE MONITOR TAPE $devicename TMF MONITOR TMF tmf-domain ** * No backslash (\) in the node names.
ASAP Conversational Interface Commands NODE Command want a particular dnode, specify the dnode by system name (such as \SUPPORT) or system number (\240). TIME hh:mm m/d/y defines the ending time of the display information in hours, minutes, month, day, and year. For example, specifying “TIME 10:15” when the rate is 5 indicates that statistics collected from 10:10 to 10:15 are displayed.
ASAP Conversational Interface Commands OBEY Command Statistics Description/Options RAW Statistics displayed in tabular format rather than the standard display SYSNO The system number of the destination Expand system node TIME Statistics starting at a time other than the current time Examples These examples show the report output that you can display with the NODE command: +NODE !Show last sample for all destination nodes connected to current active source node.
ASAP Conversational Interface Commands PAUSE Command STARTUP COLLECT PAUSE Command The PAUSE command temporarily suspends the ASAP Conversational Interface. It causes the program to suspend execution until it receives a stop, abend, or break message. PAUSE Example This example shows the PAUSE command: + PAUSE PROCESS Command The PROCESS command displays availability statistics about the processes specified in the command. PROCESS [\* ] [ [.] * ] [, [\node] [ [.
ASAP Conversational Interface Commands PROCESS Command SAMPLES count specifies the number of sample periods to be displayed, starting with the most recent sample. A sample period is defined by the RATE option in the SET command. You can specify 0 through 255 sample periods. The default sample period number is 1. DETAIL specifies to return more detailed information about the specified monitored processes.
ASAP Conversational Interface Commands PROCESS Command state shows records with at lease one attribute state equal to or higher than state. Valid states are 1 through 8. AUTO shows records with at lease one attribute state greater than state 2 (OK). COUNT defines the maximum number of records to display. MEMORY retrieves data directly from ASAP memory instead of the database. ASAP uses the MEMORY option for the EDL DETAIL property of the Process Entity definition.
ASAP Conversational Interface Commands PROCESSBUSY Command To show detail statistics for process $PROC1: + P $PROC1, DETAIL To show detail statistics and their associated ASAP states for process $SGPM: + P $SGPM, DETAIL, STATE To show aggregate process statistics along with detail statistics: + P, AGGREGATE To show only aggregate process statistics: + P, AGGREGATEONLY To retrieve all records for all processes that are issuing alerts: + P, AGG, MINSTATE To retrieve detail information about aggregate o
ASAP Conversational Interface Commands PROCESSBUSY Command OUT file specifies the spooler or line printer where the ASAP output is sent. If you do not specify an output file, the output is displayed on your terminal. \* specifies that all process information for all systems is displayed. node specifies the individual system for which availability information is displayed. If you want information for all the systems, specify PROCESSBUSY \*.
ASAP Conversational Interface Commands • • • • PROCESSBUSY Command Number of messages received per second Number of messages sent per second Number of physical memory pages currently in use Average number of link control blocks in use or reserved by this process STATE shows all attributes that have an associated state. Associated states are displayed for the ProcessBusy command without any options, and the ProcessBusy command works only with no other options.
ASAP Conversational Interface Commands PROCESSBUSY Command PROCESSBUSY Statistics Table 6-9 lists the PROCESSBUSY availability information and options displayed with the HELP PCBSTATS command. Table 6-9.
ASAP Conversational Interface Commands • QUERY Command To display four samples starting at 10:15: PROCESSBUSY \*, S4, TIME 10:15 • To display five processes: PROCESSBUSY \*, ENTRIES 5 • To display detailed process statistics: PROCESSBUSY \*, STATS • To display the detailed busy process statistics: PROCESSBUSY \*, INFO • These examples show the report output you can display with the PROCESSBUSY command: +PB !Default \ASAP TIME Busy Pin Program Object Filename Name Pri Userid -------------------
ASAP Conversational Interface Commands QUERY Command The QUERY command displays Query entity statistics for the specified nodes and domain names. domain A complete or partial domain name. SAMPLES Defines the number of samples to display per domain. TIME Defines ending time and date of samples to display. DETAIL Display detailed process attribute information. STATES Display attributes and their associated ASAP states.
ASAP Conversational Interface Commands SQLTEXT Display a more complete copy of the SQL text from a query. AGE Only return removed objects for the past number of minutes specified.
ASAP Conversational Interface Commands RANK Command RANK Command The RANK command controls the objectives used to produce alerts and spawn actions within ASAP. It controls the set of objectives and gets information about those objectives. RANK [/OUT file/] [entity | *] [\node], COMMIT [.| ]][domain]], goal [,goal,...
ASAP Conversational Interface Commands RANK Command domain is any form of an ASAP domain name. Domain names can represent physical devices ($Data) or abstract representations of applications (Funds\Transfer\Input). Some command options support the asterisk wild-card character at the end of the domain name. COMMIT sends a commit request to all entities or a specific entity on the local or a remote node. This request causes ASAP to reload its set of objectives for the entity or entities on the node.
ASAP Conversational Interface Commands RANK Command event INFO | CRITICAL [REPEAT] [NODISPLAY] [down] [-up] INFO configures ASAP to generate an informational event when the objective is not met. CRITICAL configures ASAP to generate a critical event when the objective is not met. REPEAT causes ASAP to repeat the event for each interval where the objective is not met. NODISPLAY overrides any global settings to suppress display of the event on the operator console.
ASAP Conversational Interface Commands RANK Command NOEMS Used only with the STATUS attribute. NOEMS turns off automatic event generation for status changes in ASAP system entities. action ACTION string | rule [WAIT wait] [NOREPEAT] string is an action string where the first word in the string is a command interpreter name such as TACL, SCF, or FUP, and the remainder of the string represents the command to be executed by that command interpreter.
ASAP Conversational Interface Commands RANK Command WAIT wait indicates the number of minutes ASAP should wait before retrying an action string against a particular entity and domain. The wait time also depends on the ASAP rate setting because ASAP validates objectives only once per cycle. NOREPEAT indicates that ASAP should not continue to repeat the action until the condition is corrected. LIKE sets attributes in the new or modified domain that are currently active in the LIKE domain.
ASAP Conversational Interface Commands RANK Command LIST retrieves a list from the active set of objectives for all entities or for a specific entity. The LIST command communicates directly with running ASAP components to retrieve objective information. entity must be specified when domain is specified; otherwise both are optional. Domain names can use the asterisk wild-card character as the last character in the name.
ASAP Conversational Interface Commands • RANK Command To define an action to reload a CPU after it fails: RANK CPU, STATUS ACTION "TACL RELOAD <#DOMAIN>, PRIME" WAIT 15 • To define a goal and action to secure the NonStop OS userid file to "OOOO": RANK FILE $SYSTEM.SYSTEM.
ASAP Conversational Interface Commands RDF Command RDF Command The RDF command displays RDF entity availability statistics for the specified nodes and domain names. For a description of RDF statistics, enter HELP RDFSTATS. RDF [/OUT file/] [ \* ] [ [.] * [ \node ] [ [.] domain ] ][, [, [, [, [, [, SAMPLES count ] CPU ] DETAIL ] STATES ] TIME hh[:mm [m/d/y]] VOLUMES ] node specifies the individual system for which availability information is to be displayed.
ASAP Conversational Interface Commands RDF Command m/d/y is the month, day, and year. Valid entries are mm/dd/yy, yyyy/mm/dd, or mm/dd/yyyy. VOLUMES displays the associated disk volumes.
ASAP Conversational Interface Commands 0:00:00 + • 3 2 RDF Command 185 To show related disk volumes: RDF \*, VOLUME \TANDA Domain\Name\Hierarchy Aud Vol -------------------------------- -------Dome->Tanda\Imagetrail\$Data4 n/a Dome->Tanda\Purger\$Purg n/a Dome->Tanda\Receiver\$Rec1 n/a Dome->Tanda\Updater\$Up01 n/a Dome->Tanda\Updater\$Up02 n/a Dome->Tanda\Updater\$Up03 n/a \DOME Domain\Name\Hierarchy -------------------------------Dome->Tanda\Extractor\$Ext1 Dome->Tanda\Monitor\$Mntr + • Img Vol
ASAP Conversational Interface Commands RDF Command --------------- ---------- ----- - -- ----- -------- --------- ---- ---- --Running 2001/05/11 09:50 1 01 0 0 0:00:00 2 3 185 continued...
ASAP Conversational Interface Commands SET Command SET Command The SET command displays and sets these data collection and monitoring options: SET [ ACTION ON | OFF ] [ ACTOBJECT filename ] [ ACTSHELL filename ] [ APP entity-option ] [ ASAPLOG filename ] [ BACKUPCPU cpu | * ] [ BUFFERED ON | OFF ] [ CLEANTIME time ] [ COLLECT \collect-node ] [ COMM entity-option [, entity-option], ] [ DB db-file-prefix ] [ DBMAXDAYS [ [ entity ] days ] ] [ DBMAXDAYSTOPURGE days ] [ DBROLLOVERSUBVOLPREFIX prefix ] [ DBROLL
ASAP Conversational Interface Commands [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ PRIORITY PROCESS PROCESSBUSY PROXY PROXYCONFIG PROXYCPU PROXYOBJECT PROXYPARAM QUERY RATE RDF REMOTESECURITY RETAIN SLEEPTIME SPOOLER SYNC TAPE TERM TCP TMF TRACE SET Command server-priority entity-option ENTRIES count | SUBSAMPLES count ON | OFF filename number object-filename proxy-parameter entity-option minutes entity-option ON | OFF option time,time entity-option minutes,frequency entity-option logterm ON | OFF entity-
ASAP Conversational Interface Commands SET Command SET ACTION OFF means the RANK/GOAL ... ACTION string associated with an objective is not performed when objectives are not satisfied. ACTOBJECT action-server-program-filename defines the action server program object filename. The default is SEEVIEW. ACTSHELL action-script-filename defines the action server script filename. The default is ASAPACT. APP entity-option [, entity-option]... determines settings and parameters for the APP entity.
ASAP Conversational Interface Commands SET Command BACKUPCPU cpu | * defines the preferred backup CPU number for the Collect or Monitor process started by the STARTUP command. If this CPU is unavailable, the next available CPU is used. * indicates that if a CPU is available, the Monitor or Collect process assigns the next available CPU as the backup CPU. BUFFERED ON | OFF specifies whether the information written to the database is buffered. ON specifies buffered writes. The default is OFF.
ASAP Conversational Interface Commands SET Command CPU cpu-number defines the CPU where the MEASFH process resides. If an unavailable CPU is selected, the ASPCMM process selects the next available CPU. The default is the same as the CPU that the ASAP CI is executing in. NOMEAS prevents COMM performance statistics from being collected.
ASAP Conversational Interface Commands SET Command entity specifies the entity. days specifies the max number of of statistical history that will be retained for that entity. This option works in conjunction with the SET RETAIN ROLLOVER option allowing database record sets on a per entity basis to be automatically rolled-over and saved on a daily basis. The SET DBMaxDays option is only meaningful if SET RETAIN ROLLOVER is enabled.
ASAP Conversational Interface Commands SET Command DBMAXDAYSTOPURGE days Defines the maximum number of old daily filesets that will be purged at each database cleanup rollover. This option limits the number of daily file sets that will be purged for a given rollover. days specifies the number of daily purge file attempts for each entity. A value other than 1 causes the rollover algorithm to reattempt file purges on subsequent days.
ASAP Conversational Interface Commands SET Command prefix defines the 1 through 4 alphanumeric character prefix. For example, ASAP. yyyy indicates year rollover occurred. For example, 2004. mm indicates the month rollover occurred. For example, 12. dd indicates day rollover occurred. For example, 31. EEE indicates three letter entity acronym. For example, CPU, DSK, or EXP. SET DBRolloverSubvolPrefix ASAP results in the following filename for a file containing CPU statistics from 2004, December 31: $DATA.
ASAP Conversational Interface Commands SET Command PARAMETERS "DISK-param [DISK-param}..." | null specifies the disk-specific parameter string to be passed to the ASAPDSK process at startup time. The parameter list must be enclosed in quotation marks. The default is null. DISK-param values are: CPU cpu-number defines the CPU where the MEASFH process resides. If an unavailable CPU is selected, the ASPDSK process selects the next available CPU.
ASAP Conversational Interface Commands SET Command EXPAND ON | OFF controls network-wide Expand line-handler availability reporting. CPU cpu-num defines the CPU that the EXPAND SGP process will reside in. ON | OFF ON enables or disables network-wide Expand line-handler availability reporting. The default is OFF. OBJECT ASAPEXP-program-file-name defines the ASAPEXP program object file name. If ON is specified, this program automatically starts on each node by the ASAP Monitor. The default is $SYSTEM.
ASAP Conversational Interface Commands SET Command OBJECT defines the ASAP/FILE program object filename; this program is automatically started on each node by the ASAP monitor. The default is $SYSTEM.SYSTEM.ASAPFIL. PARAMETERS "FILE-param [ FILE-param]... " | null specifies the FILE specific parameter string to be passed to the ASAPFIL process at startup time. The default is the null string. The Parameter list must be enclosed in double quotes.
ASAP Conversational Interface Commands SET Command TRACE turns $Receive tracing on in the File SGP. The SGP generates a log message for each read or reply. RATE #mins sets a specific rate for the File SGP. See SET RATE. MAXAGGS defines the maximum number of aggregate domains. The File SGP will allocate memory to support that number of aggregate domains. Valid values are 2 through 32767. ASAP will always allocate 1 less domain than you specify. The default setting can vary by ASAP version.
ASAP Conversational Interface Commands SET Command All lines starting with a TGAL backslash are ignored. ID $asap-pid defines the ASAP process ID name set. This name set identifies a collection of ASAP processes that are operating together to gather ASAP performance statistics and operational state information. The default is $ZOO. Using the ID lets you operate several ASAP programs in the same node or resolve a name conflict.
ASAP Conversational Interface Commands SET Command LOGFILE filename defines the name of the file used for ASAP CI I/O capture. LOGGING ON/OFF controls access to the file. The default is the current $volume.subvolume.logfile. LOGGING ON | OFF determines settings for the capture of ASAP CI I/O. ON enables the capture of ASAP CI I/O to a file defined by LOGFILE filename. OFF disables the capture of ASAP CI I/O. The default is OFF.
ASAP Conversational Interface Commands SET Command MONITORADD ON | OFF ON sets the default for MONITOR entity domain to ADD the domain to the set of monitored objects. This is the default. OFF sets the default for MONITOR entity domain to be INFO, to list the domain if it belongs to the set of monitored objects in the database. Examples By default, this command adds $DATA as a disk to be monitored. If $DATA is the first disk to be entered, the command also turns off auto-configuration of all disks.
ASAP Conversational Interface Commands SET Command PARAMETERS " node-param [node-param]..." | null specifies the NODE-specific parameter string to be passed to the ASAPNCP process at startup time. The parameter list must be enclosed in quotation marks. The default is null. RATE minutes defines the interval, in minutes, that NCP statistics are reported back to the Collector. The default is 10 minutes. Examples These two examples show the SET NODE command: + SET NODE ON, OBJECT $SYSTEM.ASAP.
ASAP Conversational Interface Commands SET Command The default is $SYSTEM.SYSTEM.ASAPCOL. OBJECTIVESAUDIT ON | OFF enables or disables TMF for auditing of the Objectives database. The default is OFF. OBJECTIVESDB filename defines the name of the Objectives database file. When you execute the first RANK or MONITOR command on a node for a specific ASAP ID, the ASAP CI always requests the name of the objectives database from the ASAPMON process referred to by that ASAP ID.
ASAP Conversational Interface Commands SET Command OBJECTIVESEVENTSTATE OEM-state indicates the state at which to generate an event when objectives are not met for an attribute with event generation specified. Allowed OEM States are: OEM-state is one of: LOW MEDIUM HIGH WARNING CRITICAL DOWN Low performance alert Medium performance alert High performance alert Warning alert Critical problem alert Down object alert The default is CRITICAL.
ASAP Conversational Interface Commands SET Command When used with no options, SET PARTITION displays the current partitioning settings. Note. Changes to partition settings do not automatically take effect after a SET PARTITION command. To enable changes: 1. Stop the ASAP Collector process. 2. Delete or rename the existing ASAP database. 3. Restart the Collector. This re-creates the ASAP database using the new partition settings. partition-desc. used to set partitioning attributes.
ASAP Conversational Interface Commands SET Command * Decimal integers representing byte values from 0 through 255, enclosed in brackets (for example, [10, 13, 129]). You can use this format to represent any partial key value, on a byte-by-byte basis. * A mixture of quoted character strings and decimal integer byte values enclosed in brackets (for example, [10, "ab", 13, 129]).
ASAP Conversational Interface Commands { entity | DEFAULT } { SET Command part-num | ALL } part-opt RESET resets a specific partitioning attribute for the specified entity and partition number. To reset the default setting of the specific attribute, use DEFAULT. To reset all partitions of the specified entity, use ALL. FORMAT2 { ON | OFF } enables or disables support of Format 2 files. Format 2 support lets ASAP retain much more data by allowing the creation of much larger files and partitions.
ASAP Conversational Interface Commands SET Command occurs in the Collector when the database is created, so the keys are not shown in this adjusted form in the ASAP CI. The SYSNO value is considered to be part of the key and, if specified, is factored into the key length. • • Issuing a SET DB command resets all partitioning attributes. The Collector uses only valid partition descriptions (those listed as Valid in the SET PARTITION command output) when creating the database.
ASAP Conversational Interface Commands SET Command Value Indicates That the Partition Definition Is... Used by Collector to Create Database? ??-Vol Down Questionable because the specified volume is down. Specify a volume that is not down. Yes, with errors ??-Partn Size Not optimal because the maximum potential partition size defined by PRIEXT, SECEXT, and MAXEXTENTS exceeds the limit for the specified file format.
ASAP Conversational Interface Commands • SET Command To reset the KEY value for partition 1 of the DISK entity to its default: SET PARTITION DISK 1 KEY RESET • To enable FORMAT2 support: SET PARTITION FORMAT2 ON PRIMARY cpu | * defines the primary CPU number for the Collect or Monitor process started by the STARTUP command. If this CPU is unavailable, no other CPU is used. The default is asterisk (*), which is all CPUs for the specified system.
ASAP Conversational Interface Commands SET Command MINONLY when a MINONLY state is specified, the Process SGP operates in exception mode, writing only alerting detail domain records to the database. MINONLY is used to determine the state at which a domain is considered to be alerting and ASAP writes only those domain records to the database, removing them after they return to normal. A domain is considered to be alerting if ANY attribute state is greater than or equal to MINONLY.
ASAP Conversational Interface Commands SET Command Examples To turn process monitoring on and to set the state at which ASAP considers a process to be alerting enter: SET PROCESS ON, PARAM "MINSTATE 6" To turn on aggregation for all levels of all hierarchically named processes: SET PROCESS PARAM "AGG" PROCESSBUSY ENTRIES count | SUBSAMPLES count controls the collection of process statistics.
ASAP Conversational Interface Commands SET Command Example SET PROXY ON PROXYCONFIG filename filename The fully qualified, local ASAP Hybrid Proxy server configuration filename. The default is $SYSTEM.SYSTEM.ASAPPCNF. ASAP Hybrid is an optional ASAP product. Example SET PROXYCONFIG $DATA.ASAP.ASAPPCNF PROXYCPU number number The processor where ASAP will start the ASAP Hybrid Proxy server. ASAP Hybrid is an optional ASAP product.
ASAP Conversational Interface Commands SET Command OBJECT filename specifies the name of the Query SGP program file. The default is $SYSTEM.SYSTEM.ASAPQRY. PARAMETERS "QUERY-param [ QUERY-param]... " | null specifies the QUERY specific parameter string to be passed to the ASAPQRY process at startup time. The default is the null string. The Parameter list must be enclosed in double quotes. QUERY-param options are: TRACE turns on $RECEIVE trace to the EMS and ASAP log files.
ASAP Conversational Interface Commands SET Command ENDFETCH num defines the number of intervals that an inactive query will remain in the active query list before being automatically removed. The default is the computed number of intervals to equal 5 minutes of inactivity. If the interval time is 5 minutes or more, then the default is one interval. The ASAP monitor does not check the contents of the parameter string. All parameter data is passed to the ASAPQRY process without modification.
ASAP Conversational Interface Commands SET Command OBJECT filename specifies the name of the Process SGP program file. The default is $SYSTEM.SYSTEM.ASAPRDF. PARAM "RATE #mins" overwrites the ASAP default rate parameter for the RDF SGP only. Instructs the RDF SGP to sample at this rate. PARAM "TRACE" turns $Recieve tracing on in the Process SGP. The SGP generates a log message for each read or reply.
ASAP Conversational Interface Commands SET Command This example keeps ASAP database files for historic purposes: +SET RETAIN ROLLOVER +STARTUP COLLECT The RETAIN number option can have a negative performance impact in networks that monitor large numbers of nodes in a database. This occurs when it becomes necessary to process large numbers of statistics records in the database. SLEEPTIME time, time defines the time range (hhmm,hhmm) when statistics collection does not occur.
ASAP Conversational Interface Commands SET Command DETAIL instructs the Spooler SGP to return individual detail records by default. The Spooler SGP otherwise operates in aggregation mode by default, returning one aggregate record for all collectors, one for all devices, and one for all print processes. RATE #mins overwrites the ASAP default rate parameter for the Spooler SGP only. Instructs the Spooler SGP to sample at this rate. TRACE instructs the Spooler SGP to log trace records to the ASAP log file.
ASAP Conversational Interface Commands SET Command SYNCSLOW ON | OFF defines the clock synchronization algorithm. The SET SYNC option controls when time-of-day synchronization occurs. The SET SYNCSLOW option controls the algorithm. You can manually correct the time on any node with the TACL SETTIME command, regardless of how SET SYNC or SYNCSLOW is set. ON adjusts the time-of-day clock on remote ASAP nodes very slowly to avoid sudden time of day changes.
ASAP Conversational Interface Commands SET Command TRACE instructs the Tape SGP to log trace records to the ASAP log file. Example +SET TAPE ON, OBJECT $SYSTEM.SYSTEM.ASAPTAP, PARAMETERS "RATE 5" TERM logterm | OFF defines the Collect or Monitor terminal log-file name to which internal errors and actions are logged. The default is $0. A disk error log file $SYSTEM.ASAP.ASAPLOG is always created and maintained. logterm specifies another name for the terminal log file. OFF disables terminal (or $0) logging.
ASAP Conversational Interface Commands SET Command RATE minutes defines the interval, in minutes, that TCP statistics are reported back to the Collector. The default is the ASAP RATE. The range is from 1 to 120 minutes. SCPNAME $name defines the SCP process name the SGP will use to retrieve statistics from the TCP/IP and Telserv subsystems. If no SCPNAME is specified, the SGP will attempt to start one but security concerns could prevent a successful start of an SCP process.
ASAP Conversational Interface Commands SET Command WINDOW [n] turns on monitoring of Telserv Widows, and optionally specifies the minimum number of minutes the SGP will wait before reconfiguring Telserv Windows when they are being automatically configured by the SGP. Window monitoring is off by default, and the configuration interval defaults to the ASAP rate. MAXTCP n defines the maximum of number of TCPPROCESS domain records that can be processed by the SGP.
ASAP Conversational Interface Commands SET Command MAXWIN n defines the maximum of number of TELSERVWINDOW domain records that can be processed by the SGP. Domains are either autoconfigured or entered using the MONITOR command. The default is 1000 domains. The maximum is 32767. The ASAP monitor does not check the contents of the parameter string. All parameter data is passed to the ASAPTCP process without modification.
ASAP Conversational Interface Commands SHOW Command RATE minutes defines the interval, in minutes, that TMF statistics are reported back to the Collector. ASAPTMF uses the interval provided by the operator. The default is the ASAP RATE. The ASAP monitor does not check the contents of the parameter string. All parameter data is passed to the ASAPTMF process without modification. This example shows the SET TMF command: +SET TMF ON, OBJECT $SYSTEM.ASAP.
ASAP Conversational Interface Commands SHUTDOWN Command Examples SHOW SHOW SHOW SHOW SHOW SHOW DISK DISK, DETAIL DISK, ATTRIBUTES FILE FULL FILE, DETAIL, ATTRIBUTES SHUTDOWN Command The SHUTDOWN command stops ASAP Monitor, SGPs, and Collect processes on the nodes that you specify. Only someone with a super-group user ID can use this command. SHUTDOWN [ \* [ \node-name ] ] [ COLLECT | MONITOR ] [ [.] ppd-name ] \* shuts down the ASAP Monitor or Collect process on all nodes of the network.
ASAP Conversational Interface Commands SPOOLER Command Considerations • • SHUTDOWN shuts down Monitor (default) or Collect processes. After shutdown is complete, data collection stops. SPOOLER Command The SPOOLER command displays Spooler availability information for the specified nodes and Spooler domains. For an explanation of Spooler statistics, enter HELP SPOOLERSTATS at an ASAP prompt. SPOOLER [/OUT file/] [\*] [ [.] * ] [, [\node] [ [.
ASAP Conversational Interface Commands SPOOLER Command SAMPLES count specifies the number of sample periods to be displayed. A sample period is defined by the RATE option in the SET command. You can specify 0 through 255 sample periods. The default sample period number is 1. TIME hh:mm m/d/y defines the ending time of the display information in hours, minutes, month, day, and year.
ASAP Conversational Interface Commands SPOOLER Command MINSTATE shows detailed information on subdomains with states greater than or equal to what is specified. states indicates the minimum state to report. AUTO indicates to use state 2 as the minimum. This is the default setting. AUTOSHORT indicates to return aggregate information where state is greater than or equal to two. EXACT indicates to return information about domains that exactly match spoolerspec.
ASAP Conversational Interface Commands 392 0 0 392 0 0 0 0 0 0 0 0 0 0 0 SPOOLER Command 50 0 0 50 0 0 200 8 17 53 6 6 30 50 + • To retrieve detailed information for multiple domain types in a spooler collection: + SPOOLER $SPLS, DETAIL It displays: \ASAP Spooler Domain -----------------------------$SPLS\COLL\$S $SPLS\COLL\$L $SPLS\DEV\$P275A $SPLS\DEV\%P275B $SPLS\DEV\CENTREG.$A.
ASAP Conversational Interface Commands SPOOLER Command It displays: \ASAP Spooler Collectors Status Date Time Error Cpu BCpu Prty ------------------------------ ---------- ----- ----- ----- --- ---- ---$SPLS\COLL\$S Active 03/23 8:07 0 0 1 149 continued... Data File Name Jobs Batch Open Print Hold Size UnitAlloc -------------------------- ----- ----- ---- ----- ---- ----- --------$DATA2.SPL.DATA 378 0 0 0 100 4 1916 continued...
ASAP Conversational Interface Commands STARTUP Command STARTUP Command The STARTUP command starts ASAP Monitor, SGPs, and Collect processes on the nodes that you specify. Only someone with a super-group user ID can use this command. STARTUP [\* [\node-name] ] [ COLLECT | MONITOR] \* starts the ASAP Monitor or Collect process on all nodes of the network. COLLECT starts the ASAP object specified by the SET OBJCOLLECT option. MONITOR starts the ASAP object specified by the SET OBJMONITOR option.
ASAP Conversational Interface Commands STATUS Command Considerations • • The STARTUP command starts Monitor, SGPs, or Collect processes on the specified nodes with the specified options. The object file to use is specified with the SET OBJMONITOR and OBJCOLLECT options. For SGP processes, the SGP object is specified with the SET SGPName OBJECT option. The Monitor, SGPs, and Collect process behavior is based on the current values of the SET command parameters when the process is started.
ASAP Conversational Interface Commands STATUS Command ppd-name specifies a process-pair directory name. The process pair directory is a list of the process names and corresponding pairs of process numbers that make up each process kept by the NonStop OS operating system. ACTIONS displays action server actions. STATUS ACTIONS ASAP displays analysis of last action request. STATUS ACTIONS RUN displays actions actually run. ACTREQUEST shows last action request.
ASAP Conversational Interface Commands STATUS Command The Backup column, instead of showing the backup CPU, PIN, might indicate one of: Display Meaning CMM Comm SGP DSK Disk SGP EXP Expand SGP FIL File SGP PRO Process SGP RDF RDF SGP SPL Spooler SGP TAP Tape SGP TMF TMF SGP Example +STATUS \ISLAND ! Show \ISLAND’s Status \ISLAND Primry Backup Pri Access Reqs Lmsgs Created ReqTime SrvTime Et --------- ------ ------ --- ------- ----- ----- -------- ------- ------- --$ZOOM V02 0,148 1,048
ASAP Conversational Interface Commands SYNC Command $ZOOU V03 1,154 COM 160 255,255 3309 (collect \CENTDIV.$ZOOS, rate 1, sync 60,1) 2 6/20 16 2033:10 2033:10 0 SYNC Command The SYNC command requests the Monitor on the specified node to set the NonStop OS time of day clock to the NonStop OS time of day clock on the node where the Collect server resides. SYNC [ \* ] [ MONITOR ] [ \node-name] [ [.] ppd-name ] \* synchronizes information on all nodes.
ASAP Conversational Interface Commands TAPE Command node-name specifies a node name. node-number specifies a node number. Example + SYSTEM \MEMPHIS TAPE Command The TAPE command displays Tape availability information for the specified nodes and Tape domains. For an explanation of Tape statistics, enter HELP TAPSTATS at an ASAP prompt. TAPE [/OUT file/] [\* ] [ [.] * ] [, SAMPLES count ] [\node] [ [.
ASAP Conversational Interface Commands TAPE Command EXACT indicates to retrieve only information that exactly matches tapespec. Consideration • You cannot use TIME, SAMPLES, or \* with DETAIL.
ASAP Conversational Interface Commands BK0001 + SCRATCH BACKUP $BKUP TAPE Command BACKUP 255,23 - - - If tapemount requests are pending, it displays: \ASAP -------$DLT00 $DLT00 Status Date Time DevNo CPU BCPU Sub ACS Checks Mnts Mtime --------- ----- ----- ----- --- ---- --- --- ------ ---- ----Free 3/23 8:07 378 0 1 9 Yes BLP 45 45 Free 3/23 8:07 255 0 1 9 Yes BLP 238 5 continued... TapeName -------BK0002 FUP005 TpStatus -------6250 6250 TpLabel ------BACKUP ANSI ProcName ------------\ASAP.
ASAP Conversational Interface Commands TCP Command TCP Command TCP [/OUT /] [\* ] [ [.] * ] [,SAMPLES count ] [\node] [ [.] domain][,STATES ] [,TIME hh[:mm [m/d/y]] [, MINSTATE [AUTO] ] [ [state] ] [, COUNT count ] [,EXTRACT filename ] [,NOPRINT ] [,NOLINEBREAK ] [,AGE minutes ] entity [\* ] [ [.] * ] [, DETAIL ] [\node] [ [.
ASAP Conversational Interface Commands TCP Command DETAIL displays custom detailed TCP metric values for specific sub-entities. MINSTATE records based on attribute states: state AUTO show records with at lease one attribute state equal to or higher than . Valid states are 1 through 8. show records with at lease one attribute state greater than state 2 (OK). defines the max number of records to display. extract TCP records from the ASAP database to a separate database file or to a process.
ASAP Conversational Interface Commands TMF Command TMF Command The TMF command displays TMF availability information for the specified nodes and TMF domains. For an explanation of TMF statistics, enter HELP TMFSTATS at an ASAP prompt. TMF [/OUT file/] [\* ] [ [.] * ][, [\node] [ [.] domain][, [, [, [, SAMPLES count TIME hh[:mm [m/d/y]] STATES DETAIL MINSTATE [state ] [AUTO ] [AUTOSHORT] ] ] ] ] ] ] ] * indicates to retrieve all tape records from all nodes.
ASAP Conversational Interface Commands TMF Command DETAIL indicates to display detailed information for the specified domain, without states. EXACT indicates to retrieve only information that exactly matches tapespec. MINSTATE displays TMF subdomains depending on the selected option: state shows subdomains with an OEM-state greater than or equal to state. AUTO shows subdomains with an OEM-state greater than 2, or else shows all subdomains.
ASAP Conversational Interface Commands S Tps S BeginTr - -------- - -------1 - 1 7 - 1 1 0.
ASAP Conversational Interface Commands • VOLUME Command To display details about all TMF audittrail subdomains where at least one attribute has a state value greater than 2 (if no audittrail subdomains meet this condition, all audittrail subdomains are displayed): + tmf audittrail, minstate auto \ASAP AuditTrail Date Time Ovflw S Hold S Used% S Thresh% ---------------- ----- ------ ----- - ---- - ----- - ------Master 3/14 13:18 No 1 No 1 62 7 80 continued...
A Querying the ASAP Database The ASAP database is a set of key-sequenced files that you can query using Enform or user-written programs. This section shows a sample standard Enform query and a sample ASAPCOL as an Enform server. The ENFALL file contains a complete set of sample queries. Standard Enform Query This example shows a standard Enform query: ?section cpu !----------! ! Display cpu statistics by \node and cpu for each hour of the day.
Querying the ASAP Database ASAPCOL as an Enform Server timestamp-time ( x ) as time "h2:m2" space cpubusy as i4 space cpuq as "[bz] i2" space cpudisp as "[bz] i4" space discrate as "[bz] i4" space chitrate as "[bz] i4" space swaprate as "[bz] i4" space memq as "[bz] i2" space pcbmax as "[bz] i4" space lcbmax as "[bz] i4" space ; ASAPCOL as an Enform Server This example shows ASAPCOL as an Enform server: ?section cpu-last-hour !--------------------! ! Display cpu statistics b
Querying the ASAP Database ASAPCOL as an Enform Server sysname cpuno space as i3 space timestamp-date ( x ) as date "mb2/d2" space timestamp-time ( x ) as time "h2:m2" space cpubusy as i4 space cpuq as "[bz] i2" space cpudisp as "[bz] i4" space discrate as "[bz] i4" space chitrate as "[bz] i4" space swaprate as "[bz] i4" space memq as "[bz] i2" space pcbmax as "[bz] i4" space lcbmax as "[bz] i4" space ; HP NonStop ASAP Server Manual—522303-007 A- 3
Querying the ASAP Database ASAPCOL as an Enform Server HP NonStop ASAP Server Manual—522303-007 A- 4
B ASAP Data Definitions This appendix contains the ASAP database data definitions and record layouts that are stored in a file named ASPDDLDB. These formats can change from one product version to the next. DDL Section Definitions Primary Key Definitions The primary key is (sysno entity its), where its is a character-based inverted timestamp of the event. Entries are displayed from the most recent event to the oldest event, allowing efficient online access through the ASAP CI.
ASAP Data Definitions 03 03 02 02 02 02 02 02 02 02 END. Extended Primary Key lhsysno lhlinename Entity iyear imonth iday ihour imin isec irank type binary 16 display "m<\999.>". type character 8. type character 8 redefines ikey. pic x(11) redefines ikey. pic x(12) redefines ikey. pic x(13) redefines ikey. pic x(14) redefines ikey. pic x(15) redefines ikey. pic x(16) redefines ikey. pic x(17) redefines ikey.
ASAP Data Definitions 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 END. Comm Statistics Definitions sysname P-key-x Q-key-x event Pid Cpu Pin Spare AggRec Data-count Op-Text OpText OpState Error Error-state DitemCount Ditem Data type character 8 redefines system. type *. !sysno, domain & its 8.3 type * redefines P-key-x. !enform q-key extended type *. !ts, interval & info type character 8. !the process' name type binary 16. !the process' cpu type binary 16.
ASAP Data Definitions 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 END.
ASAP Data Definitions 02 02 02 02 02 02 02 02 02 02 02 02 03 03 02 02 02 Disk Entity Statistics Definitions Qlen-State type binary 16. !cpu queue length state Swaps-State type binary 16. !cpu pagefault state Mqlen-State type binary 16. !memory queue length state Disps-State type binary 16. !cpu dispatch state Chits-State type binary 16. !cache hit rate state Discs-State type binary 16. !disc i/o rate state pcb-use-State type binary 16. !pcbs in use state mem-use-State type binary 16.
ASAP Data Definitions 03 03 03 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 END. Expand Entity Statistics Definitions Spare2 type binary 16. Spare3 type binary 16. Spare4 type binary 16. OpState type binary 16. Big-Frag type binary 32. Avail-Space-State type binary 16. B-Splits-State type binary 16. Chit-State type binary 16. Qlen-State type binary 16. Requests-State type binary 16. Reqs-Blckd-State type binary 16. Swaps-State type binary 16. Read-State type binary 16.
ASAP Data Definitions 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 Expand Entity Statistics Definitions enq-send type binary 32. !send + 8 !-- LEVEL 4 Rcvd Ops ----!rcvd-base = stat-base+21 conn-rcvd type binary 32. !rcvd + 0 trace-rcvd type binary 32. !rcvd + 1 ncpm-rcvd type binary 32. !rcvd + 2 lrq-rcvd type binary 32. !rcvd + 3 lcmp-rcvd type binary 32.
ASAP Data Definitions 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 END. File Entity Statistics Definitions dat-bytes-rcvd-state type binary 16. Conn-Cmds-sent-state type binary 16. Conn-Cmds-rcvd-state type binary 16. Conn-Rsps-sent-state type binary 16. Conn-Rsps-rcvd-state type binary 16. quer-cmds-sent-state type binary 16. quer-cmds-rcvd-state type binary 16. quer-rsps-sent-state type binary 16. quer-rsps-rcvd-state type binary 16. Mem-low-state type binary 16.
ASAP Data Definitions 02 02 02 02 02 02 02 02 02 02 02 END. Node Entity Statistics Definitions FCode FFormat FType SQLType Partitions LastOpen Last Modif type type type type type type type binary binary binary binary binary binary binary 16. 16. 16. 16. 16. 64. 64. Spare1 Spare2 Spare3 Spare4 type type type type binary binary binary binary 16. 16. 16. 16. !File code !1=Format1, 2=Format2 !Unstruct, relative, etc. !Protection view, table, etc.
ASAP Data Definitions ProcessBusy Statistics Definitions 02 Pri 02 PriState 02 Busy type binary 16. type binary 16. type binary 64. 02 02 02 02 02 02 02 02 02 02 type type type type type type type type type type 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 END. BusyState P-State PState PStateState W-State WState WStateState MPages MPagesState MSent ! Priority ! Process busy 8.14.03 implied decimal binary 16. binary 16 occurs 4 times. ! Process state character 1 redefines P-State.
ASAP Data Definitions 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 END. SQL/MX Query Statistics Definitions Rmsgs type binary 32 redefines MsgsRcvd. MsgsSent type binary 16 occurs 2 times. Smsgs type binary 32 redefines MsgsSent. userinfo type binary 16 unsigned. rfe2 type binary 16 unsigned. rfe3 type binary 16 unsigned. rfe4 type binary 16 unsigned. Elapsedtime type binary 64. PgmFileName type binary 16 occurs 12 times. ProgramName type character 24 redefines PgmFileName.
ASAP Data Definitions SQL/MX Query Statistics Definitions 02 ESPBusy-State 02 IntESPBusy 02 IntESPBusy-State 02 BusyESP 02 BusyESP-State 02 BusyESPSeg 02 BusyESPSeg-State 02 BusyESPCPU 02 BusyESPCPU-State 02 BusyESPPIN 02 BusyESPPIN-State 02 CompTime 02 CompTime-State 02 ExecTime 02 ExecTime-State 02 ErrorCode 02 ErrorCode-State 02 NumRows 02 NumRows-State 02 RowsAcc 02 RowsAcc-State 02 RowsRetr 02 RowsRetr-State 02 DiskReads 02 DiskReads-State 02 DiskMsgs 02 DiskMsgs-State 02 DiskBytes 02 DiskBytes-State
ASAP Data Definitions 02 Statement END. RDF Statistics Definitions type Query. ! Query Data RDF Statistics Definitions DEFINITION RDF-STATS. !Description 02 system type binary 16 occurs 4 times. !system name 02 word type binary 16 redefines system.!word alignment 02 sysname type character 8 redefines system. 02 P-key-x type *. !sysno, domain & its 02 Q-key-x type * redefines P-key-x. !enform q-key extended 02 event type *. !ts, interval & info 02 Pid type character 8.
ASAP Data Definitions Spooler Statistics Definitions 02 02 NumObjects NumTotObjects type binary 16. type binary 16. 02 02 02 02 02 02 02 02 02 02 NumJobs NumJobs-State BatchJobs BatchJobs-State OpenJobs OpenJobs-State PrintJobs PrintJobs-State HoldJobs HoldJobs-State type type type type type type type type type type binary binary binary binary binary binary binary binary binary binary 32. 16. 32. 16. 32. 16. 32. 16. 32. 16.
ASAP Data Definitions Tape Statistics Definitions Tape Statistics Definitions DEFINITION TAP-STATS. 02 system 02 word 02 sysname 02 P-key 02 Q-key 02 event 02 Cpu 02 Cpu-State 02 BCpu 02 BCpu-State 02 LDev 02 SubType 02 02 02 DriveStatus Op-Text OpText type type type 02 OpState type !Description binary 16 occurs 4 times. !system name binary 16 redefines system.!word alignment character 8 redefines system. *. !sysno, domain & its * redefines P-key. !enform q-key *. !ts, interval & info binary 16.
ASAP Data Definitions TCP/IP Entity Statistics TCP/IP Entity Statistics * This defines the structure written to ASAPCOL by the TCPIP SGP DEF ZTCPData.
ASAP Data Definitions TCP/IP Entity Statistics 02 pcbcachemiss 02 persistdrop 02 badsyn 02 droppedsyn 02 sc-added 02 sc-completed 02 sc-timed-out 02 sc-overflowed 02 sc-reset 02 sc-unreach 02 sc-bucketoverflow 02 sc-aborted 02 sc-dupesyn 02 sc-dropped END. DEF 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 ZTCPState.
ASAP Data Definitions TCP/IP Entity Statistics 02 rcv-win-pack 02 rcv-win-byte 02 rcv-after-close 02 rcv-win-probe 02 rcv-dup-ack 02 rcv-ack-too-much 02 rcv-ack-pack 02 rcv-ack-byte 02 rcv-win-update 02 predict-acks 02 predict-data 02 paws-drop 02 pcbcachemiss 02 persistdrop 02 badsyn 02 droppedsyn 02 sc-added 02 sc-completed 02 sc-timed-out 02 sc-overflowed 02 sc-reset 02 sc-unreach 02 sc-bucketoverflow 02 sc-aborted 02 sc-dupesyn 02 sc-dropped END. DEF 02 02 02 02 02 02 02 02 END ZUDPData.
ASAP Data Definitions 02 out-pkts END. TCP/IP Entity Statistics type binary 32. DEF ZIPState. 02 packets type binary 16. 02 Word type binary 16 redefines packets. 02 bad-xsum type binary 16. 02 too-short type binary 16. 02 too-small type binary 16. 02 bad-hdr-len type binary 16. 02 bad-len type binary 16. 02 frag type binary 16. 02 frag-drop type binary 16. 02 frag-timeout type binary 16. 02 fwd type binary 16. 02 cant-fwd type binary 16. 02 redir-sent type binary 16. 02 out-pkts type binary 16. END.
ASAP Data Definitions TCP/IP Entity Statistics 02 res-recov-run 02 qio-limit-warns 02 qio-driver-errs 02 max-pool-space 02 pool-fails 02 total-mbufs 02 curr-mbufs-inuse 02 max-mbufs-inuse 02 mbuf-fails 02 dup-driv-mds 02 max-dup-driv-mds 02 no-dup-driv-mds 02 size-128 02 size-256 02 size-512 02 size-1024 02 size-2048 02 size-4096 02 size-8192 02 size-12288 02 size-16384 02 size-32768 02 qio-so-ip 02 so-forced-close 02 qio-so-que-fulls 02 mdcopy-adj 02 outhdr-adj 02 outdata-adj END. type binary 16.
ASAP Data Definitions TCP/IP Entity Statistics 02 xsum 02 bad-len 02 reflect 02 InEchoRply 02 InDstUnrch 02 InSrcQnch 02 InRedirect 02 InEcho 02 InTimeExcd 02 InParamPrb 02 InTimeStmp 02 InTimeSRpl 02 InInfoReq 02 InInfoRpl 02 bad-rap-subcode 02 bad-addrlist 02 bad-wpa 02 rdisc-nrecorded END.
ASAP Data Definitions 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 END. OpState Error ErrorState TCPData TCPState UDPData UDPState IPData IPState QIOData QIOState RTEData RTEState ICMPData ICMPState TCP/IP Entity Statistics type type type type type type type type type type type type type type type binary 16. binary 64. binary 16. ZTCPData. ZTCPState. ZUDPData. ZUDPState. ZIPData. ZIPState. ZQIOData. ZQIOState. ZRTEData. ZRTEState. ZICMPData. ZICMPState.
ASAP Data Definitions TCP/IP Entity Statistics TCPIP ROUTE Entity Description ASAP 2.8 * This defines the structure written to ASAPCOL by the TCPIP SGP DEF ZRouteData. 02 zusage type binary 32. 02 Word type binary 16 redefines zusage. END. DEF ZRouteState. 02 zusage type binary 16. 02 Word type binary 16 redefines zusage. END. DEFINITION ROUTE-Stats1. !Description.............Sect 02 system type binary 16 occurs 4 times. ! system name 02 word type binary 16 redefines system.
ASAP Data Definitions TCP/IP Entity Statistics 02 system type binary 16 occurs 4 times. ! system name 02 word type binary 16 redefines system.! word alignment handle 02 sysname type character 8 redefines system. 02 P-key-x type *. ! sysno, domain & its 8.3 02 Q-key-x type * redefines P-key-x. ! enform q-key extended 02 event type *. ! ts, interval & info 02 Type type binary 16. ! Record type TCP,Subnet,Route,Telnet 02 AggRec type binary 16. ! AggRec indicator 02 Spare type binary 16 occurs 6 times.
ASAP Data Definitions 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 END. word sysname P-key-x Q-key-x event Type AggRec Spare OpText Status OpState Error ErrorState Data State TCP/IP Entity Statistics type type type type type type type type type type type type type type type binary 16 redefines system.! word alignment handle character 8 redefines system. *. ! sysno, domain & its 8.3 * redefines P-key-x. ! enform q-key extended *. ! ts, interval & info binary 16.
ASAP Data Definitions TCP/IP Entity Statistics 02 zforgn-addr type binary 16. 02 zloc-port type binary 16. 02 zforgn-port type binary 16. 02 zservname type binary 16. 02 zwin-typ type binary 16. 02 znvloc-addr type binary 16. 02 zcaller-port type binary 16. 02 zloc-addr6 type binary 16. 02 zloc-filler type binary 16. 02 zforgn-addr6 type binary 16. 02 zforgn-filler type binary 16. 02 zcaller-addr6 type binary 16. 02 zcaller-filler type binary 16. 02 Openers type binary 16. 02 Processes type binary 16.
ASAP Data Definitions 02 02 02 02 02 02 02 02 END. Spare OpText Status OpState Error ErrorState Data State TMF Entity Statistics Definitions type type type type type type type type binary 16 occurs 6 times. ! binary 16 occurs 4 times. ! character 1 redefines OpText. binary 16. ! binary 64. ! binary 16. ! ZServiceData. ! ZServiceState. ! reserved Op state text Operational state Error (if any) Error state (or remove) SERVICE data SERVICE states TMF Entity Statistics Definitions DEFINITION TMF-STATS.
ASAP Data Definitions DDL Section Record Declarations DDL Section Record Declarations ASAP Database Record Declarations RECORD CPU. File is DBCPU. Def is cpu-stats. Key 0 is p-key. End. RECORD SYS. File is DBSYS. Def is cpu-stats. Key 0 is p-key. End. RECORD NET. File is DBEXP. Def is net-stats. Key 0 is p-key. End. RECORD PCB. File is DBPCB. Def is pcb-stats. Key 0 is p-key. End. RECORD NCP. File is DBNCP. Def is NCP-STATS. Key 0 is P-key. End. RECORD DSK. File is DBDSK. Def is dsk-stats. Key 0 is p-key.
ASAP Data Definitions File RECORD File RECORD File RECORD File RECORD File RECORD File is $TAPDB. TMF-SRV. is $TMFDB. PRO-SRV. is $PRODB. COM-SRV. is $COMDB. QRY-SRV. is $QRYDB. TCP-SRV. is $TCPDB. Enform Server Declarations Def is tap-stats. Sequence is Q-key. Def is tmf-stats. Sequence is Q-key-x. Def is pro-stats. Sequence is Q-key. End. End. End. Def is Com-stats. Sequence is Q-key. End. Def is Qry-stats. Sequence is Q-key-x. End. Def is Tcp-stats1. Sequence is Q-key-x. End.
ASAP Data Definitions Enform Server Declarations HP NonStop ASAP Server Manual—522303-007 B -30
Index A ACTION option, SET command 6-84 ACTOBJECT option, SET command 6-84 ACTSHELL option, SET command 6-85 APP command 6-7 option, SET command 6-85 ASAP components 1-6 configuration 2-5 configuration file 2-12 Conversational Interface (CI) 1-8 full installation of 2-4 help 3-11 installation overview 2-2 Monitor process 2-15 starting 3-3, 3-5 running 3-1 setup 2-3 Statistics Gathering Process (SGP) 2-15 system requirements 2-1 ASAP Client description 1-8 features 1-1 with ASAPX 1-8 ASAP Collector descripti
Index D Commands (continued) EXIT 6-33 FC 6-33 FILE 6-33 HELP 6-44 LH 6-46 LOG 6-53 MONITOR 6-53 MONITOR, usage 4-5 NODE 6-61 OBEY 6-63 PAUSE 6-64 PROCESS 6-64 PROCESSBUSY 6-67 RANK usage considerations 4-6 RDF 6-79 SET 6-83 SHOW 6-114 SHUTDOWN 6-115 SPOOLER 6-116 STARTUP 6-121 STATUS 6-122 summary 6-2 SYNC 6-125 SYSTEM 6-125 TAPE 6-126 TMF 6-129 VOLUME 6-132 COMMIT command 6-19 Configuration file about 2-12 creating 2-12 Configuring ASAP 2-12 Conversational Interface (CI) about 1-8 ASAP 2-15 starting 3-1
Index F EXIT command 6-33 EXPAND SET option 6-91 SGP 1-11 supported objective attributes 4-11 EXPANDIP supported objective attributes 4-12 M MONITOR command description 6-53 usage considerations 4-5 Monitor process, ASAP 2-15 MONITORADD, SET option 6-96 N F FC command 6-33 FILE command 6-33 SET option 6-92 supported objective attributes 4-12 File SGP 1-13 H Help 3-11 HELP command 6-44 HELPFILE, SET option 6-94 I ID, SET option 6-94 INSPECT, SET option 6-95 Installation on remote nodes 2-7 terminating
Index P Objective attributes (continued) EXPAND-supported 4-11 FILE-supported 4-12 PROCESSBUSY-supported 4-14 PROCESS-supported 4-13 RDF-supported 4-14 SPOOLER-supported 4-14 SYSTEM-supported 4-15 TAPE-supported 4-16 TMF-supported 4-16 objectives specifying 4-3 Objectives Database 4-4 OBJECTIVESAUDIT, SET option 6-98 OBJECTIVESDB, SET option 6-98 OBJECTIVESEVENTCONSOLEUP, SET option 6-99 OBJECTIVESEVENTCONSOLE, SET option 6-99 OBJECTIVESEVENTMAX, SET option 6-100 OBJECTIVESEVENTSTATE, SET option 6-99 OBJE
Index S SET command (continued) DISK option 6-90 EDL option 6-91 EXPAND option 6-91 FILE option 6-92 HELPFILE option 6-94 ID option 6-94 INSPECT option 6-95 IOCONTROL option 6-95 LOGFILE option 6-95 LOGGING option 6-95 LOGINTERVAL option 6-96 LOGSUPPRESS option 6-96 MONITORADD option 6-96 NODE option 6-97 NODEDOWNALERT option 6-98 OBJCOLLECT option 6-98 OBJECTIVESAUDIT option 6-98 OBJECTIVESDB option 6-98 OBJECTIVESEVENT option 6-99 OBJECTIVESEVENTCONSOLE option 6-99 OBJECTIVESEVENTCONSOLEUP option 6-99 O
Index T command 6-125 SYNC (continued) SET option 6-111 SYNCSLOW, SET option 6-112 SYSTEM supported objective attributes 4-15 SYSTEM command 6-125 System requirements 2-1 T TAPE command 6-126 SET option 6-112 supported objective attributes 4-16 Tape SGP 1-12 TERM, SET option 6-113 Time, synchronizing 3-8 TMF command 6-129 SET option 6-113 supported objective attributes 4-16 TRACE, SET option 6-114 V VOLUME command 6-132 HP NonStop ASAP Server Manual—522303-007 Index -6
