\new;poff 8;text off;join off;justify off;head " ";subhead"" \sect "ASAP SERVER T0402V02 01OCT2003 Page "1;center SOFTWARE RELEASE DOCUMENT ADDENDUM Product Name: ASAP SERVER Product Number: T0402V02 Date: 01OCT2003 PVU Number: T0402AAD Copyright Notice: HP CONFIDENTIAL: NEED TO KNOW ONLY Copyright 2003 Hewlett Packard Development Company, L.P. Protected as an unpublished work. The computer program listings, specifications and documentation herein are the property of Compaq Computer Corporation and successor entities such as Hewlett Packard Development Company, L.P., 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 Hewlett Packard Development Company, L.P. Summary: This ASAP SPR provides support for super-scalar ZLE systems with tens of thousands of monitored process domains. An example ENFORM query is now provided that explains how to run reports on application entities; A limit on the maximum number of lines that can be output in reports has been removed. There is an option to prevent inadvertent ADD operations when using the MONITOR command; Support for new CPU types have been added to internal tables; A variety of minor problems have been corrected as described below. Superseded PVUs: T0402AAA T0402AAB Requisite PVUs: T0346AAE if using D42.00-D45.01 T0346AAU if using D46.00 onward or G06.03 onward T6028AAT if using D42.00-D48.01 or G06.00-G06.08 (see note) T9053ANU if using G06.11-G06.12 (see note) T9057AET if using D42.00-D48.02 (see note) T9086ACE if using D42.00-D43.01 (see note) T9117ABB if using D42.00-D48.02 or T9117ABG if using G06.00-G06.14 Note: T6028: The function needed is included in G06.09 onward. T9053: Fixes a problem introduced in G06.11 with the Dfreq queue counter. T9057: The function needed in T9057 is included in G06.00 onward. T9086: The function needed in T9086 is included in D43.02 onward and G06.00 onward. Required Hardware: NonStop 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: T9050D42 for D4x.xx T9050G06 for Gxx.xx T9550D40 T9552D40 Microsoft Windows XP, Microsoft Windows 2000, Microsoft Windows ME, or Windows NT 4.0 or later. Microsoft TCP/IP stack and FTP client Manuals: 425264-002 ASAP SERVER Installation Considerations: Subsystem interruption required - Perform these pre-installation steps: 1. Ensure that requirements for using this product are met (see Section the Required Hardware and Required Software sections above). 2. Ensure that prerequisites for the installation utility and any product-specific installation requirements are met (see Section D 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 need Adobe Acrobat Reader (available on this CD) to read or print the IPSetup User Guide. 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. If you are using the ASAP Extension make a copy of the file $System.System.Asapuser. For example from a TACL prompt enter the following command: FUP DUP $System.System.Asapuser,$System.Asaptemp.*,saveall, purge 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. 7. This SPR includes a change to the EDL definition for PROCESS and TMF. All PROCESS and TMF objective records must be deleted and re-added after installation of the new release. To save then delete the existing PROCESS and TMF objective records enter the following commands: TACL> ASAP +RANK/OUT TMFOBJS/ TMF, OBEYFORM +RANK/OUT TMFOBJS/ TMF \,OBEYFORM (preceding command must be done for each remote node) +RANK TMF *, DELETE (preceding command must be entered twice) +RANK TMF \.*, DELETE (preceding command entered twice for each remote node) +RANK/OUT PROOBJS/ PROCESS, OBEYFORM +RANK/OUT PROOBJS/ PROCESS \,OBEYFORM (preceding command must be done for each remote node) +RANK PROCESS *, DELETE (preceding command must be entered twice) +RANK PROCESS \.*, DELETE (preceding command entered twice for each remote node) 8. Follow the post-installation instructions in Section B below, if any, after using IPSetup to place and install this product. - Perform these post-installation steps: 1. Invoke the INSTALL^TEMPLATES TACL macro to install this SPR's EMS template file(s) in the running system. The macro can be found in $.ZINSAIDS.TACLMACS or Support Note S92067B. For instructions, LOAD the macro and type: INSTALL^TEMPLATES /OUT / HELP 2. Run ASAP setup to update the ASAP subsystem with the following commands: a) VOLUME $.ZASAP b) OBEY INSTALL c) Perform "Full Install on this node" from the central ASAP database node. d) Perform "Remote Monitor Install" for any additional Licensed ASAP nodes that you wish to monitor. See Section 2 of the ASAP manual for detailed information regarding subsystem configuration. e) If you are using the same volume and subvolume location for the ASAP database files, you must delete the ASAP version 1 database files before starting the ASAP Version 2 environment. f) If you had PROCESS or TMF objective records that you saved in step 7 of the pre-installation steps, then re-enter the saved objectives information. TACL> ASAP +OBEY TMFOBJS +OBEY PROOBJS 3. If you are using the ASAP Extension copy the duplicated file from the Pre-Installation instructions Step 1 to $System.System.Asapuser. For example from a TACL prompt enter the following command: Fup dup $System.Asaptemp.Asapuser,$System.Asaptemp.Asapuser ,saveall, purge 4. If upgrading from a prior version of ASAP purge the DBPRO file in the ASAP database subvolume prior to starting the ASAP 2.4 collector process. 5. When looking at ASAP data from non ASAP 2.4 databases please keep and use that version of the ASAP CI for displaying the non ASAP 2.4 data. New Features: 1. [AAD] Process ZLE. ASAP now provides support for super-scalar ZLE systems with tens of thousands of monitored process domains. A) Process ZLE provides the ability to hierarchically group processes. For example, all the Spooler collector processes might be grouped into a group called "Spooler\Collectors". Use the MONITOR command to specify the logical portion of the name preceding the actual process name to monitor a process as part of a hierarchical group. For example: MONITOR PROCESS SPOOLER\COLLECTOR\$S MONITOR PROCESS SPOOLER\COLLECTOR\$S2 MONITOR PROCESS SPOOLER\COLLECTOR\$S3 MONITOR PROCESS SPOOLER\PRINT\$SPLP MONITOR PROCESS SPOOLER\PRINT\$SPLP2 Logical process domain names can be 64 bytes in length and can contain up to 5 levels of hierarchy separated by a backslash. The actual process name must be the last level in the hierarchy. B) Process ZLE provides the capability to create aggregate domains, at any level of the logical hierarchy, that contain summary information for all domains beneath the aggregate domain in the hierarchy. For example the domain "Spooler\Collector\#" would contain aggregate information for all Spooler collector processes, and the domain "Spooler\#" would contain aggregate information about all Spooler processes. To define an aggregate process domain use the MONITOR command and the "#" character to identify the level at which to create the aggregate. For example: MONITOR PROCESS SPOOLER\COLLECTOR\# MONITOR PROCESS SPOOLER\PRINT\# MONITOR PROCESS SPOOLER\# C) Process ZLE allows you to set objectives on aggregate domains and their metric properties. For example to set an objective that the total process busy used by all Spooler Collector processes should be less than 10% and the total Spooler busy for all Spooler processes should be less than 20%, you would enter the following commands: RANK PROCESS SPOOLER\COLLECTOR\#, BUSY < 10 RANK PROCESS SPOOLER\#, BUSY < 20 D) Process ZLE lets a user control the amount of historical data being written to the ASAP database by limiting historical data to only aggregate domains. ASAP still processes each detail domain, computing statistics, and creating alerts when objectives aren't met, but can be setup to only write the aggregate summary records to disk. Use the MONITOR command and the "##" indicator to specify of an aggregate-only domain at a specific level in the hierarchy. For example: MONITOR PROCESS SPOOLER\COLLECTOR\## MONITOR PROCESS SPOOLER\PRINT\## MONITOR PROCESS SPOOLER\## E) Advanced ASAP users are given complete control over the content of aggregate records by externalizing the aggregate or propagate function for each attribute into the MetricRule formula in ASAP's Entity Definition Language (EDL). For example the Process Busy attribute defaults to summarize all the Busy attribute values into the aggregate record, so the aggregate represents the total Process Busy for all processes in the group. This default behavior is defined in the MetricRule for the Busy attribute, and it can be changed to show the average Busy for all processes, or the minimum or maximum Busy values found, or by removing the MetricRule formula ASAP will propagate the Busy value from the domain with the highest alert state for Busy. The Process MetricRule formula is defined as follows: METRICRULE "" is: SUM|AVG|MIN|MAX|CNT The default varies by attribute: Pri - MIN MRecv - SUM Busy - SUM QLen - MAX MPages - SUM MQLen - MAX MSent - SUM PFaults - SUM Attributes not in the list have no default MetricRule defined therefore the aggregate value is determined by propagating the value with the worst ASAP state to the aggregate domain. F) The state at which the Process SGP considers a domain to be alerting has been externalized into a new Process parameter. The MINSTATE parameter is used to set a state other than the default state of low alert (3). In addition, the MINONLY and NORECS parameters are added to provide additional levels of control over records written to the ASAP historical database. G) Process ZLE adds the ability to retrieve detail data for alerting domains directly from ASAP memory. This lets a user configure an aggregate-only domain but still see the alerting domains when errors occur without incurring disk I/O overhead for all the detail records. The Process EDL can now also define a detail command that uses the MEMORY, MINSTATE and COUNT command options to retrieve alerting detail domains whenever a users right-mouse's on an aggregate-only domain and chooses "Show Object Details". H) The PROCESS command now supports the AGGREGATE and AGGREGATEONLY options, in addition to the AGGONLY and AO abbreviations for AGGREGATEONLY. In summary, Process 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 Server Manual that ships with this release for more information on the Process ZLE enhancement. (SOLN 10-030822-9097) Problems Corrected: 1. [AAD] The query file ENFALL did not include a query for the APP entity. A new "?Section APP" has been added as an example of how to use ENFORM to query Application entity data in the ASAP database. LIKELIHOOD: Unlikely FIX-INFO: The ENFALL file for ASAP 2.4 has been updated to include a new APP section that can use Enform to query Application entity data in the ASAP database. (SOLN 10-030822-9109) 2. [AAD] SYMPTOMS: The Monitor command defaults to add. Some ASAP users expect the behavior to act as the information function list, info. A set option has been added to control the default behavior. For more info, enter HELP SET MONITORADD from the ASAP CI. LIKELIHOOD: Unlikely FIX-INFO: ASAP now provides the ability to alter the default behavior of the MONITOR command. The SET MONTORADD command turns off the default ADD, making it into an INFO command. (SOLN 10-030822-9098) 3. [AAD] SYMPTOMS: ASAP CI abended when MONITOR/OUT/ commands were entered. LIKELIHOOD: Unlikely WORKAROUNDS: Restart ASAP CI and re-enter the MONITOR command. FIX-INFO: ASAP CI will no longer abend after multiple monitor commands followed by a MONITOR/out/ command. (SOLN 10-030822-9099) 4. [AAD] SYMPTOMS: ASAP did not alert when a TMF auditdump enters the disabled state. LIKELIHOOD: Certain WORKAROUNDS: None FIX-INFO: ASAP now alerts for disabled TMF auditdumps. (SOLN 10-030822-9100) 5. [AAD] SYMPTOMS: CPU type S7600 or S76000 was not displayed when they were installed. LIKELIHOOD: Certain WORKAROUNDS: None FIX-INFO: Configured S76000 CPU's are displayed when using the type option for the ASAP CI CPU command. (SOLN 10-030826-9145) 6. [AAD] SYMPTOMS: Disk SGP could abend when the rate counter overflowed. LIKELIHOOD: Unlikely WORKAROUNDS: None FIX-INFO: The counters OutputKb, InputKb, and rate are now checked for overflow, and set to zero when they exceed the max value for an int(32) variable. (SOLN 10-030826-9147) 7. [AAD] SYMPTOMS: Spurious output of the Status attribute name sometimes occurred when using RANK, OBEYFORM option. LIKELIHOOD: Likely WORKAROUNDS: None FIX-INFO: Status is no longer included in OBEYFORM output unless there is a specific event objective on the Status attribute. (SOLN 10-030822-9101) 8. [AAD] SYMPTOMS: MONITOR, RANK, SHOW commands were not always parsed correctly when the domain name contains one or more slash characters. CONDITIONS: When the domain name contains a slash. LIKELIHOOD: Likely FIX-INFO: Slash is now interpreted correctly as an outfile indicator only when immediately following the command specifier. (SOLN 10-030822-9102) 9. [AAD] SYMPTOMS: Break key could cause delays for "MONITOR, LIST" commands. CONDITIONS: When many domains are in the down state. LIKELIHOOD: Likely FIX-INFO: The MONITOR command now processes the break key immediately. (SOLN 10-030822-9103) 10. [AAD] SYMPTOMS: Unprintable characters sometimes occurred in the MONITOR, LIST, DETAIL. CONDITIONS: For dataitems defined as constants. LIKELIHOOD: Likely FIX-INFO: The MONITOR command now verifies that each byte of output is printable before assuming the dataitem is a text constant. (SOLN 10-030822-9104) 11. [AAD] SYMPTOMS: Corrected spelling of the ASAP information message 1057. The word "suppression" was spelled incorrectly. LIKELIHOOD: Certain WORKAROUNDS: None FIX-INFO: Corrected spelling of suppression to suppression. (SOLN 10-030826-9148) 12. [AAD] SYMPTOMS: CPU SGP attribute PAGES was not reporting state correctly. LIKELIHOOD: Certain WORKAROUNDS: None FIX-INFO: The Int(32) metric variable pages is now used in the call to sgp_rankvalue_ (SOLN 10-030826-9149) 13. [AAD] SYMPTOMS: CPU SGP intermittently did not always report correct process queue length, when the measure subsystem was configured to collect process statistics. LIKELIHOOD: Certain WORKAROUNDS: None FIX-INFO: Replaced the call to getpeekpcb with the API call Process_getinfolist_. (SOLN 10-030826-9150) 14. [AAD] SYMPTOMS: CPU SGP could abend due to process send or receive counters overflowing. LIKELIHOOD: Likely WORKAROUNDS: None FIX-INFO: Counters pcb^this^rcvd, and pcb^this^outmsg are checked for overflow and set to zero when overflow is true. (SOLN 10-030826-9147) 15. [AAD] SYMPTOMS: CPU command did not allow 3 digit queue fields lengths to be displayed on the Asap client, or when using the raw option. LIKELIHOOD: Likely WORKAROUNDS: None FIX-INFO: Increased the output templates for the ASAP CI CPU command for the CPU queue counter length by one. (SOLN 10-030826-9156) 16. [AAD] SYMPTOMS: The ASAPLOG file could have a higher than expected I/O rate during each sample interval. LIKELIHOOD: Certain WORKAROUNDS: None FIX-INFO: Set last^write to juliantimestamp after closing the ASAPLOG. (SOLN 10-030826-9157) 17. [AAD] SYMPTOMS: The Disk command does not display the previous date when using the sample option. LIKELIHOOD: Certain WORKAROUNDS: None FIX-INFO: Output for disk command includes the date when the last^date and the current date read from ASAP data base are not equal. (SOLN 10-030826-9160) 18. [AAD] SYMPTOMS: The disk command could truncate the letter B of the mirror backup (MB) path for disk names containing 7 characters. LIKELIHOOD: Certain WORKAROUNDS: None FIX-INFO: Increased the disk output templates by one. (SOLN 10-030826-9160) 19. [AAD] SYMPTOMS: The ProcessBusy entity did not always return a state 2 (Up) when the process previous state was 7 (Critical), and the process was on the busiest process list for the current and previous sample interval. LIKELIHOOD: Likely WORKAROUNDS: None FIX-INFO: Moved stack and store of the structures this^pcb and last^pcb before the loop for checking all CPU statistics. (SOLN 10-030826-9161) 20. [AAD] SYMPTOMS: ENFORM could not read TMF floating point transaction rate; Process Busy, MSent, MRecv, and PFaults; and any TYPEDATA REAL64 value from ASAPX, due to lack of support for floating point in ENFORM. This problem has been addressed by declaring the value as TYPEDATA INT64, and then declaring an implied decimal point with the new FORMAT "F10.2" EDL clause. CONDITIONS: When using ENFORM to view ASAP data. LIKELIHOOD: Likely FIXINFO: ASAP now supports implied decimal points for attributes defined as INT64 with a FORMAT of "Fx.y" where x is the width of the field and y is the number of decimal places. The TMF transaction rate, and the Process Busy, MSent, MRecv and PFaults attributes have all been changed to INT64. Any ASAP Extension (ASAPX) user wishing to view ASAPX data with ENFORM should define all user-defined ASAPX attributes as INT64. In addition the Avail, Busy and Unavail built-in attributes should be changed to INT64 when included in application EDL files. See the ASAP Extension Manual for complete details. (SOLN 10-030822-9105) 21. [AAD] SYMPTOMS: The ASAP CI would abend when outputting more than 32767 lines. CONDITIONS: Set IOCONTROL 0 LIKELIHOOD: Certain WORKAROUNDS: Set IOControl < 32767 FIX-INFO: Line counter was changed from 16 to 32 bits. (SOLN 10-030822-9110) 22. [AAD] SYMPTOMS: The ASAP Expand SGP did not report the level 4 and level 3 stats: Connect, Ack, Nak, Cancel correctly on a multiline configuration. LIKELIHOOD: Certain WORKAROUNDS: None FIX-INFO: The EXPAND path statistics moves the counters to the Expand line record. (SOLN 10-030826-9163) 23. [AAD] SYMPTOMS: The File entity was missing the userid, Security string, Partitions and Last Open time for SQL shorthand view files. LIKELIHOOD: Certain WORKAROUNDS: None FIX-INFO: The userid, security string, number of partitions and last open time are now included for SQL shorthand view files. (SOLN 10-030822-9106) 24. [AAD] SYMPTOMS: The domain name token is not the event subject token in ASAP alert events. LIKELIHOOD: Certain WORKAROUNDS: None FIX-INFO: The SET OBJECTIVESEVENTSUBJECT command will set the event subject to be the domain name token, ZASP-TKN-ASAP-DNAME. (SOLN 10-030822-9107) 25. [AAD] SYMPTOMS: Difficulties extracting historical ASAP data into CSV files or files intended for input to SQL. LIKELIHOOD: Unlikely. WORKAROUNDS: None FIX-INFO: The APP command now supports an EXTRACT option to create separate files for each user-defined entity, or subset thereof. It also now supports a NOLINEBREAK option for output of data to programs, files and devices that are not limited to 132 characters per line. (SOLN 10-030827-9187) 26. [AAD] SYMPTOMS: The Disk SGP did not always report the EMS Down volume event when other disk attributes had thresholds set. LIKELIHOOD: Likely. WORKAROUNDS: None FIX-INFO: The Disk SGP events continuation word is now set correctly for each disk domain. (SOLN 10-030923-8437) 27. [AAD] SYMPTOMS: The CPU SGP did not display CHIT values greater than 999. LIKELIHOOD: Likely. WORKAROUNDS: None FIX-INFO: Increased the CHIT field width by 1, in the CPU command templates. (SOLN 10-031001-0080) Known Problems Remaining: 1. SYMPTOMS: Status monitor command can time out when SGP's take too long to report status information. IMPACT: CI unresponsive until 2 minute timeout occurs CONDITIONS: NONE LIKELIHOOD: Unlikely (SOLN 10-030826-9164) 2. SYMPTOMS: The ASAP command interpreter command "LH, INFO" will display the primary process ID as 255 for any "Expand" line handler process that is greater than 255. CONDITIONS: NONE LIKELIHOOD: Certain (SOLN 10-030826-9165) 3. SYMPTOMS: The RDF SGP will abend and create saveabend files when communication is lost with the backup node. CONDITIONS: NONE LIKELIHOOD: Certain (SOLN 10-020508-8800) 4. SYMPTOMS: SGP's CPU placement is not user configurable. CONDITIONS: NONE LIKELIHOOD: Certain (SOLN 10-020222-6888) 5. SYMPTOMS: Disk SGP not displaying largest fragment information, when using the raw option. CONDITIONS: NONE LIKELIHOOD: Certain (SOLN 10-020312-7324)