READ THIS FILE COMPLETELY BEFORE BEGINNING PRODUCT INSTALLATION Copyright (C) 1999, 2001-2004 Hewlett-Packard Company Product Name: ASAP Client Product Marketing ID: SE30V2.5 Component Products: T0400AAE ASAP Client T0407V01 OVSPI T8481V30 CSG T8487V30 OIL T8486V30 OEM I. Basic Product Installation Instructions 1. Ensure that requirements for using this product are met (see Section II Product Requirements below). 2. Ensure that prerequisites for the installation utility and any product-specific installation requirements are met (see Section III Installation Prerequisites below). 3. Follow the installation instructions in Section IV below, to install the product on your workstation. 4. Follow the post-installation instructions in Section V below, after installing this product. II. Product Requirements: Client Requirements Required Hardware: 200 Mhz PC or faster Memory Requirement: 128 MB Minimum Disk Space: 30 MB Minimum OS Release: Windows 2003 or later Windows XP or later Windows 2000 or later Windows NT4 or later Windows ME/98 or later Server Requirements Required Hardware: K or S systems Minimum OS Release: NonStop Kernel D42 Minimum OS Gateway: SSGCOM T8488AAB 31MAR97 III. Installation Prerequisites: NONE IV. Installation Instructions: 1) Put the ASAP Client CD in your PC. 2) Run SETUP.EXE. The CD will Auto Run if AutoRun is enabled for Windows. 3) Follow directions displayed in Setup. V. Post-Installation Instructions: 1) See INSTALLATION and STARTUP sections of ASAP.DOC or ASAP.HLP for detailed info on getting started. 2) Review ReadMe addendum sections: - "Summary" - "Overview" - "New Feature History" - "Problems Corrected History" for a complete list of new features and problem fixes in this release. 3) HP OpenView Smart Plug-In for ASAP is included on the ASAP Client CD. This Smart Plug-In (SPI) allows you to share ASAP object state with HP OpenView. This Smart Plug-In is NOT required in order to install or use ASAP, but can be used to share ASAP availability stats and performance info with HP OpenView. To install the HP OpenView SPI for ASAP refer to the "OpenView SPI" directory in the ASAP Client CD. VI. Manuals Installed by this CD ASAP ..\Program Files\Tandem\ASAP\ASAP.DOC ASAP ..\Program Files\Tandem\ASAP\ASAP.HLP CSG ..\Program Files\Tandem\CSG\CSGUser.DOC ICON ..\Program Files\Tandem\IconServ\IconServ.DOC OEM ..\Program Files\Tandem\OEM\OEMServ.DOC OIL ..\Program Files\Tandem\OIL\OIL.DOC OVSPI..on ASAP Client CD in \OpenView SPI\.. VII. CD-ROM Root Directory Contents AUTORUN.INF Standard Windows Autorun file. Will start Setup.EXE if Autorun is enabled for your PC. LICENSE.TXT File containing limited-use Software Licensing Agreement with the licensing terms governing this product. README.TXT This file containing product and installation information. SETUP.EXE Standard Windows 95/NT SETUP. Run Setup to install product. ASAP Client Subdirectory containing product documentation. OpenView SPI OpenView Smart Plug-In for ASAP includes all files needed to share ASAP object state information with HP OpenView Operations for Windows. ________________________________________________ ADDENDUM - Summary - Overview - New Feature History - Problems Corrected History Summary ======= ASAP can now notify you via email, pager, phone, or internet browser when objects change state. Alerts can be sent to wireless phones or pagers. ASAP can now email detailed reports at user defined times of the day. ASAP Graph windows are now retained from one session to the next. Sets of Graph windows can be named/saved as complete dashboards. Different dashboards can be displayed as needed. Various graph types can be shown concurrently including 2D, 3D, Surface, Tape, ... graphs. Server sessions are now automatically recovered when host session failures occur. ASAP reports can now be saved in HTML, EXCEL, EDL, and raw TEXT formats. Analysis can now be displayed in Microsoft Internet Explorer, EXCEL, NotePad, and email readers such as Outlook. ASAP Client property sheets can be selectively password protected. The client environment can now be selectively secured. Domains that have been deactivated now appear gray even when time-state is up. EDL interactive development environment now loads EDL 10-100x faster. EDL can now be dynamically downloaded from NonStop servers and compiled several new ways. EDL can now automatically synchronize versions between client and server. A new HP OpenView Smart Plug-In for ASAP is included on the Client CD. The OpenView SPI can be used to share ASAP object state information with OpenView. HP OpenView is NOT required to deploy ASAP. Minor issues corrected as described below. Overview ======== ** HP Availability Stats And Performance (ASAP) provides a service level objective monitoring intrastructure for determining and sharing the availability status and performance of NonStop Kernel and OSS system, subsystem, and application domains. The ASAP product consists of three major components: Client, Server, Extension. This addendum includes late breaking news regarding the ASAP Client. The ASAP Client provides the following general functions: 1) A graphical user interface (GUI) for the analysis of ASAP object availability and statistics info. 2) A smart proxy plug-in or forwarding agent between HP NonStop Kernel and the Open Enterprise Management Gateway(OEM). The OEM allows object state info to be shared with other products, services, and frameworks. 3) Extended support for application objects defined via the ASAPX Application Extension API. 4) Notification reports and alerts automatically sent via email, pager, and wireless phone. ** The ASAP Client analyzes availability status and performance statistics for Systems, Subsystems, and Applications. Using ASAP, you can view and analyze either real-time or historical, network wide views of Application, Comm, Cpu, Disk, Expand, File, Node, Process, Processbusy, RDF, Spooler, System, SNA, Tape, TMF, and X25 entities. ASAP Views can encompass all of your NonStop nodes, reflect a selected set of nodes, or focus on a single node, entity, or object. The ASAP Client retrieves, analyzes, displays, and alerts statistics from the ASAP Server. The Server includes an optional API Extension that allows in depth monitoring of customer and third party application domains. ** ASAP Client can also forward object statistics and state information 3 ways: 1) Customer written plug-in adapters, or 2) Via standard eMail RFC 821 servers, or 3) Via enterprise management frameworks. Enterprise management framework notification occurs via the HP Open Enterprise Management gateway. The OEM gateway integrates object stats between the ASAP Client, the Object Integration Layer (OIL), and if present, user plug-in adapters, or enterprise management frameworks. To enable the OEM Gateway, select the "Open Enterprise Management" check box on the ASAP OEM property sheet. This allows availability, statistics, and performance info to be shared with the OEM. The OEM can also integrate object state info with enterprise management frameworks such as HP OpenView via smart plug-ins (SPI) such as the HP OpenView SPI for ASAP. New Feature History =================== ** [2.5.1125] A new menu item "Dashboard" has been added to the browse window. This new menu item allows you to name, save, and display graphic dashboards consisting of a variety of graph types and node, entity, object combinations. Select View... Dashboard to name, save or display a dashboard. Using this new menu item you can define a wide variety of App, Cpu, Disk, Expand, File, Process, RDF, Spooler, TMF, ... graphics. Dashboards can be named, saved, and displayed when you want to graphically review particular area(s) of your system. There are a variety of ways that new graphs may be created from the main ASAP Client Browse (graph/grid) window. See ASAP Client documentation for complete details. One easy way to create new graph views is as follows: 1) Compose the view you want to create in the browse window using the Node, Entity, Object, Samples, MinState drop down controls. 2) Optionally use 'Graph Object History' popup menu item to define the amount of history desired. 3) Double click the column "NodeName" heading in the grid area of browse window to create a new graph window. 4) Repeat this process for each element you want to add to the dashboard. ** [2.5.1125] Dashboard graphic properties are now all saved upon client shutdown. Properties saved include Node, Entity, Object, Samples, MinState, as well as window location, size, and Graph Type. Upon client startup all graphic elements and associated properties are restored and become active elements. ** [2.5.1125] "Graph Type" is a new cascade menu item on Dashboard Graphic windows. To select Graph Type, rightmouse on the existing graphic. When you select the Graph Type menu item, it displays a list of different graph types, selecting one changes the display accordingly. Graph type is now retained upon shutdown/startup and various node, entity, object graphs can have different graph types. ** [2.5.1024] NOTIFY - ASAP can now notify you via email, pager, phone, or internet browser when objects change state, or at certain times of the day provide you with detailed availability stats and performance reports. Notifications are configured using a new ASAP Notify control panel. This control panel allows you to configure ASAP to automatically generate reports and alerts. Notifications can occur: - When Objects change state. For example when objects go down, or when their state becomes critical, or when a process becomes too busy you can receive mail and/or have reports automatically displayed. - At periodic intervals. For example you can specify when you would like to receive detailed reports e.g. every 1, 2, 4, ... hours. - At specific times of the day. For example you can specify exact times when you would like to receive detailed reports e.g. every 1, 2, 4, ... hours. A wide range of notification reports are possible. You can customize notify rules and have multiple alert/report profiles. - Alerts Profile. You can configure a profile named "Alerts" to send alerts to your wireless phone notifying you of recent critical object state changes whenever critical/down object state changes occur. - Report Profiles. You can also configure other profiles to periodically send high-level as well as detailed reports to systems management personell at various user-defined times of the day. For example, you can specify one profile to report hourly, another to report semi-hourly with a different set of report criteria, and yet another to report at specific time intervals with varying degrees of detail. - Custom Profiles. You can also configure "background" profiles to send alerts, scoreboards, and detailed reports as web content. Using this technique reports can be viewed from web servers. Directories such as inetpub/wwwroot/ can be auto updated. Web content reports can be generated for any Profile via the File field. Notity rules are configured by clicking the "Notify" button on the Object State Change (OSC) Tab of the ASAP Properties window. New secure ASAP property sheet features described below allow you to secure the Notify control panel as well as any other property sheet. For a detailed discussion of Nofity control panel options see ASAP client help. Help is accessed via the HELP button on the new Notify control panel. ** [2.5.1024] A new Auto Restart Session check box has been added to the SSG tab of the ASAP properties window. This new checkbox is enabled by default allowing ASAP client to automatically restart the client/server gateway in the event of a CSG session failure. If you do not want the client to auto recover from session failures uncheck this checkbox. This option works best when the Host service is SSGCOM. To setup a SSGCOM host service on your server, enter HELP SET VERIFYUSER from within SSGCOM ci on the server. To configure a SSGCOM service from the CSG on your workstation, enter View... Options..., and then click help. ** [2.5.1021] New FILE... SAVE ... functions have been added to the main browse window. SAVE DATA, SAVE HTML, SAVE EXCEL have all been added and now automatically spawn the process associated with each file type, eg NotePad, Internet Explorer, or Excel. An EDIT... COPY HTML menu item has also been added to the EDIT menu. These menu items allow you to save, display, and copy data in HTML format for use from Browsers, Excel, email, etc... ** [2.5.1003] Secure Property sheets. You can now password protect ASAP property sheets. To password protect specific property sheet tabs, click on the Set Password button on the General TAB of the ASAP properties window. When Set Password dialog box is displayed, select check boxes corresponding to the property sheets that you want protected. Then enter a password and click the Set Password button. To access protected property sheets, display the ASAP properties window, and select the tab of a property sheet as you would normally. If a property sheet is protected, you will be prompted for a password to unlock the property sheets. Enter the correct password to unlock all property sheets until the properties window is closed. Considerations: - if you specify a password with no tabs protected, then you "own" the Set Password dialog box even thou there are no tabs protected. - if you specify no password and no tabs protected, then you have reset property sheet protection. And anyone can enable property sheet protection. ** [2.5.1002] Time-State Deactivation. The time-state of a domain that has been deactivated now appears gray. This is consistent with the color of the operational status of an object being gray when deactivated. Before, time-state appeared green even when a domain was deactivated using ASAP the RANK , DEACTIVATE option. Now when state determination is set to UseStateGraphState for the statepair attributes for a given entity, the overall domain will appear gray when it is deactivated. Note - If late-data integrity checks are enabled (OSC Tab of ASAP property sheet); And if a domain is late with its reporting of stats, that domain's time-state will be alerted in RED even when the domain is deactivated. This allows you to be aware of late data conditions even if a domain is deactivated. ** [2.5.1001] EDL IDE file browser loads files up to 10x faster due to new fileload method. ** [2.5.1011] EDL DOWNLOAD and COMPILE. You can now let ASAP client automatically download AND compile server EDL files. There are a variety of new ways that server EDL can be downloaded and compiled some automatic, so that you don't really need to worry about EDL synchronization anymore. 1) To download and compile server EDL in a single step, select: a) FILE... Compile Server EDL... the from main ASAP client window. b) Select the file to download, and click the DOWNLOAD button to initiate download and compile. 2) When an EDL entity version mismatch occurs, a new dialog box now allows you automatically synchronize EDL. Click Yes to initiate an automatic EDL download and compile. 3) You can now also download EDL from the server into the EDL development window to analyze, edit, and compile the server EDL in the interactive development environment (EDL IDE). a) Select FILE... IMPORT EDL... from the main ASAP client window. b) Select FILE... DOWNLOAD EDL... from the ASAP EDL IDE window. Or click Download toolbar button. c) Select the desired file to download. d) Click the DOWNLOAD button. ** [2.5.1010] Whenever the EDL download dialog is displayed, the client allows you to automatically download all ASAP server EDL, including files such as the ASAPnSYS, ASAPnAPP, and ASAPUSER EDLs. Or, if primary interest is to download USER entity definitions, you can select the ASAPUSER file. (note the EDL filename input field in the EDL download dialog is a dropdown list). ** [2.5.1010] The EDL Properties window has a new combo box labeled: "On EDL Compile..." This combo currently has two options: - Do not inherit prior entity properties - Inherit prior entity enabled property If you select "Inherit prior entity enabled property" the previous ENABLED property for pre-existing entities will be automatically retained regardless of the ENABLED property settings. For example, if you had an entity named TICKETS that was previously defined and enabled, then whenever you import and compile that entity, the ENABLED property setting will be retained regardless of the ENABLED property in the compiled EDL file. When compiling EDL from within the EDL interactive development environment, this option is deliberately ignored. Thus EDL IDE source settings take precedence when compiled from the EDL IDE window. ** [2.5.1007] EDL IDE settings can now be restricted by password protecting the Entity tab of the ASAP property sheet as described in the next new feature. For environments where you do not want server EDL to be downloaded, uncheck the "Enable FILE... Compile Server EDL..." check box on the EDL Properties window. NOTICE** access to all property sheet settings can now be password protected as described in the next topic. - - - - - - - - - - - - - - - - - - - - ** [2.0.2102] New Browse window VIEW... BACK and NEXT menu items allow you to Browse backward/forward thru the view history for the Browse window. ** [2.0.2102] New Browse window toobar button allows you to Browse backward and forward thru the view history for the Browse window. ** [2.0.2086] ASAP includes a new Object State Change View. The new OSC view provides a history of Object State Changes. To display the OSC view, select VIEW... State Changes... from the main ASAP Browse window. The following functions are provided in the OSC window. Note OSC functions can be accessed three ways: 1) By selecting View... 2) By Right mouse clicks on OSC objects 3) By Clicking Toolbar buttons. ** [2.0.2086] OSC View.. "Find Related" finds all state change instances for the object you have selected. When you select "Find Related", each state change for the currenly selected object is automatically located in the OSC log and selected. This allows you to operate on all state changes for a given object. ** [2.0.2086] OSC View.. "Graph Related" first does a Find Related, and then Graphs each of the log items that was found using the find related operation. This allows you to analyze information about a state change or a series of state changes for the same object. ** [2.0.2086] OSC View.. "Graph Selected" graphs state change items that are currently selected in the OSC log. This function can be also performed on a single log item by double clicking that item in the OSC log. ** [2.0.2086] OSC View.. "Ack Selected", "Ack Above", and "Ack All" menu items allow you to track and acknowledge state changes in the OSC window. Acknowledged items are marked so that when you leave your workstation and return, you can tell which items are new the OSC view. ** [2.0.2086] OSC View.. "Remove Selected", "Remove Above", "Remove All", menu items allow you to remove selected items. Removed items are removed from the OSC log so they no longer appear. Also, when an object is removed, it no longer appears in the OSC ScoreBoard. ** [2.0.2085] OSC View.. "Show ScoreBoard" displays an annotated matrix summarizing the number of state changes that have occured since you began your monitoring session. This view is useful for tracking state changes since you last cleared your display. For example, if you do a Remove All before leaving your ASAP workstation unattended, then when you return, you will see all new state changes that have occured since you left your workstation. ** [2.0.2085] The OSC ScoreBoard contains a row for each Entity monitored, and a column for each State monitored. The option, "Minimum State Change Monitored" on the OSC Tab of the ASAP Properties window controls which states are displayed in the OSC ScoreBoard. The entities selected on the Entity Tab of the ASAP Properties window controls which entities appear in the OSC scoreboard. ** [2.0.2085] Clicking OSC ScoreBoard elements causes the OSC log to be searched for all Object State Changes that match the selected Entity and State. For example, clicking a cell that intersects the Disk row, and the Down column will automatically select all "Disk Down" state changes in the OSC log. ** [2.0.2085] Clicking OSC ScoreBoard entity icons that appear in the first column of the scoreboard, causes ASAP to select all state changes for that entity. For example clicking the Cpu Icon causes all state changes for the Cpu entity to be selected in the log. ** [2.0.2085] Clicking OSC ScoreBoard state heading names eg "Down", causes ASAP to select all state change log items for that state, regardless of object type. ** [2.0.2084] OSC View.. "Show State Counts", displays the current number of objects in each state. Values in parenthesis are the CURRENT object state counts. Values that are not in parenthesis are state CHANGE event counts. This option is useful for reviewing the total number of objects that are currently in each given state. Note the difference, the first number represents state CHANGE counts, the second number in parenthesis represents the CURRENT number of objects in that state. When "Show State Counts" is enabled, clicking on an element in the matrix, causes all objects greater than or equal to that state to be displayed in the Browse Window, it also causes all log entries to be selected for the specified element in the matrix. ** [2.0.2084] OSC View.. "Show Magnified", causes the Icons and fonts in the OSC window to alternately be magnified or shrunk. ** [2.0.2084] OSC View.. "Show Date", causes the Date to alternately be displayed or hidden for each Object State Change log entry. ** [2.0.2084] OSC View.. "Show Tips", causes status and stats information to be automatically displayed as the mouse is moved over various elements of the OSC window. For example, when the mouse is moved over the ScoreBoard matrix, statistics are displayed about current object states and state changes. When the mouse is moved over the state change log, information is displayed about the number of times an object occurs in the log. ** [2.0.2083] OSC View.. "Tile", causes the OSC window to be "docked" adjacent to the ASAP Browse. ** [2.0.2083] OSC View.. "Copy", copies to Windows Clipboard the contents of the scoreboard, and the OSC log. ** [2.0.2083] OSC View.. "Thresholds", displays the ASAP Utilization Thresholds dialog box. ** [2.0.2083] OSC View.. "Options", displays the ASAP Properties window. ** [2.0.2083] OSC View.. "Refresh", refreshes the OSC window with the latest Log and scoreboard values. ** [2.0.2083] OSC View.. "Cancel", cancels the menu. No operation is performed. ** [2.0.2083] Help... "Contents", displays the table of contents for the online help. ** [2.0.2083] Help... OSC Window, displays detailed online help for all funtions provided in the Object State Change (OSC) window. ** [2.0.2082] "Max Graph Rows" is a new property that has been added to the Graph property sheet. It allows you to limit the maximum number of rows that will appear in all Graphs, Grids, and listviews. The primary purpose of this function is to avoid needless display of too much information in the Browse window. ** [2.0.2081] "Graph Object History" is a new menu item added to the Browse Window's popup menus. This menu item can be accessed by right mousing an object in the graph or grid in the Browse window. It allows you to "back fill" and analyze the history of any object that appears in the Browse window. Note this function allows you to quickly fill in the history for an object. ** [2.0.2081] "Clear Object History" is a new menuitem added to the Browse Window's Edit menu. This menu item allows you to clear any "back filled" history for an object that appears in the Browse window. ** [2.0.2071] A new OSC Tab has been added to the ASAP Properties window. This allows you to enable and configure Object State Change properties. The following options have been added to the OSC Tab: "Monitor Object State Changes" check box controls whether state changes are monitored. "Display Log Window" Check Box controls whether the OSC Window is displayed at Startup. "State Upgrades" and "State Downgrades Monitored" check boxes control whether state improvements or degradations are displayed in the OSC view. "Minimum State Change Monitored" combo box specifies the minimum state change threshold that will be monitored. For example, a setting of Critical would exclude all state changes to Up, Low, Medium, High, Warning states. "Maximum Change History Retained" combo box specifies the maximum number of state change records that will be retained in the OSC log. "Late Data Integrity Check" combo box specifies whether Late Data checks will be formed on each data record received. No Check - Disables Late Data checking Not recommended. You can miss down sub/systems. Automatic- Enables Late Data checking. Automatic is recommended. - Enables Late Data checking. Adds to automatic late data check. Basically 2 x sample Rate + . But not to exceed 5 minutes. "Audible Alert State Threshold" combo box specifies whether audible alerts are sounded when an Object State Change occurs where the new state is greater than or equal to the value specified. ** [2.0.2068] An "ALL" button has been added to the Attriute Tab fo the ASAP Properties window. Click this button to select all StatePair Attributes for an Entity. State Pair Attributes are those attributes that can have their state determined with the new ASAP server RANK command. Properties that are not state pairs, will not have their State Determination Rule changed. ** [2.0.2067] Host Session DOWN events are logged in Object State Change view. ** [2.0.2067] Host Session UP events are logged in Object State Change view. ** [2.0.2062] The ASAP Client includes a new Entity Definition Language. The EDL language allows you to externally define and alter object definitions. EDL files allow System entities, Customer Application domains, as well as Third Party entities to be defined. An EDL file is a text file containing EDL statements. Entities are defined using ENTITY, ATTRIBUTE, DATA, and INCLUDE statements. These statements are used to define one or more ASAP entities and associated attributes. ** [2.0.2062] Access to the EDL IDE (Interactive development environment) is now disabled by default. To enable the EDL IDE, do the following. From the ASAP Browse Window select: 1) View... Options... 2) Select Entity Tab 3) Click Entity info .. button 4) Check EDL IDE checkbox 5) Click OK ** [2.0.2061] Right Mouse or Double Click on an Entity name on the Entity Tab of the ASAP Properties window to display EDL Entity info. FILE... DELETE ENTITY... allows you to manually delete a selected entity. EDIT... COPY allows you to copy the EDL for a single entity. ** [2.0.2062] A new DETAIL option was added to the EDL ENTITY statement. The Detail option defines the command that will be used when the "Show Object Details" menu item is selected in the ASAP Browse window. ** [2.0.2062] A new HISTORY option was added to the EDL ENTITY statement. The HISTORY option defines the command that will be used when the "Show Object History" menu item is selected in the ASAP Browse window. ** [2.0.2062] A new VERSION option was added to the EDL ENTITY statement. The VERSION defines the version of the the ENTITY. This version string is used to verify that the version of the Entity definition known to the ASAP client matches the version on the ASAP server. ** [2.0.2062] The EDL IDE editor now provides Right Mouse CUT/COPY/PASTE Popup menu functions. ** [2.0.2061] A check was added to the EDL compiler to detect missing Attribute declarations when attribute names are specified in the KEYFOR.... Entity properties, but the Attributes are not declared in subsequent EDL. ** [2.0.2061] Entities are now added in alphabetical order to the Entity Info table. They also now always appear in alpha order on the entity tab of the ASAP properties window. ** [2.0.2036] EDL files for App, Cpu, Disk, Expand, File, Process, RDF, and System were updated. ** [2.0.2035] EDL files are portable. They can be copied from one PC to another. EDL files can contain both entity definitions and they can also contain Data. You can share your ASAP environment with other users. Sharing is achieved by copying or mailing the EDL file to other user workstations. ** [2.0.2034] New FILE... IMPORT/EXPORT EDL menu items have been added to the main ASAP Browse window. These menu functions allow you to export your environment, and also to open the EDL Compiler development window. ** [2.0.2019] The EDL Compiler window provides online HELP for Entity Definition Language statements. HELP for EDL grammar can be obtained in the EDL Compiler window by moving the cursor to the syntactical element in question and pressing the F-1 Key. ** [2.0.2018] Entities can be dynamically added to the environment using the new FILE... IMPORT EDL function. Importing allows HP, Customer, and 3rd party ENTITY definitions to be added to your ASAP environment. By importing EDL files, ASAP can be infinitely extended. ** [2.0.2017] the Browse window has a new floating Entity toolbar. The toolbar can be moved anywhere within the graph area of the browse window. However, the best location for it is the upper left corner, which is the default. The toolbar dynamically resizes when new entities are added to the environment with the IMPORT EDL function. This toolbar can include both user defined application Icons and standard HP system icons. ** [2.0.2016] A new EDL Compiler window allows access to the EDL Development Environment. With this window you can interactively edit, develop, compile, and test new entity definitions. ** [2.0.2015] ASAP Version V1 and V2 EDL files are now automatically installed in the Program Files\Tandem\ASAP\EDL directory. See ASAP1/2 Factory EDLs. ** [2.0.2014] ASAP 2.0 Client now detects the version of the ASAP Server, and if needed switches to the correct EDL file for that server. Thus ASAP 2.0 Client can be used to view ASAP 1.0 Servers. ** [2.0.2013] EDL includes a new DATA statement. The DATA statement allows you to store test DATA along with ENTITY and ATTRIBUTE definitions. Either pseudo or real entity data can be stored within an EDL file. ** [2.0.2012] A new EXPORT EDL function allows an entire ASAP Client session, along with the data retrieved from host servers to be exported into an EDL file. This can be mailed and viewed later from other ASAP Clients on other PCs. ** [2.0.2011] ASAP now registers EDL file extensions are now Microsoft Windows. Thus EDL files can be viewed by double clicking an EDL file from the MS-Windows Explorer. This launches ASAP, when then automatically compiles the EDL file, and graphically displays entities and associated data contained in the EDL file. ** [2.0.2006] User Customization of ASAP State Icons and Colors is now officially supported. A new Icon configuration dialog allows users to select their own State Icons and Colors. You access the Icon Server by selecting the button named "ICONS" on the General Tab of the ASAP Properties window. ** [2.0.2006] Client includes online HELP for the Icon Server. You access the Icon Server by clicking the "ICON" button on the General Tab of the ASAP Properties window. A detailed explanation of how to customize Icons can be obtained by clicking the HELP button on the Icon Server control panel. ** [2.0.2005] OIL Customization of ASAP State Icons and Colors is now supported. The ASAP OIL ActiveX server now uses Icons that are configured with the Icon Server. ** [2.0.2005] OEM Customization of ASAP State Icons and Colors is now supported. The ASAP OEM ActiveX server now uses Icons that are configured with the Icon Server. Problems Corrected History ========================== ** [2.0.2116] Previously when the regional locale of a workstation did not match comma/period usage for decimal and thousand separator on the NonStop server, a regional locale dialog box would appear at startup and request that workstation settings be changed to match NonStop server locale settings. There is now a new Regional Locale dialog box that provides the following options: - Change PC Regional Settings to be the same as NonStop Server - Keep Current Regional Settings - Keep Current Regional Settings and NEVER show this dialog again Regardless of the setting selected, fractional numbers in EDL DATA statements should always use a period character to delimit the decimal point, since EDL files are shared and cross compiled on both NonStop servers and Windows workstations. ** [2.0.2116] Previously the Client would not scale and graph values correctly when workstation locale settings for the use of decimal and numeric grouping separators were different than definitions used by NonStop server. ASAP Client can now operate with different regional locale settings. The old Locale dependent conversion functions have been replaced by new locale independent functions. Thus scaling and graphic intperpretation of all values now works correctly regardless of regional settings. ** [2.0.2116] Previously redundant Unicode to Ansi conversions could occur. Now redundant conversions are eliminated when compiling EDL Entity and Attribute statements. This change improves EDL compiler performance by at least 4x. ** [2.0.2116] Previously the client accepted server initiated I/O flow control but would not by default initiate I/O flow control itself. However, server initiated flow control only occurs when the ASAP ci SET IOCONTROL option has a nonzero value. If option SET IOCONTROL 0 was added to file $System.System.ASAPCONF, flow control was turned off. This problem has been corrected by making the Client default be: Enable Flow Control. To control this option setting from the main ASAP Client browse window: - Select VIEW... OPTIONS... - Click on the SSG Tab - Click on the Advanced button - Select I/O Control options ** [2.0.2116] Previously, the OEM was not always displayed when it was first started from ASAP. The OEM is now always displayed on startup and the default view is the Custom Alerts view. If the user has not configured a custom alerts view, ASAP will create one for the user and attempt to place it in the ..\Oem\Views\Alerts.Oem file. ** [2.0.2116 Certain versions of Windows use the registry setting "ForegroundLockTimemout". This prevents applications from taking focus. Whether this is a problem is subject to user interpretation. If you consider this a problem, it can be overcome by downloading and installing the Microsoft TweakUI control panel from: http://www.microsoft.com /ntworkstation /downloads /powertoys /networking /nttweakui.asp ** [2.0.2115] Previously, when the CSG was configured to use SSGCOM as a telnet service, the connection attempt could fail if SSGCONF file contained more data than typical. This problem has been corrected by incorporating CSG version 3.0.2. ** [2.0.2114] Previously, when the host session was first started, under certain rare circumstances an additional 20-30 second delay would sometimes occur during the initial connection sequence. This problem has been corrected. ** [2.0.2114] Previously, when the Browse window was selected and the tab key was pressed, there was an invisible tab in the tab order. This problem has been corrected. ** [2.0.2113] Previously, on a Page Down operation the Microsoft Grid control would sometimes return a "memory could not be read error". This problem is fixed. ** [2.0.2112] Previously, fonts were sometimes vertically truncated in the Browse window Data Grid. This problem has been corrected. ** [2.0.2112] Previously, when POPUP menu item "Show Object Details" was selected for a FILE entity subvolume that had multiple generic peer names, eg: $data.name, $data.namea, $data.nameb; subvol information was returned for all subvols matching the generic name. This problem has been corrected so that only info for the "exact" subvolume is now displayed. ** [2.0.2112] Previously, when POPUP menu item "Show Object Details" was selected for a FILE entity subvolume that had no errors, but contained hundreds of files, all files in that subvol were accidentally displayed. This problem has been corrected. ** [2.0.2112] Previously, the EDL file for Asap1Sys.edl did not include entity version numbers. This problem has been corrected. ** [2.0.2112] Previously, the EDL IDE window was not documented. A new section, EDL IDE, has been added to ASAP documentation and the online help. ** [2.0.2106] Previously, popup menu "Show Object Details" did not check if the Host Session was enabled. This problem has been corrected. ** [2.0.2105] Previously, the APP entity EDL command did not use the AGGREGATE option. Now the APP entity displays aggregates. ** [2.0.2105] Previously, the OEM minimum state "spinner" control was not always visible when an OEM alert window was re-sized. Now the minimum state spinner remains visible, even when the custom alert window is resized. ** [2.0.2105] Previously, the OEM minimum state "spinner" control was not present on OEM custom alert windows that had specified selection criteria. Now minimum state spinners are always present. ** [2.0.2105] Previously, popup menu item "Show Related Objectives" only allowed RANK ,LIST operation. Now you can select the RANK option: - INFO for objectives from the DB. - LIST for objectives from the SGP. ** [2.0.2104] Previously, the browse View...Back/Next function would reset its position when the browse window was updated. View... Back/Next now maintains it position in the view history, even when updates occur. ** [2.0.2101] Previously, when popup menu item "Show Related Apps" was selected when either the Cpu or ProcessBusy entity is displayed in the browse window, an APP DETAIL command was issued, but the DETAIL option was not supported when the entity is not specified in the APP command. This has been fixed by not requesting a DETAIL option when a cpu is selected. ** [2.0.2100] Previously, when the OEM or OIL would send Tile/Move window requests to ASAP client, the client did not include the OSC window in the tile/move operation. This has been corrected. ** [2.0.2100] Previously, ASAP shutdown with Windows 2000 was slower than it should have been due to delays in class terminate events. This has been corrected. ** [2.0.2100] Previously, you could not save the contents of the Command Wizard window directly to disk (without first copying it). This problem has been addressed by adding a SAVE AS button to the Command Wizard window. ** [2.0.2100] Previously, HELP was missing for cetain funtions. This has been corrected. Also HELP for State Determination, the ALL Button, and the Command Wizard were updated. ** [2.0.2099] Previously, APP entities defined with EDL DETAIL or HISTORY options were not properly displayed when the SHOW OBJECT DETAILS or SHOW OBJECT HISTORY popup menu items were selected. This problem has been corrected. ** [2.0.2099] Previously, the APP entity EDL COMMAND was not properly parsed when the GRAPH OBJECT HISTORY popup menu item was selected. This problem has been corrected. ** [2.0.2097] Previously, the OSC window was not displayed upon startup. Now if the OSC window was displayed upon shutdown, it will be re-displayed on startup. ** [2.0.2096] Previously, EDL Export of user entities added a misleading comment indicating that these entities could be edited. Now the following comment is displayed instead: User Entity definitions(user defined). ** [2.0.2095] Previously, numeric values such as ' 1' were not aligned the same as '01' in Report windows. The problem has been corrected. ** [2.0.2095] Previously, if an ASAP V2 Client was communicating with an ASAP V1 server, the Show Related Objectives popup menu item was not supported, this problem has been corrected. ** [2.0.2094] ASAP2SYS.EDL was updated to reflect the fact that the Process entity Messages Sent, Messages Received, and Page Faults now are reported as rates per second rather than counts. ** [2.0.2093] Previously, when an entity was disabled from the ASAP Properties sheet, it would not be deleted from the Object Integration Layer (OIL). This problem has been corrected by adding a new method to the OIL, OIL.Object.Clear which clears all entities in the OIL. ** [2.0.2093] Previously, a double refresh could occur when OK/APPLY was clicked from the ASAP Properties window. Now only a single refresh occurs. ** [2.0.2092] Previously, Max Graph Rows property did not always return the correct number of rows when State Filtering was enabled for the Browse window. This problem has been corrected. ** [2.0.2092] Previously, when $ appeared in the ASAP Browse Window grid, it was treated as a number, and right justified, now when $ appears in the grid, it is left justified. ** [2.0.2092] Previously, report windows displayed the "+" sign prompt at the end of the ListView. The "+" is no longer displayed. ** [2.0.2092] Previously, the default Max Graph Rows drop-down value was 200. The default Max-Graph-Rows drop-down on the Graph Tab of the ASAP properties sheet is now 100. ** [2.0.2091] Previously, when "Late" data was detected, the ASAP Client would only report the time of the late data. Now that time is reported along with the number of Minutes by which the data is "Late". For example, if late data were received for 10:30 and the current time as 10:45 in the morning, "Time 10:30" is now reported as "Time 10:30+15". This indicates that the last time the ASAP Client received data from an object was 10:30 in the morning, and the +15 clarifies the fact that the data is 15 minutes late. In other words, the current time is now 10:30+15=10:45, and the data is 15 minutes "late". ** [2.0.2091] Previously, Client/Server EDL Entity Version checking was not performed. Now, version checking is performed whenever the ASAP CI displays the EDL Entity version of the form "Vn.ymmdd" in the first column of the heading of the output for an entity. When the version string is present in the CI output, the ASAP Client compares the Server EDL Entity version with the Client EDL entity version. If the entity versions match, normal Client operation continues. However, if entity definition versions do not match, the client will issue a warning dialog indicating the Entity EDL versions for the Client and Server do not match. The user can then decide whether to continue or abort monitoring. Notes: 1) Version checks are performed for both System entities and user defined entities. However, version checks are only performed if EDL Entity statements include a Version string property. 2) Version checks are only performed if both the Client and the Server have the an Entity Version string defined. If either the Client or Server Entity definition does not have a version string defined for that entity, then version checking is suppressed for that entity (this provides a way to suppress version checking for an entity). 3) The display of an Entity Version string is a function of each ASAP CI command. Stated differently, in order for versioning to work, each entity command must include support for the display of the EDL Entity Version string in the command heading. ** [2.0.2091] Previously, when the grid portion of the ASAP Browse window had any column widths resized, ASAP would revert to the old column widths whenever the grid was refreshed. Now, the resized column width is retained for the duration of the ASAP Session. ** [2.0.2091] Previously, the OSC window did not use the FONT BOLD property from the FONT tab of the ASAP Properties window. This problem has been corrected. ** [2.0.2091] Previously, Graph Object History for APP entity didn't work right because SampleCmdMacro didn't reformat the entity command properly. This problem has been corrected. ** [2.0.2090] Previously, OSC columns could not be re-ordered. Now you can reorder OSC columns by dragging and dropping a column heading. ** [2.0.2090] Previously, the OSC Reason column was the rightmost column, now it is positioned immediately after the Domain-Name column. Note you can reorder OSC columns by dragging and dropping a column heading. ** [2.0.2090] Previously, OSC multi-select mouse click avalanches caused excessive PC cpu usage. A click avalanche detector, now prevents this problem. ** [2.0.2090] Previously, on shutdown the OSC window did not unload until Windows 2000 garbage collection occurred. ASAP now immediately unloads the OSC window on shutdown. ** [2.0.2089] Previously, when a log item in the OSC window was double clicked, the Browse Node Drop-Down contained a node name that was inadvertently upcased. This problem has been corrected. ** [2.0.2089] Previously, when the Browse window was restored and the OSC window was minimized, the OSC window should have also been restored. This problem has been corrected. ** [2.0.2089] Previously, when the Browse window Object-Domain drop-down was resized the EDL progress bar was not moved. This problem has been corrected. ** [2.0.2089] Previously, the maximum number entities that could be displayed in the OSC scoreboard was 10. This limit has been removed. ** [2.0.2088] Previously, if an EDL error occurred during startup not enough error detail was displayed. Now ASAP always provides detailed information about the EDL line and syntax element in error. ** [2.0.2088] Previously, in ASAP2SYS all StatePair attributes had their StateRule set to UseThresholds. Now only attributes with scalar values have their initial default as UseThresholds. All other StatePair attributes have StateRule set to UseStateGraphState. Note you can change the StateRule via the ASAP Properties window. ** [2.0.2088] Previously, in ASAP2SYS certain Process selected entity headings were not left aligned for the fields that contained left aligned data. This problem has been corrected by using the ALIGN attribute property for the Process Name, and Program File Name attribute definitions. ** [2.0.2060] A slow Windows memory leak has been corrected. This leak was caused by a problem in the Microsoft Visual Studio runtime library. It occurred on Double Byte Character versions of Microsoft Windows, eg Japanese, Chinese, Korean, ... This problem is identified in the Microsoft support data base as MS Case SRX-000905602446. The case is also known in the Genesis data base as Solution 10-000 831 0034. ** [2.0.2060] Previously, a null filename could be entered in the in Object Filename field of the SSG Advanced dialog. This problem has been corrected. ** [2.0.2050] Previously, the popup menu "Show Related Objectives" did not do a RANK ..., LIST command. This problem has been corrected. ** [2.0.2050] Previously, the popup menu "Show Related Objectives" was only enabled for the APP entity. Now this menu item is enabled for all entity types. ** [2.0.2050] Previously, the Client EDL Compiler did not check for duplicate attribute names or headings. Duplicate attribute names or headings are now treated as a grammar error. The compiler now reports these as a syntax error. ** [2.0.2049] Previously, the Stop EDL compile toolbar button on the EDL IDE window did not stop the compile. This problem has been corrected. ** [2.0.2049] Previously, the Icons directory path label was truncated when the Icon directory path name was a very long name. This problem has been corrected. ** [2.0.2048] Previously, the path used for nested INCLUDE statements was based relative to the ASAP\EDL directory. Now PC File names that contain no path information will use the parent file's directory path instead of always referring back to the ASAP\EDL path. Example: INCLUDE C:\EDLs\UserEntity\Funds INCLUDE North.EDL INCLUDE South.EDL Will include the following: C:\EDLs\UserEntity\North.EDL C:\EDLs\UserEntity\South.EDL ** [2.0.2048] Previously, blanks were not allowed in include file names. Now you can place quotes around an include file name, and the compiler will allow blanks within the quoted include name. ** [2.0.2047] Previously, the EDL compiler did not look ahead far enough when parsing large amounts of whitespace in an EDL source file. This problem has been corrected. ** [2.0.2047] Previously, the PRINT menu function under the FILE... menu in the ASAP Browse window did not print correctly. This problem has been corrected. ** [2.0.2046] Previously, the initial Browse window width for low density screen settings such as 1024 x 768, might be less that the maximum width of the browse window Toolbar. This caused certain toolbar buttons to be hidden. This problem has been corrected. ** [2.0.2047] Previously, for an interactive heading rename the "dirty attribute" flag was not being set. The result was that the EDL was not updated when you clicked OK or APPLY. Now when you double click an attribute name on the Attribute Tab of the Properties window, and rename the property, the dirty flag is set properly. ** [2.0.2001] Previously, the statistics sample time might not be synchronized to the host time, if one and only one entity was enabled. For example, if only the App entity were enabled, the Client sample timer might not be in sync with the host update. It was also possible for the host sample time to be a few seconds late when multiple entities were enabled. Both problems have been corrected. ** [2.0.1004] Previously, the max late Time for graphed attributes was 2 x Rate, no matter how large the sample interval. Thus, if the Rate were 10 minutes, it could take up to 20 minutes to detect that data was late. Now max late cannot exceed five minutes, regardless of the host sample interval value, and as a result the "late" late problem has been corrected. Known Problems Remaining: ** None