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 SE30V3.2 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.8 January 2007 522303-008 ASAP SE30V3.0 April 2008 522303-009 ASAP SE30V3.1 December 2008 522303-010 ASAP SE30V3.
Table of Contents HP NonStop ASAP Server Manual ...................................................................................... 1 Abstract ........................................................................................................................... 1 Product Version ............................................................................................................... 1 Supported Release Version Updates (RVUs) ..................................................................
File Statistics Gathering Process ................................................................................... 42 Node Statistics Gathering Process ................................................................................ 42 Process Statistics Gathering Process............................................................................ 42 RDF Statistics Gathering Process ................................................................................. 42 Spooler Statistics Gathering Process ..
DOTs Overview................................................................................................................. 88 Specifying Domains and Objectives .............................................................................. 92 The Objectives Database .............................................................................................. 92 MONITOR Usage Considerations .....................................................................................
Default Process MetricRule Settings ............................................................................... 139 Modifying the Default Aggregation Settings .................................................................... 140 Section 6: ASAP Conversational Interface Commands ................................................ 141 Considerations............................................................................................................. 143 ACTION Command ..............................
PAUSE Command .......................................................................................................... 224 Example ...................................................................................................................... 225 PROCESS Command ..................................................................................................... 225 Examples.....................................................................................................................
DDL Section Definitions .................................................................................................. 326 Primary Key Definitions ............................................................................................... 326 Event Definitions.......................................................................................................... 327 Query Key Definitions ..................................................................................................
List of Figures and Tables Figure 1-1. ASAP Components .......................................................................................... 37 Figure 2-1. ASPSETUP Main Menu, AsapInstall ................................................................ 49 Figure 2-2. Installation Configuration for Full Install on This Node ..................................... 50 Figure 2-3. Input Help for the ASAP Install subvolume Field .............................................. 51 Figure 2-4.
What’s New in This Manual New and Changed Information The ASAP 3.2 version of this manual contains the following changes: Added escalating and Boolean goals and new action tokens to the DOTS Overview section. Added Boolean goal names and new action tokens to the ACTION Command section. Added escalating and Boolean goal information to the GOAL Command section. Added escalating and Boolean goal information to the RANK Command section.
CPU Entity - Supported Objective Attributes CPU Entity Statistics The PROCESS entity has added new attributes for use when ASAP is run on NonStop Blades systems. Process Entity - Supported Objective Attributes PROCESS Entity Statistics The PROCESSBUSY entity has added new attributes for use when ASAP is run on NonStop Blades systems. PROCESSBUSY - Supported Entity Attributes PROCESSBUSY Entity Statistics Minor corrections throughout the manual.
SWAP Statistics Definitions The CPU entity has 6 new memory statistics including memory size, swappable pages, free pages, locked pages, maximum memory that can be locked, and the highest amount of memory locked since the CPU was coldloaded. For more information see CPU Statistics. A new SET PARTITION KEY | RELATIVE options have been added to allow different historical database performance characteristics.
The sixth edition (ASAP 2.
The fifth edition of this manual contains these changes: A SET ACTION option allows you to configure ASAP to take actions when userdefined goals are not met. For more information, see the SET Command. A SET DBMAXDAYS option allows you to configure ASAP so that it automatically retains days, weeks, months, or years of long-term database history. For more information, see the SET Command.
A process for gathering communication line statistics lets you collect availability information for SWAN communication lines. For additional information, see the SET COMM, and COMM commands. Specify which CPU the SGPs will execute. See the SET entity command. A Timeout option for the Status Monitor command lets you specify the elapsed time for an ASAP SGP to reply. The Status command displays entity error information in the unlikely event an SGP is in an error state or an SGP cannot start.
The fourth edition of this manual contained these changes: The only difference between 522303-002 and 522303-004 is the correct display of Section 4.
RANK command. Added EMS Event Considerations 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. Use these new options to change default behavior of system entities and to turn off event generation for status changes in ASAP system objects, respectively.
MONITOR Command PROCESS Command 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.
OBJECTIVESEVENTCONSOLEUP OBJECTIVESEVENTSTATE OBJECTIVESEVENTMAX OBJECTIVESRANK PARTITION PROCESS SPOOLER TAPE TMF For File, Process, RDF, Spooler, Tape, TMF entities: Added statistics definitions in DDL Section Definitions Updated DDL Section Record Declarations HP NonStop ASAP Server Manual Page 19 of 381
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 CIP, CPU, Comm, Disk, Expand, File, Hybrid1, Node, Process, Processbusy, RDF, Spooler, Swap, System, Tape, TCP/IP, Telserv2, and TMF.
These service-level metrics are automatically evaluated against predefined objectives to establish alert priorities so that you can quickly identify when objectives are not being met for an application process. For more information, see the ASAP Hybrid Manual. 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.
Related Resources This manual describes the ASAP Client and ASAP Server, the ASAP base components. For details on the ASAP Client, see the ASAP Client Manual. For details on event messages generated by ASAP, see the ASAP Messages Manual. The ASAP Extension (ASAPX) is a related product that is used to collect, measure, view, and analyze application service-level metrics. This manual briefly discusses the architecture, installation, components, and functions of ASAPX.
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 Computer type letters within text indicate C and Open System Services (OSS) keywords and reserved words. Type these items exactly as shown. Items not enclosed in brackets are required. For example: myfile.
{ } Braces A group of items enclosed in braces is a list from which you are required to choose one item. The items in the list can be arranged either vertically, with aligned braces on each side of the list, or horizontally, enclosed in a pair of braces and separated by vertical lines. For example: LISTOPENS PROCESS { $appl-mgr-name } { $process-name } ALLOWSU { ON | OFF } | Vertical Line A vertical line separates alternatives in a horizontal list that is enclosed in brackets or braces.
Item Spacing Spaces shown between items are required unless one of the items is a punctuation symbol such as a parenthesis or a comma. For example: CALL STEPMOM ( process-id ) ; If there is no space between two items, spaces are not permitted. In this example, no spaces are permitted between the period and any other items: $process-name.
!o:i In procedure calls, the !o:i notation follows an output buffer parameter that has a corresponding input parameter specifying the maximum length of the output buffer in bytes. For example: error := FILE_GETINFO_ ( filenum , [ filename:maxlen ] ) ; !i !o:i Notation for Messages This list summarizes the notation conventions for the presentation of displayed messages in this manual. Bold Text Bold text in an example indicates user input typed at the terminal.
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. The items in the list can be arranged either vertically, with aligned braces on each side of the list, or horizontally, enclosed in a pair of braces and separated by vertical lines.
Notation for Management Programming Interfaces This list summarizes the notation conventions used in the boxed descriptions of programmatic commands, event messages, and error lists in this manual. UPPERCASE LETTERS Uppercase letters indicate names from definition files. Type these names exactly as shown. For example: ZCOM-TKN-SUBJ-SERV lowercase letters Words in lowercase letters are words that are part of the notation, including Data Definition Language (DDL) keywords.
Section 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 attribut
Browse windows for detailed entity analysis and reporting Graph windows for multiple real-time views of host objects Report windows for customized reporting of selected objects 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 Manag
ASAP Server Architecture NonStop servers and collectors Domain registration through the API Extension Support for multiple node availability infrastructure Microsoft Windows Client interface Support for open App, CIP, Comm, CPU, Disk, Expand, File, Node, Process, ProcessBusy, RDF, Spooler, Swap, System, Tape, TCP/IP, and TMF entities ASAP Server Database Automatically maintained Low disk space utilization Requires no operator intervention Automatic archival of Object H
Full integration with the ASAP Client and Server ASAP Extension Architecture Monitors and Statistics Gathering processes (SGPs) Nonmessaging data collection Shared memory segment counters Application Programmer Interface Multilevel domain name registration Synchronized sampling across all ASAP Server entities ASAP Extension Discrete Object Thresholds (DOTs) Features Objective thresholding based on domain names and levels of the domain name Thresholds based on the DOTs o
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 Multilevel domain name registration Synchronized sampling across all entities ASAP Hybrid Discrete Object Thresholds (DOTs) Features Objective thresholding based on domain names and levels of the domain
ASAP availability information is stored in the ASAP database for historic reference, as well as for shared access by multiple users and applications. The ASAP Server collects data with a set of CPU Monitors, Statistic Gathering processes (SGPs), and Collection processes in a network of systems. ASAP monitors operational information of system and user-defined resources. The ASAP SGPs report on performance and operational information of system and user application resources.
applications. Service-level metrics are automatically evaluated against userdefined objectives to establish alert priorities when application objectives are not being met for an application process. CIP subsystem status and statistics for NonStop servers that use CLIM devices, including information for CLIM devices, Monitor and Provider processes. Communication line availability for AM3270, ATP6100, Envoy, EnvoyACP, Multilan, Snax, and X.
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. Swap availability information from the KMSF subsystem such as total swap space, allocates, creates, frees, releases, resizes, used percentage, number of files and available pages.
Figure 1-1.
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. The ASAP CI provides interactive, formatted reports for all monitored nodes or selected nodes.
use in your program for accessing the ASAP database, refer to the released file ASPDDLDB. Command and Control The ASAP Conversational Interface provides commands and options that let you work interactively with the collection system: STATUS, STARTUP, and SHUTDOWN commands control the ASAP Monitor and Collector processes. When any entity is configured for gathering entity availability information, the ASAP Monitor process also starts the selected entities.
The Rollover option renames entity database files daily so you can archive them for historic analysis at a later date. Once started, ASAP needs no operator intervention. Even when CPUs become unavailable, the ASAP database is automatically maintained. Collection The Database Collector is a process pair that collects application and system availability information from system nodes throughout the network.
different sub-entities and ASAP record types to report CIP information to the ASAP Collector process. COMM Statistics Gathering Process Communication SGPs collect availability for all communication lines configured on the node or only user-specified communication lines on the node. This process uses the Measure subsystem programmatic interface for collecting raw communication performance counters.
with the Expand Manager. The Expand SGP reports on objective thresholds when they do not meet the user-defined values. The Expand SGP gathers availability information, bundles it in a single message, and forwards it to the ASAP Collect process. The Collect process unpacks the information and stores it in the normalized ASAP database so the ASAP LH command or ASAP Client can retrieve it. File Statistics Gathering Process File SGPs collect file availability information.
Spooler Statistics Gathering Process Spooler SGPs collect Spooler availability information. Process availability information is obtained using the Spooler API. The availability information gathered is performance utilization and operational state information. The Spooler SGP reports on objective thresholds when they do not meet the user-defined values. The Spooler SGP gathers availability information, bundles it in a single message, and forwards it to the ASAP Collector process.
TMF Statistics Gathering Process TMF SGPs collect TMF availability information. TMF availability information is obtained using the Subsystem Programmatic Interface (SPI) for the TMFSERVE process. The availability information gathered is performance utilization and operational state. The TMF SGP reports on objective thresholds when they do not meet the user-defined values. The TMF SGP gathers availability information, bundles it in a single message, and forwards it to the ASAP Collect process.
The ASAP Collector process is continuous. If a CPU fails, the backup Collector process automatically takes over so that database access is always available. The ASAP database is a real-time normalized database and can be queried online. The ASAP product subvolume includes Enform queries that allow batch-type queries of network performance and operational status.
Section 2: Installing ASAP on the Server Topic Page Task 1: Ensure Your System Meets Requirements 46 Task 2: Install ASAP Server Product Files 47 Task 3: Set Up ASAP Server 48 Task 4: Configure ASAP Components 58 Starting and Stopping ASAP 71 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.
Expand Manager, T9117D30 version AAW or later Expand line-handler, T9057D30 version ADE or later HP NonStop SeeView, T6965C31 or later DSM/Tape Catalog MediaSRV server, T6024D42 version AAT or later 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.
IPSetup returns you to the Destination Location dialog box. 10. Click Next. IPSetup transfers the files to the designated volume and subvolume and prepares them to be used as DSVs. IPSETUP displays status dialogs so you can monitor the progress of the host installation. When IPSetup is finished, it prompts you to indicate how you want to conclude your IPSetup session. 11.
To invoke any menu options, move the cursor to the menu item and press Return. For context-sensitive help for any menu item or field in ASPSETUP, move the cursor to the item or field and press Shift-Return. 3. Choose the type of installation to perform: To fully install and configure ASAP on a data collection node, proceed to Full Install on This Node. To install ASAP on remote nodes so you can monitor other nodes at the central data collection node, proceed to Remote Monitor Install. Figure 2-1.
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. ASPSETUP displays the ASAP Local Install Configuration fields (see the following figure). Figure 2-2. Installation Configuration for Full Install on This Node VST003.vsd 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. Input Help for the ASAP Install subvolume Field VST011.vsd 2. Enter the Local Install values for configuring ASAP on the local node. To start a full installation: a. Enter the ASAP installation location in the ASAP Install subvolume field. b. Enter a process ID. c. Enter the location you want for the ASAP database $volume.subvolume. d. Enter the Statistics Collection Rate. e. Enter a network user ID name. f. Enter the password for SUPER.SUPER. g. Press Return to start the installation.
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. Creates Configuration files, including an installation OBEY file.
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.
To install ASAP on remote nodes so you can monitor other nodes at the central data collection node: 1. From the AsapInstall menu, select Remote Monitor Install; then press Return. ASPSETUP displays the Asap Remote Install Configuration fields (see the following figure). Figure 2-6. ASAP Help Text for Remote Monitor Install VST006.
The following figure 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. To install one but not the other, leave the ASAP Install subvolume or ASAPX Install subvolume field blank for the product that you do not want to install. 2.
To deselect a node, move the cursor to the node in the Selected Nodes window and then press Return. The node name is removed from the Selected Nodes window. The following figure shows the results of installing ASAP and the ASAP Extension on the node \WINE. Figure 2-8. Selecting Remote Install Nodes for Remote Installation VST008.vsd 8. After you select all of the nodes to install remotely, move the cursor back to the START REMOTE INSTALL field and press Return.
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. To terminate the installation without exiting SeeView, from the AsapInstall menu, select Abort Install, and press Return. When the install completes, ASPSETUP displays output similar to the following figure.
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.
Any system with an active ASAP database should have a properly configured ASAPCONF file in the $SYSTEM.SYSTEM location, in addition to any user configuration files located on other subvolumes. When the CI cannot locate the ASAPCONF file, ASAP uses the default values you define with the SET command (see the SET Command). ASAP searches the current default subvolume, then $SYSTEM.SYSTEM for the configuration file.
Example ASAPWIZ session: 1> RUN ASAPWIZ ASAP Configuration Wizard - T0403V02.05 - (15OCT2004) - System \CENTDIV Copyright (C) 1999, 2001-2004 Hewlett-Packard Company This wizard will assist you in creating an ASAP configuration file (ASAPCONF). It should be run after installing ASAP. Is this node, \CENTDIV, the central ASAP collection node(Y):y ASAP 2.05 is installed in $SYSTEM.
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.
Creating $ASAP.TESTDB2.ASAPCONF Would you like the Wizard to restart ASAP using the new configuration(Y)?n 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.
ASAPRDF RDF Statistics Gathering Process (SGP) Gathers availability information for either the RDF Extractor or RDF Updater on the node. ASAPSPL Spooler Statistics Gathering Process (SGP) Gathers availability information for every monitored spooler subsystem on the node. ASAPSWP Swap Statistics Gathering Process (SGP) Gathers availability information for every monitored KMSF swapfiles on the node.
ASAPCMM Object File The Monitor starts the COMM SGP on its node if Comm is enabled. The ASAP Statistics Gathering (ASAPCMM) Process collects availability information for all monitored SWAN communication line types. ASAPCMM uses the Measure programmatic interface to obtain raw communication line counters from the communication processes. For a complete list of COMM availability counters, see the COMM Command.
ASAPCONF File The ASAPCONF file contains configuration information for the ASAP and ASAP Extension subsystems. Before trying to start the ASAP and ASAPX subsystems, make sure that they are properly installed. ASAPDSK Object File The ASAP Monitor starts the Disk SGP on its node if Disk is enabled. The ASAP Statistics Gathering (ASAPDSK) Process collects availability information for the ASAP for all nonphantom disk devices.
When the ASAP Conversational Interface (CI) starts a remote ASAP Monitor process, the Monitor starts various monitoring functions specified in the ASAPCONF file or from interactive user commands. The ASAP Monitor is responsible for starting and maintaining the proper monitoring software in its node. If any Monitor or Statistics Gathering process (SGP) goes down for any reason, the ASAP Monitor in that node coordinates an automatic restart of processes as needed.
Audit trail index, and Audit volume. For a complete list of RDF availability counters, see the RDF Command. ASAPSPL Object File The ASAP Monitor starts the Spooler SGP on its node if Spooler is enabled. The ASAP Statistics Gathering (ASAPSPL) Process collects availability information about spooler subsystems on the node. ASAPSPL uses the spooler procedure call interface to communicate with the spooler supervisors to get information about the spooler, collectors, devices, and print processes.
percentage of audit trail used, transaction rate of the TMF subsystem, and number of pending transactions. For a complete list of TMF availability counters, see the TMF Command. ASAPTMF communicates directly with the TMFServe server process for obtaining TMF availability information. ASAPXMON Object File The optional ASAPX Monitor process (ASAPXMON) allocates and manages shared memory in each processor and performs sampling and metric computation.
For more information about the ASAPXSGP, ASAPXMON, and ASAPX Library, see the ASAP Extension Manual. ASAPGATE The optional ASAP Hybrid for NonStop Server Gateway (ASAPGATE) process provides gateway functions between Linux systems running ASAP Hybrid for Linux and the NonStop server. ASAPPXY The optional ASAP Hybrid for NonStop Server Proxy (ASAPPXY) process acts as a proxy Statistics Gathering Process for ASAP Hybrid. The ASAP Monitor starts the optional Proxy SGP on its node if Proxy is enabled.
+ + + + + + + + + + Swapfiles * Cpus Tapes TCP TCPPort TCPRoute TCPSubnet Telserv TelservService TelservWindow TMFs * 4 * * * * * * * * * * 1548 162 1142 246 140 176 182 158 370 202 * * * * * * * * * * (1440/Rate) (1440/Rate) (1440/Rate) (1440/Rate) (1440/Rate) (1440/Rate) (1440/Rate) (1440/Rate) (1440/Rate) (1440/Rate) Where: Cpus Nodes Apps CIP Comm Disks Expand Files Ncpnodes option.
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 + 368,640 + 6,393,600 + 3,456,000 + 3,052,800 + 4,492,800 + 12,026,880 31,587,840
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.................. ON ActObject............... $SYSTEM.SYSTEM.
ProcessBusy............. Rate.................... RemoteSecurity.......... Retain.................. Sleeptime............... Sync.................... SyncSlow................ Extended Entity Information: APP..............ON Object................ Parameters............ CPU................... CIP..............ON Object................ Parameters............ CPU................... COMM.............ON Object................ Parameters............ CPU................... DISK.............ON Object...............
Object................ Parameters............ CPU................... TMF..............ON Object................ Parameters............ CPU................... $SYSTEM.SYSTEM.ASAPTCP "RATE 5,SCPNAME $ZNES,PORT,WINDOW,SERVICE" 2 $SYSTEM.SYSTEM.ASAPTMF 2 3. If the settings are not correct, do one of: Exit the ASAP Command Interpreter and change the ASAPCONF file with the correct settings; then restart ASAP as shown in Step . Override the defaults by entering the appropriate SET commands.
For example, if a node is currently collecting Expand statistics and you no longer require this type of statistic, but you still require CPU and ProcessBusy statistics, enter SET EXPAND OFF. 3. Shut down the Monitor process on the node. 4. Once successfully stopped, use the ASAP STARTUP command to restart the node. The CPU and ProcessBusy statistics are collected, but the Expand Line-handler statistics are no longer reported to the Collection node.
Section 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.
SET BUFFERED SET CLEANTIME SET DB SET DBMAXDAYS SET DBMAXDAYSTOPURGE SET DBROLLOVERSUBVOLPREFIX SET DBROLLOVERFILEPREFIX SET ID SET OBJCOLLECT SET PARTITION SET PRIMARY SET PRIORITY SET RATE SET RETAIN SET SLEEPTIME After you define the ASAP Collector options, you can start the Collector process. This example sets up the collector on $Data.asapdb, purging all records daily at 12:15 a.m. and not collecting availability records between 11:00 p.m.
+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. Options are set through OBEY files, TACL macros, or interactively from the ASAP CI.
SET OBJECTIVESEVENTSTATE SET OBJECTIVESEVENTSUBJECT SET OBJECTIVESEVENTMAX SET OBJECTIVESRANK SET OBJMONITOR SET PRIMARY SET PRIORITY SET PROCESS SET PROXY SET PROXYOBJECT SET PROXYPARAM SET RATE SET RDF SET SPOOLER SET SWAP SET SYNC SET SYNCSLOW SET TAPE SET TCP SET TMF For more information about these commands, see the SET Command.
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.APP.
The display returned from the STATUS command is defined in the following table. Table 3-1.
The STATUS command returns the node name, the process ID and version, and all of the SGPs that are running on the node. In this example, the SGPs are $ZOO1 and $ZOOJ. The options in parentheses for the Monitor process are also displayed. You can also use the ASAP LOG command to get more node status information. For example: LOG \CHICAGO Starting ASAP With the Default Configuration When the Monitor starts, it starts the SGPs that were set to ON.
+DISK +DISK \REMOTE +PB +SPOOLER There are many command options for each entity command. For more information, see Section 6: ASAP Conversational Interface Commands. Shutting Down the ASAP Collector and ASAP Monitors The SHUTDOWN command stops the Collector or Monitor processes.
Nodes should have the same GMT so that availability data can be correlated. ASAP maintains all times internally in GMT and then converts them to the local civil time of the Collect server. This lets you view system performance in the system’s own local time and ignore time zone differences when correlating statistics.
Example A Example A defines a set of ASAP processes that report statistics for all nodes in the network to the Chicago node: SET SET SET SET SET COLLECT \CHICAGO DB $DATA.ASAPDB.
08/02/28 0613:27 08/02/28 0100:29 08/02/28 0100:29 1720 ZOOJ INFO ASAPDSK ZASPZOO started. 1008 ZOOM INFO Sync, not required: 1008 ZOOM INFO Sync, not required: 0 0 The PID column in the INFO display shows the name of the ASAP process. When an ASAP process name ends with an M, it indicates the ASAP Monitor. When it ends with an S, it indicates the ASAP Collector. When it ends with a number or letters A through F, it is a standard SGP.
New Features Enter HELP NEW FEATURES for a new features history. New User Enter HELP NEW USER for getting started & product overview. NODE Reports on Expand end-to-end stats. OBEY Causes commands in OBEY file to be executed. PAUSE Suspends program until stop/abend/brk msg. PB Alias command for Reporting on busiest Process stats. PROCESS Reports on selected Processes. PROCESSBUSY Reports on busiest Process stats. RANK Controls the objectives ASAP uses to produce alerts.
Section 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.
Other ASAP components autoconfigure a small set of domains. For example, the Process SGP automatically monitors only the ASAP Monitor process. When you add a domain to monitor to any subsystem, ASAP turns off autoconfiguration for that subsystem and only monitors the domains you specified. Adding a single domain, and turning it OFF in the objectives database, makes ASAP monitor no domains for the subsystem.
Boolean objectives define multiple sets of simplex objectives in a single goal using AND and OR operators. A Boolean objective generates a critical alert for all attributes defined in the goal when it fails, and generates a single action and event if defined for the goal. For example, GOAL CPU 1, BUSYGOAL = (BUSY < 80 AND QUEUE < 2) defines a Boolean goal for the Busy and Queue length attributes for CPU 1. It states that the CPU must be less than 80% busy and the queue length must be less than 2.
<#GOAL> The objective value Tokens are expanded when using Boolean goals. The <#ATTR>, <#OP>, <#VALUE> and <#GOAL> tokens can contain multiple tab-separated entries and new tokens are added as follows: <#GNAME> The name of the Boolean goal <#GOALVAL> The attribute, operator and value in a string with no spaces followed by the goal separated with the ―|‖ character. There can be multiple tab-separated entries. <#attrGOAL> A specific goal token for the attribute.
DOTs lets you generate EMS events when objectives are not met. Using the ASAP CI GOAL or RANK command, you set objectives on attributes for any domain and include event generation keywords to make ASAP generate events. For example, RANK CPU 1, BUSY > 15 CRITICAL REPEAT makes ASAP generate a critical EMS event when percent busy for processor 1 drops to 15% or below and keeps repeating that event for each interval where the problem persists.
You define which entities and entity domains are stored in the objectives database file, which resides on each node managed by ASAP. You set the file name and location using the SET OBJECTIVESDB option of the SET Command. Host-based objectives constitute several types of objectives that you can define. You control which system or application entities and domains are monitored and define what the objective thresholds should be for an entity or a specific individual domain.
TAPE TCPARP TCPICMP TCPICMP6 TCPIGMP TCPIP TCPIP6 TCPLOOP TCPMONGQ TCPPort TCPProcess TCPQIO TCPRoute TCPRTE TCPSOCK TCPSubnet TCPUDP TelservProcess TelservService TelservWindow TMF HP NonStop ASAP Server Manual Page 94 of 381
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. For a complete list of configurable system entity objective properties, see System Entity Specifics. You configure objective thresholds for an entire entity or for a specific domain within an entity.
using the Linux application API RDF $ZOON DBRDF All RDF environments with RDF configuration files on $SYSTEM SPOOLER $ZOOO DBSPL $SPLS SWAP $ZOOA DBSWP All configured KMSF swap files SYSTEM $ZOOn (n=0 through 15) DBSYS Average utilization for all Up CPU’s TAPE $ZOOQ DBTAP All SYSGENed tape drives TCP/IP ** $ZOOV DBTCP TMF $ZOOR DBTMF All TCP/IP Processes, Routes and Subnets, and Telserv Processes All TMF components * The Expand SGP is a multi-entity (Expand and ExpandIP) SGP.
For ASAP to generate EMS events, you must turn EMS event generation on as described in EMS Event Considerations. To load objective database changes into a running copy of ASAP, you must use the COMMIT command. EMS Event Considerations ASAP generates two classes of events: Normal status and problem events describing ASAP operation These are events such as component startup messages or error messages when a component cannot obtain a system resource.
actions at all levels. Any other attributes configured for events with states of equal or higher values are not alerted via EMS events. Boolean goals are processed after simplex and escalating goals, so no event will be written for Boolean goals if an event is written for a simplex or escalating goals. To have more than one event per domain per interval, place the SET ObjectivesEventMax command in your ASAPCONF file. Other settings control whether events are displayed on the operator console.
To change the event generated for all down processes to a repeating event: RANK PROCESS, STATUS CRITICAL REPEAT To change the event generated for failures of $Abc to an informative event: RANK PROCESS $ABC, STATUS INFO To turn off event generation for status changes to process $Def: RANK PROCESS $DEF, STATUS NOEMS By default, ASAP user-defined entities do not generate EMS events for Status changes.
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.ASAP3SYS. 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.
The STATUS field, the one marked StateIsOp in EDL, is a special field. It has an associated state, but objectives cannot be set against it. That operational state is controlled only by the SGP process monitoring that object.
AgtBfrBytesHigh Highest amount of memory used for communication with NSK Integer64 AgtRecvMsgs Number of messages received from all NSK processors Integer64 AgtSendMsgs Number of messages sent to all NSK processors Integer64 AgtConnCpusCurr Current number of NSK processors connected Integer32 AgtConnCpusHigh Highest number of NSK processors connected Integer32 AgtQueuedCmds Number of SPI commands queued for processing Integer32 AgtFailedCmds Number of SPI commands that could not be comple
CIPMONITOR Entity-Supported Objective Attributes Attribute Description Value Error Collection Error Integer64 MemUsed Percent heap space used by the CIPMON process Integer Cpu CIPMON CPU Integer Pin CIPMON pin Integer Pri CIPMON priority Integer QioPoolCur Size if the QIO pool Integer64 QioPoolLmt Max size of OIO pool CIPMON can allocate or 0 for no limit Integer64 RcvScktReqs Number of receive socket requests across all CLIMs Integer64 RcvScktReqErr Number of receive socket requ
Size16384 Number of socket send requests between 12289 and 16384 bytes across all CLIMs Integer32 Size32768 Number of socket send requests between 16385 and 32768 bytes across all CLIMs Integer32 Size57344 Number of socket send requests greater than 32768 bytes across all CLIMs Integer32 ConnClimCurr Number of CLIMs connected Integer32 ConnClimHigh Highest number of CLIMs connected Integer32 RejectedConns Number of attempts to connect to a CLIM that were rejected Integer32 DeferredSends N
Transactions Number of terminal transactions all subdevices Integer32 RespTime Response time per terminal transaction Integer64 CPU Entity-Supported Objective Attributes Attribute Description Value BUSY Percent busy Integer QUEUE Queue length Integer DISP Dispatch rate Integer DISK Disk I/O rate per second Integer CHIT Disk cache hit rate per second Integer SWAP Memory manager page faults per second Integer MEMQ Average memory manager queue length Integer PGS Percent of total
REQUESTS Number of disk I/O requests per second Integer32 BUSY Percent time disk busy reading, writing, and seeking Integer WRITE Percent time disk busy writing Integer READ Percent time disk busy reading Integer CHIT Total cache hits per second for all block sizes Integer SWAP Number of disk page swaps per second Integer QLEN Disk process receive queue length Integer64 (implied decimal) INKB Input kilobytes per second Integer32 OUTKB Output kilobytes per second Integer32 RATE To
CPU Primary Cpu number of the Expand Line Handler Process for this line Integer EXPANDIP Entity-Supported Objective Attributes Attribute Description Value DFramSnt Number of IP/ATM data frames sent Integer32 DFramRvd Number of IP/ATM data frames received Integer32 DFByteSnt Data kilobytes sent per second Integer32 DFByteRvd Data kilobytes received per second Integer32 CnctCmdSnt Number of IP/ATM connect commands sent Integer32 CnctCmdRvd Number of IP/ATM connect commands received Inte
Progid Progid indicator (yes/no) Character 3 wide License License indicator (yes/no) Character 3 wide HYBRID Entity-Supported Objective Attributes Attribute Description Value Error Collection Error Integer64 Nak Negative Acknowledgement Count Integer64 DataGrams Datagram arrival rate Real64 Samples Sample datagram arrival rate Real64 RegCnt Count of ASAP_REGISTER_ calls in this interval Real64 UpdCnt Rate (per second) of ASAP_UPDATELIST_ calls for this interval Real64 RmvCnt Coun
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 per second Integer64 (implied decimal) Count Count of members in aggregate ACount Number of domains/attributes alerting
RDF Entity-Supported Objective Attributes Attribute Description Value Error Error number indicating status of data Integer RTDSecs Relative time delay in seconds Integer32 RTDTime Relative time delay in hh:mm:ss Integer32 PCpu Primary CPU Integer BCpu Backup CPU Integer Priority Execution priority Integer SPOOLER Entity-Supported Objective Attributes Attribute Description Value Error Last error encountered Integer32 PCPU CPU of primary process Integer BCPU CPU of backup proces
Avail Percentage available for all swap files Integer Creates Reservations made for process creates during the sample interval Integer32 CreateFails Failed reservations for process creates during the sample interval Integer32 Releases Reservations released during the sample interval Integer32 ReleaseFails Failed reservations released during the sample interval Integer32 Resizes Successful reservation resizes during the sample interval Integer32 ResizeFails Failed reservation resizes durin
MemSwap Swappable physical memory Integer32 MemFree Free physical memory Integer32 MemLock Locked physical memory Integer32 MemLockMax Maximum memory that can be locked in physical memory Integer32 MemLockHigh Highest amount of locked memory since CPU was loaded Integer32 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 outstandin
RcvNaks Number of ARP NAKs received Integer32 SntProbes Number of ARP probes sent Integer32 RcvProbes Number of ARP probes received Integer32 ENTITY TcpIcmp Internet Control Message Protocol Error Collection Error Integer64 Err Number of ICMP error packets that were generated Integer32 OldShort Number of short IP/ICMP packets Integer32 Oldcmp Number of bad ICMP Packets Integer32 OutEchoRply Number of Echo message output replies Integer32 OutDstUnrch Number of Destination Unreachab
InEcho Number of Echo messages input Integer32 InTimeExcd Number of Time Exceeded messages input Integer32 InParamPrb Number of Parameter Problem messages input Integer32 InTimeStmp Number of Timestamp messages input Integer32 InTimeSRpl Number of Timestamp Reply messages input Integer32 InInfoReq Number of Information Request messages input Integer32 InInfoRpl Number of Information Reply messages input Integer32 RteAdvert Number of router advertisement messages Integer32 BadRapSubco
InPackTooBig Packet too big messages received Integer32 InTimeExceed Time exceeded messages received Integer32 InParamProb Parameter problem messages received Integer32 InEchoReq Echo request messages received Integer32 InEchoReply Echo reply messages received Integer32 InMldQuery Multicast listener discovery queries received Integer32 InMldReport Multicast listener discovery reports received that match our listeners Integer32 InNdRtrAdvrt Router advertisement packets received Integer
RcvTooshort Number of packets received that were too short Integer32 RcvBadsum Number of packets received that had an incorrect checksum Integer32 RcvQueries Number of IGMP Query packets received Integer32 RcvBadQueries Query packets received with IP destination address not equal to the all hosts group Integer32 RcvReport Number of IGMP membership reports received Integer32 RcvBadReports Number of bad membership reports received Integer32 RcvOurReports Number of IGMP membership reports re
NoRoute Packets discarded due to no route Interger32 BadVers Bad ip version Interger32 RawOut Total raw ip packets generated Interger32 BadSrcIntf Incorrect source interface or no route Interger32 FragOverflow Fragments that exceeded limit Interger32 ENTITY TcpIp6 Internet Protocol v6 Error Collection Error Integer64 RxTotal Total packets received Interger32 RxIdleDiscards Packets received over a subnet not configured for IPv6 Interger32 RxTooSmall Packet length less then the size
TrlTrFailure Trl transmit failure Interger32 EncAllocFailed Enc allocation failure Interger32 RipNoProto No matching application for packet Interger32 RipNoSpace No space in socket for packet Interger32 RipDelivered Raw input packets delivered Interger32 RipAllocFailed Raw input allocation failures Interger32 RipTooShort Raw input packets too short Interger32 RipBadcksum Raw input packets with bad checksum Interger32 FragPackets Packets fragmented Interger32 FragFragments Number
FwdEother Address unreachable ENTITY TcpLoop Loopback Error Collection Error Integer64 WhoTcpSent Loopback TCP sent Interger32 WhoTcpRcvd Loopback TCP received Interger32 WhoUdpSent Loopback UDP sent Interger32 WhoUdpRcvd Loopback UDP received Interger32 HaveTcpSent TCP found sent Interger32 HaveTcpRcvd TCP found received Interger32 HaveUdpSent UDP found sent Interger32 HaveUdpRcvd UDP found received Interger32 PacketSent Packets sent Interger32 PacketRcvd Packets received
PAID Opener process access ID USERID PFName Program File Name Character 34 wide Cpu Opener CPU Integer16 Pin Opener PIN Integer16 Fnum Primary File Number Integer16 BCpu Opener backup CPU if any Integer16 BPin Opener backup PIN if any Integer16 BFnum Backup File Number if any Integer16 Proto Protocol Character 6 wide LPort Local port Integer16 LAddr Local TCP/IP address IPADDR FPort Foreign port Integer16 FAddr Foreign TCP/IP address IPADDR SendQ Bytes in send queue o
trip time Rttupdated Number times TCP succeeded getting round trip time Integer32 Delack Number of delayed ACKs sent Integer32 TimeoutDrop Number of connections dropped in retransmit timeout Integer32 RexmtTimeo Number of retransmit timeouts Integer32 PersistTimeo Number of persist timeouts Integer32 KeepTimeo Number of keepalive timeouts Integer32 KeepProbe Number of keepalive probes sent Integer32 KeepDrops Number of connections dropped in keepalive Integer32 SndTotal Total packet
RcvPartDupPack Packets with some duplicate data Integer32 RcvPartDupByte Duplicate bytes in part-duplicate packets Integer32 RcvOutPack Out-of-order packets received Integer32 RcvOutByte Out-of-order bytes received Integer32 RcvAfterWinPack Packets with data after window Integer32 RcvAfterWinByte Bytes received after window Integer32 RcvAfterClose Packets received after close Integer32 RcvWinProbe Window probe packets received Integer32 RcvDupAck Duplicate ACKs received Integer32
ENTITY TcpQio QIO Error Collection Error Integer64 DataMds Number of data message descriptors (MDs) in use by the process Integer32 MaxDataMds Maximum number of data message descriptors (MDs) that have been in use Integer32 DupMds Number of duplicate message descriptors (MDs) in use by the process not assigned to inbound driver MDs Integer32 MaxDupMds Maximum number of duplicate message descriptors (MDs) that have been in use not assigned to inbound driver MDs Integer32 NoDataMds Number of
Size256 Count of socket sends between 129 and 256 bytes Integer32 Size512 Count of socket sends between 257 and 512 bytes Integer32 Size1024 Count of socket sends between 513 and 1024 bytes Integer32 Size2048 Count of socket sends between 1025 and 2048 bytes Integer32 Size4096 Count of socket sends between 2049 and 4096 bytes Integer32 Size8192 Count of socket sends between 4097 and 8192 bytes Integer32 Size12288 Count of socket sends between 8193 and 12288 bytes Integer32 Size16384 Co
Error Collection Error Integer64 BadRedir Number of bad route redirect requests Integer32 Dyn Number dynamic redirects from smart gateways Integer32 NewGw Number redirects from new/unknown gateways Integer32 NotReach Number of unreachable destinations Integer32 WildCard Number of wild card matches found Integer32 ENTITY TcpSock Socket Migration Error Collection Error Integer64 BcastAllcpusSnt Broadcasts sent to all CPUs Integer32 BcastOnecpuSent Broadcasts sent to one CPU Integer
InErrs Number of errors detected while inputting packets on the subnet interface Integer32 MmacErrs MMAC Errors Integer32 MmacTmOts MMAC Timeouts Integer32 TcpFlts TCP filters Integer32 TcpFltErr TCP filter errors Integer32 TcpFltDreg TCP filters dereg Integer32 UdpFlts UDP filters Integer32 UdpFltErr UDP filter errors Integer32 UdpFltDreg UDP filters dereg Integer32 PrtFltDrp Port filters drop Integer32 DataDrop Data drops Integer32 SnetAbort Subnet abort Integer32 SnetR
OutPktsDropped The number of packets not sent because of interface problems – Tandem specific Integer32 Error Collection Error Integer64 Inconn The number of incoming Telnet connect requests Integer32 Open The number of open requests processed Integer32 Netdata The number of bytes received from the network Integer32 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 by
Writes The number of write requests posted by the user Integer32 WriteReads The number of writeread requests posted by the user Integer32 Ctls The number of control requests posted by the user Integer32 Setmodes The number of setmode requests posted by the user Integer32 Cancels The number of cancel requests posted by the user Integer32 LAddr Local IP Address IpAddr FAddr Foreign IP Address IpAddr LPort Local Port Integer FPort Foreign Port Integer Servname First eight characters
For more information about ASAPX, see the ASAP Extension Manual.
Section 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.
find the file or process. ASAP does provide counts of objects when viewing the wildcard domains at aggregate levels. Wild-card names can resolve into many thousands of objects. That number of records can put pressure on disk resources when storing historical data, so ASAP automatically adds an aggregate-only domain to limit the output from wild-card name specifiers after you issue a MONITOR command that contains a wild-card name.
issue a MONITOR command that contains an object filename. A user must manually delete the aggregate-only domain for individual records on each object to be written to the historical database. For example if you enter MONITOR PROCESS $DATA.OBJECT.FILE, then ASAP issues a MONITOR PROCESS $DATA.OBJECT.FILE\## command to add an aggregate-only domain. For more information on aggregate and aggregate-only domains, see the sections on aggregation later in this section.
Bin\Sh\$Name for a process named $Name or might be Bin\Sh\$.2.59.6181274 for the unnamed process running in CPU 2, PIN 59. The OSS pathname can be the complete domain name, as shown in the /bin/sh example, or it can be preceded by a logical name as described in the next section. For example, MONITOR PROCESS OSS\SHELL/bin/sh creates an ASAP domain name of OSS\SHELL\BIN\SH. The name OSS\SHELL/bin/sh is equivalent to OSS\SHELL\/bin/sh.
Note In this case, each file or process instance is monitored separately by ASAP and could produce slightly different results depending on timing and other factors. Domain Aggregation ASAP lets you aggregate File and Process domains at any level of the hierarchical group name. ASAP can automatically construct aggregate domains for all objects at all levels using a global parameter setting, or you can define only the necessary aggregate domains for individual groups (recommended).
Creating Specific Aggregate-Only Domains (Recommended) To cause ASAP to write only the aggregate record for a set of domains, use the MONITOR command to add an aggregate domain using ## as the last level specifier. For example, the command MONITOR PROCESS SALES\## causes ASAP to write only the Sales\## record to disk. ASAP still computes data for each individual process and then combines the data into the aggregate record, but it writes only the aggregate record to disk.
specific objectives are set on the attribute at the aggregate level. The state associated with the value in an aggregate record might or might not reflect the actual state of the value shown. Consider the Process Busy attribute. In the aggregate record, ASAP combines all the process busy attribute values in the group to show the total processor consumption of the group.
Attribute Propagation If no aggregation rule is defined for an attribute, the value associated with the attribute with the worst state is also propagated. For example, if you remove the SUM rule from the Process Busy attribute in the previous example, the Busy value for process Sales\$A13 is propagated to the aggregate record instead of the sum of all processes. By default, all File attribute values are propagated to the aggregate record.
Attributes without States Many attributes, such as the Process PFName attribute, have no associated state. You cannot define an objective value on those attributes, and ASAP does not rank them. For these attributes, ASAP propagates the values from the domain with the highest alert level.
Stopping XIOInit As an example, when RUL is specified, a process in the Stopping process state is considered to be worse than a process in the Runnable process state, so the Stopping value is propagated to the aggregate record based on the priority rule. Like other attributes, the worst associated state value is always propagated to the aggregate level. Default Process MetricRule Settings This table shows the MetricRule aggregate controls that are set for Process monitoring when you first install ASAP.
Modifying the Default Aggregation Settings To change the default Process aggregation controls provided in ASAP, edit the ASAP2SYS EDL file, and copy the File or Process EDL definition into a separate file. Make changes to the new file and then add an INCLUDE statement to the ASAPUSER file to include the new File or Process EDL file. Change only the MetricRule formulas for attributes. Any other EDL changes can produce unpredictable results.
Section 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.
A description of all available command options Examples illustrating the use of each command Table 6-1.
OBEY Execute the commands contained in the specified OBEY file 224 PAUSE Suspends the program until a stop, abend, or break message is received 224 PROCESS Displays statistics for the selected processes.
alone cannot be distinguished from the STARTUP command. To continue a command on a subsequent line, end the current line with the ampersand (&) character and enter the remaining portion of the command on the following line. The ASAP CI prompt changes to +& to indicate that it is operating in continuation mode. For example: +SET DISK OBJECT & +&$SYSTEM.SYSTEM.
operator A relational operator: GT, LT, EQ, NE, GE, or LE. The operator is not specified for the STATUS attribute. gname The name of a Boolean goal. Outputs the action defined for this goal name. Using gname without specifying GOALNAME can also output attribute specific actions if the action name is the same as an attribute name. GOALNAME Specifies that output will be produced in tokenized form for a specific Boolean goal named gname.
<#VALUE> <#STATE> <#LASTSTATE> <#GOAL> <#GNAME> <#GOALVAL> <#attrGOAL> <#attrOP> <#attrVALUE> The current value of the attribute The current state of the attribute The last state of the attribute The objective value The name of the Boolean goal Attribute, operator, goal and value in a string with no spaces where goal and value are separated by the | character A specific goal token for the attribute A specific goal token for the attribute’s operator A specific goal token for the attribute’s value DELETE De
ACTION RULE RELOAD = TACL RELOAD <#OBJECT>, PRIME ACTION RULE SECURE = FUP SECURE <#OBJECT>, <#GOAL> ACTION RULE SUSPEND = TACL SUSPEND <#OBJECT> Considerations Actions requiring multiple interactions with command interpreters or decision logic should be written as TACL macros or be sent to custom programs. Check that TACL macros are loaded and available for ASAP by loading them in the default TACLCSTM file for the ASAP user id.
[, MINSTATE [AUTO [state [, COUNT count [, MEMORY [, AGGONLY [, EXTRACT filename [, NOPRINT [, NOLINEBREAK [, NOAGG ]] ]] ] ] ] ] ] ] ] 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. \* 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.
* specifies that the performance and state information for all domains on the specified system are to be displayed. If you specify a domain or the wild-card character (*), statistics for all of the domains in the current system are displayed. 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.
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. AGGREGATE specifies that aggregate records be output along with the detail records. AGGREGATE is on by default. 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.
EXTRACT reads application records from the ASAP database and writes them to another file or process. NOPRINT suppresses terminal output during EXTRACT operations. NOLINEBREAK instructs ASAP to stop breaking output lines at 132 characters. Use this option when creating CSV file output from ASAP CI and directing the output to a file type or process than can accept long lines without line breaks. NOAGG suppresses displaying of aggregate domains.
Test\Onereallongname\Domaintypename\#Nextlongsubdevice.name 2/25 12:43 A1 0,115 4 0 0 0.00 The preceding example shows basic APP command output without detail attributes, and it also shows how ASAP wraps to a second line when the domain name is longer than 33 characters. The domain name appears on its own line, and its corresponding data appears on the next line.
AT TransRate GRID YES GRAPH YES GRAPHMAX 10 HELP "Transaction rate" STATEPAIR YES STATERULE UseStateGraphState TypeData REAL64 MetricRule "#0/S" Format "F8.
2/25 12:43 A1 0,131 4 0 0 0.00 1.33 16 0.13 5 +APP \CENTDIV ACCOUNTS\RECEIVE,DETAIL \CENTDIV Domain\Name\Hierarchy -------------------------------Receive\$Jx50 Receive\$Jx51 Status Date --------------- ----Up 5/10 Up 5/10 Time ----17:47 17:47 Ct Error -- ----4 0 4 0 continued... TransRate ErrCount Busy State --------- -------- ----- ----0.1500 2 0.04 3 0.6000 4 0.
used to limit the number of lines of response to 20. Setting this command lets you immediately retrieve the alerting detail records from an aggregate domain where only the aggregate domain is written to the ASAP database and to the ASAP Client. Option abbreviations are used in the EDL DETAIL command because the domain name insertion (^) can insert up to 64 additional bytes into the command. Completely CIP Command CIP [/OUT /] [\* ] [ [.] * ] [,SAMPLES count ] [\node] [ [.
STATES the objective states of CIP metric values TIME defines ending time and date of sample(s) to display DETAIL displays custom detailed CIP metric values for specific sub-entities MINSTATE displays records based on attribute states state show records with at lease one attribute state equal to or higher than .
Examples To show the latest CIP statistics for the default node: CIP To show the latest CIP statistics for all nodes: CIP \* To show the latest CIP CLIM detailed statistics for the local node: CIP CLIM, DETAIL To show the latest detailed CIP Monitor statistics for Zcam0 on \Chicago: CIP MONITOR \CHICAGO.
CLEANUP [ \node] COLLECT | collect-pid node specifies the individual system for which information is to be displayed. collect-pid specifies a Collect process ID. Example This example depicts a cleanup based on the RETAIN value for the Collect process: + CLEANUP COLLECT ! Do cleanup based on RETAIN value for the ! Collect process COMM Command The COMM command displays COMM entity availability statistics for the specified nodes and communication lines.
where the ASAP program was started, or the system specified in the ASAP SYSTEM command. commline specifies the individual communication line which performance and state information is to be displayed. All the comm lines from all the collected nodes can be output by specifying COMM \*.*. If you do not specify COMM or the wild-card character (*), the default is used. The default is all the communication lines on the current system.
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. TIME displays the time of the sample converted to the database local civil time. STATE displays the operational state of the device.
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. PIN displays the process identification number of the primary process. TYPE displays the device type and the subtype of the communication line. D.
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 the COMM Statistics table.
RETRY Number of I/O process retries because of communication line error. REQUESTS Number of comm I/O requests (reads, writes) received by the communication process for the sample. RSPTIM Time that the I/O process spent on terminal response for all measured subdevices on the communication line. TIME Time of the statistics converted to data base local civil time. TXACTN Number of terminal transactions per second performed by the I/O processes for all the subdevices on the communication line.
CPU [/OUT /] [ \* ] [ [.] * ] [, [ \ ] [ [.] ] [, [, [, [, [, [, [, [, [, [, [, SAMPLES ] DETAIL ] PERCENT ] USE ] CONFIGURED ] HISTO ] AVG ] TYPE ] TIME hh[:mm [m/d/y]] STATE ] MEMORY ] MB ] 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. \* specifies that the performance and state information for all systems is to be displayed.
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.
CPUs are down. 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.
DISP The dispatch rate for this CPU in dispatches per second ET The elapsed time of the sample in minutes up to TIME FREEPAGES Free memory pages available IBUSY The average percentage CPU interrupt busy for the sample LCB The number of link control blocks IPUs The number of IPUs in the logical CPU LOCKEDPGS Virtual Memory locked pages MAP MapPool pages used for the sample MAXLOCKED Max amount of Virtual pages ever locked MEMQ The average memory manager queue length MEMSIZE Total physica
MAP USE or CONFIGURED options. PCB PERCENT, USE, or CONFIGURED option. PGS PERCENT, USE, or CONFIGURED option. SEG USE or CONFIGURED option (Dxx and later). SEG is the number of virtual memory segments you have specified. SWAPPABLE MEMORY or MB option. Swappable is the number of swappable memory pages. SYS USE or CONFIGURED option (Cxx only). TLE PERCENT option.
Note In this example of the DEFAULT output, the state for CPUs 2 and 3 appear because these CPUs were down.
DETAIL specifies that the report will also include first and last database record timestamp information. INFO specifies that the report will show database disk file information including filename, open flag, last modification date and time, owner, and security vector. entity-name specifies that the report is limited to that entity.
DISK Command The DISK command displays DISK entity availability statistics for the specified nodes and Disk volumes. For an explanation of DISK performance statistics, type HELP DSKSTATS. For an alphabetical list, see the DISK Statistics table. DISK [/OUT file/] [ \* ] [ [.] * [node ] [ [.
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. For example, specifying ―TIME 10:15‖ when RATE is 5 indicates that statistics collected from 10:10 to 10:15 are displayed.
INFO lists the operational information for primary disk devices and the mirror devices if they exist. DATE displays the date of the sample converted to the database local civil time. TIME displays the time of the sample converted to the database local civil time. LDEV displays the logical device number of the disk volume. CPCTYMB displays the total formatted disk space in megabytes. GBUSED displays the total space used at the time of the sample in gigabytes.
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. -M Dn mirror path is Down. -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. DctCh new disk volume discovered. The sample is invalid for all disk devices 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. Chit, Queue length, and Swaps are displayed as per second. For a description of the performance statistics, see the DISK Statistics table.
DATE Date of the sample converted to the database local civil time. INPUTKB The number of kilobytes read per second from the disk. GBUSED Total gigabytes of disk space allocated. Max ExtMB The largest free extent available for the volume. MBUSE% Percentage of disk space allocated. MB AVAIL Total megabytes of disk space allocated. OUTPTKB The number of kilobytes written per second to the disk. QLEN The disk queue length of read/write operations waiting to execute.
$SYSTEM-P 4/28 14:50 $SYSTEM-M 14:50 3 3 3 3 1.20 1.20 0 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 .93 $ROJO-P 4/29 13:25 Up 0.54 0.00 $ROJO-M 13:25 Up 0.54 0.00 $SYSTEM-P 4/29 13:25 Up 1.22 0.80 $SYSTEM-M 13:25 Up 1.22 0.80 EDL Command The EDL command performs a syntax-only check of the specified EDL file.
EXIT Command The EXIT command stops the Conversational Interface. +EXIT FC Command 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. +FC FILE Command The FILE command displays FILE entity statistics and operational state information for the specified nodes and file domains.
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.
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. 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.
MINDB filters display records from a historical database based on the supplied value state. Considerations You cannot use TIME, SAMPLES, or \* with MINSTATE. You can only use EXACT and COUNT with MINSTATE. 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.
To display all available attributes without the states: +file, detail \CENTDIV File Domains ------------------------$Mm.filework $Mm.xx.disk $System.system.asap Status Date ------------- ----Corrupt 9/19 Up 9/19 Up 9/19 Time Error Full Eof ----- ----- ---- ---------10:00 0 100 978944 10:00 0 0 0 10:00 0 49 1569704 continued...
+file $mm.filework, states, minstate auto \CENTDIV File Domains Status S Date ------------------------- ------------- - ----$Mm.filework.filecorr Corrupt 7 9/19 $Mm.filework.filefull Up 2 9/19 continued...
GOAL [/OUT file/] [entity | *] [\node], COMMIT [.
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.
< << <<< = <> >= <= The attribute value must be less than the objective value. The attribute value must be less than the objective value. Used when defining more than one less-than goal (an escalating goal.) Be sure to set ObjectivesEventState to HIGH or lower when using this operator. The attribute value must be less than the objective value. Used when defining more than one less-than goal (an escalating goal.) Be sure to set ObjectivesEventState to HIGH or lower when using this operator.
AND is a logical operator used to combine attr-op-value sets into Boolean goals. When AND is specified it states that both sets must be true, failure of either attr-op-value comparison will cause the AND condition to fail. OR Is a logical operator used to combine attr-op-value sets into Boolean goals. When OR is specified it states that either set can be true for the goal to be satisfied, failure of both attr-op-value comparisons is required to cause the OR condition to fail.
-up is the event number to use for the up event, which is triggered when the objective comparison returns to normal after a failure. The number specified must be in the range 6000 through 9999. Event number 4001 is used when this is not specified. The minus sign must precede the up event number even if the down event number is not specified. The ASAP EMS event template for the up event is not applied when custom up events are defined.
<#OBJECT> The NonStop OS or OSS object name <#DOMAIN> The domain name <#D1> Leftmost part of a multilevel domain name <#D2> 2nd part of a multilevel domain name <#D3> 3rd part of a multilevel domain name <#D4> 4th part of a multilevel domain name <#D5> 5th part of a multilevel domain name <#ATTR> The attribute name <#OP> The binomial objective operator.
<#attrVALUE> A specific value token for the attribute. For example if the attribute name is BUSY the name of this token will be <#BUSYVALUE> and it will contain the value of the BUSY attribute. When using Boolean goals where one or more attributeoperator-value settings are defined, the values returned for the <#ATTR>, <#OP>, <#VALUE>, <#GOAL> and <#GOALVAL> are returned in a list separated by vertical bars.
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. Any goal specified in the command then overrides corresponding LIKE domain values. ACTIVATE turns ranking on for the specified domain(s) in the specified entity.
SIMPLEX deletes the simplex goals for an entity or domain, leaving any Boolean goals defined for the entity or domain. GOALNAMES deletes the Boolean goals for an entity or domain, leaving any simplex goals defined for the entity or domain. INFO returns information about objectives from the database. 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.
TCPLOOP LOOP TCPMONGQ MONGQ TCPPORT PORT TCPPROCESS TCP TCPQIO QIO TCPROUTE ROUTE TCPRTE RTE TCPSOCK SOCK TCPSUBNET SUBNET TCPUDP UDP TELSERVPROCESS TELSERV TELSERVSERVICE SERVICE TELSERVWINDOW WINDOW Since CIP entity names are long and difficult to type ASAP supports the following abbreviations for the entity names: CIPCLIM CLIM CIPMONITOR MONITOR CIPPROVIDER PROVIDER Examples To add or modify the record for the disk $DATA: GOAL DISK $DATA, BUSY < 65 To specify tha
To override global objectives and create critical events: GOAL FUNDS TRANSFER\WEST, BUSY > 20, BUSY < 40 CRITICAL REPEAT To turn ranking off for a file: GOAL FILE \REMOTE.$DATA.FILE.
To define a goal and action to compress a volume that is getting too full and to write a critical EMS event, but to perform the compression only once every two hours: GOAL DISK, FULL < 90 CRITICAL ACT "DCOM <#DOMAIN>" WAIT 120 To define custom up and down event numbers for CPU 0 getting too busy: GOAL CPU 0, BUSY < 90 CRITICAL 4444-5555 To define a custom down event number for CPU 0 getting too busy: GOAL CPU 0, BUSY < 90 CRITICAL 4444 To define a custom up event number for CPU 0 when it
To define an escalating goal for the BUSY attribute for all CPUs using separate commands: GOAL CPU, BUSY < 50 GOAL CPU, BUSY << 70 GOAL CPU, BUSY <<< 90 To define a normal simplex goal on the CPU BUSY attribute: GOAL CPU, BUSY << 80 Using the << or <<< operator is the same as using the < operator if only one goal is defined.
GOAL CPU, BUSY < 60 GOAL CPU 0, BUSY < 70, BUSY << 80, BUSY <<< 90 To define a Boolean goal named BUSYGOAL for all CPUs that checks the BUSY and QUEUE attributes and where failure of either will result in the goal failing: GOAL CPU, BUSYGOAL = (BUSY < 80 AND QUEUE < 3) To define a Boolean goal named BUSYGOAL for all CPUs that checks the BUSY and QUEUE attributes and where failure of both are required for the goal to fail: GOAL CPU, BUSYGOAL = (BUSY < 80 OR QUEUE < 3) To define a Boolean goal
HELP [ command | ALL | ERROR | SET option ] 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.
[, [, [, [, [, [, [, PATH POOL RATES SAMPLES count STATE TIME hh[:mm [m/d/y] USE ] ] ] ] ] ] ] OUT file specifies a spooler or line printer for the ASAP output. If you do not specify an output file, the output is displayed on your terminal. \* specifies that information for all systems is to be provided. node specifies the individual system for which availability information is to be displayed. If you want information for all the systems, specify LH \*.
FRAMES displays Level 2 information/supervisory (I/S) frames sent and received and I/S frame ratios. Level 2, the link layer, is the communications interface to the controller defined by the line type. I represents the information frames. S represents the supervisory frames. U represents the unnumbered (nonsequenced) frames. For Expand-over-IP and Expand-over-ATM Level 2 i/s frames have these meanings: IFrm(S/R) displays number of Data Frames sent and received.
KB Bytes Number of data bytes sent and received CnCmd Number of connect commands sent and received CnRsp Number of connect responses sent and received QyCmd Number of query commands sent and received QyRsp Number of query responses sent and received MML Number of times a memory low condition was sent to the line handler process IvFr Number of received frames too small for frame headers DFr Number of dropped frames IA Number of frames from an unexpected node LINE displays only Expand line h
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. The information includes: Current and maximum percentage of pool used Number of pool failures Current and maximum percentage of message buffer used Current and maximum percentage of out-of-sequence buffer used Number of times the out-of-sequence timeout has elapsed RATES displays counts normalized to number per second.
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. 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 The following table lists the LH statistics and options shown by the HELP NETSTATS command. Table 6-6.
PF Total number of buffer pool failures in this sample. POOL Combined buffer pool usage consisting of message buffer and out-ofsequence buffer in percentages or kilobytes. RATES Counts normalized to number/second. STATE State of the line. Operational States are Up, Down, or Cntg (Connecting). 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.
Msg Cur% Percentage of Message buffer used. MML Number of IP or ATM sent a memory low condition to the LH process. NAK Number of Negative Acknowledgements sent or received. OosCur% Percentage of Out of Sequence buffer used. PCHG Number of Pathchange messages sent or received. PF Total number of buffer Pool Failures in this sample. PkSnt Total number of Level 4 packets (local+passthru) sent. PkRcv Total number of Level 4 packets (local+passthru) received.
+LH +LH +LH +LH \*, \*, \*, \*, FRAMES HISTO INFO RAW HP NonStop ASAP Server Manual !show !show !show !show level 2 I/S frame counts and ratios message size distribution histogram line attribute information last sample in raw format Page 207 of 381
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.
Note When the PATH option is used the user is responsible for creating a unique ASAP domain name following the standard rules for ASAP domain names, 1-64 bytes in length, no more than 5 levels separated with a backslash, and no spaces, quotes, commas, colons, or semicolons. To commit changes from the ASAP DB to a running copy of ASAP: MONITOR [ entity ] [ \node ] ,COMMIT To list or remove user-defined (ASAPX) objects: MONITOR APP [ \node ] ,LIST [ \node.
The type of domain name specified in the MONITOR command varies by entity: APP - application CIPCLIM – CLIM CIPMONITOR – Monitor CIPPROVIDER – Provider 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 SWAP - cpu SYSTEM - \node TAPE - $tape TCPPROCESS - $tcpprocess TCPPORT - port number TCPROUTE - $tcpprocess.
Provider is the name of a CIP Provider process, for example ZTC01 or $ZZCIP. ZTC01. cpu is a processor number from 0 to 15; for example 1. $volume is a disk volume name; for example $DATA. entity is a symbolic application entity name; for example SALES. Applications can be represented as separate ASAP entities when they are defined using the ASAP Entity Definition Language (EDL). Only LIST and REMOVE are applicable for user-defined entities.
$process is a process name, object filename or process name pattern containing wildcard characters. For example, $ABC, $DATA.OBJECT.FILE and $AB*. Note Resolving the processes running from an object filename can result in excessive lowlevel messaging in the NonStop OS operating system. This method should be used judiciously in extremely high-performance application environments. primary->backup is the primary node name followed by "->" and the backup node name.
$tcpprocess.#route is the TCP/IP v4 process or TCP/IP v6 Monitor process name and route name of a TCP/IP route. If you monitor specific TCP/IP processes and then let ASAP auto-configure Routes then ASAP will only configure the routes underneath the processes you have specifically monitored. $tcpprocess.#subnet is the TCP/IP v4 process or TCP/IP v6 Monitor process name and subnet name of a TCP/IP subnet.
When monitored files and processes are specified using wild-card names, the wildcard specifier is contained within the domain name as a separate hierarchical level, and the actual object name is appended to the end as another hierarchical level or levels. When processes are monitored by specifying the object filename, the object filename is contained within the domain name as a separate hierarchical level, and an actual process name is appended to the end as another hierarchical level.
INFO returns information from the database about the set of monitored objects. 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. If domain contains a wildcard character or is not specified, INFO is the default. DETAIL returns detailed time information from the database for the set of monitored objects. When domain is specified, entity must be specified, otherwise both are optional.
REMOVE, FORCE removes a user-defined ASAPX domain from the monitored set of domains. FORCE removes the domain regardless of its state. Once removed, a domain enters a Pending Removal state until the end of the current statistics interval. It is removed once the last record is written for the domain. entity must be specified. domain can use the asterisk wildcard character as the last character in the name.
CIPMONITOR MONITOR CIPPROVIDER PROVIDER Examples To add and turn on the disk $DATA: MONITOR DISK $DATA To commit all disk database changes: MONITOR DISK, COMMIT To turn on all file domains already in the database: MONITOR FILE, ON To turn on all domains on the local node already in the database: MONITOR, ON To display all domains from the database: MONITOR To turn off all disk domains: MONITOR DISK, OFF To turn on all domains on \REMOTE already in the database: MONITOR
To save the disk domain configuration: MONITOR /OUT FILE/ DISK, INFO, OBEYFORM To list the current ASAPX ATM domains: MONITOR ATM, LIST To list the details for ASAPX FUNDS TRANSFER: MONITOR FUNDS\TRANSFER, LIST, DETAIL To monitor a spooler on the system: MONITOR SPOOLER $SPLG To remove an ASAPX user domain: MONITOR FUNDS TRANSFER\WEST\RECEIVE, REMOVE To commit all change on the local node: MONITOR, COMMIT To monitor a process directly enter the process name: MONITOR PROCESS
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.FILE To monitor processes dynamically from an object file as part of a logical process group: MONITOR PROCESS SALES\SERVER\$DATA.OBJECT.
To create an aggregate-only domain for all files on a volume named $DATA3: MONITOR FILE $DATA3\## To create an aggregate process domain and suppress writing of detail records to the ASAP database, specify the name to the level where you want the aggregation to occur using the ## symbol. Detail records are not written to the ASAP database, but they are available for display from ASAP memory using the PROCESS command MEMORY option.
EXPAND MONITOR EXPAND $linename EXPANDIP MONITOR EXPAND $linename FILE MONITOR FILE [logical\]$filename | /pathname, ADD NODE not applicable PROCESS MONITOR PROCESS [logical\]$process | /pathname, ADD PROCESSBUSY MONITOR PROCESSBUSY cpu-number RDF MONITOR RDF primary-node->backup-node * SPOOLER MONITOR SPOOLER spooler-supervisorname SWAP MONITOR SWAP cpu-number SYSTEM MONITOR SYSTEM \nodename TCPPROCESS MONITOR TCPPROCESS $tcpprocess TCPPORT MONITOR TCPPORT port TCPROUTE MONITOR TCP
OUT file specifies a spooler or line printer for the ASAP output sent. If you do not specify an output file, the output is displayed on your terminal. snode specifies the node of the sending Expand system. To send availability information from all the systems, specify NODE \*. 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, if not superseded by a system specified with the ASAP SYSTEM 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. NONULLOUT displays only nodes with nonzero end-to-end statistics. NODE Statistics The following table lists the NODE statistics and description/options displayed with the HELP NCPSTATS command. Table 6-8.
\CENTDIV \051 Time Sysno PHops PLdev NSys LSent LRecv PSent PRecv --------------- ----- ----- ----- ----- ---- ----- ----- ----- ----\CHITOWN 3/01 9:54 153 1 45 153 6 9 11 \CHITOWN 9:53 153 1 45 153 2 7 6 \CHITOWN 9:52 153 1 45 153 6 10 11 \CHITOWN 9:51 153 1 45 153 5 8 10 OBEY Command The OBEY command instructs ASAP to read commands from the specified file. After reaching the end of the primary OBEY file, ASAP reads commands from the original input device (or file).
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] [ [.] $process ] [, [, [, [, [, [, [, [ [, [, [, [, SAMPLES count ] DETAIL ] STATES ] CPU n ] TIME hh[:mm[m/d/y]]] AGGREGATE ] AGGONLY | AO ] MINSTATE [AUTO] ] [state] ] COUNT [count] ] MEMORY ] EXACT ] NOAGG ] Note The PROCESS command in ASAP Release 1 has become PROCESSBUSY in ASAP Release 2.
DETAIL specifies to return more detailed information about the specified monitored processes. STATES specifies to return associated OEM states for each attribute defined with STATEPAIR true in the EDL. CPU n specifies to return information for all processes on only the specified CPU. TIME hh:mm m/d/y specifies the ending time of the display information in hours, minutes, month, day, and year.
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. This lets a user enter ―Show Object Details‖ from ASAP Client, when aggregate only domains are used, to retrieve detail records that make up the aggregate set. EXACT shows statistics for only the specified domain.
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 only Process domains (those ending in ##), enter this EDL DETA
Note The only abbreviation for PROCESSBUSY is PB. P, PR, PRO, and so on are interpreted as PROCESS, not PROCESSBUSY. 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 \*.
STATS displays these detailed processbusy availability attributes: Time of the statistics information in database local civil time Percentage of CPU process time during a sample interval Process identification number (PIN) Program file name of this process Queue length of this process during a sample interval 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
Home terminal name of the process TIME hh:mm m/d/y specifies the ending time of the display information in hours, minutes, month, day, and year. For example, specifying ―TIME 10:15‖ when RATE is 5 indicates that statistics collected from 10:10 to 10:15 are displayed. 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.
Pin The process identification number Pri The current execution priority of this process Program File The program file name of this process RcvQ The average queue length of this process during a sample interval Rmsg The number of messages received per second Smsg The number of messages sent per second Time The time of the statistics information in database local civil time Userid The group ID and user ID of the person accessing the process %WT The wait state.
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 -------------------%-------------------------------------------------00 3/01 10:51 1.6 312 $MM.ASAPXTST.DRV7 $JX17 80 255,34 1.6 313 $MM.ASAPXTST.DRV5 $JX15 80 255,34 1.6 314 $MM.ASAPXTST.DRV4 $JX13 80 255,34 .4 283 $SYSTEM.SYS03.OMLAM 200 255,255 .3 6 $NCP 201 255,255 01 3/01 10:51 1.6 312 $MM.ASAPXTST.DRV7 $JX16 80 255,34 1.6 313 $MM.ASAPXTST.
Boolean-goal gname=(attr op value [ AND|OR attr op value … ] ) [ AND|OR Boolean-goal ] ) gname , DELETE event INFO|CRITICAL [REPEAT] [NODISPLAY] [down] [-up] NOEMS action ACTION "string" | rule [WAIT wait] [NOREPEAT] Use the RANK command to set or view preferred-property-threshold settings (objectives). When a ranked property threshold is exceeded, the state of the ranked property is assigned an alert state. States in ASAP describe the status of a property such as up, down, warning, or critical.
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. simplex-goal attr op [value] [, simplex-goal …] Boolean-goal gname=(attr op value [ AND|OR attr op value… ] ) [ AND|OR Boolean-goal ] ) gname, DELETE ( ) Parentheses are required for Boolean goals. They are used to group one or more attribute-operator-value sets. Parentheses can be nested as needed.
<<< The attribute value must be less than the objective value. Used when defining more than one less-than goal (an escalating goal.) Be sure to set ObjectivesEventState to HIGH or lower when using this operator. = The attribute value must equal the objective value. <> The attribute value cannot equal the objective value. >= The attribute value must be greater than or equal to the objective value. <= The attribute value must be less than or equal to the objective value.
AND is a logical operator used to combine attr-op-value sets into Boolean goals. When AND is specified it states that both sets must be true, failure of either attr-op-value comparison will cause the AND condition to fail. OR Is a logical operator used to combine attr-op-value sets into Boolean goals. When OR is specified it states that either set can be true for the goal to be satisfied, failure of both attr-op-value comparisons is required to cause the OR condition to fail.
-up is the event number to use for the up event, which is triggered when the objective comparison returns to normal after a failure. The number specified must be in the range 6000 through 9999. Event number 4001 is used when this is not specified. The minus sign must precede the up event number even if the down event number is not specified. The ASAP EMS event template for the up event is not applied when custom up events are defined.
<#OBJECT> The NonStop OS or OSS object name <#DOMAIN> The domain name <#D1> Leftmost part of a multilevel domain name <#D2> 2nd part of a multilevel domain name <#D3> 3rd part of a multilevel domain name <#D4> 4th part of a multilevel domain name <#D5> 5th part of a multilevel domain name <#ATTR> The attribute name <#OP> The binomial objective operator.
attribute. <#attrVALUE> A specific value token for the attribute. For example if the attribute name is BUSY the name of this token will be <#BUSYVALUE> and it will contain the value of the BUSY attribute. When using Boolean goals where one or more attributeoperator-value settings are defined, the values returned for the <#ATTR>, <#OP>, <#VALUE>, <#GOAL> and <#GOALVAL> are returned in a list separated by vertical bars.
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. Any goal specified in the command then overrides corresponding LIKE domain values. ACTIVATE turns ranking on for the specified domain(s) in the specified entity. entity must be specified when domain is specified; otherwise both are optional.
SIMPLEX deletes the simplex goals for an entity or domain, leaving any Boolean goals defined for the entity or domain. GOALNAMES deletes the Boolean goals for an entity or domain, leaving any simplex goals defined for the entity or domain. INFO returns information about objectives from the database. 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.
TCPLOOP LOOP TCPMONGQ MONGQ TCPPORT PORT TCPPROCESS TCP TCPQIO QIO TCPROUTE ROUTE TCPRTE RTE TCPSOCK SOCK TCPSUBNET SUBNET TCPUDP UDP TELSERVPROCESS TELSERV TELSERVSERVICE SERVICE TELSERVWINDOW WINDOW Since CIP entity names are long and difficult to type ASAP supports the following abbreviations for the entity names: CIPCLIM CLIM CIPMONITOR MONITOR CIPPROVIDER PROVIDER Examples To add or modify the record for the disk $DATA: RANK DISK $DATA, BUSY < 65 To specify tha
To override global objectives and create critical events: RANK FUNDS TRANSFER\WEST, BUSY > 20, BUSY < 40 CRITICAL REPEAT To turn ranking off for a file: RANK FILE \REMOTE.$DATA.FILE.
RANK CPU 0, BUSY < 90 CRITICAL 4444-5555 To define a custom down event number for CPU 0 getting too busy: RANK CPU 0, BUSY < 90 CRITICAL 4444 To define a custom up event number for CPU 0 when it returns to normal: RANK CPU 0, BUSY < 90 CRITICAL -5555 To define a goal for busy for an OSS shell process aggregate-only domain: RANK PROCESS /bin/sh\##, BUSY < 10 To define a global goal and action to resecure any monitored file using the ASAP default RESECURE rule: RANK FILE, RWEP = "AOAO" ACT
Using the << or <<< operator is the same as using the < operator if only one goal is defined.
RANK CPU, BUSYGOAL = (BUSY < 80 OR QUEUE < 3) To define a Boolean goal named BUSYGOAL for all CPUs that checks the BUSY and QUEUE attributes and writes a critical event if the goal fails: RANK CPU, BUSYGOAL = (BUSY < 80 AND QUEUE < 3) CRITICAL To define a Boolean goal named BUSYGOAL for all CPUs that checks the BUSY and QUEUE attributes and takes an action if the goal fails: RANK CPU, BUSYGOAL = (BUSY < 80 AND QUEUE < 3) ACTION “TACL RUN $SYSTEM.MACROS.
where the ASAP program was started, if not superseded by a system specified with the SYSTEM command. SAMPLES count is the number of samples to display per domain. CPU displays RDF domain or metric values in the specified CPU. DETAIL displays detailed RDF metric values. STATES displays RDF metric values and their objective states. TIME hh:mm m/d/y defines the ending time of the display information in hours, minutes, month, day, and year.
RDF \* \TANDA Domain\Name\Hierarchy -------------------------------Dome->Tanda\Imagetrail\$Data4 Dome->Tanda\Purger\$Purg Dome->Tanda\Receiver\$Rec1 Dome->Tanda\Updater\$Up01 Dome->Tanda\Updater\$Up02 Dome->Tanda\Updater\$Up03 Status Date Time ---------------- ----- ----Running 5/11 9:37 Running 5/11 9:37 Running 5/11 9:37 Running 5/11 9:37 Running 5/11 9:37 Running 5/11 9:37 Error ----0 0 0 0 0 0 \DOME Domain\Name\Hierarchy -------------------------------Dome->Tanda\Extractor\$Ext1 Dome->Tanda\Monitor\$
Dome->Tanda\Purger\$Purg Dome->Tanda\Receiver\$Rec1 Dome->Tanda\Updater\$Up01 Dome->Tanda\Updater\$Up02 Dome->Tanda\Updater\$Up03 n/a n/a n/a n/a n/a \DOME Domain\Name\Hierarchy -------------------------------Dome->Tanda\Extractor\$Ext1 Dome->Tanda\Monitor\$Mntr + n/a $DATA2 $DATA4 $DATA4 $DATA4 n/a n/a $DATA03 $DATA04 $DATA05 n/a n/a $DATA $DATA1 $DATA4 Aud Vol Img Vol Pri Vol Bkp Vol -------- -------- -------- -------$AUDIT n/a n/a n/a $AUDIT n/a n/a n/a To show statistics in RAW format: RDF \*
Status Dateymd Time v Et Error RTDSecs RTDTime PCpu BCpu Pri --------------- ---------- ----- - -- ----- -------- --------- ---- ---- --Running 2001/05/11 09:50 1 01 0 0 0:00:00 2 3 185 continued...
[ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ OBJECTIVESEVENTUP ON | OFF ] OBJECTIVESEVENTCONSOLE ON | OFF ] OBJECTIVESEVENTCONSOLEUP ON | OFF ] OBJECTIVESEVENTSTATE OEM-state ] OBJECTIVESEVENTSUBJECT ON | OFF ] OBJECTIVESEVENTMAX max events per domain per interval ] OBJECTIVESRANK STANDARD | PERCENT | HISTORICAL ] OBJMONITOR monitor-object ] PARTITION partition-descriptor ] PRIMARY cpu | * ] PRIORITY server-priority ] PROCESS entity-option ] PROCESSBUSY ENTRIES count | SUBSAMPLES count ] P
To enable ACTION processing, set ACTION on prior to starting the ASAP monitor via the START MONITOR command. The monitor will keep a persistent action server running at all times, even in the event of a failed CPU. The ASAP action server has a process name of $idX, where id is the ASAP id defined via the SET ID option. SET ACTION OFF means the RANK/GOAL ... ACTION string associated with an objective is not performed when objectives are not satisfied.
ASPLOG filename defines the name of the Monitor or Collect error logfile. This filename must be the same on all nodes that will have Monitor or Collect processes executing on them. The default is $SYSTEM.SYSTEM.ASAPLOG. 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.
SCPNAME $name defines the SCP process name the SGP will use to retrieve statistics from the CIP subsystem. If no SCPNAME is specified, the SGP will attempt to start one but security concerns could prevent a successful start of an SCP process. MAXCLIM n defines the maximum of number of CLIM domain records that can be processed by the SGP. Domains are either autoconfigured or entered using the MONITOR command. The default is 128 domains. The maximum is 32767.
CLEANTIME time defines the time of day in hours and minutes that database self-cleaning begins. The default is 0000 (midnight). The RETAIN option determines what happens at cleantime. COLLECT collect-node defines the network node where the Collect process resides. The Monitor process reports statistics to the Collect process on the specified node. The default is the system where you issued the START COLLECT command.
RATE minutes defines the interval, in minutes, that COMM statistics are reported back to the Collector. ASAPCMM uses the interval provided by the operator. The default is the ASAP RATE. VOLUME [$volume][.][subvolume] specifies the location of the Measure Data file. The default is $SYSTEM.SYSTEM. SUBVOL subvolume specifies the subvolume location of the Measure Data file. The default subvolume is SYSTEM. SWAPVOL [$volume] specifies the location for the Measfh swap volume. The default is $SYSTEM.
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. Note that setting DBMaxDays to a nonzero value also sets the RETAIN option to ROLLOVER. See HELP SET RETAIN for details.
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.
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.ASAP2004.
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. The default is the same as the CPU that the ASAP CI is executing in.
supported for user-defined entities used with the ASAP Extension. The default is SET EDL $SYSTEM.SYSTEM.ASAPEDL. 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.
ON | OFF ON enables network-wide FILE status reporting. OFF disables networkwide FILE status reporting. The default value is ON. 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.
NORECS In some rare cases no file history is required, and users do not want to monitor files using ASAP Client. For these cases, a user can specify NORECS to cause the File SGP to stop writing all detail process records to the database. The SGP still monitors the files and generates EMS events (if enabled) when they alert, but it does not write records to the ASAP database for viewing by the ASAP Client or for historical tracking. TRACE turns $Receive tracing on in the File SGP.
SET FILE PARAM SET FILE PARAM, entity-option HELPFILE filename defines the name of the ASAP help file. This name defaults to ASAPHELP in the same subvolume as the ASAP object file. The structure of the ASAP help file is: Keywords start in column 3, with the help text for the keyword following in subsequent lines that have text in column 4 or greater. Help text continues until another line with text in column 3 is encountered. All lines starting with a TGAL backslash are ignored.
IOCONTROL count defines the maximum number of output lines that can be written to the output file for any command before a prompt is issued. This option is used to perform flow control between the ASAP Client and Server. By limiting the maximum number of output lines per I/O, client/server loading on communications infrastructure is controlled. The More? prompt is a modeless prompt. Anything other than a carriage return is interpreted as a command.
Examples SET LOGINTERVAL 60 minutes SET LOGINTERVAL 1440 Suppress duplicate error events for 60 Log each error type only once per day LOGSUPPRESS ON | OFF controls the suppression of duplicate ASAPLOG file error events and EMS tokenized error events. The default is OFF. OFF disables duplicate ASAP error event suppression. ON enables duplicate ASAP error suppression. The LOGINTERVAL setting determines the time duration for duplicate event suppression.
This command adds $DATA as a disk to be monitored regardless of the SET MONITORADD setting: MONITOR DISK $DATA, ADD NODE entity-option [, entity-option]... determines settings and parameters for the NODE entity. CPU cpu-num defines the CPU that the NODE SGP process will reside in. ON|OFF enables or disables network-wide node availability reporting. The default is OFF. OBJECT ASAP/NCP-program-file-name defines the ASAP/NCP program object file name.
ON | OFF indicates whether the alert is on or off. For example: 04-03-19 13:33:41 \CENTDIV.$ZOOS *TANDEM.ASAP.V02 004000 ASAP ALERT ZOOS Node \ZERO Status Down Notes Only nodes that have an ASAP monitor reporting to the ASAP collector will have node down alerts generated for them. The collector does not generate a node down alert for all nodes in an Expand network, but rather only for nodes that have an ASAP monitor on them.
The default is $asap-database-subvolume.DBOBJ. Due to I/O activity in the ASAP database volume, HP recommends that you locate the objectives database file on another disk volume. OBJECTIVESEVENT ON | OFF enables ASAP for event generation when objectives are not met for attributes where event generation is specified. The default is OFF. OBJECTIVESEVENTUP ON | OFF enables ASAP for generation of up events when alerts for which down events were generated recover to an acceptable state. The default is OFF.
CRITICAL DOWN Critical problem alert Down object alert The default is CRITICAL. Note Escalating and de-escalating goals can create High, Warning and Critical alert states so OBJECTIVESEVENTSTATE should be set to LOW, MEDIUM or HIGH when using goals of that type if those goals create EMS events or initiate automated actions. OBJECTIVESEVENTMAX max-events-per-domain-per-interval defines the maximum number of events that ASAP should generate per domain per statistics interval. The default is 1.
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.
part-num the partition number (0 through 15) to which the partitioning options apply. 0 (or BASE) indicates the base partition of the entity. To specify primary and secondary extent sizes for all partitions of the entity, use ALL. part-opt is one of these partition options: { KEY key-value { SYSNO system-number { PRIEXT ext-value { SECEXT ext-value { MAXEXTENTS maxext-value { VOLUME volume-name } } } } } } key-value a partial key value, defining the lowest key value that can reside in the partition.
extent. This value can be rounded up to an even number when the partition is created. maxext-value an integer value from 16 through 978, that specifies the maximum number of extents in the partition. volume-name the name of the NonStop OS volume on which the partition will reside. reset-desc. RESET resets all partitioning attributes for all entities, including the default settings.
You must provide a KEY or SYSNO value, or both, and a VOLUME for all secondary partitions. If you do not, the partition description is marked Invalid in the output of the SET PARTITION command, and the Collector does not create the partition. You must define partitioning keys (made up of a combination of the SYSNO and KEY values) in ascending order for each partition.
beginning at partition 0, until it encounters an invalid description. All further partition descriptions for that entity are ignored. For example, if partitions 0, 1, 2, and 4 are valid for the CPU entity, but partition 3 is invalid, only partition descriptions 0, 1, and 2 are used when creating the CPU database. Partition description 4 is ignored, even though it is valid, because description 3 is invalid.
format. ??-Max Ext n/a Not optimal because the MAXEXTENTS value for the secondary partition is ignored since FORMAT2 is on. The partition is created, but the MAXEXTENTS of the base partition is used.
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. PRIORITY server-priority defines the execution priority of the Monitor or Collect process started by the STARTUP command. The default is 160.
MINSTATE defines the state at which the Process SGP should consider a domain to be in an alert state. Valid values are 2 through 8; the default is 3. 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.
MBYTES defines the size in megabytes of the memory pool allocated to store domains that are dynamically resolved at each interval. The default setting can vary by ASAP version. Note The MONITOR PROCESS, LIST, DETAIL command will return information about the maximum value parameters and the memory pool utilization.
PROXY ON|OFF ON|OFF The SET PROXY ON command enables ASAP Hybrid within ASAP Server. Hybrid settings are not visible within ASAP until this command is executed. ASAP Hybrid is an optional ASAP product. For information about configuring the ASAP Hybrid product, see the ASAP Hybrid Manual. Examples 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.
PROXYPARAM proxy-parameter proxy-parameter A startup parameter for the ASAP Hybrid Proxy server. This item is for future use. ASAP Hybrid is an optional ASAP product. RATE minutes defines the interval, in minutes, that ASAP entity availability information are reported back to the process defined by the Collect and ID options.
REMOTESECURITY ON | OFF defines whether remote passwords are checked when shutting down a remote ASAP monitored node or when obtaining status information about a remote ASAP monitored node. SET REMOTESECURITY OFF bypasses RemotePassword security checks. SET REMOTESECURITY ON forces RemotePassword checking of any remote node. The default is ON. RETAIN option defines the action to be performed against the database at cleantime. ALL retains all records indefinitely.
down Collect and restarting it with a different sleep time reactivates collection to the database. time, time defines the beginning and ending times of the time range. The default is 0000,0000; it disables sleeping. Examples This example sets the sleeptime: +SET SLEEPTIME 0000, 0300 !No database collection between Midnight and 3:00 AM daily occurrence. +STARTUP COLLECT SPOOLER entity-option [, entity-option] determines settings and parameters for the Spooler entity. The default is OFF, $SYSTEM.SYSTEM.
PLUS the PLUS option turns on high performance enhancements for Spooler environments with a large number of jobs. When PLUS is specified ASAP does not analyze and count each job in the Spooler. This reduces resource consumption dramatically but does have some limitations: Job detail information is reported at the Supervisor level only, it is not broken down for each Spooler component. Jobs in a HOLD state are not reported, the value for Hold is always zero.
CPU cpu-num defines the CPU that the SWAP SGP process will reside in. ON|OFF enables or disables network-wide swap availability reporting. OBJECT ASAP-swap-program-filename specifies the name of the Swap SGP program file. The default is $SYSTEM.SYSTEM.ASAPSWP. PARAMETERS specifies swap-specific parameter string to pass to each Swap SGP at startup. RATE #mins overwrites the ASAP default rate parameter for the Swap SGP only. Instructs the Swap SGP to sample at this rate.
Examples This example synchronizes all the nodes in the network twice a day, first at 2:30 a.m. and again at 5:00 a.m. +SET SYNC 150, 2 +STARTUP \* 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.
PARAMETERS specifies tape-specific parameter string to pass to each Tape SGP at startup. RATE #mins overwrites the ASAP default rate parameter for the Tape SGP only. Instructs the Tape SGP to sample at this rate. TRACE instructs the Tape SGP to log trace records to the ASAP log file. Examples +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.
PARAMETERS "TCP-param [ TCP-param ]... " | null specifies the TCP specific parameter string to be passed to the ASAPTCP process at startup time. The default is the string. The Parameter list must be enclosed in double quotes. TCP-param options are: TRACE turns on $RECEIVE trace to the EMS and ASAP log files. 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.
PORT [n] turns on monitoring of TCP Ports, and optionally specifies the minimum number of minutes the SGP will wait before reconfiguring TCP ports when they are being automatically configured by the SGP. Port monitoring is off by default, and the configuration interval defaults to the ASAP rate.
entered using the MONITOR command. The default is 1000 domains. The maximum is 32767. MAXTEL n defines the maximum of number of TELSERVPROCESS 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. MAXSRV n defines the maximum of number of TELSERVSERVICE domain records that can be processed by the SGP. Domains are either autoconfigured or entered using the MONITOR command.
ON | OFF enables or disables network-wide TMF availability reporting. The default value is OFF. OBJECT ASAP-TMF-program-file-name defines the ASAP-TMF program object filename; this program is automatically started on each node by the ASAP monitor. The default is $SYSTEM.SYSTEM.ASAPTMF. PARAMETERS "TMF-param [ TMF-param]... " | null specifies the TMF specific parameter string to be passed to the ASAPTMF process at startup. The default is the null string.
SHOW [entity] [attribute] [, DETAIL] [, ATTRIBUTES] Note Attributes that support objectives are identified with an asterisk in SHOW command output. entity is the name of an ASAP entity as defined in EDL. attribute is the name of an attribute as defined for the entity in EDL. DETAIL shows detailed information about the entity. ATTRIBUTES shows the attributes defined for an entity.
COLLECT specifies a Collect process. MONITOR specifies a Monitor process. This is the default. If SET DISK ON was specified at startup, shutdown of the Monitor process causes the DISK to be shut down as well. node-name specifies the individual system for which information is to be monitored or collected. It stops the ASAP Monitor or Collect process on this node only. ppd-name specifies a process pair directory name.
[, EXACT [AUTO ] ] [AUTOSHORT]] ] 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. \* specifies that the performance and state 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 SPOOLER \*.
When a ―<‖ appears immediately after the timestamp, the statistics were received late by the Collector process. Late statistics indicate 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. STATES shows states associated to spooler attributes. DETAIL shows detailed information for the specified spooler domain (supervisor, collector, device, print process).
EXACT indicates to return information about domains that exactly match spoolerspec. Consideration You cannot use TIME, SAMPLES, or \* with DETAIL or MINSTATE.
$SPLS\COLL\$L $SPLS\DEV\$P275A $SPLS\DEV\%P275B $SPLS\DEV\CENTREG.$A.#S $SPLS\PRINT\$SPLP $SPLS\PRINT\$FASTP $SPLS\SUPER\$SPLS Active Waiting Waiting Waiting Dormant Dormant Active 03/23 03/23 03/23 03/23 03/23 03/23 03/23 8:07 8:07 8:07 8:07 8:07 8:07 8:07 0 0 0 0 0 0 0 1 3 1 1 0 2 2 2 149 130 130 149 continued... Jobs Batch Open Print Hold DevQs Locs Full% File/Process Name ----- ----- ----- ----- ----- ----- ----- ----- -------------------------378 0 0 0 100 75 $DATA2.SPL.
Data File Name Jobs Batch Open Print Hold Size UnitAlloc -------------------------- ----- ----- ---- ----- ---- ----- --------$DATA2.SPL.DATA 378 0 0 0 100 4 1916 continued...
\* 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. If SET SGPName ON is specified, the SGPName specified by SET SGPName OBJECT is started. SGP options are sent to each remote monitor. If different SGP options are required for different SGPs, each SGP must have the options set before starting the remote monitor.
The Monitor, SGPs, and Collect process behavior is based on the current values of the SET command parameters when the process is started. STATUS Command The STATUS command provides status information about the ASAP system in the specified node.
ACTIONS option displays detailed action server information: STATUS ACTIONS ASAP shows analysis of last action request. STATUS ACTREQUEST shows XML parameters for last action request. STATUS ACTIONS RUN shows date-time-detail of actions run. STATUS ACTIONS MSGS shows oldest action server log messages. STATUS ACTIONS MSGS shows the most recent actions. STATUS ACTIONS MSGS shows actions for STATUS ACTIONS LOG ON | DETAIL turns on action logging.
Access Indicates the process NonStop OS operating system Security GROUP,USER access ID Reqs Indicates the number of requests this process has received since it was started Lmsgs Indicates the number of log messages this process has logged Created Indicates the month/day/hour that this process was started ReqTime Indicates the time in hours/minutes/seconds that this status request was received by each process SrvTime Indicates the time in hours/minutes/seconds that this status request was replie
Example - Status Monitor +STATUS \ISLAND ! Show \ISLAND’s Status \ISLAND Primry Backup ---------- ------ -----$BOOM V05 1,196 0,177 $BOOM0 V05 0,145 $BOOM1 V05 1,203 $BOOM2 V05 2,216 $BOOM3 V05 3,003 $BOON V04 0,142 RDF $BOOG V05 1,245 NCP $BOOJ V05 1,180 DSK $BOOK V05 0,120 EXP $BOOL V05 1,021 FIL $BOOO V05 1,119 SPL $BOOQ V05 1,117 TAP $BOOR V05 1,246 TMF $BOOT V05 1,103 PRO $BOOU V05 1,208 COM $BOOV V05 2,069 TCP $BOOA V05 1,204 SWP $BOOC V05 1,204 CIP (collect \CENTDIV.
Example - Status Actions STATUS \CHICAGO ACTIONS ! Status chicago action server STATUS \CHICAGO ACTIONS RUN ! Status chicago of actions run STATUS \CHICAGO ACTIONS ASAP ! Analysis of last action request STATUS ACTIONS MSGS 10 ! Show 10 most recent action msgs STATUS ACTIONS MSGS 100 10 ! Show 100th thru 91st most recent msgs STATUS ACTIONS ** ! Show taskids for all action tasks STATUS ACTIONS LOG ON ! Enable detail log, will show logname STATUS ACTIONS LOG OFF ! Disables detail logging HP No
SWAP Command The SWAP command displays SWAP availability statistics for the specified nodes and swap file domains. Type HELP SWAPSTATS at the ASAP prompt for an explanation of SWAP performance statistics. For an alphabetical list, see the CPU Statistics table. SWAP [/OUT /] [\* ] [\] [ [.
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. For example, specifying ―TIME 10:15‖ when RATE is 5 indicates that statistics collected from 10:10 to 10:15 are to be displayed.
CPU number lists the statistics for swap files that are currently operating in the specified CPU number, cpu-number. DETAIL displays the processors swap files statistics as a whole for the specified CPU or system. Displays both the good and failed statistics for the following: OK/FAILED for each CPU ALLOCATES The number of allocations made. CREATES The number of reservations made for process creations. FREES The number of allocations freed. RELEASES The number of reservations released.
Table 6-11. SWAP Statistics and Descriptions Statistics Description/Option ALLOCATES Number of good and failed allocations made for each CPU. AVAILABLE The default display is the number of memory pages available for each CPU. With the file option it displays number of memory pages available for each file. AVAIL% Percent of swap space available for each CPU. CREATES Number of good and the number of failed reservations made for process creations for each CPU.
Examples These examples show some of the available options and their output: +swap, sample 4 \CENTDIV -------00 3/18 00 3/18 00 3/18 00 3/18 01 3/18 01 3/18 01 3/18 01 3/18 02 3/18 02 3/18 02 3/18 02 3/18 03 3/18 03 3/18 03 3/18 03 3/18 Time ----- Status Files SWAPTOTAL Avail FUll Reserved Reservations Available -------- ----- ---------- ----% ---% -------- ------------ -------- 12:59 12:58 12:57 12:56 12:59 12:58 12:57 12:56 12:59 12:58 12:57 12:56 12:59 12:58 12:57 12:56 Up Up Up Up Up Up Up Up Up Up
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 [ \* ] [ \node-name] [ MONITOR ] [ [.] ppd-name ] \* synchronizes information on all nodes. MONITOR synchronizes information on the Monitor process. node-name specifies the individual system for which information is to be displayed. ppd-name specifies a process pair directory name.
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] [ [.] tapespec] [, TIME hh[:mm [m/d/y]]] [, STATES ] [, DETAIL ] [, EXACT ] OUT file specifies the spooler or line printer where the ASAP output is to be sent.
STATES indicates to display states associated with tape attributes. DETAIL indicates to display detailed tapemount information for the specified tape domain. EXACT indicates to retrieve only information that exactly matches tapespec. Consideration You cannot use TIME, SAMPLES, or \* with DETAIL.
Checks Mnts Mtime TapeName ------ ---- ----- -------NL,BLP 0 0 BLP 0 0 BK001 + TpStatus -------SCRATCH TpLabel ------BACKUP ProcName -------------\ASAP.
TapeName TpStatus TpLabel ProcName ProgName UserId Prot IO -------- -------- ------- -------------- -------- ------- ---- --ANSI \ASAP.$PROC FUP 33,23 No OUT continued... Action ---------------------------------MOUNT ANY APPROPRIATE SCRATCH TAPE + 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 [\* ] [ [.
TCPPROCESS TCPQIO TCPROUTE TCPRTE TCPSOCK TCPSUBNET TCPUDP TELSERVPROCESS TELSERVSERVICE TELSERVWINDOW (or (or (or (or (or (or (or (or (or (or TCP) QIO) ROUTE) RTE) SOCK) SUBNET) UDP) TELSERV, or TP) SERVICE, or TS) WINDOW, or TW) domain Any TCP or Telserv domain (object) name SAMPLES the number of samples to display per domain STATES the objective states of TCP metric values TIME defines ending time and date of sample(s) to display DETAIL displays custom detailed TCP metric values for specific sub-entit
EXTRACT extract TCP records from the ASAP database to a separate database file or to a process. If the specified file does not exist, it will be created NOPRINT suppress terminal output for EXTRACT commands NOLINEBREAK do not break output lines at 132 characters.
TCP/OUT IPCSV/IP, RAW, DE, ST, TAB ",", NOLINEBREAK, SAMPLES 1000 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.
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. STATES indicates to display all states associated with attributes. 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.
Audittrail Tmf Transactions + Up Enabled Up 3/14 13:18 Master 3/14 13:18 3/14 13:18 - - 62 - 0.00 - - - 0 No To display only the attributes associated with a state: + tmf, states \ASAP TMF Used -------------Auditdump Audittrail Tmf Transactions Status S Date Time Error S Active -------Enabled Up Started Up - ----- ----2 3/14 13:18 2 3/14 13:18 2 3/14 13:18 2 3/14 13:18 ----0 0 0 0 1 1 1 1 ------Yes - S Ovflw S Hold S 7 1 1 1 ----No - 1 1 1 1 ---No - - ---1 1 62 1 1 - continued...
continued... Hold ---No + S Used S Tps S BeginTr - ---- - -------- - -------1 - 1 - 1 1 62 7 - 1 1 - 1 0.00 1 Enabled 1 - 1 - 1 - S 1 1 1 1 Catalog Trans S Hung -------- ----- - ---- 1 - 1 Active - 1 0 1 No S Duration S - -------- 1 - 1 1 - 1 1 - 1 1 0 1 To display details about all TMF transactions subdomains: + tmf transactions, minstate \ASAP Transactions ---------------------------\Asap.0.
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... FirstPinnedFile Reason Dump TransDsbl% -------------------------- --------------- ---- ---------$DSV.
Appendix 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.
"Cpu Date Time Busy Q Disp Disc Chit Swap MQ Pcbx Lcbx"skip 1 "-------- --- ----- ----- ---- -- ---- ---- ---- ---- -- ---- ----" after change on ihour print space 9 cpuno 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 lcbm
cpubusy := avg (busy over ihour) noprint cpuq := avg (qlen over ihour) noprint cpudisp := avg (disps over ihour) noprint discrate := avg (discs over ihour) noprint chitrate := avg (chits over ihour) noprint swaprate := avg (swaps over ihour) noprint memq := avg (mqlen over ihour) noprint pcbmax := max (pcb-use over ihour) noprint lcbmax := max (lcb-use over ihour) noprint after change on ihour print sysname cpuno space as i3 space timestamp-date ( x ) as date "mb2/d2"
Appendix 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.
Event Definitions DEF 02 02 02 02 02 END. Event. Ts Tsword Word Et Etword type type type type type binary binary binary binary binary 64. !GMT usec start timestamp 16 redefines Ts. 16 redefines Ts. 64. !elapsed time of event usecs 16 redefines Et. Query Key Definitions DEF 02 02 03 03 02 03 03 02 02 02 02 02 02 02 02 END. Q-key. ikey cpu-entity csysno ccpuno lh-entity lhsysno lhlinename Entity iyear imonth iday ihour imin isec irank !For Enform pic x(18). redefines ikey.
04 END. nssvnn type binary 16. ! Extended Query Key The ASAP extended queue q-key with the domain name required for APP processing is: DEF Q-key-x. !For Enform 02 02 03 03 02 02 02 02 02 02 02 02 END. ikey pic x(74). app-entity redefines ikey. sysno type binary 16 display “m<\999.>”. domain type character 64. entity type character 66 redefines ikey. iyear pic x(67) redefines ikey. imonth pic x(68) redefines ikey. iday pic x(69) redefines ikey. ihour pic x(70) redefines ikey.
02 clim-present 02 word present.
DEF ZClimState. 02 clim-present 02 word present.
DEFINITION CLIM-Stats. !Description.............Sect 02 system type binary 16 occurs 4 times. ! 02 word type binary 16 redefines system.! 02 sysname type character 8 redefines system. 02 P-key-x type *. ! 8.3 02 Q-key-x type * redefines P-key-x. ! 02 event type *. ! 02 Type type binary 16. ! PROV 02 AggRec type binary 16. ! 02 Spare type binary 16 occurs 6 times. ! 02 OpText type binary 16 occurs 5 times. ! 02 Status type character 1 redefines OpText. 02 OpState type binary 16. ! 02 Error type binary 64.
02 02 02 02 02 02 02 END. size-32769-and-larger connected-clim-curr connected-clim-high rejected-connections deferred-sends total-messages-sent total-messages-recv type type type type type type type binary binary binary binary binary binary binary 32. 32. 32. 32. 32. 64. 64. DEF ZMonState.
02 Q-key-x 02 event 02 Type PROV 02 AggRec 02 Spare 02 OpText 02 Status 02 OpState 02 Error 02 ErrorState remove) 02 Data 02 State END. type * redefines P-key-x. type *. type binary 16. type type type type type type type ! enform q-key extended ! ts, interval & info ! Record type CLIM, MON, binary 16. ! binary 16 occurs 6 times. ! binary 16 occurs 5 times. ! character 1 redefines OpText. binary 16. ! binary 64. ! binary 16. ! type ZMONData. type ZMONState. * CIP\CLIM\ DEF ZPROVData.
Comm Statistics Definitions DEFINITION COM-STATS. 02 system 02 word 02 sysname 02 P-key 02 Q-key 02 event 02 Invalid 02 PCpu 02 PCpu-State 02 PPin 02 BCpu 02 BCpu-State 02 BPin 02 LDev 02 Type 02 SubType type type type type type type type type type type type type type type type 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.
02 02 02 02 02 02 02 02 02 02 END. NumRetries NumRetries-State NumTrans NumTrans-State AvgRespTime AvgRespTime-State type type type type type type binary binary binary binary binary binary 32. 16. 32. 16. 64. 16. Spare1 Spare2 Spare3 Spare4 type type type type binary binary binary binary 16. 16. 16. 16. ! ! ! ! ! ! Number retries perfor NumRetries State. Number transasctions. NumTrans State. Avg Response time/xac AvgRespTime State. CPU Statistics Definitions DEFINITION Cpu-stats.
02 02 02 02 02 02 02 02 02 03 03 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 END. 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. !pages locked state sys-use-State type binary 16. !syspool in use state pcbx-use-State type binary 16. !High Pin pcbs in use state tle-use-State type binary 16.
02 Cmiss type binary 16. !Cache miss tot 512-4096 02 Qlen type binary 16. !Request Queue 02 Qmax type binary 16. !Request Qlen 02 Requests type binary 32. !Total write, read, seek 02 Reqs-blckd type binary 16. !Request blckd file locks 02 Swaps type binary 16. !Swap rate 02 Volsm-Qlen type binary 16. !Volume Semaphore queue 02 Volsm-Qmax type binary 16. !Volume semaphore qlen 02 Extra type binary 16 occurs 4 times. 02 Disk-devices occurs 2 times. 03 Invalid type binary 16.
Expand Entity Statistics Definitions DEFINITION NET-stats.
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 frame-cnt error-cnt type binary 32. !base + 33 type binary 32. !base + 34 !-- LEVEL 4 Buff/Msg use -net-cur-io-buf type binary 32.!base + 35 net-max-io-buf type binary 32.!base + 36 net-lt64 type binary 32.!base + 37 net-lt128 type binary 32.!base + 38 net-lt256 type binary 32.!base + 39 net-lt512 type binary 32.
02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 END. quer-rsps-sent-state type binary 16. quer-rsps-rcvd-state type binary 16. Mem-low-state type binary 16. Invalid-Frames-state type binary 16. frame-dropped-state type binary 16. Invalid-address-state type binary 16. Client-OpState type binary 16. Cpu-B type binary 16. Pin-B type binary 16 Cpu-State type binary 16. spare1 type binary 16. !Spare spare2 type binary 32. !Spare spare3 type binary 32. !Spare spare4 type binary 32. !Spare spare5 type binary 32.
02 Files-State type binary 16. 02 02 02 02 02 02 02 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. 02 02 02 02 END. !Number of files state !File code !1=Format1, 2=Format2 !Unstruct, relative, etc. !Protection view, table, etc.
02 02 02 02 02 02 02 02 02 02 02 02 02 02 Spare OpText Status OpState Error ErrorState Cpu Cpustate BCpu BCpustate BPin Pri PriState Busy 02 BusyState 02 CBusy decimal 02 CBusyState 02 Affinity-w 02 Affinity Affinity 02 AffState 02 IPU 02 IPUState 02 BIPU 02 BIPUState 02 P-State 02 PState 02 PStateState 02 W-State 02 WState 02 WStateState 02 MPages 02 MPagesState 02 MSent 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 type type type type type type type type type type type type type type binary 16 oc
02 SMode 02 SReq 02 PFS END. type binary 16. type binary 16. type binary 32. ! Stop mode ! Stop request mode ! Current PFS ProcessBusy Statistics Definitions DEFINITION Pcb-stats. 02 System 02 Word 02 Sysname 02 P-key 02 Q-key 02 Event 02 Cputype 02 Invalid 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 type type type type type type type type binary 16 occurs 4 times.!system name binary 16 redefines system. character 8 redefines system. *.
02 02 02 02 Spare2 Spare3 Spare4 Spare5 type type type type Binary Binary Binary Binary 16 16 16 16 unsigned. unsigned. unsigned. unsigned.END. 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 *.
02 02 02 02 02 BCpu BCpu-State Priority Op-Text OpText type type type type type 02 02 02 02 OpState Error Error-State SplType type type type type 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.
02 02 03 FName 03 UnitSize 03 UnitAlloc 03 TotalUnits Device-ext 03 FName 03 Flags 03 FormName 03 RetryIntvl 03 NumRetries 03 RestartIntvl 03 MaxRetries PrintProc-ext 03 FName 03 Flags type character 26. !Collectors File name. type binary 16. type binary 32. type binary 32. redefines Buffer-int. type character 8. !Associated Print Process name. type binary 16. type character 16. type binary 16. type binary 16. type binary 16. type binary 16. redefines Buffer-int. type character 26.
02 02 02 02 02 02 02 02 02 02 02 02 03 03 03 03 03 03 03 03 03 03 03 03 03 03 03 03 03 02 02 02 02 02 02 02 END. resize-ok-state type binary 16. !Resizes ok state resize-fail type binary 32. !Resizes failed resize-fail-state type binary 16. !Resizes failed state alloc-ok type binary 32. !Allocates ok alloc-ok-state type binary 16. !Allocates ok state alloc-fail type binary 32. !Allocates failed alloc-fail-state type binary 16. !Allocates failed state frees-ok type binary 32.
02 02 Op-Text OpText 02 OpState type binary 16 occurs 12 times. !Operational status type character 1 redefines op-text. !Operational Status type binary 16.
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 SockLstn connattempt accepts connects drops conndrops closed segstimed rttupdated delack timeoutdrop rexmttimeo persisttimeo keeptimeo keepprobe keepdrops snd-total snd-pack snd-byte snd-rexmitpack snd-rexmitbyte snd-rexmitfast snd-acks snd-probe snd-urg snd-winup snd-ctrl bad-hdr-len rcv-total rcv-pack rcv-byte rcv-badsum rcv-badoff rcv-
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 type type type type type type type type type type type type type type binary binary binary binary binary binary binary binary binary binary binary binary binary binary 32. 32.
02 badseqs 02 unack 02 timeout 02 noport 02 rcv-urg 02 rcv-dup-pack 02 rcv-dup-byte 02 rcv-part-dup-pack 02 rcv-part-dup-byte 02 rcv-out-pack 02 rcv-out-byte 02 rcv-after-win-pack 02 rcv-after-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 paws-drop 02 predict-acks 02 predict-data 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
02 Word 02 bad-hdr-len 02 bad-xsum 02 nosum 02 bad-len 02 noport 02 noportbcast 02 fullsock 02 pcbcachemiss 02 out-pkts 02 in-pkts-dropped 02 out-pkts-dropped END. type type type type type type type type type type type type binary binary binary binary binary binary binary binary binary binary binary binary DEF ZICMP6Data. 02 err type binary 02 Word type binary 16 redefines err.
02 old-short 02 old-icmp 02 OutEchoRply 02 OutDstUnrch 02 OutSrcQnch 02 OutRedirect 02 OutEcho 02 OutTimeExcd 02 OutParamPrb 02 OutTimeStmp 02 OutTimeSRpl 02 OutInfoReq 02 OutInfoRpl 02 RouterSolicit 02 badcode 02 too-short 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 RouterAdvertise 02 bad-rap-subcode 02 bad-addrlist 02 bad-wpa 02 rdisc-nrecorded END.
02 fragmented 02 ofragmented 02 cantfrag 02 badoptions 02 noroute 02 badvers 02 rawout 02 badsrcintf 02 fragoverflow END. type type type type type type type type type binary binary binary binary binary binary binary binary binary 32. 32. 32. 32. 32. 32. 32. 32. 32. DEF ZIP6State. 02 ztotal type binary 16. 02 Word type binary 16 redefines ztotal. 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 wild-card END. type binary 16. DEF ZQIO6Data. 02 data-mds type binary 32. 02 Word type binary 16 redefines data-mds. 02 max-data-mds type binary 32. 02 dup-mds type binary 32. 02 max-dup-mds type binary 32. 02 no-data-mds type binary 32. 02 no-dup-mds type binary 32. 02 res-recov-run type binary 32. 02 qio-limit-warns type binary 32. 02 qio-driver-errs type binary 32. 02 curr-pool-space type binary 32. 02 max-pool-space type binary 32. 02 pool-fails type binary 32. 02 total-mbufs type binary 32.
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 size-57344 02 qio-so-ip 02 so-forced-close 02 qio-so-que-fulls 02 mdcopy-adj 02 outhdr-adj 02 outdata-adj END.
DEF ZIGMP6Data. 02 rcv-total type binary 32. 02 Word type binary 16 redefines rcv-total. 02 rcv-tooshort type binary 32. 02 rcv-badsum type binary 32. 02 rcv-queries type binary 32. 02 rcv-badqueries type binary 32. 02 rcv-report type binary 32. 02 rcv-badreports type binary 32. 02 rcv-ourreports type binary 32. 02 snd-reports type binary 32. END. DEF ZIGMP6State. 02 rcv-total type binary 16. 02 Word type binary 16 redefines rcv-total. 02 rcv-tooshort type binary 16. 02 rcv-badsum type binary 16.
02 Word type binary 16 redefines allmons-sent. 02 somemons-sent type binary 32. 02 allbutme-sent type binary 32. 02 dpas-rcvd type binary 32. 02 migr-rcvd type binary 32. 02 loopbk-rcvd type binary 32. 02 ipfrag-rcvd type binary 32. 02 unk-rcvd type binary 32. 02 bad-frmt-rcvd type binary 32. END. DEF ZMONGQ6State. 02 allmons-sent type binary 16. 02 Word type binary 16 redefines allmons-sent. 02 somemons-sent type binary 16. 02 allbutme-sent type binary 16. 02 dpas-rcvd type binary 16.
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 rx-total type binary 32. Word type binary 16 redefines rx-total. rx-idle-discards type binary 32. rx-toosmall type binary 32. rx-tooshort type binary 32. rx-badvers type binary 32. rx-errors type binary 32. rx-local type binary 32. rx-nonlocal type binary 32. rx-multicast type binary 32. rx-badaligns type binary 32.
02 fwd-eother 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 02 02 02 02 type binary 32. ZIP66State. rx-total type binary 16. Word type binary 16 redefines rx-total. rx-idle-discards type binary 16. rx-toosmall type binary 16. rx-tooshort type binary 16. rx-badvers type binary 16. rx-errors type binary 16. rx-local type binary 16. rx-nonlocal type binary 16. rx-multicast type binary 16.
02 fwd-baddst 02 fwd-badsrc 02 fwd-enobufs 02 fwd-emsgsize 02 fwd-eother END. type type type type type binary binary binary binary binary 16. 16. 16. 16. 16. DEF ZICMP66Data. 02 tx-error type binary 32. 02 Word type binary 16 redefines tx-error. 02 tx-error-drops type binary 32. 02 tx-nobufs type binary 32. 02 tx-rlimit-drops type binary 32. 02 rx-total type binary 32. 02 rx-info type binary 32. 02 rx-error type binary 32. 02 rx-tooshort type binary 32. 02 rx-checksum type binary 32.
DEF ZICMP66State. 02 tx-error type binary 16. 02 Word type binary 16 redefines tx-error. 02 tx-error-drops type binary 16. 02 tx-nobufs type binary 16. 02 tx-rlimit-drops type binary 16. 02 rx-total type binary 16. 02 rx-info type binary 16. 02 rx-error type binary 16. 02 rx-tooshort type binary 16. 02 rx-checksum type binary 16. 02 rx-notifications type binary 16. 02 rx-torawip6 type binary 16. 02 rcv-queries type binary 16. 02 rcv-badqueries type binary 16. 02 rcv-reports type binary 16.
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 END.
02 udp-filters-err 02 udp-filters-dereg 02 port-filters-drop 02 data-drop 02 subnet-abort 02 subnet-reset 02 subnet-last-err 02 media-lost END. DEF zSubnet6State.
DEF ZROUTE6Data. 02 zref-cnt 02 word 02 zsubnet-name 02 zallroute 02 zsa-family 02 zradix-type 02 zusage END. type type type type type type type binary 32. binary 16 redefines zref-cnt. character 8. character 4. character 6. character 6. binary 32. DEF ZROUTE6State. 02 zref-cnt 02 word 02 zsubnet-name 02 zallroute 02 zsa-family 02 zradix-type 02 zusage END. type type type type type type type binary binary binary binary binary binary binary 16. 16 redefines zref-cnt. 16. 16. 16. 16. 16.
02 02 02 02 02 02 02 02 02 END. zsend zrecv family zloc-addr6 zloc-word zloc-filler zforgn-addr6 zforgn-word zforgn-filler type type type type type type type type type binary binary binary binary binary binary binary binary binary 16. 16. 16. 64. 16 redefines zloc-addr6. 64. 64. 16 redefines zforgn-addr6. 64. DEF ZPORT6State.
TCPIP TELNET Entity Description ASAP 2.8 * This defines the structure written to ASAPCOL by the TCPIP SGP DEF ZTelnetData. 02 zin-conn 02 Word 02 ztotal-open 02 ztotal-net-data 02 zavg-actv-term 02 ztotal-spi-req 02 ztotal-user-data 02 ztotal-net-req 02 ztotal-user-req END. type type type type type type type type type binary binary binary binary binary binary binary binary binary 32. 16 redefines zin-conn. 32. 32. 32. 32. 32. 32. 32. DEF ZTelnetState.
02 02 02 02 02 02 02 02 02 02 02 02 02 END. zprim-cpu zprim-pin zprim-fnum zbkup-cpu zbkup-pin zbkup-fnum zproto zlport zloc-addr zfport zforgn-addr zsend zrecv DEF ZPortState. 02 zprocname 02 Word 02 Caid 02 Paid 02 objectfile 02 zprim-cpu 02 zprim-pin 02 zprim-fnum 02 zbkup-cpu 02 zbkup-pin 02 zbkup-fnum 02 zproto 02 zlport 02 zloc-addr 02 zfport 02 zforgn-addr 02 zsend 02 zrecv END.
* This defines the structure written to ASAPCOL by the TCPIP SGP DEF ZWindowData.
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. 02 Active type binary 16. END. DEFINITION WINDOW-Stats1. !Description.............Sect 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.
02 02 02 02 02 02 02 END. OpText Status OpState Error ErrorState Data State type type type type type type type binary 16 occurs 4 times. ! character 1 redefines OpText. binary 16. ! binary 64. ! binary 16. ! ZServiceData. ! ZServiceState. ! Op state text Operational state Error (if any) Error state (or remove) SERVICE data SERVICE states TMF Entity Statistics Definitions DEFINITION TMF-STATS.
02 END. Spare4 type binary 16. DDL Section Record Declarations ASAP Database Record Declarations RECORD File RECORD File RECORD File RECORD File RECORD File RECORD File RECORD File RECORD File RECORD File RECORD File RECORD File RECORD File RECORD File RECORD File RECORD File RECORD File RECORD File CPU. is DBCPU. SYS. is DBSYS. NET. is DBEXP. PCB. is DBPCB. NCP. is DBNCP. DSK. is DBDSK. APP. is DBAPP. RDF. is DBRDF. FIL. is DBFIL. SPL. is DBSPL. TAP. is DBTAP. TMF. is DBTMF. PRO. is DBPRO. COM.
File RECORD File RECORD File RECORD File RECORD File RECORD File RECORD File RECORD File RECORD File RECORD File RECORD File RECORD File RECORD File RECORD File RECORD File is $EXPDB. PCB-SRV. is $PCBDB. NCP-SRV. is $NCPDB. DSK-SRV. is $DSKDB. APP-SRV. is $APPDB. RDF-SRV. is $RDFDB. FIL-SRV. is $FILDB. SPL-SRV. is $SPLDB. TAP-SRV. is $TAPDB. TMF-SRV. is $TMFDB. PRO-SRV. is $PRODB. COM-SRV. is $COMDB. TCP-SRV. is $TCPDB. SWP-SRV. is $SWPDB. CIP-SRV. is $CIPDB. Def is net-stats. Sequence is Q-key. End.
Appendix C: ASAP CI DOTs Warning Messages The ASAP Command Interperter will return warning messages in response to certain conditions it finds while processing Discrete Objective Thresholds (DOTs) settings, starting ASAP, or processing DOTs commands. This appendix describes those warning messages. Actions enabled but Action Server is not started as SUPER.SUPER. Cause The Action server is enabled (SET ACTION ON) but ASAP is not running as SUPER.SUPER. Effect There might be actions that ASAP cannot perform.
The ASAP version on node is newer than this version. Please upgrade all systems to the most current ASAP version. Please enter HELP VERSIONS for more information on versioning. Cause The ASAP version on the specified remote node is newer than the version on this node. Effect It is possible to run mixed versions of ASAP but the central collector node should always be the most current version. If it is not then ASAP might not be collecting data from the remote nodes.
The Objectives database on node is newer than this ASAP version. Objectives databases need to be a consistent version. Please enter HELP VERSIONS and HELP CONVERT for more information. Cause The objectives database on the specified node was created by an newer version of ASAP. Effect The ASAP command interpreter on the current node will not be able to write to that database, and might not be able to read from the database if EDL changed in the newer version.
ASAP will auto-configure entity domains on node. Cause The are no monitored objects for the specified entity on the specified node. Effect ASAP will auto-configure domains for that entity, based on its auto-configuration rules. Recovery This might not be a problem. See MONITOR Usage Considerations for more information on auto-configuration. ASAP will auto-configure all domains on node. Cause There are no monitored objects specified for any entity on the specified node.
ASAP will not auto-configure entity domains on node. Cause There is at least one monitored object specified for the entity so ASAP will not autoconfigure domains for that entity. Effect ASAP will only monitor domains that you specify for the entity. Recovery This might not be a problem. See MONITOR Usage Considerations for more information on auto-configuration. No entity domains will be monitored on node.
Use COMMIT to place database changes into production use. Cause A change has been made to the ASAP objectives database by adding, deleting or modifying a monitored object or goal. Effect The ASAP database has been updated but a running copy of ASAP has not loaded the changes. Recovery Enter the COMMIT command to place the database changes into production use. Entity entity is not currently defined in EDL. Cause A entity defined in the ASAP database no longer exists in the current EDL.
Domains must be added to the database before using On/Off Cause An attempt was made to turn monitoring off or on for an object before using the add option to actually add the monitored object to the database. Effect No operation is performed on the object. Recovery Add the object using the MONITOR command. The current Objectives DB setting does not match the Objectives DB in use by the running copy of ASAP on node.
Please set ObjectivesEventState to LOW, MEDIUM or HIGH when using escalating or de-escalating goals Cause An escalating or de-escalating goal was entered but the setting for SET OBJECTIVESEVENTSTATE is higher than the HIGH state. Effect EMS events and/or actions created by escalating or de-escalating goals might not be emitted. Recovery Change the setting for OBJECTIVESEVENTSTATE to LOW, MEDIUM or HIGH.
