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.0 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.
Table of Contents HP NonStop ASAP Server Manual ...................................................................................... 1 Abstract ........................................................................................................................... 1 Product Version ............................................................................................................... 1 Supported Release Version Updates (RVUs)..................................................................
File Statistics Gathering Process ................................................................................... 41 Node Statistics Gathering Process ................................................................................ 41 Process Statistics Gathering Process............................................................................ 41 RDF Statistics Gathering Process ................................................................................. 41 Spooler Statistics Gathering Process ..
DOTs Overview................................................................................................................. 84 Specifying Domains and Objectives .............................................................................. 86 The Objectives Database .............................................................................................. 87 MONITOR Usage Considerations .....................................................................................
Considerations............................................................................................................. 132 ACTION Command ......................................................................................................... 133 APP Command ............................................................................................................... 135 Examples.....................................................................................................................
PROCESSBUSY Command ........................................................................................... 206 PROCESSBUSY Statistics .......................................................................................... 209 Examples..................................................................................................................... 210 RANK Command............................................................................................................. 211 Considerations........
OBJECTIVESEVENTSUBJECT .................................................................................. 244 OBJECTIVESEVENTSTATE ....................................................................................... 244 OBJECTIVESEVENTMAX .......................................................................................... 245 OBJECTIVESRANK .................................................................................................... 245 OBJMONITOR.............................................
SYSTEM Command ........................................................................................................ 286 Example ...................................................................................................................... 286 TAPE Command ............................................................................................................. 286 Consideration ..............................................................................................................
List of Figures and Tables Figure 1-1. ASAP Components .......................................................................................... 36 Figure 2-1. ASPSETUP Main Menu, AsapInstall ................................................................ 47 Figure 2-2. Installation Configuration for Full Install on This Node ..................................... 48 Figure 2-3. Input Help for the ASAP Install subvolume Field .............................................. 48 Figure 2-4.
What’s New in This Manual New and Changed Information The ASAP 3.0 version of this manual contains these changes: The TCP/IP and Telserv entities have undergone major revisions. For more information, see the following sections: TCP/IP Statistics Gathering Process TCP/IP and Telserv Entities- Supported Objective Attributes TCP Command TCP/IP Statistics Definitions A new Swap SGP is being introduced in this release. The Swap SGP collects availability and performance information about the KMSF subsystem.
The SET EVENTS option and its related settings for SET CPU, SET DISK and SET LH have been removed. The FORMAT command and its references have been removed. Previous Changes The seventh edition (ASAP 2.8 version) of this manual contains these changes: A new TCP command was added. For more information, see the following sections: TCP/IP Statistics Gathering Process TCP/IP and Telserv Entities- Supported Objective Attributes TCP Command TCP/IP Statistics Definitions A new Query command was added.
A SET ACTION option allows you to configure ASAP to take actions when userdefined goals are not met. For more information, see the Goal, Rank and SET ACTION commands. 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 DB command displays detailed information about disk space utilization for ASAP database files when the SET DBMAXDAYS option is enabled.
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 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. Updated Process Statistics Gathering Process.
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.
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.
OBJECTIVESRANK PARTITION PROCESS SPOOLER TAPE TMF For File, Process, RDF, Spooler, Tape, TMF entities: Added statistics definitions in DDL Definitions section Updated DDL Definitions HP NonStop ASAP Server Manual Page 18 of 342
About This Manual This manual describes these Availability Statistics and Performance (ASAP) products: The ASAP Server monitors, gathers, and analyzes system availability throughout a network of NonStop servers. System Entities are CPU, Comm, Disk, Expand, File, Hybrid1, Node, Process, Processbusy, RDF, Spooler, Swap, System, Tape, TCP/IP, Telserv2, and TMF. The ASAP Extension provides an Application Programmer Interface (API) so you can monitor the availability and performance of your application domains.
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.
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.c italic computer type Italic computer type letters within text indicate C and Open System Services (OSS) variable items that you supply. Items not enclosed in brackets are required. For example: pathname [ ] Brackets Brackets enclose optional syntax items.
| Vertical Line A vertical line separates alternatives in a horizontal list that is enclosed in brackets or braces. For example: INSPECT { OFF | ON | SAVEABEND } … Ellipsis An ellipsis immediately following a pair of brackets or braces indicates that you can repeat the enclosed sequence of syntax items any number of times.
Line Spacing If the syntax of a command is too long to fit on a single line, each continuation line is indented three spaces and is separated from the preceding line by a blank line. This spacing distinguishes items in a continuation line from items in a vertical list of selections.
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. For example: ENTER RUN CODE ?123 CODE RECEIVED: 123.00 The user must press the Return key after typing the input. Nonitalic text Nonitalic letters, numbers, and punctuation indicate text that is displayed or returned exactly as shown. For example: Backup Up.
{ } 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. For example: obj-type obj-name state changed to state, caused by { Object | Operator | Service } process-name State changed from old-objstate to objstate { Operator Request. } { Unknown.
lowercase letters Words in lowercase letters are words that are part of the notation, including Data Definition Language (DDL) keywords. For example: token-type !r The !r notation following a token or field name indicates that the token or field is required. For example: ZCOM-TKN-OBJNAME token-type ZSPI-TYP-STRING. !r !o The !o notation following a token or field name indicates that the token or field is optional. For example: ZSPI-TKN-MANAGER HP NonStop ASAP Server Manual token-type ZSPI-TYP-FNAME32.
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 attributes, which
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 Management (OEM) Gateway Reporting of
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, 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 History Provides network-wide performance an
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 operators >, <, =, <>, <=, and >= on
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 name Data sent to and objectives ap
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. Communication line availability for AM3270, ATP6100, Envoy, EnvoyACP, Multilan, Snax, and X.25 such as percent line busy, Input/Output bytes read and written InputData/OutputData bytes read and received, and Retries, state of the line are reported by the COMM SGP.
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.. System availability information, such as percent system busy, queue lengths, and memory swap rates. Tape availability information, such as mounts, tape status, and tape label.
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.
performance counters. The COMM SGP reports on objective thresholds that exceed the user-defined values maintained in the objectives database. The COMM SGP gathers availability information, bundles it in a single message, and forwards it to the ASAP Collector process. The Collector process unpacks the information and stores it in the normalized ASAP database so the ASAP COMM command or ASAP client can retrieve it.
File Statistics Gathering Process File SGPs collect file availability information. You define which files or subvolumes the File SGP monitors. File availability information is obtained using the Guardian API. The File SGP reports on objective thresholds when they do not meet the user-defined values. File monitoring in ASAP 2.
information and stores it in the normalized ASAP database so the ASAP SPOOLER command or ASAP Client can retrieve it. SWAP Statistics Gathering Process Swap SGPs collect KMSF availability information. Swap availability information is obtained from the NSKCOM interface using the Seeview Server Gateway. The availability information gathered is performance utilization and operational state. The Swap 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 Collect process unpacks the information and stores it in the normalized ASAP database so the ASAP TMF command or ASAP Client can retrieve it. CSG TheClient Server Gateway works with the SeeView Server Gateway to provide a bridge between programs running on Windows NT, Windows 95, or Windows98 systems and programs running on NonStop OS systems.
Section 2: Installing ASAP on the Server Topic Task 1: Ensure Your System Meets Requirements Task 2: Installing ASAP Server Product Files Tase 3: Set Up ASAP Server Task 4: Configure ASAP Components Starting and Stopping ASAP 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.
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. The following figure shows the result of pressing Shift-Return with the cursor on the ASAP Install subvolume field. ASPSETUP displays default values in uppercase when it displays the configuration panel.
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. The following figure shows a sample first page of output when you start a full installation. Figure 2-4.
Creates Configuration files, including an installation OBEY file. Shuts down the existing ASAP system if it is running. Starts the installation process. 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 Full Install completes, ASPSETUP displays output similar to the following figure. Figure 2-5.
Note To use context-sensitive help, put the cursor in the Remote Monitor Install field and press Shift-Return. The following figure displays the ASAP context-sensitive help text for the Remote Monitor Install menu item. 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.
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. Enter the ASAP installation location in the ASAP Install subvolume field. 3. Optionally, enter the ASAP Extension subvolume in the ASAPX Install subvolume field. 4. Enter a network user ID. 5.
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. ASPSETUP shuts down the remote monitors on the selected nodes, creates an installation OBEY file, and starts the remote installation process (see the following figure).
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.
\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.SYSTEM Do you want to build the ASAP configuration for that ASAP version(Y)?y Please enter a subvolume for the ASAP database($SYSTEM.ZASAP):$asap.testdb *** There are files in the subvolume you specified $ASAP.
Do you want ASAP to automatically retain data for a number of days(Y)?y What is the default number of days you would like to retain(7)? Would you like to specify the number of days to save per entity(Y)?n If this instance of ASAP will be used to monitor multiple nodes, then it is important to synchronize time across all nodes in the collection. Would you like ASAP to synchronize time on the nodes(N):y ASAP can automatically enter actions against objects to recover from failure conditions.
You may now run ASAP CI and enter MONITOR FILE and MONITOR PROCESS commands to configure the files and processes that ASAP will monitor. The ASAP Wizard has successfully completed. 2> ASAP Object Files The ASAP system consists of these files on $SYSTEM.SYSTEM: Object File Description ASAP Full Name ASAP Conversational Interface ASAPCMM COMM Statistics Gathering process Gathers availability information for every monitored SWAN line on the node.
monitored tape device on the node. ASAPTCP Process (SGP) TCP Statistics Gathering Process (SGP) ASAPTMF TMF Statistics Gathering Process (SGP) Gathers availability information for the TMF subsystem on the node. ASAPXSGP ASAP Statistics Gathering Process (SGP) Gathers service-level metrics about customer applications. It is an optional product, part of the ASAP Extension product (ASAPX). Gathers availability and statistics information for nine TCP/IP entities and three Telserv entities.
configure database history to only retain data since the last cleanup time; for example, every night at midnight. Or you can configure it to retain ASAP history for a longer period of time, or indefinitely. The ASAP Collect process is continuous. If a CPU fails, the backup Collect process automatically takes over so database access is always available. The ASAP database is a real-time normalized database and can be queried online.
ASAPFIL Object File The ASAP Monitor starts the File SGP on its node if File is enabled. The ASAP Statistics Gathering (ASAPFIL) Process collects availability information for userselected files or subvolumes. The utilization counters gathered include percent file full, number of files in the subvolume, and number of partitions.
to-end node statistics. The statistics gathered are path information statistics and traffic statistics between two Expand nodes. ASAPNCP communicates directly with the Expand Manager process to obtain raw counters. The Node SGP does not support monitoring or Discrete Objectives Thresholds (DOTs). ASAPPRO Object File The ASAP Monitor starts the Process SGP on its node if Process is enabled. The ASAP Statistics Gathering (ASAPPRO) Process collects availability information for the user-selected processes.
about the tape devices and tape mount requests on the node. The utilization counters gathered include number of outstanding tape mounts and Label mode checks. ASAPTCP Object File The optional ASAP TCP/IP Plug-in Statistics Gathering (ASAPTCP) process collects availability information for nine separate TCP/IP entities and three Telserv entities, including availability, usage, performance, and connection information. The ASAP Monitor starts the optional TCP SGP on its node if TCP is enabled.
The ASAPX Library The optional ASAPX Library is made of four object files: Object File ASAPXDLL Description A dynamic link library (DLL) containing the ASAPX API procedures ASAPXLIB A TNS user-library containing the ASAPX API procedures ASAPXSRL A private Shared Runtime Library containing the ASAPX API procedures ASAPXSRO A native linkable object for binding the native API into an existing private Shared Runtime Library Installation Installed by the ASAPX installation process.
The Database subvol Install only option looks identical to the Full Install on this Node option, but it only creates the database subvolume location and compiles the database DDL.
TelservWindow * = TMFs Rate = = Total number of monitored and active Telserv services on all nodes. Total TMF systems monitored on all nodes. Sample interval (in minutes).
2 minutes for a 25 node network with 4 CPUs per node 3 minutes for a 50 node network with 2 CPUs per node 5 minutes for a 100 node network with 4 CPUs per node 10 minutes for a 100 node network with 8 CPUs per node Starting and Stopping ASAP This subsection explains how to stop and start the ASAP Environment. For frequent use, you can put these commands in OBEY files. Starting ASAP 1. Start ASAP by entering ASAP at a TACL prompt: TACL 1 > ASAP ASAP - Availability Stats and Performance - T0402V02.
LogInterval............. LogSuppress............. MonitorAdd.............. NodeDownAlert........... Objcollect.............. Objmonitor.............. ObjectivesAudit......... ObjectivesDB............ ObjectivesEvent........ ObjectivesEventConsole. ObjectivesEventConsoleUp ObjectivesEventMax...... ObjectivesEventSubject. ObjectivesEventState.... ObjectivesEventUp...... ObjectivesRank......... Primary................. Priority................ ProcessBusy............. Rate.................... RemoteSecurity...
CPU................... SPOOLER..........ON Object................ Parameters............ CPU................... SWAP.............ON Object................ Parameters............ CPU................... TAPE.............ON Object................ Parameters............ CPU................... TCP..............ON Object................ Parameters............ CPU................... TMF..............ON Object................ Parameters............ CPU................... 0 $SYSTEM.SYSTEM.ASAPSPL 0 $SYSTEM.SYSTEM.
+STATUS \NY !Status of the Monitor in New York +STATUS !Status of the local node Stopping ASAP To stop the Collector or Monitor processes: 1. Use the ASAP SHUTDOWN command. 2. After using the SET command on nodes currently executing the Collector or Monitor processes, stop and restart the processes so that the configuration changes take effect.
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. and 12:30 a.m.: +set db $data.asapdb.
+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 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.
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.ASAPXCNF” +SET EXPAND ON +SET RATE 5 +STARTUP \NY +SET APP OFF +STARTUP \LA Getting Collector and Monitor Status Information The ASAP STATUS command obtains the status of the Collector or Monitor processes.
Table 3-1.
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. The SGPs get the list of domains they should monitor from the Objectives Database. Each SGP configures some domains by default when no entity records are found in the Objectives Database. For more information, see MONITOR Usage Considerations.
+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. The Monitor also shuts down all executing SGPs in each CPU.
ASAP’s clock synchronization algorithm makes instantaneous time changes if the time difference between the central Collect node and the Remote node is greater than two minutes, and uses slow synchronization only if the time difference between the Central node and the Remote node is less than two minutes. To avoid sudden time changes on the Remote nodes, set the ASAP SET command option SET SYNCSLOW ON | OFF to ON to slowly synchronize the time of day between selected nodes.
SET RATE 15 SET DISK ON SET ID $CHI !define sample interval !Enable disk reporting !ID for first process set START \CHICAGO COLLECT START \* !Start collector on \Chicago !Start monitors & SGPs on all nodes in the network Example B Example B defines a second set of processes that report statistics for a selected regional group of nodes to the LA node: SET SET SET SET SET COLLECT \LA DB $DATA2.ASAPDB.
F, it is a standard SGP. In the previous example, H represents the optional APP SGP, H1 represents the ASAPX Monitor, J represents the Disk SGP, and Parms can be Guardian errors or other ASAP error numbers. Report these messages when submitting problem reports against ASAP.
RANK RDF SET SHOW SHUTDOWN SPOOLER STARTUP STATUS SWAP SYNC SYSTEM TAPE TCP TMF VOLUME ! Controls the objectives ASAP uses to produce alerts. Reports on Remote Database Facility (RDF) stats. Displays and/or alters option settings. Displays Entity information. Stops COLLECT and/or MONITOR in specified nodes. Reports on Spooler stats. Starts COLLECT and/or MONITOR in specified nodes. Status COLLECT or MONITOR or ACTION server. Reports on KMSF stats. Manually requests MONITOR to sync specified nodes.
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.
<#D4> 4th part of a multilevel domain name <#D5> 5th part of a multilevel domain name <#ATTR> The attribute name <#OP> The objective operator <#STATE> The current state of the attribute <#LASTSTATE> The last state of the attribute <#VALUE> The value of the attribute <#GOAL> The objective value Action strings can also be stored as predefined rules by using the ASAP CI ACTION command.
States can also indicate utilization such as low, medium, and high. ASAP displays ranked alert states in the ASAP Client, the EMS subsystem, or both. To enable ranked property alerts in the ASAP Client, set State Determination to UseStateGraphState for each ranked property in the ASAP Client Attribute Property sheet. For more information, see the ASAP Client Manual. To enable ranked property events in EMS, SET OBJECTIVESEVENT ON from the ASAP command interpreter before starting ASAP Server components.
PROCESS PROCESS BUSY domains 0-15 RDF SPOOLER SWAP SYSTEM TAPE TCPICMP (Optional) TCPIP (Optional) TCPPort (Optional) TCPProcess (Optional) TCPQIO (Optional) TCPRoute (Optional) TCPRTE (Optional) TCPSubnet (Optional) TCPUDP (Optional) TelservProcess (Optional) TelservService (Optional) TelservWindow (Optional) TMF Once the monitored entities are loaded in the database, you can set individual userdefined objectives against entity domains by using the GOAL or RANK commands.
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. For example, a BUSY attribute for the CPU entity could have BUSY < 50 and BUSY > 10, meaning the interval value reported for the attribute must be greater than 10 and less than 50. The commands for configuring this objective threshold are the GOAL and RANK commands. GOAL CPU, BUSY > 10, BUSY < 50.
$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. Use the Expand entity for setting monitoring of any Expand line.
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. They are written to EMS and the ASAPLOG log file, and are subject to event suppression if turned on within ASAP.
To turn on down and up events for warnings and higher alerts, allowing two events per domain per interval, put these event commands in your ASAPCONF file: SET ObjectivesEvent ON SET ObjectivesEventUp ON SET ObjectivesEventMax 2 SET ObjectivesEventState Warning To create an informative EMS event when process $Abc is not executing in CPU 1: RANK PROCESS $ABC, CPU = 1 INFO Status Change Events ASAP DOTs automatically generates EMS events for Status changes in ASAP system entities when events are turned on.
RANK PROCESS $DEF, STATUS NOEMS By default, ASAP user-defined entities do not generate EMS events for Status changes. Because a single process can register hundreds of user domains with ASAP, failure of that process could generate hundreds of EMS messages. User-defined entities are created to describe your applications that use the ASAP Extension to register with ASAP.
File Nodename Sysnum Domain Op Date Time Valid Error Errorstate Full Fullstate Eof Eofstate Owner Ownerstate Rwep Rwepstate Open Openstate Tmf Tmfstate Files Filesstate Code Format Type Partitions Lastopen Lastmodif An attribute defined with StatePair YES in the EDL definition is immediately followed by its associated state attribute. For example, ErrorState is the associated state for the Error attribute. When StatePair is true, you can set objectives on the attribute.
Requests IO Requests per second Integer32 Busy Percent time line busy reading and writing Integer ReadBusy Percent Time Line Busy Reading Integer WriteBusy Percent Time Line Busy Writing Integer InKB Kilobytes read per second Integer64 OutKB Kilobytes written per second Integer64 InDataKB Data kilobytes read per second Integer64 OutDataKB Data kilobytes written per second Integer64 Rate Total of reads, writes per second Integer64 Reads Number of read operations per second Intege
MemLockMax Maximum memory that can be locked in physical memory Integer32 MemLockHigh Highest amount of locked memory since CPU was loaded Integer32 DISK Entity-Supported Objective Attributes Attribute Description Value P* Primary disk path in use, value = P or B Char 1 wide M ** Mirror disk path in use, value = P or B Char 1 wide CPU Primary CPU number of the Disk process for this volume Integer FULL Percentage of disk space currently used Integer REQUESTS Number of disk I/O requests
POOL Percent utilization of Expand line handler I/O pool Integer PFAIL Number of pool failures during the sample interval Integer32 NoBuf Number of no buffer failures Integer32 BCC Number of BCC errors during the sample interval Integer32 NakSnt Number of Level-4 negative acks sent Integer32 NakRvd Number of Level-4 negative acks received Integer32 PktSnt Number of Level-4 packets sent Integer32 PktRvd Number of Level-4 packets received Integer32 PThruSnt Number of Level-4 PassThru
FILE Entity-Supported Objective Attributes Attribute Description Value Error Error number indicating status of data Integer64 Full Percentage full Integer Eof Size in bytes Integer64 Owner Group, User Character 7 wide RWEP Read, Write, Execute, Purge security (Safe = Safeguard) Character 4 wide Open Yes = Open; No = Not open Character 3 wide TMF Yes = Audited by TMF; No = Not audited Character 3 wide Files Number of files in subvolume Integer32 Permissio n OSS permissions string
Attribute Value Error Description Collection error Cpu Process primary CPU Integer Pri Primary process priority Integer BCpu Process backup CPU Integer Busy Process Busy Integer64 (implied decimal) PState Character 8 wide WState Unalloc, Start, Run, Suspnd, Dbg brk, Dbg trap, Dbg req, Insp Lsig/Lpipe(status), Pon(cpu pwr), Iopon (I/O pwr), Intr MPages Memory pages in use Integer64 (implied decimal) MSent * Messages sent per second Integer64 (implied decimal) MRecvd * Messages rece
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 process Integer NumJobs Number of jobs defined for this entity Integer32 BatchJobs Number of batch jobs defined for this entity
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 during the sample interval Integer32 Allocates Successful allocations made in the swap files during the sample interval Integer32 AllocateFails Failed allocations in the swap files during the sample interval Integer32 FreesOk Succe
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 outstanding for this tape drive or node Integer MountTime Amount of time since MountReq > 0 Integer TapeStatus Status of the tape currently loaded in the tape drive Character 8 wide TapeLabel Label type of the t
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 Unreachable messages output Integer32 OutSrcQnch Number of Source Quench messages output Integer32 OutRedirect Number of Redirect messages output Integer
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 BadRapSubcode Number of IRDP messages with bad ICMP subcodes Integer32 BadAddrlst Number of IRDP messages with a bad address list Integer32 BadWpa Number of IRDP messages with an incorrect address length Integer32 RdiscNrecorded Number of v
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 Integer32 InNdNborSol Neighbor solicitation packets received Integer32 InNdNborAdv Neighbor advertisement packets received Integer32 InNdRdirect Redirect packets received Integer32 OutDstUnrech Destination unreachable messages s
address not equal to the all hosts group RcvReport Number of IGMP membership reports received Integer32 RcvBadReports Number of bad membership reports received Integer32 RcvOurReports Number of IGMP membership reports received for groups we belong too Integer32 SndReports Number of IGMP membership reports sent Integer32 ENTITY TcpIp Internet Protocol Error Collection Error Integer64 Total Total number of input packets received Interger32 BadXsum Packets with bad checksum Integer32 Too
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 of an IPv6 header Interger32 RxTooShort Packets with lengths shorter than specified in their header Interger32 RxBadVers Version number not equal to 6 Interger32 RxErrors Received packets resulting in the sending of an ICMPv6 error message Interger32 RxL
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 of fragments built Interger32 FragNoFragPart Fragment not found Interger32 FragBadHopByHop Packets with hop by hop header not after IPv6 header Interger32 FragUfpBadAlign Packets with unfragmented part not quad word aligned Interger32 FragUfpTooBig Transmit
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 Interger32 UpdateSent Update port sent Interger32 UpdateRcvd Update port sent Interger
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 of socket Integer16 RecvQ Bytes in receive queue of socket Integer16 Family Protocol family Integer16 ZLocAddr6 Local TCP/IP v6 address IPADDR6 ZForgnAddr6 Foreign TCP/I
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 packets sent Integer32 SndPack Data packets sent Integer32 SndByte Data bytes sent Integer32 SndRexmitPack Data packets retransmitted Integer32 SndRexmitByte Data bytes retransmitted Integer32 SndRexmit
RcvAfterWinByte Bytes received after window Integer32 RcvAfterClose Packets received after close Integer32 RcvWinProbe Window probe packets received Integer32 RcvDupAck Duplicate ACKs received Integer32 RcvAckTooMuch Received ACKs for unsent data Integer32 RcvAckPack ACK packets received Integer32 RcvAckByte Bytes ACKed by received ACKs Integer32 RcvWinUpdate Window update packets received Integer32 PawsDrop Segments dropped due to PAWS Integer32 PredictAcks Times header predict
use by the process not assigned to inbound driver MDs MaxDupMds Maximum number of duplicate message descriptors (MDs) that have been in use not assigned to inbound driver MDs Integer32 NoDataMds Number of times the process failed to get a data message descriptor (MD) Integer32 NoDupMds Number of times the process failed to get a duplicate message descriptor (MD) Integer32 ResRecovRun Number of times the send or receive queue on a TCP session exceeded the limit of MDs queued Integer32 QioLimitWar
bytes Size16384 Count of socket sends between 12289 and 16384 bytes Integer32 Size32768 Count of socket sends between 16385 and 32768 bytes Integer32 Size57344 Count of socket sends greater than 32768 bytes Integer32 QioSoIp Number of SO IP allocations Integer32 SoForcedClose Number of SO force closes Integer32 QioSoQueFulls Number of SO queue fulls Integer32 MdcopyAdj Number of message descriptor (MD) copy adjustments Integer32 OuthdrAdj Number of message descriptor (MD) header adjust
Error Collection Error Integer64 BcastAllcpusSnt Broadcasts sent to all CPUs Integer32 BcastOnecpuSent Broadcasts sent to one CPU Integer32 BcastRcvd Broadcasts received Integer32 MigrSent Migration requests sent Integer32 MigrContSent Migration continuation requests sent Integer32 MigrRcvd Migration continuation received Integer32 MigrContRcvd Migration continuation requests received Integer32 MigrTimedout Migration timeouts Integer32 MigrUxpRcvd Unexpected migrations received
PrtFltDrp Port filters drop Integer32 DataDrop Data drops Integer32 SnetAbort Subnet abort Integer32 SnetReset Subnet reset Integer32 SnetLstErr Subnet last error Integer32 MdaLost Media lost Integer32 ENTITY TcpUdp User Datagram Protocol Error Collection Error Integer64 InPkts Total input packets Integer32 BadHdrLen Number of packets received with invalid header size specified Integer32 BadXsum Number of packets received with bad checksums Integer32 NoSum Number of packets
Userdata The number of bytes sent by the user to the network Integer32 Netreq The number of packets received from the network Integer32 Userreq The number of user requests Integer32 Error Collection Error Integer64 Wins The number of windows associated with a service Integer32 Sessions The number of connection attempts to the service Integer32 Aborts Number of connections aborted because client cannot be authenticated, did not have priviledges, or no login Integer32 Inuses The maximum
CAddr Caller's IP address IpAddr CPort Caller's Port Integer LAddr6 Local IP Address IpAddr6 FAddr6 Foreign IP Address IpAddr6 CAddr6 Caller's IP address IpAddr6 Openers Number of opens against the window Integer32 Processes Number of processes found running against the window Integer32 Active The number of processes that appear to be logged on and active Integer32 TMF Entity-Supported Objective Attributes Attribute Description Value Error Error number indicating status of data
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.
Modifying the Default Aggregation Settings Specifying Wildcard Names You can use the "*" and "?" wildcard characters to specify Guardian file or process names to monitor. Wildcards are not accepted at the volume name level of a filename. Wildcards are only permissible in the subvolume and filename portions. When wildcard names are specified, ASAP resolves the name at each interval to determine if the files or processes meet the criteria, and ASAP computes and creates a record for each object found.
Monitoring Processes from an Object File ASAP supports monitoring of all processes running from an object file. The object file can be a Guardian or OSS object filename. When object filenames are specified, ASAP resolves the name at each interval to determine the processes that are executing from that object file. ASAP computes and creates a record for each process found.
Monitoring Files and Processes Using OSS Pathnames OSS pathnames can be specified as domain names or separately using the PATH option to the MONITOR command when monitoring OSS files and processes. Because OSS pathnames can be longer and can contain more levels than ASAP domain names, ASAP truncates any OSS pathname specified as a domain name when the entire domain name exceeds 64 bytes or contains more than 5 levels.
Monitor Process Sales\Order\Entry\$A10 Monitor Process Sales\Order\Entry\$A11 Monitor Process Sales\Order\Fullfillment\$A12 Monitor Process Sales\Mfg\Build\Westcoast\$A13 Monitor Process Sales\Shipments\International\$A14 The rules for the logical domain names are: 1. The entire name must be between 2 through 64 bytes in length. 2. The name can contain up to five levels separated by a backslash. 3.
Setting Global Aggregates for All Domains An ASAPCONF parameter setting for File and Process, AGG, causes ASAP to automatically create aggregate records at each level of any hierarchical file or process name. If AGG is defined, you need not add aggregate domains to the database. ASAP creates them automatically.
aggregate record, so you can see the total consumption of processor resources across the group. However, it does not make sense to sum the values of the Pri attribute, which represents the priority of the processes. ASAP assumes you are interested in the process with the lowest priority, by default, so it uses the minimum Pri attribute value found among all processes in the group when creating the Pri value in the summary record.
SUM Sum the value across all members of the aggregate grouping AVG Average the value across all members of the aggregate grouping MIN Use the minimum value found in the aggregate grouping MAX Use the maximum value found in the aggregate grouping CNT Use a count of the number of values found in the aggregate group RUL Use the ASAP rule for PState and WState.
counted in the number of alerting domains shown in the Status text field. If you prefer a different alert level, you can change the state at which ASAP considers a process to be alerting. See the SET FILE and SET PROCESS options for the SET command. ASAP Alert Levels: 1 Exists 2 OK 3 Low Alert 4 Medium Alert 5 High Alert 6 Warning 7 Critical 8 Down The associated state for Status, OpState, is propagated from the worst state within the set like all other state attributes.
behavior can be turned on with the RUL aggregate control and results in this priority ranking of the possible values, from low to high: PState WState UnAlloc None Starting Lreq Runnable Lpipe DebugBrk Pon DebugTrp Iopon DebugReq Intr InspMBrk Lcan InspBrk Ldone InspTrp Ltmf InspReq Linsp SaveAben Stopping XIOInit As an example, when RUL is specified, a process in the Stopping process state is considered to be worse than a process in the Runnable process state, so the Stopping value is
Mpages SUM Msent SUM MRecv SUM QLen MAX MQLen MAX Pfaults SUM The Process Count attribute provides an automatic count of all domains in the group and is always one for a detail domain. The Process ACount attribute provides the number of attributes that are alerting when viewed in a detail process record and provides the number of domains that are alerting when viewed in an aggregate domain record.
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.
SET Displays or alters data collection and monitoring options SHOW Displays entity information SHUTDOWN Stops the Monitor, SGPs, and Collect servers on specified nodes SPOOLER Reports on Spooler statistics STARTUP Starts the Monitor, SGPs, and Collect servers on specified nodes STATUS Provides status information about the Monitor, SGPs, and Collect processes SWAP Reports on KMSF statistics SYNC Manually requests Monitor to synchronize time in the specified nodes SYSTEM Specifies a default s
ACTION Command The ACTION command is used to list action strings for a specific domain or domains and to define, delete and list rules, or stored action strings that can be used in RANK commands to define actions for failed objectives. ACTION[/OUT file/] [LIST] [\node][entity][domain][attribute [operator]] RULE [\node][rule][=string] |[, DELETE] LIST The LIST option is used to output information about all actions defined in the objectives database.
string An action string not enclosed in quotes, where the first word in the string represents the command interpreter the command should be sent to and the remainder of the string is the command to be sent to the CI. The string should be entered exactly as it will be sent to the command interpreter. Include any of the tokens below in the string, and ASAP will substitute actual names for the symbolic tokens.
ACTION CPU 0 BUSY GT gets action/wait for CPU 0 BUSY GT. Default Rules ASAP automatically loads several rules into its database of Action Rules when it creates it for the first time. These may be used in any GOAL or RANK command.
[, [, [, [, [, [ [.] domain ][, [, [, [, [, [, [, [, [, [, [, [, [, [, [, AGGONLY EXTRACT filename NOPRINT NOLINEBREAK NOAGG ] ] ] ] ] DETAIL ] SAMPLES count ] CPU ] STATES ] TIME hh[:mm [m/d/y]] AGGREGATE ] AGGREGATEONLY ] 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.
character (*), the default is used. The default is all of the Application domains in the current system. The entity name as defined in EDL must be the first part of a domain name, and must be supplied to show DETAIL statistics for any domain. For example, APP \*ATM, DETAIL shows detailed statistics for all ATM domains on all nodes. Note If you do not specify an entity name in an APP command, the default APP entity is used to display information.
High 5 Object utilization is high. Warning 6 Object is at Warning level. Critical 7 Object is at Critical level. Down 8 Object is down or not operational. 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. hh is the hour. mm is the minute. m/d/y is the month, day, and year.
AGGONLY is an abbreviation for the AGGREGATEONLY option. It can also be abbreviated as AO. MEMORY fetches APP data from memory instead of the database. The MEMORY option, in conjunction with MINSTATE and COUNT, should be used in the EDL DETAIL command for entities where SET AGGREGATE ONLY has been defined in ASAPXCNF. Note MEMORY does not work with SAMPLES, TIME, or \*. EXTRACT reads application records from the ASAP database and writes them to another file or process.
Atm\Guest\Chicago\$Jx00 Atm\Guest\Chicago\$Jx01 Atm\Guest\Chicago\$Jx20 Atm\Guest\Chicago\$Jx21 Up Up Up Up 5/10 5/10 5/10 5/10 16:56 16:56 16:56 16:56 17 17 17 17 0 0 0 0 +APP \CENTDIV MARKET \CENTDIV Domain\Name\Hierarchy Status Date Time Ct Error -------------------------------- --------------- ----- ----- -- ----Market\Commodities\Corn\Frozen Up 5/10 16:58 12 0 Market\Commodities\Corn\Futures Up 5/10 16:58 12 0 Market\Commodities\Porkbellies\Futures Up 5/10 16:58 12 0 Market\Commodities\Porkbellie
State"; AT Dateymd GRID NO GRAPH NO GRAPHMAX 0 HELP "Date of Stats"; AT Time GRID YES GRAPH YES GRAPHMAX 0 HELP "Time of Stats"; AT Valid GRID NO GRAPH NO GRAPHMAX 0 HELP "Validity Flag"; AT ET GRID NO GRAPH NO GRAPHMAX 0 HELP "Elapsed Time in Minutes"; AT CT GRID NO GRAPH NO GRAPHMAX 0 HELP "Count of Attributes"; AT Error GRID YES GRAPH NO GRAPHMAX 1 HELP "Collection Error" STATEPAIR YES STATERULE UseStateGraphState TypeData INT64 Format "I4"; AT ErrorState GRID NO GRAPH NO GRAPHMAX
TransRate ErrCount Busy State --------- -------- ----- ----0.3000 2 0.05 5 0.7500 4 0.12 1 0.3000 3 0.07 4 1.2000 8 0.20 4 \CENTDIV Domain\Name\Hierarchy Date Time Ver CpuPin Ct Error Nak UnAvail TransRate ErrCount Busy State --------------------------------------------------------------------------Accounts\Payable\$Tt29 2/25 12:43 A1 1,121 4 0 0 0.00 1.33 16 0.12 3 Accounts\Payable\$Tt30 2/25 12:43 A1 0,130 4 0 0 0.00 0.67 8 0.06 7 Accounts\Receive\$Tt31 2/25 12:43 A1 1,122 4 0 0 0.00 0.50 6 0.
This example illustrates writing comma-separated value (CSV) records to a preexisting entry-sequenced file named ATMCSV. Only aggregate ATM records are written to the CSV file, for 1000 samples. The TAB option replaces normal tab characters in the output with a comma. APP/OUT ATMCSV/ATM, DE, ST, AO,RAW, TAB ",", NOLINEBREAK, S1000 The next example illustrates the EDL DETAIL command for a user-defined ASAP entity where the entity is controlled by a SET AGGREGATE ONLY command in ASAPXCNF.
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. For an explanation of COMM performance statistics, type HELP COMMSTATS. For an alphabetical list, see the COMM Statistics table.
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. * specifies that the performance and state information for all communication lines on the specified system is displayed. If you do not specify a communication line or the wild-card character (*), statistics for all communication lines on the current system are displayed.
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.
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.xx NonStop OS displays the following: CTRL displays the controller address (in Octal) that the device was using. UNIT displays the unit number of the communication line.
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.
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. WRITE Number of writes per second. WRIT% Percent communication busy writing data.
[, [, [, [, [, [, [, [, [, [, 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. node specifies the individual system for which statistical information 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 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 physical memory size MemSwap Swappable memory Mem
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.
+CPU \SOLAR,MB \SOLAR Time -------- ----00 3/17 22:54 01 3/17 22:54 02 3/17 22:54 03 3/17 22:54 PageSz MemSize MemSwap MemLocked MemFree MemLckMax ------- --------- --------- --------- --------- --------16384 4295 4294 542 3597 3757 16384 4295 4294 533 3607 3757 16384 4295 4294 356 3868 3757 16384 4295 4294 354 3877 3757 In this example the output displays the enhanced memory statistics in megabytes.
Examples This example shows database file information including filename, open flag, last modification date and time, group and user ID, and read and write execute purge security vector information for CPU files: +DB CPU INFO DETAIL $HIT.ASAP2004.
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. If you want information for all the systems, specify DISK \*. If you do not specify a node or the wild-card character (*), the default is used.
Disk being revived, formatted, or mounted 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. AVG displays the largest statistical values for the entire volume. Only one line of output is displayed. This can be used in conjunction with the CPU, RATE, PERCENT, and QUEUE options.
GBUSED displays the total space used at the time of the sample in gigabytes. Max ExtMB displays the largest extent available for the volume. MB AVAIL displays the total space available at the time of the sample in megabytes. ADDR displays the controllers octal address that is controlling the disk device. Dseries only. UNIT displays the unit number of the disk device. D-series only. GRP displays the group number. G-series. MOD displays the module number. G-series. SLT displays the slot number. G-series.
-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.
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. NoCtr unable to obtain DP2 counters. Check the ASAP log for additional error messages. Performance statistics are unavailable. State information is available. NoMes unable to communicate with Measure subsystem. For more error messages, check the ASAP log. Performance statistics are unavailable.
RATE displays disk utilization in I/Os per second, including: rate per second, reads per seconds, writes per second, Chit, Queue length, and Swaps per second. GBUSED shows the number of gigabytes allocated. For a description of the performance statistics, see the DISK Statistics table. STATE shows all attributes that have an associated state. Associated states are displayed for the disk command without any options, and the disk command with these options: RATE, QUEUE, AVG, PERCENT (Default).
VQLN The disk volume semaphore queue length (exclusive and shared modes operation). VQ The maximum number of volume semaphore requests for the semaphore queue. WRITE Number of writes per second. WRITE% The percentage of time spent writing. TIME The time of the sample converted to database local civil time.
SUMMARY shows summary of entity and attribute names in EDL file. LIST shows listing of all statements in EDL file. DUMP lists and dumps each EDL control block; for debugging only. COMMENT prefixes compile info with -- comment characters (used by Client). SUPPRESS suppresses everything except errors in EDL file. Examples EDL $System.System.AsapSys2, LIST EDL $System.System.AsapSys2, SUMMARY EXIT Command The EXIT command stops the Conversational Interface.
FILE Command The FILE command displays FILE entity statistics and operational state information for the specified nodes and file domains. For an explanation of FILE statistics, enter HELP FILESTATS at an ASAP prompt. FILE [/OUT file/] [ \* ] [, SAMPLES count [node ] [ [.
* specifies to display the performance and state information for all monitored file domains on the specified system. If you do not specify a file or the wild-card character (*), statistics for all files on 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.
state shows files with an OEM-state greater than or equal to state. AUTO shows files with an OEM-state higher than 2, or else shows all files. EXACT shows statistics for only the specified domain. COUNT max-value indicates the maximum number of subdomains to display. AGGREGATE shows statistics for aggregate domains. AGGREGATE is on by default. AGGREGATEONLY | AGGONLY | AO shows only statistics for aggregate domains. MEMORY shows statistics for domains directly from ASAP memory.
To display a list of file domains being monitored and a few attributes: +file \CENTDIV File Domains --------------------------$Mm.filework $Mm.xx.disk $System.system.asap + Status Date Time Full Files Error ---------------- ----- ----- ---- ------ ----Corrupt 9/19 9:59 100 25 0 Up 9/19 9:59 0 0 Up 9/19 9:59 49 0 To display only the attributes associated with a state: +file, states \CENTDIV File Domains ------------------------$Mm.filework $Mm.xx.disk $System.system.
+file, states, detail \CENTDIV File Domains ------------------------$Mm.filework $Mm.xx.disk $System.system.asapmon Status ------------Corrupt Up Up S Date - ----7 9/19 2 9/19 2 9/19 Time Error S Full S ----- ----- - ---- 10:00 0 1 100 7 10:00 0 1 0 2 10:00 0 1 49 2 continued...
GOAL Command The GOAL command controls the objectives used to produce alerts and spawn actions within ASAP. It controls the set of objectives and gets information about those objectives. GOAL [/OUT file/] [entity | *] [\node], COMMIT [.| ]][domain]], goal [,goal,...
entity is the name of an ASAP Entity as defined in EDL. node is the node name the command applies to. 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.
value is the stated goal for this attribute. If no value is specified, the existing value for attribute-operator is deleted. The value must match the TypeData setting as defined for the attribute in EDL. (See SHOW command.) For example, you cannot set a decimal value objective for an attribute defined as an integer. value has no meaning for the STATUS attribute. event INFO | CRITICAL [REPEAT] [NODISPLAY] [down] [-up] INFO configures ASAP to generate an informational event when the objective is not met.
STATUS When events are turned on (using SET OBJECTIVESEVENT ON), status changes in ASAP system entities default to generate one critical EMS event. The STATUS attribute specifies changes to the default behavior for system entities. Use STATUS with ASAP user-defined entities to define all event behavior for status changes. NOEMS Used only with the STATUS attribute. NOEMS turns off automatic event generation for status changes in ASAP system entities.
<#STATE> The current state of the attribute <#LASTSTATE> The last state of the attribute <#GOAL> The objective value rule is an action rule defined using the ACTION command. Action rules are stored action strings that can be applied to multiple domains. WAIT wait indicates the number of minutes ASAP should wait before retrying an action string against a particular entity and domain. The wait time also depends on the ASAP rate setting because ASAP validates objectives only once per cycle.
domain name requires the command to be entered twice for confirmation before any action is taken. 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. OBEYFORM returns objective information in OBEY file format suitable for playback to ASAP CI. entity must be specified when domain is specified; otherwise both are optional.
TCPRTE RTE TCPSOCK SOCK TCPSUBNET SUBNET TCPUDP UDP TELSERVPROCESS TELSERV TELSERVSERVICE SERVICE TELSERVWINDOW WINDOW Examples To add or modify the record for the disk $DATA: GOAL DISK $DATA, BUSY < 65 To specify that a file must be less than 90 percent full: GOAL FILE $SYSTEM.FILE.
GOAL ATM\CHICAGO\$ABC, LIST To display all records from the local database: GOAL To deactivate a broken spooler device while it is repaired: GOAL SPOOLER $SPLG\DEV\$LP, DEACTIVATE To turn on all domains for all entities: GOAL, ACTIVATE To commit all objectives changes: GOAL, COMMIT To define an action to reload a CPU after it fails: GOAL CPU, STATUS ACTION "TACL RELOAD <#DOMAIN>, PRIME" WAIT 15 To define a goal and action to secure the NonStop OS userid file to "OOOO": GOAL FILE $SYSTEM.SYSTEM.
To define a global goal and action to resecure any monitored file using the ASAP default RESECURE rule: GOAL FILE, RWEP = "AOAO" ACTION RESECURE To define a goal that all foreign TCP/IP Port connections must originate from net 16: GOAL TCPPORT, FADDR = 16.0.0.0 To define a goal that all foreign TCP/IP Port connections on Port 23 must originate from subnet 16.150: GOAL TCPPORT 23, FADDR = 16.150.0.0 HELP Command The HELP command provides an explanation for the command or keyword that you specify.
HELP ERROR HELP SET
line specifies the individual Expand line of a system for which availability information is displayed. This information includes statistics about the execution history of the line, such as request counts and numbers of errors and operational state information such as Up, Down, or Connecting states. If you want all of the lines, specify LH \*.* or just LH \*. If you do not specify a line or the wild-card character (*), ASAP uses the default, which is all Expand lines for the current system.
IFrm(S/R) displays number of Data Frames sent and received. SFrm(S/R) displays number of Active Connect Cmnds sent & rcvd. UFrm(S/R) displays number of Passive Connects sent & rcvd. HISTO displays a histogram of the message size distribution. The histogram provides information about message sizes less than the values of 64, 128, 256, 512, 1024, 2048, and 4096. IP displays the Expand statistics for Expand lines configured using either the IP transport or the ATM transport.
TRCE Trace requests NCPM Network-control-process to network-control-process messages LREQ Link requests LCOMP Link completion messages CAN Cancel requests ACK Acknowledgment requests NAK Negative acknowledgments ENQ Enquiry requests PCHG Pathchange messages 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.
SAMPLES count specifies the number of sample periods to display. A sample period is defined by the RATE option in the SET command. You can specify 0 through 255 sample periods. STATE shows all attributes that have an associated state. Associated states are displayed for the Expand command without any options, and the disk command with these options: IP, PATH, LINE, RATE, PERCENT(Default). TIME hh:mm m/d/y defines the ending time of the display information in hours, minutes, month, day, and year.
LH Statistics The following table lists the LH statistics and options shown by the HELP NETSTATS command. Table 6-6. LH Statistics and Options Statistics Options BCC Total number of block-check character errors in this sample. FRAME Number of Level 2 I/S frames sent and received, and I/S ratios. HISTO Message size histogram <64 <128 <256 <512 <1024 <2048 <4096. INFO LDEV, primary/backup PIDs, subtype, and ASAP error, if any. IP Displays statistics for Expand lines using the transports IP or ATM.
CnCmd Number of IP/ATM Connect commands sent or received. CnRsp Number of IP/ATM Connect responses sent or received. CONN Number of Connect requests sent or received. Cur% Percentage of combine Pool pages used Msg + Oos. DFr Number of IP/ATM rates of frames dropped. DFrame Number of IP/ATM Data Frames sent or received. ENQ Number of Enquiry requests sent or received. IA Number of IP/ATM frames received from a unexpected node.
Examples These examples show the LH command with the ASAP output: +LH \ISLAND \ISLAND \249 !Default command Time State PF NoB Bcc L4naks L4packets L4passtru L4links ----------------------------------------------------------------------$LHCSO 3/01 9:12 Cntg $LHIST 3/01 9:12? Down $LHPAN 3/01 9:12 Up 7 $LHREC s 3/01 9:12 Up $LHSUP 3/01 9:12? Down $LHWIN 3/01 9:12 Up 16 6 2 +LH, POOL \CENTDIV !Shows pool utilization.
MONITOR Command The MONITOR command controls monitored objects (domains) within ASAP. It controls the set of monitored domains and obtains information about those domains. The MONITOR command is best explained with several different syntax displays. To add objects to the ASAP DB for ASAP to monitor: MONITOR entity [ \node. ]domain [ ,ADD [ ,OFF ] ] Note ADD is not optional if "SET MONITORADD OFF" has been entered in ASAPCONF or previously in the current ASAP CI session.
[\node.domain ] ,OFF [ domain ] ,DELETE ,INFO [ ,DETAIL ] [ ,OBEYFORM ] ,DETAIL ,OBEYFORM ,LIST [ ,DETAIL ] entity is the name of an ASAP entity as defined in EDL. node is the node name the command applies to. domain is a form of an ASAP domain name. Domain names can represent physical devices ($Data) or abstract representations of applications (Funds, Transfer, or Input). Some command options support the asterisk wild-card character at the end of the domain name.
APP - application COMM - $line CPU - cpu DISK - $volume entity - application EXPAND - $line EXPANDIP - $line FILE - [logical\]$file | /pathname, ADD PROCESS - [logical\]$process | /pathname, ADD PROCESSBUSY - cpu RDF - primary->backup SPOOLER - $supervisor SYSTEM - \node TAPE - $tape TCPPROCESS - $tcpprocess TCPPORT - port number TCPROUTE - $tcpprocess.#route TCPSUBNET - $tcpprocess.#subnet TELSERVPROCESS - $telservprocess TELSERVSERVICE - $telservprocess.service TELSERVWINDOW - $teservlprocess.
logical\ is a hierarchical, logical prefix that can be used to group and create aggregates for files or processes. It can contain from one through four levels using the backslash character as a level separator, depending on the entity and type of domain name specified. For more information on using logical names, see Section 5: File and Process Monitoring. SALES\ is an example of a logical prefix.
$supervisor is the process name of the SPOOLER supervisor process for the SPOOLER subsystem you want to monitor; for example, $SPLS. $node is a node name; for example, \NODE1. $tape is a tape device name; for example, $TAPE. $tcpprocess is the process name of a TCP/IP v4 process or a TCP/IPv6 Monitor process. When you monitor a TCP/IP process you monitor the process (TCPPROCESS) entity and all sub-entities that represent layers of it's statistics.
$telservprocess.service is the TELSERV process name and service name of a TELSERV service. If you monitor specific TELSERV processes and then let ASAP auto-configure Services then ASAP will only configure the services underneath the processes you have specifically monitored. $telservprocess.#window is the TELSERV process and window name of a TELSERV window.
OFF turns monitoring off in the database for the specified domain in the specified entity. When domain is specified, entity must be specified, otherwise both are optional. Domain names can use the asterisk wildcard character as the last character in the name. OFF also outputs each domain turned off (INFO). DELETE deletes records from the database. When domain is specified, entity must be specified, otherwise both are optional.
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. REMOVE removes a user-defined ASAPX domain from the monitored set of domains. An ASAPX domain must be down before it can be removed. 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.
TCPSUBNET SUBNET TCPUDP UDP TELSERVPROCESS TELSERV TELSERVSERVICE SERVICE TELSERVWINDOW WINDOW 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 alread
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 $ABC To monitor a process as part of a hierarchical group of processes,
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 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. The single aggregate record written to the ASAP database can summarize 10, 100, or even 1000 or more individual processes.
SPOOLER MONITOR SPOOLER spooler-supervisorname SWAP MONITOR SWAP cpu-number SYSTEM MONITOR SYSTEM \nodename TCPPROCESS MONITOR TCPPROCESS $tcpprocess TCPPORT MONITOR TCPPORT port TCPROUTE MONITOR TCPROUTE $tcpprocess.#route TCPSUBNET MONITOR TCPSUBNET $tcpprocess.#subnet TELSERV PROCESS MONITOR TELSERVPROCESS $telservprocess TELSERV SERVICE MONITOR TELSERVSERVICE $telservprocess.service TELSERVWINDOW MONITOR TELSERVWINDOW $telservprocess.
\* specifies that information for all systems is provided. SAMPLES count specifies the number of sample periods to display. A sample period is defined by the RATE option in the SET command. You can specify 0 through 255 sample periods. dnode specifies the node of the destination Expand system. The default is all the systems connected to the sending node (snode), which has the same effect as \*. If you want a particular dnode, specify the dnode by system name (such as \SUPPORT) or system number (\240).
NODE Statistics The following table lists the NODE statistics and description/options displayed with the HELP NCPSTATS command. Table 6-8.
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). For more information, see the Guardian User’ s Guide. OBEY filename filename is the name of the file containing ASAP commands. Example The OBEY file can contain this information to indicate which systems to start: STARTUP SET DB $DATA.ASAPDB.
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.
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. 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.
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. Note SAMPLES, TIME, and \* cannot be used with the MEMORY option.
+ 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 DETAIL command: EDL DETAIL "P ^,DE,ST,MEM,MIN,EX,C
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 use or reserved by this process STATE
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.
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. The bits in the wait field are numbered from left to right; thus a wait state of %003 means that bits 14 and 15 are set: Wait-field .8 wait on PON CPU power on .9 wait on IOPON I/O power on .10 wait on INTR Interrupt .11 wait on LINSP INSPECT event .
00 3/01 10:51 01 3/01 10:51 1.6 1.6 1.6 .4 .3 1.6 1.6 1.6 .6 .3 312 313 314 283 6 312 313 314 13 108 $MM.ASAPXTST.DRV7 $MM.ASAPXTST.DRV5 $MM.ASAPXTST.DRV4 $SYSTEM.SYS03.OMLAM $NCP $MM.ASAPXTST.DRV7 $MM.ASAPXTST.DRV5 $MM.ASAPXTST.DRV4 $BR $SYSTEM.SYSTEM.
property is assigned an alert state. States in ASAP describe the status of a property such as up, down, warning, or critical. ASAP displays ranked alert states in the ASAP Client, the EMS subsystem, or both. To enable ranked property alerts in ASAP Client, set State Determination to UseStateGraphState for each ranked property in the ASAP Client Attribute Property sheet. For more information, see "Configuring ASAP" in the ASAP Client help.
goal attribute operator [value] [event] [action] STATUS [event] [action] STATUS NOEMS [action] event INFO|CRITICAL [REPEAT] [NODISPLAY] [down] [-up] action ACTION "string" | rule [WAIT wait] [NOREPEAT] attribute is the name of an attribute name as defined in ASAP EDL for the entity. The attribute must be defined with StatePair Yes, and it cannot be the StateIsOp (STATUS) attribute. operator is one of the following objective operators: > The calculated value must be greater than the objective value.
event INFO | CRITICAL [REPEAT] [NODISPLAY] [down] [-up] INFO configures ASAP to generate an informational event when the objective is not met. CRITICAL configures ASAP to generate a critical event when the objective is not met. REPEAT causes ASAP to repeat the event for each interval where the objective is not met. NODISPLAY overrides any global settings to suppress display of the event on the operator console. down is the event number to use for the down event, when the objective comparison fails.
NOEMS Used only with the STATUS attribute. NOEMS turns off automatic event generation for status changes in ASAP system entities. action ACTION string | rule [WAIT wait] [NOREPEAT] string is an action string where the first word in the string is a command interpreter name such as TACL, SCF, or FUP, and the remainder of the string represents the command to be executed by that command interpreter.
rule is an action rule defined using the ACTION command. Action rules are stored action strings that can be applied to multiple domains. WAIT wait indicates the number of minutes ASAP should wait before retrying an action string against a particular entity and domain. The wait time also depends on the ASAP rate setting because ASAP validates objectives only once per cycle. NOREPEAT indicates that ASAP should not continue to repeat the action until the condition is corrected.
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. OBEYFORM returns objective information in OBEY file format suitable for playback to ASAP CI. 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.
TCPSUBNET SUBNET TCPUDP UDP TELSERVPROCESS TELSERV TELSERVSERVICE SERVICE TELSERVWINDOW WINDOW Examples To add or modify the record for the disk $DATA: RANK DISK $DATA, BUSY < 65 To specify that a file must be less than 90 percent full: RANK FILE $SYSTEM.FILE.
To deactivate a broken spooler device while it is repaired: RANK SPOOLER $SPLG\DEV\$LP, DEACTIVATE To turn on all domains for all entities: RANK, ACTIVATE To commit all objectives changes: RANK, COMMIT To define an action to reload a CPU after it fails: RANK CPU, STATUS ACTION "TACL RELOAD <#DOMAIN>, PRIME" WAIT 15 To define a goal and action to secure the NonStop OS userid file to "OOOO": RANK FILE $SYSTEM.SYSTEM.
To define a goal that all foreign TCP/IP Port connections must originate from net 16: RANK TCPPORT, FADDR = 16.0.0.0 To define a goal that all foreign TCP/IP Port connections on Port 23 must originate from subnet 16.150: RANK TCPPORT 23, FADDR = 16.150.0.0 RDF Command The RDF command displays RDF entity availability statistics for the specified nodes and domain names. For a description of RDF statistics, enter HELP RDFSTATS. RDF [/OUT file/] [ \* ] [ [.] * [ \node ] [ [.
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 to display statistics collected from 10:10 to 10:15. hh is the hour. mm is the minute. m/d/y is the month, day, and year. Valid entries are mm/dd/yy, yyyy/mm/dd, or mm/dd/yyyy. VOLUMES displays the associated disk volumes.
\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:39 Running 5/11 9:39 Running 5/11 9:39 Running 5/11 9:39 Running 5/11 9:39 Running 5/11 9:39 Error ----0 0 0 0 0 0 \DOME Domain\Name\Hierarchy -------------------------------Dome->Tanda\Extractor\$Ext1 Dome->Tanda\Monitor\$Mntr S
\TANDA \TANDA \TANDA \TANDA \DOME \DOME 230 230 230 230 245 245 Dome->Tanda\Receiver\$Rec1 Dome->Tanda\Updater\$Up01 Dome->Tanda\Updater\$Up02 Dome->Tanda\Updater\$Up03 Dome->Tanda\Extractor\$Ext1 Dome->Tanda\Monitor\$Mntr continued...
SET [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ ACTION ON | OFF ] ACTOBJECT filename ] ACTSHELL filename ] APP entity-option ] ASAPLOG filename ] BACKUPCPU cpu | * ] BUFFERED ON | OFF ] CLEANTIME time ] COLLECT \collect-node ] COMM entity-option [, entity-option], ] DB db-file-prefix ] DBMAXDAYS [ [ entity ] days ] ] DBMAXDAYSTOPURGE days ] DBROLLOVERSUBVOLPREFIX prefix ] DBROLLOVERFILEPREFIX prefix ] DISK entity-option ] EDL filename ] E
[ [ [ [ [ [ [ [ [ SLEEPTIME SPOOLER SWAP SYNC TAPE TERM TCP TMF TRACE time,time entity-option entity-option minutes,frequency entity-option logterm ON | OFF entity-option entity-option ON | OFF ] ] ] ] ] ] ] ] ] ACTION ACTION ON | OFF defines whether the ASAP action processing components are enabled. ON | OFF enables or disables ASAP action processing components. The default value is OFF. When action is on, ASAP will execute user defined actions associated with the RANK ACTION option.
ACTSHELL ACTSHELL action-script-filename defines the action server script filename. The default is ASAPACT. APP APP entity-option [, entity-option ] determines settings and parameters for the APP entity. CPU cpu-num defines the CPU that the APP SGP process will reside in. ON | OFF enables or disables network-wide App availability statistics reporting. The default is OFF. OBJECT ASAP APP-program-file-name defines the ASAPX SGP program object file name.
ASAPLOG ASAPLOG 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 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.
COMM COMM entity-option [, entity-option ] determines settings, parameters, alarm threshold settings for the COMM entity. CPU cpu-num defines the CPU that the COMM SGP process will reside in. ON | OFF ON enables network-wide comm statistics reporting. OFF disables networkwide comm statistics reporting. The default is OFF. OBJECT ASAP COMM-program-file-name defines the ASAP/COMM program object file name. The program is started automatically on each node by the ASAP Monitor if ON is specified.
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. Example +SET COMM ON, CPU 3, PARAMETERS "SUBVOL ASAPMEAS, RATE 15" DB DB db-file-prefix defines the database volume, subvolume, and file prefix of the collector server statistics files.
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 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 The Default value is ASAP. Thus if SET RETAIN ROLLOVER is specified, and SET DB equals $DATA.ASAPDB.DB, and SET DBRolloverSubvolPrefix is ASAP, rollover files will be named using the following subvol-file template: $DATA.ASAPyyyy.ZmmddEEE Where: 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.
CPU cpu-num defines the CPU that the DISK SGP process will reside in. ON | OFF ON enables network-wide disk statistics reporting. OFF disables network-wide disk statistics reporting. The default is OFF. OBJECT ASAP DISK-program-file-name defines the ASAP/DISK program object file name. The program is started automatically on each node by the ASAP Monitor if ON is specified. The default is $SYSTEM.SYSTEM.ASAPDSK. PARAMETERS "DISK-param [DISK-param}...
The default location is $SYSTEM.SYSTEM. SWAPVOL [$ volume] specifies the location for the MEASFH swap volume. The default is $SYSTEM. Example +SET DISK ON, PARAMETERS "SUBVOL ASAPMEAS, RATE 15" EDL EDL filename defines and compiles a file containing ASAP Entity Definition Language (EDL) statements. EDL is used within ASAP to define all entities and their attributes. You can enter multiple SET EDL commands, but a maximum of 10 EDL files are supported for user-defined entities used with the ASAP Extension.
PARAMETERS " expand-param [ expand-param]..." | null specifies the NODE-specific parameter string to be passed to the ASAPEXP process at startup time. You must enclose the parameter list in quotation marks. The default is null. RATE minutes defines the interval, in minutes, that Expand availability statistics are reported back to the Collector. FILE FILE entity-option defines the settings and parameters for the FILE entity.
AGGONLY when present, ASAP creates aggregate and/or state propagated group records for files defined as a part of logical file groups, and it writes only these group records to the ASAP database. MINSTATE state defines the state at which the File SGP should consider a domain to be in an alert state. Valid values are 2 through 8, the default is 3. MINONLY state When a MINONLY state is specified, the File SGP operates in exception mode, writing only alerting detail domain records to the database.
MAXDOMAINS defines the maximum number of monitored domains. The File SGP will allocate memory to support that number of monitored domains. Valid values are 2 through 32767. ASAP will always allocate 1 less domain than you specify. The default setting can vary by ASAP version. 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.
ASAP processes that are operating together to gather ASAP performance statistics and operational state information. The default is $ZOO. Using the ID lets you operate several ASAP programs in the same node or resolve a name conflict.
The default is 72 lines of output. To disable this feature, enter SET IOCONTROL 0. LOGFILE LOGFILE filename defines the name of the file used for ASAP CI I/O capture. LOGGING ON/OFF controls access to the file. The default is the current $volume.subvolume.logfile. LOGGING LOGGING ON | OFF determines settings for the capture of ASAP CI I/O. ON enables the capture of ASAP CI I/O to a file defined by LOGFILE filename. OFF disables the capture of ASAP CI I/O. The default is OFF.
LOGSUPPRESS 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.
MONITORADD setting: MONITOR DISK $DATA, ADD NODE 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. If ON is specified, this program automatically starts on each node by the ASAP Monitor. The default is $SYSTEM.SYSTEM.ASAPNCP.
NODEDOWNALERT NODEDOWNALERT ON | OFF controls whether the ASAP Collector will generate a node down/up alert when a node monitored by ASAP goes down/up. 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.
OBJECTIVESAUDIT OBJECTIVESAUDIT ON | OFF enables or disables TMF for auditing of the Objectives database. The default is OFF. OBJECTIVESDB OBJECTIVESDB filename defines the name of the Objectives database file. When you execute the first RANK or MONITOR command on a node for a specific ASAP ID, the ASAP CI always requests the name of the objectives database from the ASAPMON process referred to by that ASAP ID.
OBJECTIVESEVENTCONSOLEUP OBJECTIVESEVENTCONSOLEUP ON | OFF displays up event messages on the operator console. The default is ON. OBJECTIVESEVENTSUBJECT OBJECTIVESEVENTSUBJECT ON | OFF controls the subject token in the ASAP event buffer. ON causes ASAP to mark the domain name token (zasp-tkn-asap-dname) as the subject token in ASAP event buffers. OFF causes ASAP to mark the ASAP component token (zasp-tkn-asap-component) as the subject token in ASAP event buffers.
OBJECTIVESEVENTMAX OBJECTIVESEVENTMAX max-events defines the maximum number of events that ASAP should generate per domain per statistics interval. The default is 1. OBJECTIVESRANK OBJECTIVESRANK STANDARD | PERCENT | HISTORICAL sets the type of analysis and ranking by ASAP when applying objectives against attribute values. The default is STANDARD. STANDARD ASAP reports on attributes as nonranked, up, down and critical.
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-description 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-description 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 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 PRIORITY server-priority defines the execution priority of the Monitor or Collect process started by the STARTUP command. The default is 160.
AGG when present, ASAP creates aggregate and/or state propagated group records for processes defined as a part of logical process groups. AGGONLY when present, ASAP creates aggregate and/or state propagated group records for processes defined as a part of logical process groups, and it writes only these group records to the ASAP database. 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.
values are 2 through 32767. ASAP will allocate at least 1 less domain than you specify. The default setting can vary by ASAP version. MAXDOMAINS defines the maximum number of monitored domains. The Process SGP will allocate memory to support that number of monitored domains. Valid values are 2 through 32767. ASAP will allocate at least 1 less domain than you specify. The default setting can vary by ASAP version.
processes might not run during the entire sample period. This makes subsampling a requirement. For example, if a sample interval is 15 minutes (SET RATE 15) and the subsample count is equal to 3, ASAP takes an internal data sample every 5 minutes (15/3). However, the final %busy CPU time of the busiest processes must be adjusted by the actual CPU process time during the sample interval (15 minutes in this example).
Examples SET PROXYCONFIG $DATA.ASAP.ASAPPCNF PROXYCPU PROXYCPU number specifies the CPU number for the Proxy SGP. number The processor where ASAP will start the ASAP Hybrid Proxy server. ASAP Hybrid is an optional ASAP product. Examples SET PROXYCPU 3 PROXYOBJECT PROXYOBJECT object-filename specifies the name of the Proxy SGP object file. object-filename The fully-qualified local filename of the ASAP Hybrid Proxy server. The default is SYSTEM.SYSTEM.ASAPPXY. ASAP Hybrid is an optional ASAP product.
RATE 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 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 RETAIN option defines the action to be performed against the database at cleantime. ALL retains all records indefinitely.
The RETAIN number option can have a negative performance impact in networks that monitor large numbers of nodes in a database. This occurs when it becomes necessary to process large numbers of statistics records in the database. SLEEPTIME SLEEPTIME time, time defines the time range (hhmm,hhmm) when statistics collection does not occur. Although statistics collection ceases, the ASAP system remains active.
PARAMETERS specifies spooler-specific parameter string to pass to each Spooler SGP at startup. DETAIL instructs the Spooler SGP to return individual detail records by default. The Spooler SGP otherwise operates in aggregation mode by default, returning one aggregate record for all collectors, one for all devices, and one for all print processes. RATE #mins overwrites the ASAP default rate parameter for the Spooler SGP only. Instructs the Spooler SGP to sample at this rate.
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 +SET SWAP ON, CPU 3, OBJECT $SYSTEM.SYSTEM.
SYNCSLOW SYNCSLOW ON | OFF defines the clock synchronization algorithm. The SET SYNC option controls when time-of-day synchronization occurs. The SET SYNCSLOW option controls the algorithm. You can manually correct the time on any node with the TACL SETTIME command, regardless of how SET SYNC or SYNCSLOW is set. ON adjusts the time-of-day clock on remote ASAP nodes very slowly to avoid sudden time of day changes.
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 TERM logterm | OFF defines the Collect or Monitor terminal log-file name to which internal errors and actions are logged. The default is $0.
OBJECT filename specifies the name of the TCP SGP program file. The default is $SYSTEM.SYSTEM.ASAPTCP. 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.
TELNET n defines the minimum number of minutes the SGP will wait before reconfiguring Telserv processes when they are being automatically configured by the SGP. The default is 60 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. MAXPRT n defines the maximum of number of TCPPORT 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. 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.
TMF TMF entity-option [,entity-option ] defines the settings and parameters for the TMF entity. entity-option is one of: CPU cpu-num defines the CPU that the TMF SGP process will reside in. 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].
TRACE TRACE ON | OFF turns an internal trace on and off for debugging purposes only. Use this option only when assisting the HP Global Customer Support Center in problem diagnosis. The default is OFF. SHOW Command The SHOW command displays information about the Entities defined to ASAP using the ASAP Entity Definition Language (EDL). SHOW [entity] [attribute] [, DETAIL] [, ATTRIBUTES] Note Attributes that support objectives are identified with an asterisk in SHOW command output.
SHOW FILE FULL SHOW FILE, DETAIL, ATTRIBUTES SHUTDOWN Command The SHUTDOWN command stops ASAP Monitor, SGPs, and Collect processes on the nodes that you specify. Only someone with a super-group user ID can use this command. SHUTDOWN [ \* [ \node-name ] ] [ COLLECT | MONITOR ] [ [.] ppd-name ] \* shuts down the ASAP Monitor or Collect process on all nodes of the network. COLLECT specifies a Collect process. MONITOR specifies a Monitor process. This is the default.
Considerations SHUTDOWN shuts down Monitor (default) or Collect processes. After shutdown is complete, data collection stops. SPOOLER Command The SPOOLER command displays Spooler availability information for the specified nodes and Spooler domains. For an explanation of Spooler statistics, enter HELP SPOOLERSTATS at an ASAP prompt. SPOOLER [/OUT file/] [\*] [ [.] * ] [, [\node] [ [.
* specifies to display the performance and state information for all spoolers on the specified system. If you do not specify a spooler or the wild-card character (*), statistics for all spoolers on 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.
Use this display only if your spooler configuration is not too large, or if you specify only certain spooler components using the EXACT option. SHORT when used with DETAIL or MINSTATE, displays information in short form. MINSTATE shows detailed information on subdomains with states greater than or equal to what is specified. states indicates the minimum state to report. AUTO indicates to use state 2 as the minimum. This is the default setting.
+ SPOOLER, RAW It displays: VersionStr Sys Domain Name Status ---------- --- --------------- ---------\ASAP 1 $SPLS\COLL Active \ASAP 1 $SPLS\DEV Waiting \ASAP 1 $SPLS\PRINT Dormant \ASAP 1 $SPLS\SUPER Active Date Time ---------- ----2000/03/23 8:07 2000/03/23 8:07 2000/03/23 8:07 2000/03/23 8:07 V Error NumObjs - ----- ------1 0 2/---2 1 0 3/---3 1 0 2/---2 1 0 1/---1 continued...
\ASAP Spooler Supervisor Status Date Time Error Cpu BCpu Prty ------------------------------ ---------- ----- ----- ----- --- ---- ---$SPLS\SUPER\$SPLS Active 03/23 8:07 0 1 2 149 continued... Jobs Batch Open Print Hold Fonts DevQs Locs Colls Devs PProcs Full% ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ------ ----392 0 0 0 100 6 200 53 2 6 3 50 continued...
To retrieve detailed information about the spooler print process $SPLS\PRINT\$FASTP: + SPOOLER $SPLS\PRINT\$FASTP, DETAIL It displays: \ASAP Spooler PrintProcess Status Date Time Error Cpu BCpu Prty Flags --------------------------- ---------- ----- ----- ----- --- ---- ---- ----$SPLS\PRINT\$FASTP Dormant 03/23 8:07 0 3 2 130 continued... Program File Name Jobs Batch Print Hold Locs Devs DevQs ------------------------ ----- ----- ----- ---- ---- ---- ----$SYSTEM.FASTP.
+SET DISK ON, PARAMETERS +START \NODEB !Parameters nulled node-name specifies the individual system for which information is to be monitored or collected. This starts the ASAP Monitor or Collect process on this node only. The default is Monitor. Example This example shows how to use the STARTUP command: + + + + + + SET DB $DATA1.
[ TRACE | DISK ] ] node specifies the individual system for which information is displayed. * specifies status information on all systems. MONITOR requests status information on the Monitor process. This is the default. If SGPs are active on the reporting system, status for the SGP is returned as well. COLLECT requests status information on the Collect process. TIMEOUT specifies how many seconds the status command should wait for a response.
STATUS ACTIONS MSGS shows the most recent actions. STATUS ACTIONS MSGS shows actions for STATUS ACTIONS LOG ON | DETAIL turns on action logging. This option is not recommended except for debugging due to overhead. STATUS ACTIONS TRACE ... is for development purposes only. Table 6-10.
APP ASAP Extension CMM Comm SGP DSK Disk SGP EXP Expand SGP FIL File SGP NCP Node SGP PRO Process SGP RDF RDF SGP SPL Spooler SGP SWP Swap SGP TAP Tape SGP TCP TCP/IP SGP TMF TMF SGP Example - Status Monitor +STATUS \ISLAND ! Show \ISLAND’s Status \ISLAND Primry Backup ---------- ------ -----$BOOM V04 1,196 0,177 $BOOM0 V04 0,145 $BOOM1 V04 1,203 $BOOM2 V04 2,216 $BOOM3 V04 3,003 $BOON V04 0,142 RDF $BOOG V04 1,245 NCP $BOOJ V04 1,180 DSK $BOOK V04 0,120 EXP $BOOL V04 1,021 FIL $
$HIT.ASAPDB.DBAPP Open(0) $HIT.ASAPDB.DBCOM Open(0) $HIT.ASAPDB.DBCPU Open(0) $HIT.ASAPDB.DBDSK Open(0) $HIT.ASAPDB.DBEXP Open(0) $HIT.ASAPDB.DBFIL Open(0) $HIT.ASAPDB.DBNCP Open(0) $HIT.ASAPDB.DBPRO Open(0) $HIT.ASAPDB.DBPCB Open(0) $HIT.ASAPDB.DBRDF Open(0) $HIT.ASAPDB.DBSPL Open(0) $HIT.ASAPDB.DBSWP Open(0) $HIT.ASAPDB.DBTAP Open(0) $HIT.ASAPDB.DBTCP Open(0) $HIT.ASAPDB.
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. If you want information for all the systems, specify SWAP \*. If you do not specify a node or the wild-card character (*), the default is used.
The CPU is being reloaded for the swap files. A swap file 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.
MB displays usage statistics in megabytes STATE shows all attributes that have an associated state. RAW displays USE statistics in a dense tabular format rather than the standard ASAP sparse format. When used with the file option the individual swap file statistics and the addional 2 statistics will be displayed: MAXRSRVD The highest number of memory pages ever reserved in the file.
allocated for each CPU. With the file option it displays the number of pages reserved in each swap file. RESERVATIONS Number of outstanding reservations for all segments RESIZES Number of good and the number of failed reservations resized for each CPU. STATUS Current status of the swap files for the CPU. THRESHOLD Number of memory pages that must be allocated to generate an NSK subsystem threshold alert message 200 TIME Time of the stats converted to data base local civil time.
+Swap 3, \CENTDIV -------03 3/18 03 3/18 03 3/18 03 3/18 03 3/18 03 3/18 03 3/18 03 3/18 03 3/18 03 3/18 Detail, samples 5, time 13:43 Time OK/Fail Creates Releases Resizes Allocates Frees ----- ------- --------- --------- --------- --------- --------13:43 OK 7 7 3 13:43 Failed 13:42 OK 13:42 Failed 13:41 OK 1 13:41 Failed 13:40 OK 13:40 Failed 13:39 OK 1 13:39 Failed 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
+ STARTUP \SANFRAN COLLECT ! San Francisco collector startup + STARTUP \CHICAGO MONITOR ! Chicago Monitor startup + SYNC \CHICAGO ! Sync CHICAGO gmt to SANFRAN gmt SYSTEM Command The SYSTEM command specifies another default node name or number. Entering SYSTEM alone sets the system to the local system name. SYSTEM [ \node-name ] [ \node-number ] node-name specifies a node name. node-number specifies a node number.
* indicates to retrieve all tape records from all nodes. node indicates to retrieve tape records only from the specified node. tapespec indicates to retrieve only tape records related to the specified tape device. SAMPLES count indicates the number of records to return. TIME hh:mm m/d/y indicates to retrieve information starting at the specified time. STATES indicates to display states associated with tape attributes. DETAIL indicates to display detailed tapemount information for the specified tape domain.
ProgName -------BACKUP + To display a list of all tape information for all monitored tape domains: + TAPE, RAW It displays: Version Sys Domain Status -------- --- -------- ---------\ASAP 1 $TAPE0 Free \ASAP 1 $DLT00 InUse Date ---------2000/03/23 2000/03/23 Time ----08:07 08:07 V DevNo CPU BCPU Sub ACS - ----- --- ---- --- --1 378 2 1 6 No 1 255 0 1 9 Yes continued...
continued... Action -------------------------------------MOUNT REQUESTED TAPE MOUNT REQUESTED TAPE + To display detailed information for the node (\ASAP) tape drive: + TAPE ASAP, DETAIL It displays: \ASAP Status Date Time DevNo CPU BCPU Sub ACS Checks Mnts Mtime -------- --------- ----- ----- ----- --- ---- --- --- ------ ---- ----ASAP NotFound 3/23 8:07 - 100 15 continued...
[,NOLINEBREAK [,AGE minutes ] ] The TCP command displays TCP and Telserv entity statistics for the specified nodes, entities, and domain names. entity Any TCP or Telserv sub-entity name.
displays records based on attribute states state show records with at lease one attribute state equal to or higher than . Valid states are 1 through 8 AUTO show records with at lease one attribute state greater than state 2 (OK) COUNT defines the max number of records to display EXTRACT extract TCP records from the ASAP database to a separate database file or to a process.
TCP TCPROUTE, DETAIL To show the latest detailed TCP/IP statistics for Port 23 on \Chicago: TCP TCPPORT \CHICAGO.23, DETAIL To show the latest detailed TELSERV Window statistics for the last four samples: TCP WINDOW, DE, S4 To extract the latest TCPICMP statistics for all for 1000 samples to a file: TCP ICMP, EXTRACT $DATA.DATA.
TIME hh:mm m/d/y indicates to retrieve information starting at the specified time. 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 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.
Examples For descriptions of the fields displayed in TMF command output, enter help tmfstats. To display a list of monitored TMF domains, and a few attributes: + tmf \ASAP TMF -------------Auditdump Audittrail Tmf Transactions + Status Date -------- ----Enabled 3/14 Up 3/14 Enabled 3/14 Up 3/14 Time ----13:18 13:18 13:18 13:18 Type -------Master Master - Active Used Tps Trans Hung ------- ---- ------- ----- ---Yes - 62 - 0.
- - - 0 No 0 + To display all the available attributes with the associated states: + tmf, states, \ASAP TMF -------------Auditdump Audittrail Tmf Transactions detail Status -------Enabled Up Started Up S Date - ----2 3/14 2 3/14 2 3/14 2 3/14 Time ----13:18 13:18 13:18 13:18 Error ----0 0 0 0 S 1 1 1 1 Type -------Master Master - Active -------Yes - S 7 1 1 1 Ovflw ----No - S 1 1 1 1 continued... Hold ---No + S Used S Tps S BeginTr - ---- - -------- - -------1 - 1 - 1 1 62 7 - 1 1 - 1 0.
To display details about all TMF auditdump subdomains where at least one attribute has a state value greater than 2 (if no auditdump subdomains meet this condition, all auditdump subdomains are displayed): + tmf auditdump, minstate auto \ASAP AuditDump Status Date Time Active --------------- ---------------- ----- ------ -----Master Enabled 3/14 13:18 Yes S Process - ------------------7 \ASAP.$X943 continued... CurrentFile -------------------------$DSV.ZTMFAT.
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.
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. type binary 16 display "m<\999.>". type binary 16 display "m<99>". redefines ikey. type binary 16 display "m<\999.>". type character 8. type character 8 redefines ikey. pic x(11) redefines ikey. pic x(12) redefines ikey. pic x(13) redefines ikey. pic x(14) redefines ikey.
03 03 02 02 02 02 02 02 02 02 END. sysno domain entity iyear imonth iday ihour imin isec irank type binary 16 display “m<\999.>”. type character 64. type character 66 redefines ikey. pic x(67) redefines ikey. pic x(68) redefines ikey. pic x(69) redefines ikey. pic x(70) redefines ikey. pic x(71) redefines ikey. pic x(72) redefines ikey. pic x(73) redefines ikey. Application Entity Statistics Definitions DEFINITION APP-STATS2. 02 system 02 word 02 sysname 02 P-key-x 8.
02 02 02 LDev Type SubType type binary 32. type binary 16. type binary 16. 02 02 02 Op-Text OpText OpState type binary 16 occurs 5 times. !Operational Status type character 1 redefines op-text. type binary 16. !Operational State 02 02 02 Line-Stat LineStat LineStat-State type binary 16 occurs 4 times. !Line Status type character 1 redefines line-stat. type binary 16. !LineStat state.
CPU Statistics Definitions DEFINITION 02 02 02 02 02 02 02 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 02 02 02 02 03 03 02 02 02 CPU-STATS System type binary 16 occurs 4 times.!system name Word type binary 16 redefines system. Sysname type character 8 redefines system. P-key type *. !sysno & cpuno & its Q-key type * redefines P-key. Event type *. !timestamp & interval info Cputype type binary 16.
02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 page-size mem-size mem-size-state first-vrtl-page first-vrtl-page-state swappable-pages swappable-pages-state free-pages free-pages-state cur-locked-mem cur-locked-mem-state max-locked-mem max-locked-mem-state high-locked-mem high-locked-mem-state spare1 spare2 spare3 spare4 spare5 spare6 type type type type type type type type type type type type type type type type type type type type type binary binary binary binary binary binary binary bi
03 03 03 03 03 03 03 03 03 03 03 03 03 03 03 03 03 03 03 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 END. State type character 1.!Up; Down; Revive; Etc P-B type character 2.!Path designtn p,b,etc Ctrl type binary 16. !Controller number Unit type binary 16. !Physical unit number Reads type binary 16. !Read rate Writes type binary 16. !Write rate Seeks type binary 16. !Seek rate Rate type binary 16. !Total write,read,seeek Busy type binary 16. !Total write,read,seek Write-busy 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 L2-Proto type character 8. !Level 2 protocol !-- LEVEL 2 ---------i-frames-sent type binary 32. !base + 0 Data type binary 32 redefines i-frames-sent. i-frames-rcvd type binary 32. !base + 1 s-frames-sent type binary 32. !base + 2 s-frames-rcvd type binary 32. !base + 3 u-frames-sent type binary 32. !base + 4 u-frames-rcvd type binary 32.
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 net-max-combined-buf type binary 32.!base+47 net-oos-timeouts type binary 32.!base+48 pchg-send type binary 32.!base + 49 pchg-rcvd type binary 32.!base + 50 net-pool-size type binary 32.!base + 51 net-pool-fails type binary 32.!base + 52 time-factor type binary 32.!base + 53 sbw d21 dat-bytes-sent type binary 32.
02 END. spare6 type binary 32. !Spare File Entity Statistics Definitions DEFINITION FIL-STATS. 02 system 02 word 02 sysname 02 P-key-x 02 Q-key-x 02 event 02 Pid 02 Cpu 02 Pin 02 C-code 02 Op-Text 02 OpText 02 OpState 02 Error 02 Error-State 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-x.
02 END. Spare4 type binary 16. Node Entity Statistics Definitions DEFINITION Exp-End-to-End-Stats. 02 End-Sys-Num type 02 Num-of-Path type 02 Cur-Path-Hop-Count type 02 Cur-Path-Neighbor-Num type 02 Cur-Path-Ldev type 02 Link-sent type 02 Link-recv type 02 Pkts-sent type 02 Pkts-recv type END. binary binary binary binary binary binary binary binary binary 8. 8. 8. 8. 16. 16. 16. 16. 16. DEFINITION NCP-STATS. 02 System type binary 16 occurs 4 times. 02 Word type binary redefines system.
02 PriState 02 Busy type binary 16. type binary 64. 02 02 02 02 02 02 02 02 02 02 type type type type type type type type type type 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 END. BusyState P-State PState PStateState W-State WState WStateState MPages MPagesState MSent ! Process busy 8.14.03 implied decimal binary 16. binary 16 occurs 4 times. ! Process state character 1 redefines P-State. binary 16. binary 16 occurs 4 times. ! Wait state character 1 redefines W-State. 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 END. flags type binary 16 unsigned. groupinfo type binary 16 unsigned. rfe type binary 16 unsigned. processname type character 6. lcbs type binary 16 unsigned. Pages type binary 16 unsigned. Processtime type binary 64. RcvQLen type binary 16 unsigned. MsgsRcvd type binary 16 occurs 2 times. Rmsgs type binary 32 redefines MsgsRcvd. MsgsSent type binary 16 occurs 2 times.
02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 END. PCpu-State BCpu BCpu-State Record-type Primary-vol Primary-volch Secondary-vol Secondary-volch Audittrail-index Ai-volume Ai-volch Ai-sno Ai-rba Spare RtdTime RtdTime-State RtdSecs-State type type type type type type type type type type type type type type type type type binary 16. !Primary CPU State binary 16. !Backup CPU binary 16. !Backup CPU State binary 16. !Type for this record binary 16 occurs 4 times.
02 02 02 02 NumDevQ NumDevQ-State NumLocs NumLocs-State type type type type 32. 16. 16. 16. !Number of Device Queues used !SplNumDevQ state !Number of locations defined !NumLocs State 02 02 02 NumDevs SplNumCols SplNumPrts type binary 16. type binary 16. type binary 16. !Number of devices defined !Number of collectors defined !Number of print processes defined 02 02 NumFontJobs NumFontJobs-State type binary 16. 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 03 03 03 03 03 03 03 03 03 03 03 03 03 System type binary 16 occurs 4 times.!sys name Word type binary 16 redefines system. Sysname type character 8 redefines system. P-key-x type *. !Sysno & cpuno & its Q-key-x type * redefines P-key-x. Event type *. !Timestamp/interval info Cpu type binary 16. !Cpu number Invalid type binary 16. OpState type binary 16.
03 03 03 03 02 02 02 02 02 02 02 END. max-reserved-state type binary 16. Threshold type binary 32. Threshold-state type binary 16. File-Error type binary 16. SwapGBMB type Character 2. spare1 type binary 16. spare2 type binary 16. spare3 type binary 16. spare4 type binary 16. spare5 type binary 16. spare6 type binary 16.
02 Proc-Name type binary 16 occurs 8 times. 02 02 ProcName Prog-Name type type 02 02 ProgName UserId type type ! Process name using tape drive. character 1 redefines Proc-Name. binary 16 occurs 5 times. ! Filename using tape drive. character 1 redefines Prog-Name. binary 16. ! UserId using tape drive. Spare1 Spare2 Spare3 Spare4 type type type type binary binary binary binary 02 02 02 02 END. 16. 16. 16. 16. *--This extension layout is for the Tape detail statistics. DEFINITION TAP-EXT.
02 snd-probe 02 snd-urg 02 snd-winup 02 snd-ctrl 02 bad-hdr-len 02 rcv-total 02 rcv-pack 02 rcv-byte 02 rcv-badsum 02 rcv-badoff 02 rcv-short 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
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. 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 16. 16. 16. 16. 16. 16. 16. 16. 16. 16. 16. 16. 16. 16. DEF ZUDP6Data.
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 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. type type type type type type type type type type type type binary binary binary binary binary binary binary binary binary binary binary binary 16. 16. 16. 16. 16. 16. 16. 16. 16. 16. 16. 16. DEF ZIP6Data. 02 ztotal type binary 32. 02 Word type binary 16 redefines ztotal. 02 bad-xsum type binary 32.
02 cant-fwd 02 redir-sent 02 out-pkts 02 noproto 02 delivered 02 localout 02 odropped 02 reassembled 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 type type type type type type type type binary binary binary binary binary binary binary binary binary binary binary binary binary binary binary binary binary 16. 16. 16. 16. 16. 16. 16. 16. 16. 16. 16. 16. 16. 16. 16. 16. 16.
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.
02 outdata-adj END. type binary 16. DEF ZARP6Data. 02 snt-arpreq type binary 32. 02 Word type binary 16 redefines snt-arpreq. 02 rcv-arpreq type binary 32. 02 snt-arprsp type binary 32. 02 rcv-arprsp type binary 32. 02 snt-invreq type binary 32. 02 rcv-invreq type binary 32. 02 snt-invrsp type binary 32. 02 rcv-invrsp type binary 32. 02 snt-naks type binary 32. 02 rcv-naks type binary 32. 02 snt-probes type binary 32. 02 rcv-probes type binary 32. END. DEF ZARP6State. 02 snt-arpreq type binary 16.
02 rcv-ourreports 02 snd-reports END. type binary 16. type binary 16. DEF ZSOCK6Data. 02 bcast-allcpus-sent type binary 32. 02 Word type binary 16 redefines bcast-allcpus-sent. 02 bcast-onecpu-sent type binary 32. 02 bcast-rcvd type binary 32. 02 migr-sent type binary 32. 02 migr-cont-sent type binary 32. 02 migr-rcvd type binary 32. 02 migr-cont-rcvd type binary 32. 02 migr-timedout type binary 32. 02 migr-uxp-rcvd type binary 32. 02 migr-cont-uxp-rcvd type binary 32. END. DEF ZSOCK6State.
DEF ZLOOP6Data. 02 who-tcp-sent type binary 32. 02 Word type binary 16 redefines who-tcp-sent. 02 who-tcp-rcvd type binary 32. 02 who-udp-sent type binary 32. 02 who-udp-rcvd type binary 32. 02 have-tcp-sent type binary 32. 02 have-tcp-rcvd type binary 32. 02 have-udp-sent type binary 32. 02 have-udp-rcvd type binary 32. 02 packet-sent type binary 32. 02 packet-rcvd type binary 32. 02 update-sent type binary 32. 02 update-rcvd type binary 32. END. DEF ZLOOP6State. 02 who-tcp-sent type binary 16.
02 tx-looped-mcasts 02 trl-trfailure 02 enc-allocfailed 02 rip-noproto 02 rip-nospace 02 rip-delivered 02 rip-allocfailed 02 rip-tooshort 02 rip-badcksum 02 frag-packets 02 frag-fragments 02 frag-nofragpart 02 frag-badhopbyhop 02 frag-ufpbadalign 02 frag-ufptoobig 02 frag-hdrtoobig 02 frag-jumbo 02 frag-allocfailed 02 reas-fragsrcvd 02 reas-pktsreass 02 reas-timeout 02 reas-copy 02 reas-ufptoobig 02 reas-badfraglen 02 reas-payloadtoobig 02 reas-overlap 02 reas-dupfrag 02 reas-jumbo 02 reas-allocfailed 02 fw
02 tx-multicast 02 tx-forward 02 tx-attempts 02 tx-failures 02 tx-looped-mcasts 02 trl-trfailure 02 enc-allocfailed 02 rip-noproto 02 rip-nospace 02 rip-delivered 02 rip-allocfailed 02 rip-tooshort 02 rip-badcksum 02 frag-packets 02 frag-fragments 02 frag-nofragpart 02 frag-badhopbyhop 02 frag-ufpbadalign 02 frag-ufptoobig 02 frag-hdrtoobig 02 frag-jumbo 02 frag-allocfailed 02 reas-fragsrcvd 02 reas-pktsreass 02 reas-timeout 02 reas-copy 02 reas-ufptoobig 02 reas-badfraglen 02 reas-payloadtoobig 02 reas-ove
02 rcv-badreports 02 rcv-ourreports 02 in-dst-unreach 02 in-packet-too-big 02 in-time-exceeded 02 in-param-prob 02 in-echo-request 02 in-echo-reply 02 in-mld-query 02 in-mld-report 02 in-nd-router-advert 02 in-nd-neighbor-solicit 02 in-nd-neighbor-advert 02 in-nd-redirect 02 out-dst-unreach 02 out-packet-too-big 02 out-time-exceeded 02 out-param-prob 02 out-echo-request 02 out-echo-reply 02 out-mld-report 02 out-mld-reduction 02 out-nd-router-solicit 02 out-nd-neighbor-solicit 02 out-nd-neighbor-advert 02 n
02 in-echo-request 02 in-echo-reply 02 in-mld-query 02 in-mld-report 02 in-nd-router-advert 02 in-nd-neighbor-solicit 02 in-nd-neighbor-advert 02 in-nd-redirect 02 out-dst-unreach 02 out-packet-too-big 02 out-time-exceeded 02 out-param-prob 02 out-echo-request 02 out-echo-reply 02 out-mld-report 02 out-mld-reduction 02 out-nd-router-solicit 02 out-nd-neighbor-solicit 02 out-nd-neighbor-advert 02 nd-badsolicit 02 nd-badadvertise 02 nd-badoptions 02 nd-badcachelookup 02 nd-badcacheupdate 02 nd-badredirect 02
02 02 02 02 02 02 02 02 02 02 02 02 02 END. ARPState IGMPData IGMPState SOCKData SOCKState MONGQData MONGQState LOOPData LOOPState IP6Data IP6State ICMP6Data ICMP6State type type type type type type type type type type type type type DEF zSubnet6Data.
02 mmacerrors 02 mmactimeouts 02 tcp-filters 02 tcp-filters-err 02 tcp-filters-dereg 02 udp-filters 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. 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 16. 16. 16. 16. 16. 16. 16. 16. 16. 16. 16. 16. 16. 16. DEFINITION SUBNET-Stats2. !Description..
02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 END. word sysname P-key-x Q-key-x event Type AggRec Spare OpText Status OpState Error ErrorState Data State type type type type type type type type type type type type type type type DEF ZPORT6Data.
02 02 02 02 02 02 02 02 02 02 02 02 END. zproto zlport zloc-addr zfport zforgn-addr zsend zrecv family zloc-addr6 zloc-filler zforgn-addr6 zforgn-filler type type type type type type type type type type type type binary binary binary binary binary binary binary binary binary binary binary binary 16. 16. 16. 16. 16. 16. 16. 16. 16. 16. 16. 16. DEFINITION PORT-Stats2. !Description.............Sect 02 system type binary 16 occurs 4 times. ! system name 02 word type binary 16 redefines system.
02 ztotal-net-req 02 ztotal-user-req END. type binary 16. type binary 16. DEFINITION TELNET-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. ! enform q-key extended 02 event type *. ! ts, interval & info 02 Type type binary 16.
02 02 02 02 02 02 02 02 02 02 END. zbkup-cpu zbkup-pin zbkup-fnum zproto zlport zloc-addr zfport zforgn-addr zsend zrecv type type type type type type type type type type binary binary binary binary binary binary binary binary binary binary 16. 16. 16. 16. 16. 16. 16. 16. 16. 16. DEFINITION PORT-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 02 02 02 02 02 02 02 02 END. zforgn-addr6 zforgn-word zforgn-filler zcaller-addr6 zcaller-word zcaller-filler Openers Processes Active type type type type type type type type type binary binary binary binary binary binary binary binary binary 64. 16 redefines zforgn-addr6. 64. 64. 16 redefines zcaller-addr6. 64. 32. 32. 32. DEF ZWindowState. 02 zdata-transfer type binary 16. 02 Word type binary 16 redefines zdata-transfer. 02 zuser-bytes type binary 16. 02 znet-bytes type binary 16.
02 State END. type ZWindowState. ! WINDOW states TELNET SERVICE Entity Description ASAP 2.8 * This defines the structure written to ASAPCOL by the TCPIP SGP DEF ZServiceData. 02 ztotal-wins 02 Word 02 ztotal-sessions 02 ztotal-aborts 02 ztotal-inuses END. type type type type type binary binary binary binary binary 32. 16 redefines ztotal-wins. 32. 32. 32. DEF ZServiceState. 02 ztotal-wins 02 Word 02 ztotal-sessions 02 ztotal-aborts 02 ztotal-inuses END.
02 02 02 02 OpText OpState Error Error-State type type type type character 1 redefines op-text !Operational Status binary 16. !Operational State binary 64. !Error condition, if any binary 16. !Error state, 0 for remove 02 02 02 02 02 Tps Tps-State BeginTrans BeginTrans-State Catalog type type type type type float binary binary binary binary 64. 16. 16. 16. 16.
File RECORD File RECORD File RECORD File RECORD File RECORD File RECORD File RECORD File RECORD File is DBRDF. FIL. is DBFIL. SPL. is DBSPL. TAP. is DBTAP. TMF. is DBTMF. PRO. is DBPRO. COM. is DBCOM. TCP. is DBTCP. SWP. is DBSWP. Def is rdf-stats. Key 0 is p-key-x. End. Def is fil-stats. Key 0 is p-key-x. End. Def is spl-stats. Key 0 is p-key-x. End. Def is tap-stats. Key 0 is p-key. End. Def is tmf-stats. Key 0 is p-key-x. Def is pro-stats. Key 0 is p-key. End. End. Def is Com-stats.
File is $SWPDB. Def is Swp-stats. Sequence is Q-key-x. End.
