READ THIS FILE COMPLETELY BEFORE BEGINNING PRODUCT INSTALLATION Copyright (C) 1999, 2001-2004 Hewlett-Packard Company Product Name: ASAP SRVR EXTENSION Marketing Product ID: SE31V2.5 Component Products: T0403AAE I. Basic Product Installation Instructions 1. Ensure that requirements for using this product are met (see Section IV Product Requirements below). 2. Ensure that prerequisites for the installation utility and any product-specific installation requirements are met (see Section V Installation Prerequisites below). 3. Review the file USRGUIDE.PDF (in the subdirectory NSK_SW on this CD) containing the IPSetup User Guide, which provides instructions for using IPSetup, a utility provided on the CD that enables installation of Independent Products. You will need Adobe Acrobat Reader to read or print the IPSetup User Guide. Visit Adobe's website to download the latest Adobe Acrobat Reader: http://www.adobe.com 4. Decide whether you will use DSM/SCM to move files to Installation Subvolumes (ISVs) after files are placed on the workstation. Using DSM/SCM is optional, but is recommended when DSM/SCM is available. 5. Follow the pre-installation instructions in Section II below, if any, before continuing to Step 6. 6. Run IPSetup to place (move files from the CD to the workstation) and install (move NonStop Kernel files to correct ISVs) this product. If TCP/IP and FTP are unavailable, or if you have problems with automatic file placement, use the instructions in the IPSetup User Guide section "Manual Software Placement Using the IPSetup TACL Program" to manually place NonStop Kernel files. This product contains both NonStop Kernel components and workstation components. You must place each component type separately. To restart the installation program after placing the first component type, click SETUP.EXE in the root directory. IMPORTANT: Always reinstall this product after using the Install product to install a Site Update Tape (SUT). Installing a SUT using the Install product can result in overwriting this Independent Product with older versions of software. This problem does not occur when using DSM/SCM to install SUTs. 7. Follow the post-installation instructions in Section III below, if any, after using IPSetup to place and install this product. II. Pre-Installation Instructions 1. Stop all running copies of ASAP. III. Post-Installation Instructions 1. Modify the ASAP configuration file (ASAPCONF) to include the SET APP ON command. 2. If ASAP and ASAPX are not running from $SYSTEM.SYSTEM, modify the ASAP configuration file (ASAPCONF) to include the SET APP PARAM command identifying the location of the ASAPX configuration file (ASAPXCNF). 3. Create and edit the ASAPX configuration file (ASAPXCNF) to include SET commands to tailor ASAPX to your environment and applications. See the ASAPX manual for a description of all ASAPX SET commands. Note you may execute the INSTALL macro in the ASAPX ISV to re-install ASAPX and automatically create an initial ASAPXCNF file the first time you install ASAPX. 4. If you are migrating from release 1 of ASAPX read the comments and examples on release 1 to release 2 migration in the ASAPX Manual and perform the tasks described therein. 5. Restart ASAP to start the ASAPX environment. Note at this point ASAPX has been started without any custom entity definitions to describe your application. 6. Modify your applications to use ASAPX as described in the Programmers Guide section of the ASAPX manual. 7. Create custom ASAP EDL files to describe your application. 8. Restart all parts of ASAP after distributing the new EDL to all NSK servers and ASAP Clients. IV. Product Requirements Required Hardware: HP NonStop RISC-based servers Minimum OS Release: NonStop Kernel release D42 NonStop Kernel release G06 Required Software: T0402V02 - Availability, Stats and Performance (ASAP) Server Disk Space Requirement: ISV Subvolume: 3.9mb Install Subvolume: 3.1mb APPDB Database: 556 bytes * num domains * intervals per day Memory Requirement: Approximately 4k bytes per registered domain V. Installation Prerequisites Required Hardware: HP NonStop server Communications controller allowing file transfer from PC to HP NonStop server PC with 486 or higher processor and all of the following: CD-ROM drive VGA or higher-resolution video adapter and monitor Microsoft Mouse or similar pointing device Communications controller allowing file transfer from PC to HP NonStop server Required Software: T9550D30 SOCKET LIBRARY or higher version T9552D30 TCP/IP FTP with IPM ABG or superseding IPM (for releases D31.00 to D40.00) T9552D40 TCP/IP FTP with IPM ABJ or superseding IPM (for releases D40.01 and higher) Microsoft Windows 95, or Windows NT 4.0 or later Microsoft TCP/IP stack and FTP client VI. Manuals Included On this CD ASAP Extension Manual VII. CD-ROM Root Directory Contents AUTORUN.INF File containing CD AutoRun commands. AXDIST.EXE Microsoft redistributable library files. IPSETUP.CNT File containing help contents for the CD installation utility IPSetup. IPSETUP.EXE File containing the main executable for IPSetup. IPSETUP.HLP File containing help text for IPSetup. LICENSE.TXT File containing limited-use Software Licensing Agreement with the licensing terms governing this product. README.TXT File containing product and installation information (this file). SETUP.EXE File containing the Launcher executable. NSK_SW Subdirectory containing NonStop Kernel component files, including installation utilities and instructions. WS_SW Subdirectory containing workstation component files (if applicable to this product), including installation utilities if any. SOFTDOCS Subdirectory containing all Initial Product Version / Product Version Update Softdocs. CD_DOCS Subdirectory containing product documentation in the following subdirectories: PDF_DOCS Subdirectory of CD_DOCS containing: 1. Product manuals in PDF format for viewing with Adobe Acrobat Reader 2. ACROBAT_VIEWER providing Adobe URL for downloading the latest Adobe Acrobat Reader. Visit Adobe's website at http://www.adobe.com ADDENDUM Overview: ========= The ASAP Extension (ASAPX) allows customer applications to be monitored by the Availability, Stats and Performance (ASAP) product. ASAPX provides a direct view into an application so a customer can always know if an application is meeting its service level objectives. ASAPX executes on D42.00/G06.00 onward. New Feature History: ==================== 2.4 [AAD] ASPAX ZLE. ASAPX now provides support for super-scalar ZLE systems with tens of thousands of monitored domains. The domain per CPU limit is now user-defined with a new upper limit of 10,000 domains per CPU. Use the new SET MAXDOMAINS configuration command to increase the 1,024 domain per CPU default. The aggregate domain per CPU limit is now user-defined with a new upper limit of 10,000 aggregate domains per CPU. Use the new SET MAXAGGREGATES congiguration command to increase the 1,024 aggregate domain per CPU default. The SET AGGREGATE ONLY option is made into a viable method to reduce disk I/O to the historical database. A new MEMORY option on the APP command allows ASAP to retrieve detail domain data directly from ASAP memory. This lets a user write only aggregate records to the database, but still view detail records when domains alert. Set the following as the EDL DETAIL command in all user-defined EDL files: DETAIL "APP ^, DE, ST, MEM, MIN, COUNT 20" When the command defined by the EDL DETAIL property string is set as shown above, a user can right-mouse on an aggregate domain that is alerting and then choose "Show Object Details" to see alerting detail domains. Next, the user is given complete control over the content of aggregate domain records with the addition of aggregation syntax to the EDL MetricRule formula. The new MetricRule syntax is: is: # [SUM|AVG|MIN|MAX|CNT] (default SUM) C S [SUM|AVG] (default varies) is: +, -, / or * - arithmetic operators Examples: METRICRULE "#0 SUM/S SUM" METRICRULE "#0 MIN/S AVG" METRICRULE "#0 MIN" METRICRULE "C100*((#0 MIN + #1 MAX)/#2 AVG)" Finally, because the APP command's AGGREGATEONLY option is more frequently used, it has been abbreviated to "AGGONLY" and "AO" in addition to the complete spelling. In summary, ASAPX ZLE lets a user monitor tens of thousands of detail domains while reducing disk I/O to the historical database by writing only aggregate records to disk. Please see the new version of the ASAP Extension Manual that ships with this release for more information on the ASAPX ZLE enhancement. (SOLN 10-030822-9092) 2.0 [V02] ASAPX now supports multiple application definitions using the ASAP Entity Definition Language. Each EDL entity has its own set of DataItem and Metric(EDL Attribute) definitions. 2.0 [V02] The ASAPX host-based objectives concept has been extended to all components of ASAP Server as Discrete Object Thresholds (DOTs). The ACTIVATE, ADD, ALTER, ASSUME, COMMIT, DEACTIVATE, DELETE, INFO, LIST, OPEN and REMOVE commands have been replaced by the ASAP MONITOR and RANK commands. Many ASAPX SET commands have also been deleted or replaced with ASAP SET commands. Due to the DOTs conversion the objectives database in the Release 1 version of ASAPX is obsolete. All objectives from Release 1 databases should be saved to an edit file using the ASAPX INFO, OBEYFORM command. They can then be edited into ASAP RANK commands. 2.0 [V02] Operational Status and State. Each ASAPX Entity now includes the operational status and state of the process that registered the domain. Both the 15-byte operational status and the resulting OEM state can also be set directly by an application using a new ASAPX API procedure called ASAP_OPSTATE_. 2.0 [V02] Each ASAPXMON process can now be configured to write detail records directly to the ASAP Collector, bypassing the ASAPXSGP process. Note the ASAP ID must not exceed 2 characters if the ASAP Collector resides on a remote node. For example, change $ZOO to $ZO. 2.0 [V02] ASAPX now computes and displays aggregate data for any of the 4 possible levels within a domain name. For example if Atm\West\SanFran\Loc23 is a typical domain then ASAPX can compute aggregate totals for Atm, Atm\West and Atm\West\Sanfran. 2.0 [V02] The NAK and UNAVAIL metrics from Release 1 have been added to a set of 11 optional metrics that ASAPX will compute on behalf of the application. Each optional metric, except Registration Time, also has an associated OEM state. The built-in metrics are: Nak Negative acknowledgement counter. UnAvail The unavailability of the registering process during the interval. Cpu The primary processor of the registering process. Pri The priority of the registering process. Busy Percent CPU busy for the registering process. PState The process state of the registering process. WState The wait state of the registering process. RegTime The registration date and time the domain was registered. DownTime Total downtime (in seconds) for the registering process. Avail The overall availability of the registering process. Version The application version supplied to ASAP_REGISTER_, or a default version supplied by ASAP. 2.0 [V02] ASAPX supports 1024 domains per processor and a maximum of approximately 90 user-defined application entities. Problems Corrected History: =========================== 2.5 [AAE] ASAPXMON no longer assumes that a process running in another CPU has re-registered all the domains that it had previously registered. Domains that have not been re-registed in the other CPU will continue to be reported as down in the original CPU. (SOLN 10-040412-5021) 2.5 [AAE] ASAPXMON could repeat a domain in the next buffer written to the ASAP collector if the number of domains was the exact number that would fit into a buffer, and if aggregation was turned on so there would be a subsequent aggregate data buffer. This resulted in the ASAP Collector reporting an error 10 against ASAPXMON. (SOLN 10-040412-5020) 2.4 [AAD] ASAPX could remove a domain table from memory but leave it in the domain table if errors occurred when removing the domain from the domain table. (SOLN 10-030822-6067) 2.4 [AAD] ASAPX could open and close the domain table many times during an interval if many domains were down. (SOLN 10-030822-9087) 2.4 [AAD] ASAPXMON restart time is dramatically improved by improvements to its list insertion algorithm. (SOLN 10-030822-9088) 2.4 [AAD] ASAPXMON restarts are throttled to once per interval until 3 failures when it becomes the maximum of once per interval or once per hour. (SOLN 10-030822-9089) 2.4 [AAD] ASAPX now propagates the value associated with the worst state for the CPU, Pri, PState, WState and Version built-in attributes. For example, if there are 10 domains that make up the aggregate and one of the domains has a critical alert on the CPU attribute, then that CPU attribute value and state will be propagated to the aggregate record. (SOLN 10-030822-9090) 2.4 [AAD] ENFORM cannot read attributes defined as floating point (REAL64). ASAPX now supports implied decimal points so attributes can be defined as TYPEDATA INT64 and still output decimal values using the fixed format option, for example FORMAT "Fx.y". ASAPX stores the value as FIXED(y) in the APP record. (SOLN 10-030822-9096) 2.4 [AAD] ASAPX now provides a DLL for the API library (ASAPXDLL) for use with G06.20 and beyond. HP recommends use of the ASAPXDLL instead of the older libraries. (SOLN 10-030822-9093) 2.4 [AAD] ASAPX modules are now accelerated for better performance. (SOLN 10-030822-9091) 2.4 [AAD] ASAP_REGISTER_ now returns error -6 when statistics collection has been disabled by issuing the ASAPX DISABLE STATS command. (SOLN 10-030912-9607) 2.3 [AAC] Some C++ compilers returned a syntax error when compiling and referencing asapx.h due to use of parenthesis instead of braces and a missing #endinf statement. (SOLN 10-021002-2120) 2.3 [AAC] If very short timeout values were passed to ASAP_REGISTER_ the I/O to ASAPXMON could time out, resulting in cancellation of the I/O. This could abort an in-flight user transaction, causing ENDTRANSACTION to return error 97. (SOLN 10-021205-6906) 2.3 [AAC] Duplicate domains in the domain table. ASAPXMON did not correctly report problems when attempting to remove domains from the domain table. (NO SOLN) 2.2 [AAB] Certain compilers returned a syntax error when compiling and referencing asapx.h due to an extraneous comma in the declare for ASAP_OPSTATE_. (SOLN 10-011213-5384) 2.2 [AAB] ASAPX sometimes displayed a Status of "Up" while at the same time showing the operational state as down (state 8). This occurred because ASAPX would override the operational state when a process failed, but it would not override the Status text of "Up" if it was set by an application using the ASAP_OPSTATE_ procedure. (SOLN 10-020207-6537) 2.2 [AAB] ASAPX would display incorrect Status text and operational states for many domains when domain aggregation was turned on and hundreds of aggregate domains were created in a CPU. (SOLN 10-020212-6619) 2.2 [AAB] ASAP_REGISTER_ failed to close the ASAPXMON if an I/O error occurred during a registration request. (SOLN 10-020212-6625) 2.2 [AAB] The ASAPXSGP process failed to open the ASAP Collector process with Error 18 when running on a node with Expand node number 0. (SOLN 10-020404-7917) 2.2 [AAB] In very large ASAP environments running with a low ASAP rate the ASAPXSGP process timed out I/O to the ASAPXMON processes too soon resulting in frequent stops and restarts of the ASAPXMON processes. (SOLN 10-020410-8084) 2.1 [AAA] ASAPX failed to write EMS alerts for Status/operational state changes when configured to do so using the RANK command. For example, the command "RANK ATM, STATUS CRITICAL", did not cause ASAPX to generate a critical event when the Status attribute produced an alert condition. (SOLN 10-010803-1955) 2.1 [AAA] ASAPX would not allow definition of more than 11 (approximately) user-defined entities even though the ASAP maximum entity count is much greater. (SOLN 10-010809-2101) 2.1 [AAA] ASAPX reported invalid Busy percentages for the first interval after a process registered a domain in a CPU. ASAPX now reports 0.00 for the first interval and reports the actual Busy percent for the 2nd sample after establishing its baseline measurement. (SOLN 10-010820-2310) 2.1 [AAA] Invalid elapsed times were computed when SET TEST ON was specified in the ASAPXCNF configuration file and ASAPX missed at least one sample. The ASAP RATE value was multiplied by 60 seconds, not taking into account the extra time caused by the missed sample. ASAPX now rounds to the nearest minute and takes the difference between samples instead of using the ASAP RATE value. (SOLN 10-010822-2427) 2.1 [AAA] The command "MONITOR APP [], REMOVE" failed to remove the specified APP domain, and failed to remove all APP domains when no domain was specified. (SOLN 10-010823-2481) 2.1 [AAA] ASAPX computed DownTime, Avail and UnAvail incorrectly for the interval where a domain failed. It also failed to preserve the contents of those 3 built-in attributes when a domain stopped and restarted. (SOLN 10-010823-2487) 2.1 [AAA] ASAPX computed DownTime incorrectly when a domain re-registered in a different CPU after at least one sample interval had passed since it stopped processing in the original CPU. (SOLN 10-010830-2759) 2.1 [AAA] ASAPX would incorrectly return a domain name error to callers of the ASAP_REGISTER_ procedure when the domain name being registered contained the name of an ASAP entity at a lower level of domain name. For example, the domain name "Atm\Disk" would produce an error even though it is a valid domain name. (SOLN 10-010919-3206) 2.1 [AAA] ASAPX would write duplicate records to the ASAP collector under certain conditions. If several hundred aggregate domains were processed in a single CPU, ASAPX occassionally wrote duplicate records for one or more of the aggregate domains. (SOLN 10-011002-3507) 2.1 [AAA] ASAPXMON processes mysteriously stopped and restarted without notification. The 3rd I/O error encountered over any span of time caused the ASAPXSGP process to mistakenly stop and restart an ASAPXMON. The ASAPXSGP process now stops and restarts an ASAPXMON only after 3 consecutive I/O errors. (SOLN 10-011002-3508) 2.0 [V02] To limit data flow to ASAP Client and still show pertinent information, the APP command now supports the MINSTATE and COUNT options. MINSTATE and COUNT are intended for use with EDL DETAIL commands in user-defined entity definitions. (No SOLN) 2.0 [V02] For large domain populations the AGGREGATEONLY option now processes fewer records resulting in improved response time. (No SOLN) 2.0 [V02] ASAPXMON no longer abends on problems with MONITOR, LIST, DETAIL commands when the length of a dataitem exceeds 20 bytes. (No SOLN) 2.0 [V02] ASAPXMON now outputs the exponent sign correctly in large floating point numbers. (No SOLN) 2.0 [V02] The list insertion algorithm in ASAPXSGP is modified for better performance with large domain populations. (No SOLN) 2.0 [V02] The APP command no longer returns invalid records when Entity names exceed 8 characters. (No SOLN) 2.0 [V02] The EDL compile process now enforces the following for user-defined EDL files: 1. The Dataitems Entity property must be defined. 2. The MetricRule Attribute property must be defined for all user-defined attributes except ASAPX header and builtin attributes. (No SOLN) 2.0 [V02] In ASAPX 1.0 the ASAPXMON processes attempted to use shared memory and the domain table to reconstruct the environment after a restart. Under some cases the contents of shared memory are not valid after a restart, which causes ASAPXMON to mistakenly register multiple domains with no name into slot 0. This is known as the 0-domain problem. ASAP 2.0 removes the reliance on shared memory at restart time. ASAPXMON now uses only the contents of the domain table to reconstruct its environment after a restart. (SOLN 10-001229-8182) Known Problems Remaining: ========================= 2.1 [V02] ASAPX can corrupt ASCII text supplied as the replace value on calls to ASAP_UPDATE_ or ASAP_UPDATELIST_ when it translates the input value to 64-bit floating point. To avoid this problem starting with ASAPX 2.2 use Math option 2. When Math 2 is used ASAPX assumes the replace value is text and will not automatically translate the value. As of ASAP 2.4 define all text DataItems as type "T" in addition to using Math 2. (SOLN 10-020207-6531) 2.1 [V02] When ASAPX is configured in "write-to-collector" mode on systems with resource limitations it is possible that calls to ASAP_REGISTER_ can be delayed while ASAPXMON is busy writing records. To avoid this problem starting with ASAPX 2.2 use the Timeout parameter to set a shorter time limit on calls to ASAP_REGISTER_. (SOLN 10-020222-6886)