\new;poff 8;text off;join off;justify off;head " ";subhead " " \sect "ASAP SRVR EXTENSION T0403V02 01JUN2002 Page "1;center SOFTWARE RELEASE DOCUMENT ADDENDUM Product Name: ASAP SRVR EXTENSION Product Number: T0403V02 Date: 01JUN2002 IPM Number: T0403AAB Summary: This SPR corrects problems with certain compilers returning a syntax error on asapx.h, corruption of ASCII text when supplied as a replace value for constant DATAITEMs, incorrect display of Status "Up" when the state is down, incorrect display of Status text and state when hundreds of aggregate domains are created in a CPU, up to 3-minute application hangs on ASAP_REGISTER_ procedure calls, the ASAPXSGP process failing to open the ASAP Collector on nodes numbered 0, and constant restarts of ASAPXMON processes in very large environments with downstream queuing. Superseded IPMs: T0403AAA Requisite IPMs: T0402AAB Required Hardware: HP "NonStop"(TM) RISC-based server Communications controller allowing file transfer from PC to "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 Required Firmware: NONE Required Software: T0402V02 T9050D42 if using D4x.xx T9050G06 if using G0x.xx T9550D40 T9552D40 Microsoft Windows 95, or Windows NT 4.0 Microsoft TCP/IP stack and FTP client Manuals: 425265-002 ASAP Extension Manual Installation Considerations: Subsystem interruption required New Features: NONE Problems Corrected: 1. [AAB] SYMPTOMS: Compiler errors when referencing asapx.h. CONDITIONS: Dependent upon the C compiler. LIKELIHOOD: Likely WORKAROUNDS: Edit $SYSTEM.SYSTEM.ASAPXH and remove the extraneous comma from the ASAP_OPSTATE_ procedure definition. (SOLN 10-011213-5384) 2. [AAB] CAVEAT: This change just provides a method to avoid the problem. SYMPTOMS: Corrupted ASCII text when supplied as the replace value (math 1) for a constant dataitem. CONDITIONS: NONE LIKELIHOOD: Certain FIX-INFO: Math 2 (replace text) was added as a workaround to this problem. Use math 2 to replace a constant dataitem with 8 bytes of printable ASCII text. See Known Problems Remaining #1. (SOLN 10-020207-6531) 3. [AAB] SYMPTOMS: Status text of "Up" shown on ASAP Client for a domain that is actually down. CONDITIONS: Occurs when processes set their own operational status and state using ASAP_OPSTATE_, and the registering process fails after setting the status text to "Up". LIKELIHOOD: Certain FIX-INFO: ASAPX now overrides both the Status text and state for a domain after the registering process fails if the Status text is "Up". If the text is anything else, only the state is overridden. (SOLN 10-020207-6537) 4. [AAB] SYMPTOMS: Application domains shown as down when they are actually up. CONDITIONS: Occurs when hundreds of aggregate domains are created in a single CPU. LIKELIHOOD: Likely (SOLN 10-020212-6619) 5. [AAB] SYMPTOMS: Hanging opens after calling ASAP_REGISTER_ with an error return code. CONDITIONS: Occurs on I/O errors between ASAPXMON and ASAP_REGISTER_. LIKELIHOOD: Certain (SOLN 10-020212-6625) 6. [AAB] CAVEAT: This change just provides a method to minimize the impact of this problem. SYMPTOMS: Up to 3-minute application hangs when calling ASAP_REGISTER_. CONDITIONS: Can occur when ASAPX is running in "write-to-collector" mode on very busy systems with downstream queueing on ASAP Collector(s) and/or disk processes. LIKELIHOOD: Somewhat likely FIX-INFO: The TIMEOUT parameter used by ASAP_REGISTER_ to timeout its registration request to ASAPXMON has been externalized so callers can now set a shorter timeout value to reduce the impact of this problem on applications. The default timeout value is 3 minutes. See Known Problems Remaining #2. (SOLN 10-020222-6886) 7. [AAB] SYMPTOMS: File error 18 when opening the ASAP Collector. CONDITIONS: Occurs when the ASAP Collector resided on a node numbered 0. LIKELIHOOD: Certain (SOLN 10-020404-7917) 8. [AAB] SYMPTOMS: Unexplained restarts of ASAPXMON processes and/or missed aggregate sample data. CONDITIONS: Can occur on very busy systems with thousands of application domains. LIKELIHOOD: Likely WORKAROUNDS: Run multiple ASAP Collectors and partition the ASAP database to reduce downstream queueing on ASAP Collector and/or database disk devices. FIX-INFO: ASAPXSGP now waits longer for data from ASAPXMON processes. Its wait time is now a function of the ASAP rate instead of a fixed value. (SOLN 10-020410-8084) Known Problems Remaining: 1. SYMPTOMS: Corrupted ASCII text when supplied as the replace value (math 1) for a constant dataitem. CONDITIONS: NONE LIKELIHOOD: Certain WORKAROUNDS: As of T0403AAB, use math 2 to replace a constant dataitem with 8 bytes of printable ASCII text. (SOLN 10-020207-6531) 2. SYMPTOMS: Up to 3-minute application hangs when calling ASAP_REGISTER_. CONDITIONS: Can occur when ASAPX is running in "write-to-collector" mode on very busy systems with downstream queueing on ASAP Collector(s) and/or disk processes. LIKELIHOOD: Somewhat likely WORKAROUNDS: As of T0403AAB, use the ASAP_REGISTER_ Timeout parameter to set a lower timeout value to reduce the impact of this problem on applications. The default timeout value is 3 minutes (SOLN 10-020222-6886) Installation Instructions: A. Pre-Installation Steps: 1. If you are migrating from release 1 of ASAPX, read the comments and examples on release 1 to release 2 migration in the ASAP Extension Manual and perform the tasks described there. 2. Ensure that requirements for using this SPR are met (see Requisite IPMs, Required Hardware, and Required Software). 3. Review the IPSetup User Guide (file USRGUIDE.PDF in the NSK_SW subdirectory on the ASAPX CD). IPSetup is provided on the CD to facilitate installation of Independent Products. Use Adobe Acrobat Reader (available on the CD) to read or print the IPSetup User Guide. 4. Decide whether you will use DSM/SCM to move the SPR's files to the Installation Subvolumes (ISVs) after they are placed on the "NonStop"(TM) server. Using DSM/SCM is optional, but recommended when DSM/SCM is available. B. Installation Steps: 1. Run IPSetup to place (move files from the CD to the "NonStop" server) and optionally install (move files to correct ISVs) this SPR. If TCP/IP and FTP are unavailable, or if you have problems with automatic file placement, follow the instructions in the IPSetup User's Guide section "Manual Software Placement Using the IPSetup TACL Program" to manually place the files. 2. If you are using DSM/SCM to install this SPR: - COPY the SPR to a new revision of the software configuration you want to update. - BUILD and APPLY the configuration revision. - Run ZPHIRNM to perform the RENAME step. C. Post-Installation Steps: 1. Run ASAP Extension INSTALL to update the ASAPX subsystem: a. TACL 1 > VOLUME $.ZASAPX b. TACL 2 > RUN INSTALL c. Fill in the source and destination subvolumes. To install to a remote node, fully qualify the destination subvolume name. For example, \remote.$system.system. Legal Notices: HP Confidential: NEED TO KNOW ONLY Copyright (C) 1999, 2001-2002 Hewlett-Packard Company HP and NonStop are trademarks of Hewlett-Packard Company in the U.S. and/or other countries. Microsoft, Windows, and Windows NT are trademarks of Microsoft Corporation in the U.S. and/or other countries. HP shall not be liable for technical or editorial errors or omissions contained herein. The information is provided "as is" without warranty of any kind and is subject to change without notice. The warranties for HP products are set forth in the express limited warranty statements accompanying such products. Nothing herein should be construed as constituting an additional warranty.