\new;poff 8;text off;join off;justify off;head " ";subhead " " \sect "Compaq ASAP Extension T0403V01 15JUN1999 Page "1;center SOFTWARE RELEASE DOCUMENT Product Name: Compaq ASAP Extension Product Number: T0403V02 - EAP Refresh Date: 27MAR2001 Copyright Notice: COMPAQ CONFIDENTIAL: NEED TO KNOW ONLY Copyright (C) 1999, 2000, 2001 Compaq Computer Corporation Protected as an unpublished work. All rights reserved. The computer program listings, specifications and documentation herein are the property of Compaq Computer Corporation or a third party supplier and shall not be reproduced, copied, disclosed, or used in whole or in part for any reason without the prior express written permission of Compaq Computer Corporation. Summary: The Compaq ASAP Extension (ASAPX) enables customer applications for monitoring 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 and later Dxx.xx releases and G03.00 and later Gxx.xx releases. Required Hardware: NonStop RISC-based servers Required Firmware: None Required Software: T0403 ASAP Server Manuals: Compaq ASAP Extension Manual Migration Considerations: None Installation Considerations: 1) Insert the ASAPX CD into a CD-ROM drive and follow the instructions contained in the file named README.TXT in the root directory to install the ASAPX ISV onto a NonStop RISC-based server. 2) For systems using DSM/SCM for software management, use DSM/SCM to accept the ASAPX software from the ISV and complete the installation process. 3) Create and edit the ASAPX configuration file, ASAPXCNF. It must contain SET commands to configure ASAPX for your environment. 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) Configure ASAP to enable ASAPX by including the SET APP ON command in the ASAP configuration file, ASAPCONF. If the ASAPX configuration file, ASAPXCNF, does not reside on $SYSTEM.SYSTEM, then a PARAM option must also be used to indicate the location of the file. 5) Start or restart ASAP. Use EMS to verify that all components start successfully. ASAP START [\] 6) Change application source code to use the ASAPX API procedures. 7) Point your applications to the ASAPX procedure library, ASAPXLIB or the native Shared-Runtime Library, ASAPXSRL. This can be done using the ?library or ?search compiler directive, the LIB runtime parameter or by binding the library into your application object file. New Features: 1) Use of D-Series Enhancements: Can be created by a high PIN process Y D42.00 Can communicate with a high PIN requester Y D42.00 Can communicate with a high PIN server Y D42.00 Can create a high PIN process Y D42.00 Can run at a high PIN Y D42.00 Defaults to run at a high PIN N (HIGHPIN on) Has a new (since C30 FCS) maximum of OPENS Y D42.00 on a device, process name, or subdevice Issues new (since C30 FCS) operator messages Y D42.00 Issues new (since C30 FCS) tokens Y D42.00 Recognizes high PIN process IDs Y D42.00 Recognizes new (since C30 FCS) tokens Y D42.00 Recognizes remote 8-character Y D42.00 (including $) device/volume/file names Recognizes remote 6-character Y D42.00 (including $) process names Recognizes variable-length-string Y D42.00 file names 2) 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. 3) The ASAPX host-based objectives concept has been extended to all components of ASAP Server as Discrete Object Thresholds (DOTs). The ASAPX ADD, ALTER, COMMIT, DELETE, INFO and LIST commands have been replaced by the ASAP MONITOR and RANK commands. Many ASAPX SET commands have also been deleted and 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 INFO, OBEYFORM. They can then be edited into ASAP RANK commands. 4) 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_. 5) 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. 6) 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. 7) 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 Domain Registration Time, also has an associated OEM state. The 11 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. 8) ASAPX supports 256 domains per processor and a maximum of approximately 90 user-defined application entities. Problems Corrected: 032701-001 Inactive domains reported as warnings. If a domain is inactive and ASAPX is controlling its operational state (see ASAP_OPSTATE_), then ASAPX reports the domain as "Inactive" in a warning (yellow) state. The user had no way to control the alert level. Now, to control alerting for inactive domains add the NAK built-in metric to the set of attributes for the entity the domain belongs to. If NAK is present, ASAPX uses its state as the operational state for inactive domains. ASAPX still reports it as "Inactive" but will not alert on the domain until NAK objectives aren't met. This does not apply if your program uses ASAP_OPSTATE_ to set the operational text and state directly. 032601-001 Re-enabled the DISABLE and ENABLE STATS commands. The commands were disabled with the intention of removing them from this release. They have been re-enabled on behalf of a customer request. 032601-002 Header alignment off. Corrected header alignment in APP , DETAIL output. 032601-003 OPEN command not removed. OPEN is a leftover from Release 1 when ASAPX controlled Objectives. Now that work is done by ASAP Server, so OPEN has been removed from the ASAPX CI. 032601-004 ASSUME command not removed. ASSUME is a leftover from Release 1 when ASAPX controlled Objectives. Now that work is done by ASAP Server, so ASSUME has been removed from the ASAPX CI. 032301-001 States not propagating correctly for aggregate domains. ASAPXSGP did not use the state from the aggregate record in all cases. It now correctly propagates the worst state to the aggregate level unless a specific objective has been set for the attribute at the aggregate level. For multiple aggregate levels, the worst state propagates to any level without a specific objective on the attribute. 032301-002 APP \* command produces invalid results. ASAP CI wasn't reading the right record set based on the entity name key when dealing with multiple nodes. The APP command has been corrected. Note this problem produced many varied symptoms, some minor and some severe. 031901-001 Aggregate domains aren't removing themselves. If all detail domains in the aggregate set of domains were removed, the aggregate domain remained because it failed to signal its state to ASAP Client. Aggregate domains now correctly remove themselves the interval after the last domain from the aggregate set is removed. 031401-001 RANK, LIST sometimes does not work. Also reported as a problem with SHOW RELATED OBJECTIVES. If aggregation wasn't turned on for the entity, objectives weren't always being loaded. This has been corrected. Note: RANK, LIST (and SHOW RELATED OBJECTIVES) only work after the 1st sampling interval because ASAP components only load objectives during sample processing. 031401-002 APP comand producing strange results. If the EDL attribute property FORMAT is not specified then APP doesn't know how to display the attribute value. ASAP now automatically sets the following default FORMATs, based on the TYPEDATA of the attribute: INT "I3", INT32 "I6", INT64 "I9", REAL64 "F6.2", CHAR "S". 031401-003 Errors in the METRICRULE formula aren't handled well. The formula wasn't being parsed at EDL compile time, ASAPX waited until the 1st sample interval then checked the formulas. The EDL compilation now validates the formula specified in METRICRULE. Known Problems Remaining: None