HP NonStop ASAP Client Manual Abstract This manual describes use of the HP NonStop™ Availability Statistics and Performance (ASAP) Client to monitor availability, state, and performance statistics that are collected by the ASAP Server. Product Version ASAP SE30V3.0 Supported Release Version Updates (RVUs) This manual supports D43.00 and subsequent D-series RVUs, G06.00 and subsequent G-series RVUs, and H06.03 and subsequent H-series RVUs until otherwise indicated by its replacement publication.
Document History Part Number Product Version Published 424820-001 ASAP SE30V1 December 1999 425263-001 ASAP SE30V2 June 2001 425263-002 ASAP SE30V2 October 2003 425263-003 ASAP SE30V2.5 October 2004 425263-004 ASAP SE30V2.8 January 2007 425263-005 ASAP SE30V3.
Table of Contents HP NonStop ASAP Client Manual........................................................................................ 1 Abstract ........................................................................................................................... 1 Product Version ............................................................................................................... 1 Supported Release Version Updates (RVUs) ..................................................................
Selecting Minimum State ............................................................................................... 52 Status of PC-Host Session ............................................................................................ 53 Rotate Graph Control .................................................................................................... 54 Refresh With Latest Data Button ...................................................................................
Show Related Apps ....................................................................................................... 78 Show Related Disks ...................................................................................................... 78 Show Related Processes .............................................................................................. 78 Show Related Expand Lines .........................................................................................
Enabled - EDL Entity Property ..................................................................................... 136 ErrorStateName - EDL Entity Property ........................................................................ 137 Help - EDL Entity Property .......................................................................................... 138 History - EDL Entity Property ....................................................................................... 138 KeyForNode - EDL Entity Property .
List of Figures and Tables Figure Figure Figure Figure Figure 1-1. Sample ASAP Client Screen ............................................................................. 24 1-2. ASAP Architectural Overview Diagram ............................................................. 27 1-3. OEM Architectural Overview Diagram ............................................................... 30 2-1. ASAP Installation Overview Diagram ................................................................ 31 4-1.
What’s New in This Manual New and Changed Information The fifth edition of the ASAP 3.0 Client supports the following features: HP ASAP 3.0 Availability Stats And Performance data can now be integrated with local/remote websites including optional integration with HP Systems Insight Manager (SIM). To add ASAP statistics to a website, do the following: a) Click the new WEBSITE button on Notify control panel. b) Select desired content: Score, Alerts, Detail, Entity, ..
Seven new TCP/IP EDL sub-entity definitions provide additional monitoring and goals for a total of 977 TCP attributes and 111 Telserv attributes. The total TCP/IP/TelServ entities monitored are 19 TCP subsystem entities and 1088 attributes. For more info about TCP/IP entities see the Asap3Sys.edl file. Summary of current TCP/IP Icons (new ASAP 3.0 entities are in bold).
New HTML Entity-Attribute Grid Reports allow interactive color-encoded gridgraph HTML reports. These reports can be accessed either via the Current Entity Report toolbar button that appears directly below the Entity drop-down on the main client window, or via FILE ... SAVE HTML as ... menu-items. For more information about interactive HTML reports, see Selecting an Entity on page 49; and the File... Save HTML as.... menu items.
and formatted in ASAP report windows. This new feature allows users to determine which files and processes are causing a disk, file, process, or processor to be busy. For details, see Show Related Measurement on page 79. Sort View columns are now auto-sized to the maximum heading and/or context size. For more details, see new section Sizing Sort View Columns on page 60 preceding the Browse Window Popup menus section.
A new Notify control panel allows you to configure sending of automatic alerts and reports. Notifications can be sent automatically via e-mail, wireless phone, pager, or Internet browser. For more detail, see Notify Control Panel on page 108. Notifications can be configured to be sent in either color-coded HTML format for use with e-mail or Internet servers and browsers or as plain text messages for use with wireless phones or pagers. See Notify Control Panel on page 108.
dashboard can contain a variety of graphs. As you define more dashboards, this menu grows dynamically, retaining each of your named dashboards. When the client is shut-down, graphic elements and associated properties are retained and upon startup are restored and become active elements once again. See View Menu Items on page 65. Graph Type is a new menu item on Dashboard graph windows.
Added information about the Icon Server Control Panel on page 97. Added information about trace audits to SSG Property Sheet on page 116. Added Section 6: Entity Definition Language (EDL).
About This Manual This manual describes the Availability Statistics and Performance (ASAP) product, which provides a network-wide system monitoring, statistics collection, and presentation infrastructure for NonStop systems. Using ASAP, you can monitor the performance and availability objectives of many entities, including Application, CPU, Disk, Expand, File, Node, Process, Processbusy, RDF, Spooler, System, Tape, and TMF.
Notation Conventions Hypertext Links Blue underline is used to indicate a hypertext link within text. By clicking a passage of text with a blue underline, you are taken to the location described. For example: This requirement is described under Backup DAM Volumes and Physical Disk Drives on page 3-2. General Syntax Notation This list summarizes the notation conventions for syntax presentation in this manual. UPPERCASE LETTERS Uppercase letters indicate keywords and reserved words.
TERM [\system-name.]$terminal-name INT[ERRUPTS] A group of items enclosed in brackets is a list from which you can choose one item or none. The items in the list can be arranged either vertically, with aligned brackets on each side of the list, or horizontally, enclosed in a pair of brackets and separated by vertical lines. For example: FC [ num ] [ -num ] [ text ] K [ X | D ] address { } Braces A group of items enclosed in braces is a list from which you are required to choose one item.
Punctuation Parentheses, commas, semicolons, and other symbols not previously described must be typed as shown. For example: error := NEXTFILENAME ( file-name ) ; LISTOPENS SU $process-name.#su-name Quotation marks around a symbol such as a bracket or brace indicate the symbol is a required character that you must type as shown. For example: "[" repetition-constant-list "]" Item Spacing Spaces shown between items are required unless one of the items is a punctuation symbol such as a parenthesis or a comma.
!i,o In procedure calls, the !i,o notation follows an input/output parameter (one that both passes data to the called procedure and returns data to the calling program). For example: error := COMPRESSEDIT ( filenum ) ; !i,o !i:i In procedure calls, the !i:i notation follows an input string parameter that has a corresponding parameter specifying the length of the string in bytes.
lowercase italic letters Lowercase italic letters indicate variable items whose values are displayed or returned. For example: p-register process-name [ ] Brackets Brackets enclose items that are sometimes, but not always, displayed. For example: Event number = number [ Subject = first-subject-value ] A group of items enclosed in brackets is a list of all possible items that can be displayed, of which one or none might actually be displayed.
%005400 %B101111 %H2F P=%p-register E=%e-register Notation for Management Programming Interfaces This list summarizes the notation conventions used in the boxed descriptions of programmatic commands, event messages, and error lists in this manual. UPPERCASE LETTERS Uppercase letters indicate names from definition files. Type these names exactly as shown.
Section 1: Introduction to ASAP This section provides an overview of the ASAP product: HP Availability Statistics and Performance (ASAP) software product provides an infrastructure for monitoring the availability and performance of system and application objects: System object information includes the operational status and performance of NonStop servers. Application information includes user-defined application domain availability statistics.
integrated in ASAP on one or more NonStop servers providing an overall view of entire application sets as they span one or more remote NonStop And Linux servers. Topic Page Feature Summary 24 ASAP Architectural Overview 26 ASAP Client Component Overview 27 OEM Architectural Overview 29 The ASAP Client graphical user interface (GUI), the primary data analysis interface to ASAP displays NonStop OS performance and state information, as well as customer application availability statistics.
Figure 1-1. Sample ASAP Client Screen Feature Summary The ASAP Client includes a powerful set of graphics, controls, and toolbars that help you browse, report, and analyze application and system statistics.
workstations connected by TCP/IP or asynchronous communications links to one or more NonStop systems.
Automated alerts and detailed notification reports that can be sent via wireless phone, pager, e-mail, or internet browser Reports that can be sent when objects change state, scheduled to report at various times of the day or stored for use in web content at the end of each analysis sample Dashboard views that can be named, saved, and displayed to provide unique sets of user-defined graphical views Reports can be obtained by selecting a busy object such as a disk, and then selecting Show Related Measurement
Figure 1-2.
Graph Window You can create one or more Graph windows from a Browse window. Graph windows are useful for maintaining multiple views of specific node-entity-object combinations. These windows update in real-time to reflect the nodes, entities, and objects you select. For more information, see Graph Window on page 75. Report Window You can get detailed reports about a selected node, entity, or object in Browse or Graph windows from context-sensitive pop-up menus.
OSC View You can use the Object State Change (OSC) view to obtain a history of object state changes. The OSC view provides both a high-level graphical overview and a detailed log of object state changes. The OSC scoreboard displays an annotated matrix summarizing the number and type of state changes that have occurred. The scoreboard contains a row for each entity type monitored and a column for each state monitored.
The ASAP subsystem communicates node, entity, and object information to the OEM Gateway. It reports object state information, so objects and their operational states are displayed in Enterprise Management Frameworks supported by OEM Gateway adapters. The OEM consists of a Server component and one or more Adapter components. Statistics agents such as the ASAP Client communicate with the OEM Server component.
Section 2: Installing ASAP Topic Page Installing Monitoring Components 32 Installing the SSG 33 34 Installing ASAP on the Workstation The ASAP GUI and Agent components running on your Windows workstation communicate with NonStop servers. ASAP uses the SeeView Server Gateway (SSG) to communicate with your NonStop OS node. Figure 2-1.
Installing Monitoring Components For a detailed description of how to install ASAP host components on local and remote NonStop servers, see the ASAP Server Manual and the ASAP Extension Manual. To install ASAP Server on the host: 1. Upload the ASAP Server files from the ASAP Server CD. 2. TACL 1 > LOGON network-group.userid 3. TACL 2 > VOLUME $ASAP-ISV-Volume.ZASAP 4. TACL 3 > OBEY INSTALL 5. Follow the directions for “Full Install on this node” in the online help. 6.
Installing the SSG For a detailed description of how to install the SSG on NonStop servers, see the SeeView Server Gateway (SSG) Manual. For D43 and later, the SSG is normally already installed on NonStop systems. If SSG is already installed, you do not need to reinstall it. To see if the SSG is installed on your local host node: TACL 1 > SSGCOM If START or STATUS commands are available from within SSGCOM, the SSG command interpreter, the SSG is installed on your system.
Installing ASAP on the Workstation How you install ASAP on your Windows workstation depends on whether you are installing from a CD or from a NonStop server. Installing ASAP From a CD ASAP is normally distributed on an HP Independent Product CD. To install ASAP from CD: 1. Insert the CD into your PC. 2. Run Setup.EXE. Setup runs automatically if the Windows AutoRun feature is enabled on your system. If AutoRun is not enabled, manually run Setup.EXE from the CD. 3. Follow the directions in Setup.
Section 3: Starting the ASAP Client Before running the ASAP Client, start the ASAP Server subsystem on your NonStop OS host systems by using the ASAP Server command interpreter START MONITOR and START COLLECT commands. For detailed information about installing and starting ASAP on the host, see the ASAP Server Manual.
Running the CSG You can start the CSG in two ways: Manually: Double-click the CSG.EXE file. Automatically: ASAP starts the CSG through ActiveX OLE automation. Either method is acceptable, but to fully understand the process you might want to manually start and configure the CSG the first time. Starting and Configuring the CSG Once the CSG is installed successfully, launch and configure it. The first time you click the Connect button, you need to configure the CSG for your workstation.
If you use an asynchronous connection to your host, select the Async property sheet; then specify the attributes for your connection. For example: Com Port: Com1 Baud Rate: 19200 Date Bits: 7 Stop Bits: 1 Parity: Even Flow Control: None Echo: Host Connection Type: Modem (Hayes Compatible) Phone Number: 555-1234 (if you are using a modem) 5. Select the Session property sheet to specify host connection options. For example: [x] Auto Logon [ ] Auto Logoff [x] Auto Start Session Host SSGCOM File Name: $SYSTEM.
Configuring a secure SSGCOM service This section describes the steps involved in configuring a secure, Telnet-based communication link for use by the ASAP Client. This section would be of interest if you are concerned about the possibility of user ID and password information being transmitted in clear text across the local network. By following the steps below, CSG and SSG can be configured in such a way that no logon userid or password information are required to the NonStop server.
TACL 3> SCF 1-> ASSUME PROCESS $TLSV 2-> ADD SERVICE ssgcom, PROGRAM $system.system.ssgcom, ACCESS ALL, SUBTYPE DYNAMIC, TYPE CONVERSATION, DISPLAY OFF, DEFAULT ON There is no requirement that the service name be “SSGCOM”. You can call the service whatever you’d like. Also, as mentioned above, by specifying “DEFAULT ON”, any user who connects to the port will be presented with an SSGCOM prompt.
Configuring CSG to use secure SSGCOM service If the NonStop server has been configured with an SSGCOM service as described in the prior section, you can configure the CSG to use the SSGCOM service to completely eliminate the need for userid's and/or passwords. To do this perform the following steps: 1. From the CSG main window, click on View…Options from the CSG main menu to bring up the CSG Options dialog, and click on the “TCP/IP” tab. 2.
4. If you configured the SSGCOM service with DEFAULT set to OFF (i.e. SSGCOM is not the default service), then set the “Host Service Name” field to “SSGCOM” (or whatever value you specified for the service name in step 2 of “Configuring NonStop server SSGCOM service” above).
5. Finally, you can disable all logon/security-related settings on the Session tab of the CSG Options dialog. These settings are no longer needed. In addition, if the PC you are configuring has previously been running the ASAP Client and CSG, you may want to click on the “Reset Security” button to clear saved ID and password information from the CSG. The Session tab should look something like this when you are done: You can now start the ASAP Client as you would normally.
Configuring ASAP Entities Once you establish a host connection through the CSG and the ASAP Host Session is enabled, ASAP automatically retrieves availability and performance information periodically. The ASAP update interval is based on the ASAP SET RATE configured on the host. For example, if the host sample rate is five minutes, the ASAP Client refreshes itself with host information every five minutes. The actual time of the ASAP Client update is automatically synchronized with the host update time.
For example, if you select Disk in your Client configuration but your ASAP host configuration does not have the Disk entity enabled with an ASAP SET DISK ON command, the Client cannot display disk information. You do not need to select an entity to get detailed reports about it. The Entity property sheet controls which entities are automatically downloaded and cached in the ASAP hierarchical cache memory.
Section 4: Using ASAP Using ASAP, you can obtain real-time and historic views of your NonStop OS to see everything from generalized overviews of availability and performance for system and application objects to detailed customized views of specific node-entity-object-attribute combinations. ASAP also provides a consistent viewing paradigm for all application domain and NonStop OS objects: Application, CPU, Disk, Expand, File, Node, Process, ProcessBusy, RDF, Spooler, System, Tape, and TMF.
OIL tree view Provides a hierarchical view of host nodes, entities, and objects so that you can view the overall availability and performance of many nodes, entities, and objects. 100 Availability and Performance icons are displayed in the OIL, guiding you to the nodes, entities, and objects with the highest alerts. Browse Window Use the Browse window to: View system and application statistics Browse and analyze nodes, entities, and objects status and performance: a.
Display Disk entity information Display Expand entity information Display File entity information Display Process entity information Display ProcessBusy entity information Display RDF entity information Display Spooler entity information Display System entity information Display Tape entity information Display TMF entity information Select All objects for the current node-entity Select First object in the Object drop-down list Select Last object in the Object drop-down list Select Previous object in the Obj
\Chicago, \Newyork, and \Sanfran, these node names appear in the ASAP Node dropdown list. To select a node using the Node drop-down list: 1. Click the arrow in the Node drop-down list. 2. Select the desired node from the list, or choose all items in the list by selecting the asterisk (*).
To see the previous view, select View... Back. To see the next view in the history, select View... Next. Selecting an Entity Entities include classes of objects such as CPUs, Disks, Expand lines, and Processes. You can change the entity displayed in the Browse window using the Entity drop-down list or the Entity toolbar buttons. The Entity drop-down list contains only entities that are enabled.
Considerations You can add or remove entities from the ASAP environment using the EDL language. For more information, see Section 6: Entity Definition Language (EDL). You can dynamically configure icons using the Icon Server. For more information, see Icon Server Control Panel on page 97. To obtain HTML Entity-Attribute Grid reports: 1. Click the Current Entity toolbar button to generate HTML Reports for either the current entity or for all enabled entities.
Selecting an Object To change the object or objects displayed in the Browse window, use the Object dropdown list. The object names in the Object drop-down list depend on which host entities your ASAP host configuration monitors. For example, if AsapMon processes are running on a node but do not have the currently selected entity enabled on the host node, the Object drop-down list is empty for that entity because the host systems are not configured to report on objects under this entity.
Slow workstation responsiveness might indicate that you are trying to display too many samples. When your workstation does not respond in a reasonable amount of time, try looking at data one node at a time or creating individual Graph windows for each node. For more information, see Browse Window Pop-Up Menus on page 60. Selecting Minimum State Figure 4-1. Minimum State Menu VST005.
To remind you that not all objects can be displayed, the Browse window status bar (at the bottom of the Browse window) displays the number of objects shown and found as a pair of numbers. For example, => 3/16 displayed in the status bar indicates the number of objects shown with state equal to or greater than the minimum state is 3 out of 16 total objects found. This reminds you that more objects might be found than actually displayed when Minimum State filtering is enabled.
window for a few minutes to see if ASAP recovers automatically. If it does not, stop and restart your Host Session. The communications link between the PC and host shows actual data movement when the ASAP Client is communicating with the ASAP Server. An explanation of the ASAP Client health indicators appears when you click the Communications Link icon between the PC and Host icons.
Suppress States Toolbar Button Use the Suppress States toolbar button to suppress state reporting for selected objects. To select a single object, click the row associated with the object in the data grid or graph portion of the Browse window. To select a range of objects, click and drag the range of rows in the data grid; the range is highlighted. Once you select the objects for state suppression, click the Suppress States toolbar button. You can also select Suppress States from the View menu.
Download Wizard Toolbar Button For help downloading statistics for analysis, use the Download Wizard. The Download Wizard lets you download data for a selected date, time, and sample interval. Normally, ASAP retrieves the most recent data in your host database. The Download Wizard lets you analyze data in the NonStop OS database for a different time or day, provided the database contains data for the specified time and date. To download data for a different date or time: 1.
Save EDL Button Click the Save EDL toolbar button to save your current environment in an EDL file. When you click the Save EDL button, entity, attribute, and data statements that describe your environment are saved in an ASAP Custom EDL file. You can exchange EDL files between different copies of the ASAP Client. Thus, you can copy a saved EDL file to another workstation so others can see the information displayed in your ASAP environment.
4. From the Font drop-down list, specify the font. 5. Use the Log command to display a list of recent performance monitor host log events for the specified node. 6. Use the Status Monitor command to display the status of the ASAP subsystems on the specified node. 7. Click the Save As toolbar button on the Command Wizard window to save the contents of the window to disk. To display help for the command wizard window, use the Help toolbar.
To specify additional options that control how ASAP accesses the OIL, use the OIL property sheet in the ASAP Properties window. Selecting Grid Rows and Columns You can select grid rows, columns, or cells in a Browse window. You can graph or copy selected cells to the clipboard using context-sensitive pop-up menus. To select a grid row, click the first element of the row; the entire row is highlighted. To select a grid column, click the heading of the column; the entire column is highlighted.
Sizing Sort View Columns Sort View column widths are automatically sized. To change the column sizing algorithm: 1. Select Sort View by selecting the View… Sort-Grid View menu item in the Browse window. 2. Move the mouse cursor over the area above the column headings and single-click. 3.
Show Object History Displays the recent history of object performance. The EDL Entity statement History property controls the behavior of this menu item. For more information, see History - EDL Entity Property on page 138.
Save grid data to a file in comma-separated-values format Copy grid data to the clipboard Clear the history for a particular object View the Host Session window Open the ASAP Properties window Create new instances of graphs for each node Arrange and tile Graph windows Minimize and restore Graph windows Open Help File Menu Items Menu Items Description New Creates a new instance of a Browse window. The new Browse window is created with node, entity, and object settings that match the current window.
entity definitions, you can select the file ASAPUSER in the dialog box, and then only user-defined EDL files will be downloaded. The EDL file name input field in the EDL download dialog box is a drop-down list of file names. Import EDL Imports additional entity and attribute settings from an EDL file. When you select this menu item, the EDL ADE source window appears. You then use this window to browse various EDL files. For more information, see Section 6: Entity Definition Language (EDL).
Edit Menu Items Menu Items Description Copy Copies selected grid rows, columns, or cells to the clipboard. Copy delimits data columns with commas. You can then paste clipboard information into a text window. From the File menu, select Save Data to save all of the information in the grid to a disk file. Copy HTML Select Copy to copy selected grid rows, columns, or cells to the clipboard in HTML text format. Copy HTML delimits data with color-coded state information.
Test Data Generates a set of random test data for the ASAP Client. When you select this menu item, a dialog box asks if you are sure you want to clear all ASAP data and generate a set of pseudo-data. To clear all data and generate a set of pseudo-data, click OK. To continue using ASAP leaving the view unchanged, click Cancel. Test data is defined by the EDL DATA statement. For more information, see EDL - DATA Statement on page 154.
Dashboard graphic properties are all saved whenever you select Save Dashboard As… or when the client is shutdown. Properties saved include Node, Entity, Object, Samples, and MinState, as well as each window location, size, and Graph Type. When the client is started, all graphic elements and associated properties are restored and become active once again. Graph Type is a new cascade menu item on Dashboard graphic windows.
Download Wizard Downloads statistics for analysis. The Download Wizard lets you download data for a selected date, time, and sample interval. Normally, ASAP retrieves the most recent data in your host database. The Download Wizard lets you analyze data in the database for a different time or day, provided the database contains data for the specified date and time. Command Wizard Displays the Command Wizard window. Use the Command Wizard to display host logs and subsystem status.
node, entity, object, samples, and minimum state settings for that view. This menu item serves the same purpose as the up arrow on the View Back/Next toolbar button. Next >> Browses forward through the view history. The Browse window retains the last two dozen view settings. You change these settings by selecting items in the drop-down lists along the top of the Browse window. Each time you select a different view, ASAP retains the node, entity, object, samples, and minimum state settings for that view.
OSC Window Toolbar Button Summary Find all items in change log related to the currently selected object Graph all items in change log related to the currently selected object Graph the most recently selected item in the log Acknowledge selected items in log Remove selected items from log Tile or dock window with Browse window Copy scoreboard and log information to clipboard Magnify or shrink scoreboard Display or hide date in state change log Show or hide scoreboard Show or hide statistics tips Show or hide
When you select a log item in the OSC change log and select Find Related, ASAP finds all state change instances in the OSC log for the object you selected. Each of these state changes is then also selected. You can then examine all state changes related to a given object and perform other operations on these items such as Acknowledge or Remove. OSC Graph Related Use the Graph Related function to analyze state changes related to the currently selected object.
To manually select multiple log items, for example the first three above at 11:00, 11:10, and 11:20, control-click them. To control-click multiple items in the log, hold down the control key while you click the log items you want to add to the selection list. To graph these items, select the Graph Selected menu item or toolbar button. If you select multiple log items and use the Graph Selected function, the selected items should all be log items for the same object.
OSC Copy Use the Copy OSC function to copy scoreboard and log information to clipboard. This function is useful when you want to include information from the OSC view in a Microsoft Word document or Excel spreadsheet. Copied information is delimited with tabs and carriage-return line-feeds so that you can paste it into an Excel spreadsheet. OSC Magnify Use the Magnify OSC function to magnify or shrink OSC window contents.
the cell that intersects the Disk row and the Down column, ASAP automatically selects all Down object state changes that have occurred on all disk drives. To select all state changes for a given entity, click the entity icon in the first column of the scoreboard. For example, if you click the CPU icon, all state changes for the CPU entity are selected. You can then use the Ack and Remove functions on the selected items.
in entity-state cells that do not represent state changes. As a result, only cells that represent state changes are annotated with colored state icons. When Show State Counts is enabled, and you click a cell in the scoreboard, the ASAP Browse window displays all objects that have a state greater than or equal to the selected state and entity. If you click a row icon in the scoreboard, all objects for that entity type appear regardless of their state.
Graph Window A Graph window provides a compact graphical performance view that is useful for maintaining multiple status-orientated views of various node-entity-object combinations. Each Graph window contains only one graph and can be made small enough to maintain numerous views at once. Graph windows update in real-time. Many Graph windows can be created from a Browse window, and can be automatically tiled or arranged.
Graph Window Pop-Up Menus Function Description Show Object Details Displays a graph and a list view of object details or opens a report window with detail information Show Object History Displays the recent history of object performance Graph Object History Displays recent object history of selected object Show Related Apps Shows applications related to the selected object Show Related Disks Shows disks related to the selected object Show Related Processes Shows processes related to the selecte
To copy and paste report window contents: 1. Select either no text to imply all text, or select only the desired text. 2. Select either the Copy menu item from the popup menu to copy all text. 3. Select the Copy Special menu item to copy text without headings and carriage returns. This subsection describes the available reports. Report windows contain reports that are either static or updated automatically over time. For more information, see Reports Auto Refresh Check Box on page 93.
Show Related Apps To display a report of applications related to the selected object, select Show Related Apps. When this report is generated, a query is first posted to your host system, and then the response appears in a scrollable view of application statistics information related to the selected object. If the selected object is a CPU or a Process, the report shows the application processes running in that CPU.
Show Related Measurement Select Show Related Measurement to configure and display detailed measurement on demand reports. When you select an object in a grid or graph and then select Show Related Measurement, an ASAP Measurement control panel is displayed with the options shown below. This allows a detailed measurement to be configured and started. Upon completion, it provides a series of in-depth reports that are automatically displayed in a report window.
Show Related Objectives To display a report of high and low objectives for the selected application domain, select Show Related Objectives. When this report is generated, a query is posted to your host system, then the response appears in a scrollable view of Application domain objectives related to the selected object. Session Window ASAP obtains object status and performance information via an active Host session to a NonStop Server.
View Menu Items Menu Item Description Statistics Displays host I/O statistics for your session. These statistics are used primarily for diagnostic purposes. Clear Log Clears the contents of the Session log. This is used primarily for diagnostic purposes. Version Info Displays version information for the CSGDLL, CSG, SSG, and SeeView products. This is used primarily for diagnostic purposes. Data Window Opens or gives focus to a Browse window.
Session Window Toolbar Buttons Start/Stop Session Toolbar Button Click the Start/Stop Session toolbar button to start and stop your Host Session. To start or stop your Host Session, click the button with the Tandem logo on it. The Start/Stop Session button appears pressed when ASAP is in session, and not pressed when ASAP is not in session. Save Session Log Toolbar Button Click the Save Session Log toolbar button to save the current Session log to disk.
Section 5: Configuring ASAP The ASAP Properties window gives you many options for customizing the ASAP environment, including the ability to specify which entities are retrieved from NonStop OS host systems, the attributes to display for each entity, the state determination algorithm for each attribute, and the font, graphing options, and host retrieval options to use. 1. Open the ASAP Properties window by doing any of: In the Browse window, select View>Options. In the Session window, select View>Options.
103 OSC Object State Change properties SSG Host Session properties for the Client Server and SeeView Server 116 Attribute Property Sheet The Attribute property sheet controls which entity attributes are displayed in grids and graphs, and their state determination algorithm. Entity attributes are the properties of an entity such as status, date, time, and busy.
2. Check the Show Attribute in Grid check box, or double-click the first column of the selected attribute. Show Attribute in Graph Check Box To display or suppress an attribute in the graph portion of Graph and Browse windows: 1. Select the attribute from the Attribute property sheet. 2. Click the Show in Graph check box, or double-click the second column of the selected attribute.
State Determination You can specify how the state of each attribute is determined when an attribute has its Show in Graph property set. For more information, see StateRule - EDL Attribute Property on page 153. In ASAP, each data attribute has a state associated with it when the attribute has its Show in Graph property set. ASAP assigns the state to that attribute based on the State Determination Option for each attribute.
For example, to set the State Determination rule for all StatePairs to UseStateGraphState, click the ALL button, then select the State Determination Rule labelled Use State...Graph State. Conversely, to set the State Determination rule for all StatePairs to UseThresholds, click the ALL button, then select the State Determination Rule labelled Use Thresholds. The Status attribute for the entity is not set to UseThresholds. By definition, its state determination rule is UseStateGraphState.
Use Value Graph Value Option The Use Value Graph Value option indicates that attribute state information is determined directly by the value of that attribute. This value is graphed. Entities such as App have user-defined metrics that provide both value and state information in ordered pairs of numbers; for example, Busy and BusyState. The metric portion is the actual value of the attribute, and the state portion is the entity agent’s state determination objective associated with the metric.
portion is the actual value of the performance attribute. The state portion is the entity agent’s state determination objective associated with the metric. When you select the Use State Graph State option, the state value is graphed and used to determine the state of the metric. When you choose this option, although the value of the state is graphed, the actual metric value appears in all numeric fields such as the grid portion of the Browse window, pop-up captions in the graph, and the OEM context fields.
The time required for data retrieval depends on the size of your NonStop OS network, the number of entities you select, the number of application objects, and the speed of your host connection: For a medium-size network (5 to 10-node), data retrieval for a few key entities takes up to 15 seconds. Retrieving the data for a 30-node network with many entities enabled can take several minutes.
Spooler Date, time, operational status of collectors, devices, print processes, supervisor processes, jobs, fonts, full, and primary and backup CPUs System Date, time, busy, queue, dispatch, disk I/O, cache hits, swaps, memory queue, and pages locked Tape Date, time, operational status of tape drive, drive subtype, label processing status, mount status, mount wait time, status of physical tape, tape label; process name, user ID, program filename of process using tape drive, and primary and backup CPU n
Annotate Grid With States Check Box To display state icons in the grid portion of all Browse Windows, check the Annotate Grid with States check box. When this check box is checked, a state icon appears next to the attribute with the highest alert state for each object graphed in the Browse window. The state icon that appears in the Browse window is the same icon that appears in the OEM, OIL, and any optional Enterprise Management Frameworks.
window or Graph Row/Column to display the selected row or column in the graph portion of the same window. Reports Auto Refresh Check Box To automatically refresh the contents of Report windows whenever ASAP performs a host sample update, select the Reports Auto Refresh check box. When this check box is not selected, Report windows are static, displaying data for the specific request that initially created the Report window. This data is not updated.
If you specify no password and no property sheets are protected, then you have reset property sheet protection. Other users can then enable property sheet protection. If you select the ALL checkbox, all property are selected. If you clear the ALL checkbox, all property sheets will be cleared. Show Help in Grid Check Box To display context-sensitive definitions of attributes when you move the mouse over data in the grid portion of the Browse window, select the Show Help in Grid check box.
Depending on server behavior, a removed object may reappear after it has been removed because some server entities continue to redisplay a removed object, or because the object may actually be re-created (for example, a process $name that comes back). If so, the object reappears in the client. If After N minutes is specified, and if the EDL Command associated with an entity supports an AGE N option, the value of N in the Delete Removed After N minutes dropdown should be greater than the value of AGE N.
Graph Color Sync Check Box To synchronize the color of graph elements to ASAP Utilization Threshold colors, select the Graph Color Sync check box. When you select this check box, graph elements that exceed utilization thresholds match the utilization threshold color for the object. Object colors in ASAP, OEM, and OIL are synchronized, indicating the relative utilization state of each object.
Max Graph Rows Drop-Down List The Max Graph Rows property lets you limit the maximum number of rows that appear in the Browse window graph and associated grid or list view. The primary purpose of this function is to avoid displaying too much information in the Browse window. Select ALL to remove the limit altogether. However, selecting ALL can lead to performance degradation when you display a large number of objects or rows.
For more information about configuring your own icons and colors, click the Help button on the Icon Server control panel. OEM Property Sheet The OEM property sheet controls how ASAP nodes, entities, and objects are displayed in the Open Enterprise Management (OEM) gateway. Also use this property sheet to control the display of availability and performance icons. Enable the OEM gateway when you want an enterprise management gateway view of nodes, entities, and objects known to ASAP.
The Show Context Values as Percent of Graph-Max option has no effect on the utilization threshold state reported for OEM objects. It simply controls how the value appears in the OEM Context field. Report on Objects in Related OEM Subdomain Check Box On the OEM property sheet, the Report on Objects in Related Subdomain check box controls how ASAP behaves when objects are selected in the OEM gateway. When this check box is checked, a selected object and all objects in the same subdomain are graphed.
heading property; for example, 98 66. Prior to value pairs, a context sting similar to Normal context appears. For example: \Chicago\Cpu\01:6:"Busy% 72 Up
When you click an entity or object in the OIL tree, the main Browse window to the right of the OIL displays availability and performance information for the selected object or objects. When you use ASAP with the OIL, the main ASAP Browse window is positioned to the right of the OIL window and resized to match the OIL window's size. You can then display Graph and Report windows to the right of the main Browse window.
If you do not check this check box, availability and performance utilization icons are not displayed in the OIL. OIL Thresholds Button Click the Thresholds button to open the Utilization Thresholds control panel. You can use this control panel to set performance utilization thresholds for your ASAP environment. You can also access the Utilization Thresholds control panel by clicking the Thresholds toolbar button in the Browse window or by selecting Thresholds from the View menu in the Browse window.
Setting an icon threshold value to 0 (zero) disables the display of an icon and all icons to its left. Setting an icon threshold value exactly equal to the slider on its right nullifies that icon because icons to the right have higher priority. Each slider controls the percent utilization threshold level where its icon appears in the OIL or OEM.
Specify whether state change upgrades are monitored Specify whether state change downgrades are monitored Specify the minimum state change monitored Specify the maximum number of changes to be retained Specify how late data integrity checks are performed Specify an audible alert state change threshold To configure e-mail, wireless phone, and pager alerts and report notifications Monitor Object State Changes Check Box The Monitor Object State Changes check box controls whether ASAP performs object state cha
improved. When the state of an object changes from Warning to Up, its state has improved. For operations management purposes, state upgrades are not always monitored. Operations management functions are typically concerned with tracking when things degrade. Downgrades occur when the state of an object has degraded. For example, when an object's state changes from Up to Down, the state of the object has degraded. For performance analysis purposes, both state upgrades and downgrades are sometimes monitored.
State Downgrades Monitored Check Box The State Downgrades Monitored check box controls whether state downgrades are monitored. When you select this check box and click the Apply button, ASAP monitors state downgrades. If you do not select this check box, state downgrades are not logged in the OSC log. State downgrades occur when the state of an object degrades. For example, when an object's state changes from Up to Down, the state of the object is said to have degraded.
Late Data Integrity Check Drop-Down List The Late Data Integrity Check drop-down list controls whether late data integrity checking is performed and, if so, how early or late data can be before it is flagged as a down time. When you select Automatic, ASAP automatically determines whether data received from each node, entity, and object is arriving in a timely manner. If not, ASAP flags the time for the object as down time.
change transitions below that state do not sound an audible alert but are still logged in the OSC log and appear in the OSC scoreboard. You can configure the audible alert sound. If you select Audible Alert State Threshold, a simple code string of dots and dashes appears. By specifying your own set of dots and dashes, you can create a unique code. For example, you might specify …---… to sound the morse code for SOS.
Test Button - allows you to test the current profile configuration. Show check box - indicates whether notifications should appear on your workstation. For example, if you select Show, and select a content style of HTML, whenever a notification occurs, a report will also appear on your workstation in an internet browser. If the content style is text, the report appears in a text file viewer; for example, Note Pad.
Notify Rule menu - ASAP determines when to send reports to you based on the Notify Rule setting. This menu allows you to control what conditions will cause a profile to send a notification. Notifications can occur: At periodic time intervals such as Every 1, 2, 3, 4, 6, 8, 12 ...
Color Max - indicates the color of all graphs in each row match the highest attribute state color for that row. Color Each - indicates the color of each graph for each attribute in a row is set to the state color of each attribute. Shade check box - alternately shade the background of every other row. Pages check box - reserved for future use. Shell Show check box - show shell launch window each time Shell file is shelled. This option is primarily for Shell debugging purposes.
ASAP file in a website directory. This path can be in an ASAP directory, or a customer website directory, or an HP SIM directory. One use of this option is as a dynamically updating web page. For example: 1. Specify Notify Rule - OnEachSample. 2. Specify desired Alerts, Scoreboard, Detail, Entity, Graphs, Icons, ... reports. 3. Specify Style - HTML. (Do not select Short) 4. Specify File such as …/inetpub/wwwroot/Alerts. 5. Specify Refresh - 30 Seconds.
D) For: Description, enter some descriptive text such as shown below Description, eg this is my custom tool [ ASAP home page ] E) For: Help comment, enter some text such as shown below Help comment, eg to use this tool type [ To access ASAP select this tool ] F) For: Menu placement, enter desired menu name as shown below Menu placement: help on menu place [ ASAP ] G) For: User account on target system that will be used, select Logged-in user as shown (*) Logged-in user H) For: Maximum number of targets the
Style Short Check Box - indicates reports should be extremely abbreviated. Select this check box if you want only brief Alerts, Score, and Details reports. This is especially useful if you are sending a report to a short text message device (for example, a wireless pager or a cell phone). Suggestion: To send notifications via a short message service such as an SMTP gateway, create a different profile for each report type, (Alerts, Score, and Detail), each with Short Text selected.
Importance Menu - defines the relative importance of the message. Standard levels of importance are Low, Medium, and High. If your notification is an alert, you probably will want to set the importance to High. Append check box - if selected, indicates text will be appended to the end of the message. If Style HTML is specified, appended text can be HTML. Otherwise it should be plain text.
Valid options for configuring access to intranet and or internet mail servers follow. You should contact your system administrator for assistance if you are not familiar with configuring access to e-mail servers. Three configuration possibilities: 1. POP and SMTP Server fields blank - leaving both the POP and SMTP fields blank allows you to use the ASAP notification mechanism locally, without sending e-mail or pager notifications.
Control whether the Client Server Gateway (CSG) is enabled Control the type of host retrieval option Control whether session tracing is enabled Specify the amount of object history to retain Access advanced properties Client Server Gateway Check Box The Client Server Gateway check box controls whether ASAP is in session with your host system. If this check box is not checked, there is no Host Session.
also specifies that ASAP performs synchronized updates based on the host data arrival rate from your remote host nodes (specified by the ASAP SET RATE command). When you select Automatic and a Host Session is in progress, the update interval automatically appears in parentheses next to the Automatic option. Automatic is the recommended setting. Fixed Interval To manually specify the ASAP update interval in seconds, select the Fixed Interval option.
Trace Replies Check Box To have replies from the host system traced in the ASAP Session window, check the Trace Replies check box. To view this trace, choose Session from the View menu of the Browse window. Because ASAP performance is degraded while tracing, you should usually disable tracing. Trace Audits Check Box To trace each entity sample in the ASAP Session window, check the Trace Audits check box. To view this trace, choose Session from the View menu of the Browse window.
For more information about how to configure the CSG Host Service Name property, run the CSG, select View... Options..., click Help, and view information on the Host Service Name field. Max Rows/Object Field ASAP maintains a hierarchical real-time data cache to minimize the amount of host I/O required for standard real-time displays and to provide improved response times for specific interactive queries.
CI Startup Vol Field The CI Startup Vol field specifies the default startup volume for the ASAP Server configuration. The default value when the field is blank is the $SYSTEM.SYSTEM subvolume. By default, the ASAP Client and Server normally use the configuration settings contained in $SYSTEM.SYSTEM.ASAPCONF. The default database used by the ASAP Client is specified in the $SYSTEM.SYSTEM.ASAPCONF file.
server on the host on startup. If you do not check the Exit Shutdown check box, the Client reuses the same command interpreter each time the ASAP client is started. Data Cache Check Box When you check the Data Cache check box, the object-state data cache contained in the ASAP Client is cleared when you click OK. Checking this check box erases and reinitializes all object-state data in the OIL, OEM, and ASAP.
Accept Server Initiated Flow Control Option The Accept Server Initiated Flow Control option lets the ASAP Server initiate I/O Flow Control to your ASAP Client if the ASAP Server SET IOCONTROL option is set. If you add this line to your ASAP Server ASAPCONF file, the ASAP Server globally initiates I/O Flow Control to all clients from the Server: SET IOCONTROL 64 For more information about this option, see the ASAP Server HELP SET IOCONTROL documentation.
Section 6: Entity Definition Language (EDL) ASAP provides an Entity Definition Language (EDL) that you can use to define abstract entities and their associated properties. To define entities, use ENTITY, ATTRIBUTE, DATA, and INCLUDE statements. The EDL lets you define system entities, customer application domains, and third party entities outside of the ASAP environment. Entities defined using the EDL are those entities for which ASAP provides monitoring services.
EDL Features and Terminology An EDL file is a text file with an EDL file extension. EDL files contain one or more EDL statements. EDL files provide a portable container for ASAP Client properties and data representing the client environment. When an ASAP Client is configured, users and developers can decide to share the EDL with other users or workstations. To share files, copy and mail the EDL file to another user or workstation.
Always - DATA statements will always be included in an exported EDL file. You might not want to select this option if you are monitoring a large number of objects. 5. Check the Entity Definition Language - Interactive Development Environment checkbox to enable the EDL menu items that appear under the File menu of the ASAP Browse window. 6. Check the Enable FILE... Compile Server EDL… menu item check box to enable server EDL download and compile.
EDL Term Description Entity Defines a class of objects such as a CPU, Disk, Expand, or Application domain. ENTITY statements are used to define entities to the ASAP environment. Attribute Defines a user-defined property of an entity. Use an ATTRIBUTE statement to define an entity attribute in EDL. Attributes include properties such as NodeName, CPU Number, CPU Busy, CPU Queue, and Transactions. Data statement Optionally defines a simple table of data to associate with an entity.
customize your ASAP environment, your customized settings are stored in file names such as: ASAP1 Custom.EDL ASAP2 Custom.EDL If you are communicating with the V1 ASAP server, the custom EDL file is named ASAP1 Custom.EDL. If you are connected to an ASAP V2 server, the EDL is named ASAP2 Custom.EDL. You can modify (and share) ASAP Custom EDL files.
distributed across different NonStop servers, and Client components and EDL files are also distributed across different Microsoft Windows workstations. ASAP Client EDL files do not have to include all entities known to the ASAP Server and Extension. You can choose to not define various entities, or to define only subsets of objects for an entity using the Command Entity property. For more information, see Command - EDL Entity Property on page 134.
All information about a compiled entity is saved in the ASAPn Custom.EDL file. When you later run the ASAP Client, it retains all imported entities and their property settings.
Exit Closes IDE window.
If there are syntax errors, the progress bar turns red and the source statement or token in error is automatically selected. Error messages appear in red below the source text. When you successfully compile entity definitions in the EDL environment, the progress bar turns green, and the definitions are automatically added to your ASAP Client environment. Once a compile completes, you can use the ASAP Client immediately to analyze data for that entity.
Command DataItems Detail Enabled ErrorStateName Help History KeyForNode KeyForObject KeyForRow MaxObjectives Rate Reserved SGPFile SGPManaged SGPSuffix Version 134 135 136 136 137 138 138 139 139 140 140 140 141 141 142 142 142 Example This example defines EDL properties of the CPU entity.
::= YES | NO | TRUE | FALSE ::= Numeric characters, such as 123 ::= Any Chars between double quotes, such as "Any Text, 123" ::= | | | Ci - EDL Entity Property Ci string The Ci entity property defines the name of the command interpreter that provides information for this entity. The default value is ASAP; use of other values is not supported.
ENTITY CpuSpecial CI Command Command Command Command ENABLED ASAP "CPU "CPU "CPU "CPU YES; \Chicago,RAW,TAB" \Newyork,RAW,TAB" \Tuson.0,RAW,TAB" \Tuson.1,RAW,TAB" ----- Chicago Newyork Tuson.0 Tuson.
DATAITEMS "0 I, 1 I, 2 M, 3 C" Detail - EDL Entity Property Detail string The Detail entity property controls how the Show Object Details popup menu item behaves. This property is optional. When a Detail string is not specified, the ASAP Client automatically displays a graph and a list view of object details. When a Detail string is specified, the contents of string are used to form a database query that is sent to the ASAP Server, and the result appears in an ASAP Report Window.
Examples ENABLED TRUE ENABLED FALSE ErrorStateName - EDL Entity Property ErrorStateName string The ErrorStateName entity property defines the name of the attribute that defines the error state for this entity. Entities are not required to have an error state attribute.
Help - EDL Entity Property Help string The Help entity property defines the help text associated with the specified entity. This text appears to the right of the entity name check box on the Entity Tab of the ASAP Properties window. Applies to: Client Default: HELP "" -– null Examples HELP "Central Processor Unit" HELP "Disk Volumes" History - EDL Entity Property History string The History entity property controls how the Show Object History popup menu item behaves. This property is optional.
HISTORY “CPU ^, TAB, SAMPLES 12” HISTORY “DISK ^, AVG, TAB, SAMPLES 12” KeyForNode - EDL Entity Property KeyForNode string The KeyForNode entity property is a string that defines a list of one or more data attribute names representing the column attribute names that define the node primary key for each object instance of this entity. For the CPU entity, the Node Key is the NodeName data attribute. That data attribute contains a string that represents the name of the node for each CPU entity instance.
KeyForRow - EDL Entity Property KeyForRow string The KeyForRow entity property is a string that defines a list of one or more data attribute names that represent the columns that uniquely define the row primary key for each object instance of this entity. For example for the CPU entity, the Row Key consists of the Date Time data attributes. These attributes contain values that, when concatenated together, uniquely define each row instance of this entity.
If the Rate property is not specified for a given entity, the entity sampling rate is determined by the global ASAP server SET RATE value. The ASAP Client uses a nonzero RATE associated with an entity to determine whether data for that entity is too late (or too early). Late data provides an overall health indicator for a given entity or subsystem because late data can indicate that an entity is down, hung, or that time of day is not synchronized between different nodes.
Default: SGPFile "" Examples SGPFile "$SYSTEM.SYSTEM.ASAPDSK" -- Disk SGP code file SGPFile "$SYSTEM.SYSTEM.ASAPEXP" -- Expand SGP SGPFile "$SYSTEM.SYSTEM.ASAPXSGP" -- App SGP SGPManaged - EDL Entity Property SGPManaged Boolean The SGPManaged entity property indicates whether the Statistics Gathering Process is to be managed by the ASAP subsystem. A managed SGP is one that can be started, get status, and shutdown via the ASAP STARTUP, STATUS, and SHUTDOWN commands.
The Version entity property defines the version number of the Entity definition. The version number is used by the ASAP Client and Server to validate that they are both using the same version of the Entity definition. Providing a version number on both the Client and Server lets the ASAP Client verify that the Entity definition on the Client matches the Entity definition on the Server. Although the Version property is optional, HP recommends that you always specify an entity version.
The notion of entity and attribute are synonymous with table and column in the SQL data model. An entity can be thought of as a table. An attribute can be thought of as a column in a given table. An attribute is a user-defined property of an entity such as Node Name, or CPU number. An attribute can also be a performance or state property such as a Status string attribute or its associated Operational State property.
AT NodeName GRID YES AT Sysnum GRID NO AT Cpu GRID YES AT Status GRAPH NO GRAPH NO GRAPH NO GRAPHMAX 0 GRAPHMAX 0 GRAPHMAX 0 HELP "NSK System Name"; HELP "System Number"; HELP "CPU Number"; HELP "Operational Status" AT OpState GRID YES GRAPH YES GRAPHMAX 0 STATEPAIR YES STATEISOP YES STATERULE UseStateGraphState TYPE CHAR5; GRID NO GRAPH NO GRAPHMAX 9 AT AT AT AT AT GRID GRID GRID GRID GRID HELP HELP HELP HELP HELP Date Time Valid CpuType ET AT Busy AT AT AT AT AT Queue Disp Disk Chit Swap NO YE
determine how best to align attribute data. The Align attribute property might not affect certain user defined attributes. Align Left causes the Client to left align data for the associated attribute. Align Right causes the Client to right align data for the associated attribute. Align “” causes the client to align data based on internal best-fit client rules. Applies to: Client Default: ALIGN "" Examples ALIGN LEFT ALIGN RIGHT ALIGN "" Format - EDL Attribute Property Format Fw.
Examples Format “F5.2” Format I8 Format S8 -- 12.45 -- 12345678 -- PathDown Graph - EDL Attribute Property Graph Boolean The Graph attribute property determines whether a user-defined attribute has state analysis performed on it by the ASAP Client. If the Graph attribute property is enabled (TRUE or YES), the attribute has a state assigned to it (either directly through client numerical analysis, or indirectly through an associated data, state pair).
The Graph-Max value appears in the ASAP Client as the unlabeled field immediately to the right of the Show in Graph check box. This value determines the maximum graph amplitude or normalization value for the attribute. For example, if the attribute Queue has a Graph-Max value of 10, and the value of the Queue attribute is 5, the Queue value appears in the graph at one-half of the maximum graph height.
If the Heading is not specified then it defaults to the attribute-name. If heading is specified it appears in the heading instead of the attribute-name. Applies to: Client and Server This property appears in the ASAP Client Properties window as the Attribute name.
Help - EDL Attribute Property Help String The Help string attribute property defines the Help text displayed by the ASAP Client when you move the mouse over a user-defined attribute in the grid portion of the ASAP Client Browse window. This help text also appears on the Attribute tab of the ASAP Client Properties window.
The MetricRule string contains a formula in ASAP extension format for the metric so that its value can be properly computed. See Format - EDL Attribute Property on page 146. Applies to: Server Default: null Examples AT TranCount METRICRULE "#1"; AT TranRate METRICRULE "#1/S" FORMAT F10.2; AT OkPercent METRICRULE "#1/(#0+#1)*C100" FORMAT F6.
user-defined attribute; for example, what type of number the attribute represents. For more information, see TypeData - EDL Attribute Property on page 154. Applies to: Client and Server This property appears in the Attribute tab of the ASAP Client Properties window.
Example AT Status GRID YES GRAPH YES GRAPHMAX 0 STATEPAIR YES –- Implies Status has associated state STATEISOP YES –- Implies State is operational state of obj STATERULE UseStateGraphState HELP "Operational Status"; AT OpState GRID NO GRAPH NO GRAPHMAX 9 HELP "Operational State of object"; StateRule - EDL Attribute Property StateRule String The StateRule attribute property defines how the ASAP Client determines the state of an attribute.
STATEPAIR YES STATERULE UseStateGraphState; TypeData - EDL Attribute Property TypeData String The TypeData attribute property defines the data type of a user-defined attribute. Possible data types are: INT | INT32 | INT64 | REAL64 | CHARnn Applies to: Server Default: NULL Example AT TranCount METRICRULE "#1" STATEPAIR YES STATERULE UseStateGraphState TYPEDATA REAL64; AT TranRate METRICRULE "#1/S" FORMAT F10.
Considerations Each record after the DATA statement is stored in the ASAP object cache for the entity specified as entity-name. The DATA statement must be terminated with a semicolon after the first record that does not begin with a backslash. Column widths are determined by the number of dashes in the heading for each column. Data record attribute properties must align with the corresponding dashes character underlining headings. Data records represent the contents of attribute data columns.
Example HP developers must be able to define system entities in one EDL file, perhaps named AsapSys. Users must be able to define application entities in EDL files of your own, perhaps one of which is named AsapApp. Using this approach, INCLUDE statements let you modify application entity definitions in AsapApp, and lets development organizations contain their system entity definitions in AsapSys, without either group having to edit files belonging to the other.
INCLUDE Asap2App; INCLUDE Asap2Sys; INCLUDE $SYSTEM.SYSTEM.ASAPEDL; INCLUDE Asap2App; INCLUDE Asap2Sys; When filename is partially qualified, the default path or subvolume for that file is the same as the path or subvolume of the parent file that included the INCLUDE statement. For example, if a file $SYSTEM.SYSTEM.ASAPEDL contains INCLUDE statements with simple file names, those INCLUDE files have a default subvolume of $SYSTEM.SYSTEM, which is the same as the parent EDL file name. INCLUDE $SYSTEM.SYSTEM.
INCLUDE INCLUDE INCLUDE INCLUDE Atm; Funds; Teller; $DATA.THIRD.PARTY; $Data.THIRD.PARTY: INCLUDE ACI; INCLUDE EDS; INCLUDE DATX; EDL-Relation Statement The RELATION statement allows you to define hierarchical relationships between EDL entities and container names. This aspect of EDL is sometimes referred to as RDL.
Applies To: Client Example --------------------------------------------------------------------- RELATIONs -- -------------------------------------------------------------------RELATION OBJECT * PARENT NULL; -- -------- Node container \Nodename RELATION OBJECT NodeClass PARENT NULL -------- TCPIP container \Nodename\Tcpip RELATION OBJECT PARENT NodeClass TcpipClass -------- ICMP IcmpClass RELATION OBJECT TcpICMP -------- IP IPClass RELATION OBJECT TcpIP -------- QIO QioClass RELATION O
RELATION OBJECT PortNumClass RELATION OBJECT PortPid1Class RELATION OBJECT PortPid2Class RELATION OBJECT TcpPORT PARENT PortClass Caption *; PARENT PortNumClass Caption *; PARENT PortPid1Class Caption *; PARENT PortPid2Class INSTANCE; -------- UDP \Nodename\Tcpip\Udp\$Ztc01 RELATION OBJECT UDPClass PARENT TcpipClass Caption RELATION OBJECT TcpUdp PARENT UDPClass INSTANCE; -------- TELSERV RELATION OBJECT "Udp"; \Nodename\Telserv TelservClass PARENT NodeClass Caption "Telserv";
MAP UdpClass TO TcpUdp; MAP TelservClass TO TelservProcess; MAP ServiceClass TO TelservService; MAP ServicePidClass TO TelservService; MAP WindowClass TO TelservWindow; MAP WindowPidClass TO TelservWindow; MAP ProcessClass TO TelservProcess; EDL-MAP Statement The MAP statement allows you to assign a relationship between an ObjectID and an Entity. An abstract ObjectID is used as a "handle" to declare hierarchical relationships using the Relation statement.
