SPR - Softdoc T0402H03^AAX/T0402L01^AAY SOFTWARE RELEASE DOCUMENT Product Name: ASAP 3.2.4 SERVER SPR ID: T0402L01^AAY - L-series T0402H03^AAX - H-/J-series DATE: 30SEP2016 Copyright Notice: HPE Restricted Copyright 2016 Hewlett Packard Enterprise Development LP. Confidential computer software. Valid license from HPED LP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. Summary: To get the full benefit of this SPR contact license.manager@hpe.com. Continues operation on license renewal in production environments. Provides improved software license notification messages. ASAP Monitor would allow remote nodes to be started when the remote node was at a higher revision than the starting collector node. Disk SGP displayed down, when the disk was Hard Down. T0402V03^AAX for H-series/J-series processors is equivalent to T0402L01^AAY for NonStop L-series processors. [H03^AAV] ASAP 3.2.3 is a minor bug fix release that corrects the following: EXPAND SGP did not show Path error when configured incorrectly. CIP SGP reported persistent error 21 when CLIM timeouts occurred. PROCESSBUSY command showed only first 5 letters of OVDP process. DISK SGP did not display data for certain disk types. EXPAND SGP was missing the DFRAME info in the LH display. CIP SGP CLIMCMD command bond IP address event 4617 was displayed. DISK SGP reported Unexpected Error 3403. DISK SGP reported errors when SSD switched to backup paths. DISK SGP did not display an event when disk controller went down. COMM SGP displayed wrong COMM domains after MONITOR COMM command. ASAP CI CPU, DETAIL Swap data was shifted right one column. CIP SGP counters were not displayed correctly. CIP SGP reported Error 4617 ASAPCIP GET CLIM INFO SPI Error 0. CIP Entity definitions in ASPDDLDB were not complete. TCP SGP would not startup on Expand node number zero. PROCESS SGP messages sent were not reported if value was large. PROCESS SGP messages received were not reported for large values. PROCESS SGP page faults were not reported if value was large. PROCESSBUSY SGP did not show Rmsg or Smsg with high message rates. PROCESSBUSY SGP output showed wrong value for Smsg & Pages. DISK SGP showed incorrect value after receiving an error 40. DISK SGP showed requests counts of zero. SWAP SGP did not display an added or deleted swap file. CPU SGP could abend when there were high page faults values. T0402V03^AAV for H-series/J-series processors is equivalent to T0402L01^AAW for NonStop L-series processors. [H03^AAT] ASAP 3.2.2 is a bug fix release that corrects the following: GOAL statements with STATUS ACTION clause would not execute. Process SGP at times showed zero value for messages sent/received. Process SGP at times showed zero value for page faults. Expand SGP showed an operation state as zero for incorrect lines. Expand SGP did not show Path error when configured incorrectly. CIP SGP reported persistent error 21 when CLIM timeouts occurred. CPU SGP did not always display the correct number of IPUs for CPUs. CPU SGP did not determine correct state for the BLADES attribute. CPU SGP could ABEND if process busy ENTRIES>20 or Subsamples>7. ENFALL DSK query incorrectly computed value of %Used disk space. ASAP Client setup will now install on 64-bit Windows versions. The ASAP Monitor displays the correct email address when an optional ASAP plug-in product is not licensed. T0402V03^AAS for S-series/K-series processors is equivalent to T0402H03^AAT for Integrity NonStop servers and NonStop Blades servers. [H03^AAR] ASAP 3.2 adds support for escalating and Boolean goals. With escalating goals users can define up to 3 alert levels for an attribute, generating a separate alert and optional EMS event or automated action at each level of severity. Boolean goals let a user combine attributes from an entity into a goal using the AND | OR Boolean operators to generate a single alert, EMS event or automated action when the combined goal comparison fails. ASAP 3.2 also provides enhanced warning messages for version mismatches, configuration inconsistencies and other problems that can affect operational performance. This version also contains corrections for the following problems. Goal/Rank command output could be difficult to read. ASAP CI commands against an Objectives database could timeout. Precision could be lost for some CPU attribute values when the values were output in EMS events or substitution tokens for the Action server. State values for attributes of phantom disk drives could be set to zero. ASAP collector startup failures could occur when Set Retain was set to Rollover and the start of the collector was attempted during the Cleantime interval. The Measure on demand function invoked by Show Related Measurement could inadvertently purge files in the fileset $System.System.ZX*. The PRIORITY procedure call could return an unexpected value. In a mixed JBOD/CLIM disk environment the ASAP CI could incorrectly display the CLIM location when using the INFO option of the Disk command. Enhanced memory statistics for ASAP 3.0 records could be set to zero when using a later version of the collector. CPU metrics Dispatches, Chits, Disc I/O, and Swaps could be calculated incorrectly on heavily utilized processors. The Status Collect command could display a blank value for the Swap database file location. Refer to the Problems Corrected Section below for further details. T0402V03^AAQ for S-series/K-series processors is equivalent to T0402H03^AAR for Integrity NonStop servers and NonStop Blades servers. [H03^AAP] ASAP 3.1 T0402^AAP is a TCF bug fix only release that: Eliminates limits on the maximum number of Spooler jobs. Adds a new ASAP SPOOLER PLUS option to reduce SPOOLER PLUS overhead. Fixes problems with EMS UP events generated by the Expand SGP. Fixes problems where PROCESS MEMPAGES value was incorrect in queries. Fixes CLIM DISK stats for Requests, Blocked, Chits, Semaphore Queue. Fixes CPU Page/Memory Size compatibility between ASAP 2.8 and 3.0. T0402V03^AAO for S-series/K-series processors is equivalent to T0402H03^AAP for Integrity NonStop servers and NonStop Blades servers. [H03^AAN] ASAP 3.1 is a bug fix release that also includes changes to support NonStop Blades servers. For NonStop Blades servers the Disk entity has been changed to support storage Cluster I/O Module (CLIM) devices; the Process and ProcessBusy entities are changed to support process Affinity, IPU, and CBusy attributes; and the CPU entity is changed to support the number of IPU's for a logical CPU. The CLIM Interface Protocol (CIP) is now supported with a master CIP entity that contains 3 sub-entities: CIPCLIM to show statistics for CLIM devices; CIPMonitor for CIP Monitor processes; and CIPProvider for CIP Provider processes. Minor problems have also been corrected with the Comm, Disk, File, Process, Swap and TCP/IP entities. Refer to the problems corrected section for further information. T0402V03 for S-series/K-series processors is equivalent to T0402H03 for Integrity NonStop servers and NonStop Blades servers. [H03] ASAP 3.0 core server now includes TCP/IP subsystem monitoring. TCP/IP includes 19 TCP/IP and Telserv entities, and over 1000 new attributes. New SWAP entity provides in-depth virtual memory statistics allowing ASAP to set thresholds, alert, and take actions on KMSF statistics. New CPU memory statistics include swap, free, locked memory, etc, and allows thresholds, alerts, and actions to be taken on memory usage. ASAP can now host one or more real-time local/proxy websites. ASAP can optionally integrate with the HP Systems Insight Manager (SIM). New HTML entity-attribute grid-graph reports can be sent via website, email, or phone. ASAP Reports now support SIM level 1 integration. New notify control panel has 15 new notify content controls. New ASAP database structures support relative files to greatly reduce I/O overhead given large-record high-volume entities, such as the TCP/IP entity. ASAP 3.0 is now a licensed product. Run SYSINFO on each system to be licensed and E-mail the SYSINFO output for each system to License.Manager@HP.Com. Several minor problems have been fixed. The following SGP's have had corrections made to them: CPU, DISK, FILE, PROCESS, RDF, TAPE, SPOOLER, TCP, and TMF. Also there were corrections to custom events, goals, and the ASAP Monitor. Refer to the problems corrected section for further information. T0402V03 for S-series/K-series processors is equivalent to T0402H03 for Itanium Integrity NonStop servers. Superseded SPRs: T0402H03^AAN T0402H03^AAP T0402H03^AAR T0402H03^AAT T0402H03^AAV Requisite SPRs: T0346H09^ACH RDF/IMP if using RDF see note. T6028H01^ABL MEDIACOM/MEDIASRV H06.03-H06.23 or J06.03-J06.12 T6965H01^AAL SEEVIEW H06.01-H06.26 or J06.03-J06.12 T9053H02^AYF DP2 H06.09-H06.23 or J06.03-J06.10 T9057H01^AGQ EXPAND H06.03-H06.23 or J06.03-J06.12 T9086H01^AGC MEASURE H06.03-H06.08 T9086H03^AFV MEASURE H06.14-H06.16.02 T9086H04^AGV MEASURE H06.14-H06.19.03 T9086H05^AGZ MEASURE H06.20-H06.21.02 T9086H06^AGU MEASURE H06.22-H06.22.01 T9086J01^AFW MEASURE J06.04-J06.05.02 T9086J02^AGW MEASURE J06.04.00-J06.08.04 T9086J03^AHC MEASURE J06.09.00-J06.10.02 T9117H01^ABQ EXPAND MGR H06.03-J06.12 Note: T0346: The SPR required for RDF is GREATER than the SPR shown above. Please contact HP to verify that an RDF SPR that supports this version of ASAP exists, and DO NOT UPGRADE to this ASAP version (if ASAP is used to monitor RDF)until a correct RDF SPR is identified and installed. Contact the GMCSC to request an RDF SPR if you require it and it does not already exist. The function in T0346 is required only if you SET RDF ON. T6965: The function needed in T6965 is required only if you SET ACTION ON. The above SPR's listed are the minimum required SPR levels. For each product. Required Hardware: HPE Integrity NonStop servers Required Firmware: NONE Required Software: T0346H08 RDF/IMP if using RDF T0403H03 ASAP SRVR EXTENSION if using ASAP Extension T9050H01 NONSTOP KERNEL T9550H01 SOCKET LIBRARY T9552H01 TCP/IP FTP Microsoft Windows Vista, Microsoft Windows XP, Microsoft Windows 2000, Microsoft Windows ME, or Windows NT 4.0 or later. Microsoft TCP/IP stack and FTP client Manuals: 425263-005 ASAP Client Manual 429917-006 ASAP Messages Manual 522303-010 ASAP Server Manual 545871-001 ASAP QuickStart Manual Installation Considerations: Subsystem interruption required Installation Instructions: * When using DSM/SCM to install this SPR: - RECEIVE the SPR from disk or tape. - COPY the SPR to a new revision of the software configuration you want to update. - BUILD and APPLY the configuration revision. - Perform the pre-installation steps shown below. - Run ZPHIRNM to perform the RENAME step. - If not using H01.00 onward, VOLUME to the new/updated SYSnn, and run VTILT to determine if Shared Runtime Library conflicts must be resolved before loading the system. - Perform these pre-installation steps. 1. ASAP 3.0 and above are licensed products. Run SYSINFO on each system to be licensed and E-mail the SYSINFO output for each system to License.Manager@HPE.Com. Please be sure to obtain and install the license files before attempting to install ASAP 3.0 or any subsequent release. Note this only has to be done once. If you have obtained license files for ASAP 3.0 or subsequent then you do not need to obtain license files for any future release unless the term for the original license has expired. 2. Ensure that requirements for using this product are met (see Section the Required Hardware and Required Software sections above). 3. Ensure that prerequisites for the installation utility and any product-specific installation requirements are met (see Section D Installation Prerequisites below). 4. 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. 5. 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. 6. If you are using the ASAP Extension make a copy of the file $SYSTEM.SYSTEM.ASAPUSER. FUP - VOLUME $SYSTEM.SYSTEM - DUP ASAPUSER, ASAPSAVE.*, SAVEALL 7. If you are upgrading from ASAP 3.0 or an earlier release to ASAP 3.2 then this SPR includes a structural change to the Objectives database. All records in any old ASAP databases need to be saved prior to installing this version of ASAP. It is very important that you save the records using the old version of ASAP, then restore them using the new version of ASAP. Please follow these instructions to save your current ASAP databases. From the central ASAP collection node: TACL> ASAP +VOLUME $SYSTEM.ASAPSAVE +MONITOR/OUT ASAPOBEY/, OBEYFORM +RANK/OUT ASAPOBEY/, OBEYFORM +MONITOR/OUT ASAPOBEY/ \, OBEYFORM +RANK/OUT ASAPOBEY/ \,OBEYFORM (preceding commands must be done for each remote node) Once data from all nodes has been saved then shutdown ASAP and purge the ASAP objectives database files on each node. The objectives database files location is set with the SET OBJECTIVESDB command, or it defaults to $SYSTEM.ZASAP.DBOBJ. In addition to the file named in the SET OBJECTIVESDB statement a file named DBACT also exists in the same subvolume and should also be purged. NOTE: It is possible to run different versions of ASAP on different nodes in the network as long as the most current version runs on the main collector node. If a node is not going to be upgraded until later you should not convert the databases on that node to the new format until the new ASAP version is installed there. Please enter the ASAP CI HELP VERSIONS and HELP CONVERT commands for more information on versioning and database conversion. 8. If you are upgrading from an earlier version of ASAP please read the following steps. If you have archived data with the old version of ASAP that you would like to view later, you must save the following files: FUP - VOLUME $SYSTEM.SYSTEM - DUP ASAP, ASAPSAVE.*, SAVEALL - DUP ASAPxEDL, ASAPSAVE.*, SAVEALL - DUP ASAPxSYS, ASAPSAVE.*, SAVEALL - DUP ASAPxAPP, ASAPSAVE.*, SAVEALL where x is 3 if your old version is ASAP 3.0 or 3.1 otherwise x is 2. 9. 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. 10. 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 old database files before starting the new ASAP environment. FUP PURGE $..DB*! f) If you saved ASAP database records prior to the install then reload them now. First edit the file and add statements to delete automatically added aggregate domains that you want deleted. For example if there is a statement in the file that monitors all processes that begin with $A: MONITOR PROCESS $A*, ADD Then ASAP will automatically create an aggregate-only domain named $A*\## when that statement is processed from the obey file. If you do not want that aggregate-only domain then enter a line into the obey file immediately following that statement to delete the aggregate-only domain. For example: MONITOR PROCESS $A*, ADD MONITOR PROCESS $A*\##, DELETE ASAP automatically adds aggregate-only domains for FILE and PROCESS objects when wildcards are used, when subvolumes are specified for file monitoring and when processes are monitored using object filenames. Once the edit file has been modified and checked for completeness then from the same central node that you saved the data on please enter: ASAP + OBEY $SYSTEM.ASAPSAVE.ASAPOBEY 3. If you are using the ASAP Extension copy the duplicated file from the Pre-Installation instructions Step 1 back to $SYSTEM.SYSTEM. FUP - VOLUME $SYSTEM.ASAPSAVE - DUP ASAPUSER, SYSTEM.*, PURGE, SAVEALL 4. Start the new ASAP version. 5. When looking at ASAP data from earlier ASAP versions please be sure to use the old ASAP CI and EDL files saved to the $SYSTEM.ASAPSAVE subvolume if you performed the save step defined above 6. With ASAP versions H0402H03^AAY and L0402L01^AAW the ASAP Process Busy record changed for longer process names. In a multi node mixed ASAP Version environment, update the collector node with this version or T0402H03^AAV or L0402L01^AAW before updating any other nodes. New Features: 1. [H03^AAR] New escalating goals feature lets a user define up to 3 alert levels for the same attribute. Alerts and optional EMS events and/or automated actions can be generated at each level. The goals can specify escalating or de-escalating alert levels. As an example this command defines an escalating goal for a busy CPU: GOAL CPU, BUSY < 60, BUSY << 80 INFO, BUSY <<< 90 CRITICAL (SOLN 10-061213-1099) 2. [H03^AAR] New Boolean goal feature lets a user combine attributes using the AND | OR Boolean operators into a goal that can generate an alert and optional EMS event and/or automated action when the combined goal comparison fails. Boolean goals are named and can be nested using parentheses. For example this command sets a goal to alert on busy CPUs: G CPU, BUSYGOAL=(BUSY < 80 AND QUEUE < 2) CRITICAL REPEAT (SOLN 10-061213-1101) 3. [H03^AAR] ASAP CI now issues improved warning messages when version, configuration or other problems are found during installation, startup or normal operation. (SOLN 10-100128-7825) 4. [H03^AAN] The CLIM Interface Protocol (CIP) entity and its sub-entities have been added to better support NonStop Blades Servers. (No SOLN) 5. [H03^AAN] Several Blades-specific attributes have been added to the CPU, PROCESS and PROCESSBUSY entities to better support NonStop Blades servers. These include process Affinity, IPU number, CBusy and the count of IPUs. (No SOLN) 6. [H03] The ASAP server now requires a license per node in order for ASAP to run. To obtain a valid license, run SYSINFO on each system to be licensed and E-mail the SYSINFO output along with the type of license and number of CPUs to license.manager@hp.com. (No SOLN) 7. [H03] ASAP TCPIP is now included in the ASAP core products T0402V03 and T0402H03. TCP/IP supports v4, v6 in all modes, ICMP, IP, Process, QIO, RTE and UDP, ARP, IGMP, LOOP, MONGQ, SOCK ICMP6, IP6, SubNet, Route and Port stats. Support for TELSERV process, Service and Window stats are also included in ASAP core products. This results in 19 new TCP/IP and TELSERV entities and more than 1000 attributes. (No SOLN) 8. [H03] Virtual memory (Swap SGP) support has been added. ASAP 3.0 Reports on virtual memory (KMSF) per processor and monitors and reports on all the configured swap files for each CPU. A total of 49 SWAP attributes are now provided in ASAP 3.0. Some of the statistics maintained by the Swap SGP are percent full for all configured swap files, percent full for each individual swap file, reserved memory which is the total virtual memory allocated for the CPU. The Swap SGP also displays the amount of virtual memory allocated for each swap file. See the ASAP Server manual for all of Swap SGP statistics and threshold support, or mouse over the SWAP entity attributes in ASAP client for an explanation of each SWAP attribute. (No SOLN) 9. [H03] CPU memory statistics have been added. New attributes include memory size, swappable memory, free memory, locked memory, maximum locked memory, and highest locked memory. (No SOLN) 10. [H03] ASAP can now host real-time local/proxy websites and can now optionally integrate with Systems Insight Manager. New reporting capabilities are highly customizable, eg there are 15 new notify content controls and checkboxes for setting up ASAP's reporting. New HTML entity attribute grid and graph reports that can also send notifications to ASAP users about the overall state of objects. Reports can be sent via Email, wireless phones, or customer websites. Reports can also be integrated with HP Systems Insight Manager (SIM). Refer to the ASAP Client Manual for further detail. (No SOLN) 11. [H03] New HTML entity attribute grid and graph reports that can notify ASAP users about the overall state of their NonStop servers. Reports can be sent to Email addresses, or wireless phones, or to a customers websites. Reports can also be integrated with HP Systems Insight Manager (SIM). (No SOLN) 12. [H03] ASAP database performance can be greatly improved in high-volume large-record environments. A new SET option allows you to configure the ASAP database to use a Relative database file. The new set option allows ASAP users to control which entity should be configured to use relation files. One possible indication that a relative file DB is needed is when the ASAP Log has a high volume of missed sample log records. To achieve higher ASAP database performance the user simply configures an ASAP collector to create a Relative file by using the new SET PARTITION option. (No SOLN) 13. [H03] The count of unique batch jobs has been added to the Spooler SGP. A new attribute, UBatch, counts the number of unique batch jobs in a Spooler subsystem. (SOLN 10-061201-0829) 14. [H03] RDF domain name parsing and support has been strengthened, so that MONITOR commands cannot be issued against RDF subdomains. (SOLN 10-061219-1264) Problems Corrected: 1. [H03^AAX] SYMPTOMS: The ASAP Disk SGP displayed down state when the disk is in a Hard Down state. CONDITIONS: When an individual disk or disk volume is in a Hard Down state. LIKELIHOOD: Likely (SOLN 10-160901-1152) 2. [H03^AAX] SYMPTOMS: ASAP would start a remote node with a higher ASAP version than the collector node. IMPACT: The remote nodes would produce errors and would most likely not return any performance or availability metrics. The ASAP CI on the collection node would abend when the ASAP CI command STATUS \REMOTE1 is entered from the CI. CONDITIONS: When a down rev collector node would start a remote node with a higher revision. LIKELIHOOD: Certain (SOLN 10-160121-8716) 3. [H03^AAX] SYMPTOMS: To obtain the full functionality of this SPR obtain a new ASAP license by sending SYSINFO to License.Manager@HPE.com. Previously upon license expiry ASAP might stop running or collect statistics. Now ASAP continues to run in production environments even upon license expiration. ASAP now also provides improved software license status EMS messages. CONDITIONS: When the ASAP License expired. LIKELIHOOD: Likely (SOLN 10-160901-1153) 4. [H03^AAV] SYMPTOMS: ASAP Monitor could abend. When the process busy page fault counter overflows. CONDITIONS: When the Process Busy page fault counter overflows. LIKELIHOOD: Unlikely (SOLN 10-150810-3299) 5. [H03^AAV] SYMPTOMS: ASAP CPU SGP may abend when the page fault values were very high. CONDITIONS: The ASAP CIP SGP could abend when the Page Faults values were very large, and the CPU utilization was high. LIKELIHOOD: Not Likely (SOLN 10-150819-3321) 6. [H03^AAV] SYMPTOMS: ASAP TCP SGP would not startup if Expand node was \zero. CONDITIONS: Node that has the Expand node number zero. LIKELIHOOD: Certain (SOLN 10-120905-4619) 7. [H03^AAV] SYMPTOMS: ASAP Process SGP Page Faults were not reported when counter value was large. CONDITIONS: Processes have a very large page fault rate for a long time. LIKELIHOOD: Likely (SOLN 10-150726-7196) 8. [H03^AAV] SYMPTOMS: ASAP Process SGP Messages Received were not reported when counter value was large. CONDITIONS: Processes have high message receive rate for a long time. LIKELIHOOD: Likely (SOLN 10-150726-7195) 9. [H03^AAV] SYMPTOMS: ASAP Process SGP Messages Sent not reported when counter value was large. CONDITIONS: Processes have a high message sent rate for a long time. LIKELIHOOD: Likely (SOLN 10-150726-7194) 10. [H03^AAV] SYMPTOMS: ASAP Swap SGP did not recognize the addition/deletion of swap files. CONDITIONS: Deletion or addition of a KMSF swap file on any CPU. LIKELIHOOD: Certain (SOLN 10-150709-7008) 11. [H03^AAV] SYMPTOMS: ASAP DISK SGP displayed incorrect values after getting error 40. Request counters were displayed as zero. CONDITIONS: Error occurred when Disk SGP was discovering disk devices and a Guardian API call was executed and a disk failure occurred. Requests at times were shown as zero for very busy disk drives. LIKELIHOOD: Likely (SOLN 10-150224-5554) 12. [H03^AAV] SYMPTOMS: ASAP PB command showed incorrect sent or received messages (Smsg or Rmsg) if their value was greater than 9999. CONDITIONS: Messages received or sent exceed 9999. LIKELIHOOD: Certain (SOLN 10-141219-4971) 13. [H03^AAV] SYMPTOMS: ASAP PROCESSBUSY output showed incorrect values for Smsg and Pages. CONDITIONS: When sent and received message rates are high. LIKELIHOOD: Likely (SOLN 10-141219-4969) 14. [H03^AAV] SYMPTOMS: ASAP PROCESSBUSY did not show correct Rmsg or Smsg values for processes with very high message rates. CONDITIONS: PROCESSBUSY Smsgs and Rmsgs are greater than 32K per second, ASAP may display the values incorrectly. LIKELIHOOD: Likely (SOLN 10-141219-4968) 15. [H03^AAV] SYMPTOMS: CIP definitions Monitor and Provider were missing in ASPDDLDB. CONDITIONS: Create an Enform query specifying data for the CIP monitor or provider. LIKELIHOOD: Likely (SOLN 10-140407-1367) 16. [H03^AAV] SYMPTOMS: ASAP CIP SGP returned TRAP Description Error 4617 ASAPCIP GET CLIM INFO SPI Error 0. CONDITIONS: Intermittent depending on CLIM traffic. Same as solution 10-120709-4041. LIKELIHOOD: Unlikely (SOLN 10-140205-0610) 17. [H03^AAV] SYMPTOMS: ASAP CIP counters were not displayed correctly. CONDITIONS: When server messages received/sent were greater than 9999 the CIP SGP displayed the values as 9999 instead of the correct value. The ASAP3SYS EDL file for the Entity CIPClim format was changed to display higher values. LIKELIHOOD: Unlikely (SOLN 10-131125-9813) 18. [H03^AAV] SYMPTOMS: ASAP Swap column in CPU DETAIL output shifted the swap output to the right by one position. CONDITIONS: From the ASAP CI enter the command CPU, Detail. LIKELIHOOD: Certain (SOLN 10-130304-6471) 19. [H03^AAV] SYMPTOMS: ASAP COMM SGP displayed incorrect information after MONITOR command. CONDITIONS: Add another comm line and let the ASAP COMM SGP autodiscover the newly added domain. LIKELIHOOD: Certain (SOLN 10-130219-6317) 20. [H03^AAV] SYMPTOMS: ASAPDSK DSK reported errors when SSD disks (subtype 50) were switched to the backup paths. CONDITIONS: Switch the volume to either -M or -M or both. LIKELIHOOD: Certain (SOLN 10-120919-4772) 21. [H03^AAV] SYMPTOMS: ASAPDSK SGP dislplayed unexpected Error 3403. CONDITIONS: ADD Solid State disk subtype 50. LIKELIHOOD: Certain (SOLN 10-120912-4691) 22. [H03^AAV] SYMPTOMS: If the CLIMCMD command were used to bond an IP address, would cause ASAPCIP SGP event 4617 for each ASAP sample interval. CONDITIONS: Bond an additional IP address. LIKELIHOOD: Unlikely (SOLN 10-120709-4041) 23. [H03^AAV] SYMPTOMS: ASAP CI LH command did not display DFRAME information. CONDITIONS: When a new Expand line is added. LIKELIHOOD: Likely (SOLN 10-120612-3687) 24. [H03^AAV] SYMPTOMS: ASAP did not display data for certain disk types. CONDITIONS: SSD drives are configured subtype 50. LIKELIHOOD: Certain (SOLN 10-120308-1979) 25. [H03^AAV] SYMPTOMS: ASAP PROCESSBUSY command showed only first 5 letters of a process name. CONDITIONS: In the PROCESS-NAME column of the PROCESSBUSY report there was only sufficient space for 6 character ($ + 5) process names. When a process busy name is $PROCESS only $PROCE was displayed. LIKELIHOOD: Certain. (SOLN 10-100604-0849) 26. [H03^AAT] SYMPTOMS: ASAP GOAL statements with an ACTION of the form: GOAL .. STATUS ACTION would not execute. CONDITIONS: GOAL command with a STATUS ACTION clause (in ASAP 3.2 only). LIKELIHOOD: Likely FIX-INFO: The ASAP command interpreter ACTION LIST command did not correctly parse and return the action string for ACTION LIST statement STATUS ACTION lookups. ACTION LIST commands of the form ACTION LIST [] without the would fail with the message: "No ACTION found for action tuple. No Action to take". Since the STATUS ACTION is the only ACTION with no operator, it was the only ACTION type that failed. This problem has been corrected by properly parsing "operator-less" action commands of the form: ACTION LIST STATUS ACTION. (SOLN 10-110618-8181) 27. [H03^AAT] SYMPTOMS: The ASAP PROCESS entity sometimes incorrectly displayed zero values for Messages Sent, Messages Received, and Page Faults. CONDITIONS: NonStop server has been running long enough for the internal system counter value for messages sent, messages received, or page faults to exceed 2,147,483,647. LIKELIHOOD: Likely, once the counter exceeds 2,147,483,647. Depending on system load, it can take months or years after a processor reload before this condition would be present. FIX-INFO: This problem has been corrected by treating values of messages sent, messages received, and page faults as unsigned. (SOLN 10-110809-9077) 28. [H03^AAT] SYMPTOMS: The Expand SGP creates an EMS message with an incorrect Expand line name in the event when the operational state value is equal to zero. CONDITIONS: When adding Expand lines to a node. LIKELIHOOD: Likely FIX-INFO: The problem occurs when an Expand line is added to the node and not when the line is deleted. When the call to sgp_rankvalues_ was called, the Expand SGP was using an incorrect last state values to be used, producing the incorrect EMS event. (SOLN 10-110502-7432) 29. [H03^AAT] SYMPTOMS: Error 21's being reported by the ASAP CIP SGP. CONDITIONS: The CIP manager can timeout on a SPI request when the CLIM device is busy or unresponsive. LIKELIHOOD: Not Likely FIX-INFO: Move zeros from Error (not ErrorDetail) to reset the header error value at each pass. (SOLN 10-110331-6963) 30. [H03^AAT] SYMPTOMS: The Expand SGP did not report a Path error for incorrectly configured Expand Paths. CONDITIONS: When an Expand Path that has multiple lines associated with the path is incorrectly configured. LIKELIHOOD: Certain FIX-INFO: The EMS message "Can't obtain path statistics" was suppressed due to not checking the L2 protocol for an Expand Path. (SOLN 10-110217-6196) 31. [H03^AAT] SYMPTOMS: ASAP CI was not displaying the correct value for the number of IPUs. The ASAP Client displays the correct value. CONDITIONS: When using the ASAP CI command "CPU, Type" the value for IPU's is incorrect. The values for MemQ and PgLk are also incorrect. LIKELIHOOD: Certain FIX-INFO: The ASAP CI array did not include the value for the memory queue length counter. The array is used by the call for producing the ASAP CI Output. The missing value for Memory queue was added to the array (SOLN 10-110217-6195) 32. [H03^AAT] SYMPTOMS: ASAP CPU SGP was not determining the correct state for the Blades attribute CONDITIONS: The ASAP CPU SGP is not showing the correct state for the threshold attribute blades, when the goal: "GOAL CPU, BLADES = " was configured. LIKELIHOOD: Certain FIX-INFO: Use the correct string value for number of blades in the call to SGP_RankValues (SOLN 10-110217-6194) 33. [H03^AAT] SYMPTOMS: ASAP CPU SGP would abend when processbusy entries are greater than 20 or subsamples are greater than 7. CONDITIONS: When the ASAP CI commands Set ProcessBusy entries 21 or the CI command Set ProcessBusy subsamples 8 are used for configuring the ProcessBusy entity. LIKELIHOOD: Certain FIX-INFO: Add a check for the value for number of ProcessBusy entries, and check for value specified for number of subsamples, so the internal structures of the CPU SGP do not exceed their boundaries. (SOLN 10-111102-0344) 34. [H03^AAT] SYMPTOMS: ASAP Client would not install on 64-bit versions of Windows. CONDITIONS: Original ASAP Client setup was constructed using a version of InstallShield that pre-dated 64-bit Windows PCs/workstations. LIKELIHOOD: Likely FIX-INFO: The ASAP 3.2.2 Client setup is now constructed using the latest Version of InstallShield. (SOLN 10-110826-9398) 35. [H03^AAT] SYMPTOMS: The ASAP monitor writes an EMS event with an incorrect email address for obtaining a new license key. It displayed the email address as License.Manage@HP.com when it should display License.Manager@HP.com. CONDITIONS: When an optional plug-in product is enabled but not licensed. LIKELIHOOD: Certain FIX-INFO: Change the Error text to License.Manager@HP.Com. (SOLN 10-120103-1184) 36. [H03^AAR] SYMPTOMS: Goal/Rank command output could be difficult to read. CONDITIONS: When entities were enabled that contained long attribute names. LIKELIHOOD: Likely FIX-INFO: Previously ASAP CI aligned Rank/Goal output based on the longest attribute name across all enabled entities. Now ASAP CI aligns output for each entity separately based on the longest attribute name in the entity while also ignoring extra long attribute names to perform the alignment. (SOLN 10-100104-7266) 37. [H03^AAR] CAVEAT: The timeout would only occur on the first command that accessed the Objectives database on a node. SYMPTOMS: An ASAP CI command that accessed the Objectives database could timeout. CONDITIONS: When the command was the first command that would access the Objectives database. LIKELIHOOD: Unlikely SIDE-EFFECTS: Commands could fail by timing out including commands from the Action server to retrieve action information about specific goals. FIX-INFO: ASAP CI would ask a running ASAP Monitor process for the name of the Objectives database file in case the running copy was using a different database than the one specified in the most recent SET OBJECTIVESDB command. If the ASAP Monitor process was busy then the command could timeout. The ASAP Monitor process now outputs a control file at startup that contains the name of the Objectives database file and other configuration information. ASAP CI now reads the control file instead of talking to the ASAP Monitor process. (SOLN 10-091230-7240) 38. [H03^AAR] SYMPTOMS: Precision could be lost for some CPU attributes when their values were output in EMS events or sent to the Action server. CONDITIONS: When some CPU attribute values were displayed in EMS events or when those values were sent to the Action server using substitution tokens. LIKELIHOOD: Likely FIX-INFO: The CPU entity definition language was updated to include the correct decimal point precision for all attributes. (SOLN 10-091230-7239) 39. [H03^AAR] SYMPTOMS: Phantom disk drives have attribute state values set to zero. IMPACT: This could result in invalid states being displayed for attributes of phantom disk drives. CONDITIONS: Normal operation. LIKELIHOOD: Likely (SOLN 10-091230-7245) 40. [H03^AAR] SYMPTOMS: Previously ASAP STARTUP COLLECT failures occurred when SET RETAIN was set to ROLLOVER and when STARTUP COLLECT was attempted during the time range between CLEANTIME and (CLEANTIME + 15 minutes). This issue has been corrected. CONDITIONS: When starting the ASAP collector during cleantime and when SET RETAIN is set to Rollover. LIKELIHOOD: Unlikely (SOLN 10-091207-6905) 41. [H03^AAR] SYMPTOMS: Previously Measure on Demand function invoked by Show Related Measurement could inadvertently purge files in the file set $SYSTEM.SYSTEM.ZX*. This issue has been corrected. CONDITIONS: When invoked by Show Related Measurement. LIKELIHOOD: Likely (SOLN 10-091209-6964) 42. [H03^AAR] SYMPTOMS: The Guardian NonStop Procedure call PRIORITY was changed to return the value of the current priority instead of the Initial priority. ASAP now supports the updated change to the API call PRIORITY. CONDITIONS: Normal ASAP operation. LIKELIHOOD: Likely (SOLN 10-090326-0316) 43. [H03^AAR] SYMPTOMS: When ASAP is running in a mixed JBOD/CLIM environment ASAP will display GMS instead of Location for the CLIM disks when the first record in the ASAP DB is for a JBOD or servernet disk. CONDITIONS: When ASAP is running in a mixed CLIM/JBOD configuration. LIKELIHOOD: Likely (SOLN 10-091228-7235) 44. [H03^AAR] SYMPTOMS: The CPU SGP Enhanced memory statistics MemSize, MemSwap, MemLocked, MemFree and MemLckMax are set to zero when the records are sent to an ASAP collector that is version 3.1 or higher. CONDITIONS: When ASAP is running in a mixed 3.0 3.1 environment. LIKELIHOOD: Likely (SOLN 10-091228-7234) 45. [H03^AAR] SYMPTOMS: The CPU SGP metrics Dispatches, Cache Hits, Disc I/O and Swaps could have been inaccurately calculated. Internal structures were not large enough and could overflow when a processor was very busy with very high dispatch rates, Disk I/O rates, high swap rates or high Cache hit rates. CONDITIONS: Can occur on very busy processors LIKELIHOOD: Likely (SOLN 10-091228-7233) 46. [H03^AAR] SYMPTOMS: The ASAP command STATUS COLLECT did not display the data base file information for the SWAP SGP. CONDITIONS: When using the ASAP CI Command STATUS COLLECT. LIKELIHOOD: Certain (SOLN 10-100126-7753) 47. [H03^AAP] CAVEAT: A new Spooler Smart Gathering Process param called PLUS was added in this release. Using the PLUS parameter will only collect data at the supervisor level. The attributes Jobs, Batch, Open, Print, Hold, Dev's, Locs, and UBatch will equal zero at the Collector, Device and Print levels. SYMPTOMS: The Spooler Smart Gathering Process would generate an incorrect 4315 event message in large spooler environments. The ASAP Spooler SGP in a large Spooler Plus environment could cause the Spooler Supervisor process to become very busy. CONDITIONS: When there are 10000 or more jobs in the Spooler collector, or there are 10000 or more batch jobs in the Spooler collector. LIKELIHOOD: Likely (SOLN 10-090326-0316) 48. [H03^AAP] SYMPTOMS: Process SGP MemPages value is not correct when executing an ENFORM query against historical data. CONDITIONS: When processing historical data using an ENFORM query LIKELIHOOD: Likely FIX-INFO: Changed DDL to reference PRO^STATS4 record. (SOLN 10-090915-4590) 49. [H03^AAP] SYMPTOMS: The Expand Smart Gathering Process could generate incorrect ASAP or EMS UP events when an Expand line is deleted from the NonStop Server configuration CONDITIONS: When an Expand line handler is deleted from the Servers configuration and other Expand line handlers are down. LIKELIHOOD: Unlikely (SOLN 10-090309-9846) 50. [H03^AAP] SYMPTOMS: Disk counters Requests, Requests Blocked, Cache Hits, Volume Semaphore queues always show a zero when the backup path of a Clim disk is being used. CONDITIONS: When using the -B or -MB paths of Clim disk drives. LIKELIHOOD: Likely (SOLN 10-091230-7244) 51. [H03^AAP] SYMPTOMS: When using a 3.0 or higher collector ASAP 2.8 records do not include the Page size or Memory size. CONDITIONS: Nodes running a version of ASAP 2.8, and the ASAP database is 3.0 or higher. LIKELIHOOD: Likely (SOLN 10-091230-7246) 52. [H03^AAN] SYMPTOMS: The ASAP Client Graph Object History function sometimes fails when issued against TCP or TELSERV objects or against any other entity where the database is defined as a type relative file, or an ASAP CI command using the TIME option sometimes fails against an entity where the database is defined as a type relative file. CONDITIONS: When a previous Graph Object History command was issued at least one hour prior to the issuance of the new command, or where a previous database command using the TIME option was issued from an ASAP CI session at least one hour prior to the issuance of the new command. LIKELIHOOD: Likely (SOLN 10-090121-8554) 53. [H03^AAN] SYMPTOMS: Comm SGP could create a saveabend file due to an arithmetic overflow. CONDITIONS: Measure counter Read^Busy^Time overflows. LIKELIHOOD: Unlikely (SOLN 10-090116-8474) 54. [H03^AAN] SYMPTOMS: Goal set on TCP UDP BadHdrLen attribute does not work correctly. CONDITIONS: When a goal is set on BadHdrLen. LIKELIHOOD: Likely (SOLN 10-090112-8349) 55. [H03^AAN] SYMPTOMS: ARP abbreviation for TCPARP entity does not work in ASAP CI commands. CONDITIONS: In all cases when trying to abbreviate "TCPARP" with "ARP". LIKELIHOOD: Likely (SOLN 10-081223-8136) 56. [H03^AAN] SYMPTOMS: Errors in the TCP ICMP and ICMP6 entities where XSum and InPackTooBig did not support goals correctly and some ICMP6 data was shown as ICMP data. CONDITIONS: When setting goals on the ICMP XSum attribute or when using TCP/IP v6 and viewing the ICMP6 entity. LIKELIHOOD: Likely (SOLN 10-081223-8131) 57. [H03^AAN] SYMPTOMS: Cannot display specific APP domains. CONDITIONS: When the APP database is defined as a TYPE RELATIVE file. LIKELIHOOD: Likely (SOLN 10-081206-7785) 58. [H03^AAN] SYMPTOMS: Intermittent save abend files created for the ASAP process $ZOOK. CONDITIONS: Can occur when $ZOOK looses communication with the Expand manager process $ZEXP. LIKELIHOOD: Likely (SOLN 10-090113-8370) 59. [H03^AAN] SYMPTOMS: ASAP monitor generating false 1031 messages intermittently. CONDITIONS: When the Action server $ZOOX is busy. LIKELIHOOD: Likely (SOLN 10-090113-5045) 60. [H03^AAN] SYMPTOMS: CPU statistics Pgs%, Pcb%, Pcbx%, TLE%, Seg% and Map values were not displayed correctly. CONDITIONS: When using the ASAP CI commands: CPU, DETAIL CPU, RAW CPU, RAW, TAB, STATE, MB LIKELIHOOD: Likely (SOLN 10-090113-5013) 61. [H03^AAN] SYMPTOMS: Error 1028 Invalid Sys.Sysname received. When a Monitor System \, ADD is performed from the ASAP CI. CONDITIONS: Monitor System entity from the ASAP CI. LIKELIHOOD: Unlikely (SOLN 10-0901058189) 62. [H03^AAN] SYMPTOMS: SET PARTITION TYPE or SET PARTITION REFRESH are applied to the DEFAULT (all entities) instead of the entity specified. CONDITIONS: When attempting to create specific type RELATIVE files for an entity. LIKELIHOOD: Likely (SOLN 10-081125-7540) 63. [H03^AAN] SYMPTOMS: The Process entity did not round to the closest decimal point for several attributes in all prior versions of ASAP, resulting in values that weren't as accurate as they could be when very small values were produced. CONDITIONS: When utilization values were less than 1%. LIKELIHOOD: Likely (SOLN 10-081010-6478) 64. [H03^AAN] SYMPTOMS: Could not use the MONITOR command to monitor specific TELSERV processes, services or windows. CONDITIONS: When attempting to monitor specific TELSERV objects. LIKELIHOOD: Likely (SOLN 10-081117-7323) 65. [H03^AAN] SYMPTOMS: The Comm SGP could report error 4744 device inaccessible messages when there are a large number of monitored communication objects. CONDITIONS: When there are a large number of X25 objects being monitored. LIKELIHOOD: Likely (SOLN 10-081125-7545) 66. [H03^AAN] SYMPTOMS: False EMS alerts "CPU Switch" or "Path switch" against DISK objects could occur under high system load. CONDITIONS: When the DP2 disk process is busy. LIKELIHOOD: Likely (SOLN 10-081030-6942) 67. [H03^AAN] SYMPTOMS: Disk volume names are truncated for Disk < disk>, Samples command. CONDITIONS: When volumes named have similar names prefixes: $Data1, $Data11, $Data15. LIKELIHOOD: Likely (SOLN 10-080814-5200) 68. [H03^AAN] SYMPTOMS: The Disk SGP could report error 1744 Disk device inaccessible errors. CONDITIONS: When a disk device is primaried to the -B and -MB paths. LIKELIHOOD: Likely (SOLN 10-080723-4728) 69. [H03^AAN] SYMPTOMS: The Disk SGP could abend on J06.02. CONDITIONS: When disk devices on storage CLIM are being monitored by the Disk SGP. LIKELIHOOD: Certain (SOLN 10-080709-4398) 70. [H03^AAN] SYMPTOMS: Swap SGP is not reporting on stopped swap files or when a CPU is down. CONDITIONS: When a monitored CPU is down on the node. LIKELIHOOD: Certain (SOLN 10-080708-4391) 71. [H03^AAN] SYMPTOMS: ASAP Swap SGP may generate "unknown stat^sum^requests" in the ASAPLOG file when more than 5 CPU's are configured on the node. CONDITIONS: When 5 or more processors exist on the node. (SOLN 10-080708-4390) 72. [H03] SYMPTOMS: Comm SGP not always setting correct state for the attributes that the user had set goals against. CONDITIONS: Goal comm, requests > 0 commit LIKELIHOOD: Likely. (SOLN 10-080410-2289) 73. [H03] SYMPTOMS: Expand SGP abends when the MONITOR EXPAND, LIST command is entered from the ASAP CI. CONDITIONS: The ASAP command Monitor Expand, list is entered. LIKELIHOOD: Likely. (SOLN 10-080405-2151) 74. [H03] SYMPTOMS: Disk SGP could abend when volumes are deleted from the configuration. CONDITIONS: When a large number of disk volumes are deleted from the nodes configuration. LIKELIHOOD: Unlikely. (SOLN 10-071211-9389) 75. [H03] SYMPTOMS: Cannot start ASAP collector if the system is a different node than the system where ASAP collector is to be started. CONDITIONS: ASAP database name is not resolved correctly when defaults are fully qualified and the node number is greater than 96. LIKELIHOOD: Likely. (SOLN 10-070122-4463) 76. [H03] SYMPTOMS: False CPU alert notifications being sent and displayed by the ASAP Client. CONDITIONS: When the monitor sends a request to an SGP and the request times out. The timeout occurs because a CPU SGP is busy. 15:51 \FIELD ASAP ERR Send to SGP $AAA error: 40 LIKELIHOOD: Unlikely. (SOLN 10-070927-7807) 77. [H03] SYMPTOMS: ASAP monitor not allowing sufficient time for SGP's to shutdown. SGP processes may be running after the monitor shuts down. CONDITIONS: When an SGP is busy the ASAP monitor does not allow sufficient time for the SGP to shutdown. LIKELIHOOD: Unlikely. (SOLN 10-080405-2152) 78. [H03] SYMPTOMS: Disk Error 3402 generated when volume is configured for different groups. CONDITIONS: $VOL-P configured group 1 $VOL-M configured group 2. LIKELIHOOD: Likely. (SOLN 10-070626-5827) 79. [H03] SYMPTOMS: Running in a mixed ASAP version down rev CPU records could have incorrect values for Chits and discs. CONDITIONS: ASAP 2.7 CPU SGP sending records to an ASAP 2.8 collector or later collector. LIKELIHOOD: Likely. (SOLN 10-070927-7807) 80. [H03] SYMPTOMS: ASAP could stop a process not started by ASAP after issuing the shutdown command. CONDITIONS: When the ASAP ID is $ZOO and there is a process by the name of $ZOO8 the CPU SGP $ZOO8 fails to start in CPU 8. During shutdown ASAP could stop the process $zoo8 if the permissions were correct. LIKELIHOOD: Unlikely. (SOLN 10-080405-2153) 81. [H03] SYMPTOMS: Disk SGP reporting error 3402 when using -B path. CONDITIONS: Disk drive is using the -B path and using the Y Fabric. LIKELIHOOD: Likely. (SOLN 10-070626-5827) 82. [H03] SYMPTOMS: Multiple records could be displayed for the same disk volume when an object was running and then deleted. CONDITIONS: Disk objects auto-discovered are deleted from the nodes configuration. LIKELIHOOD: Unlikely. (SOLN 10-071211-9389) 83. [H03] SYMPTOMS: TMF mounts show as a warning in ASAP Client after they have been removed. CONDITIONS: When SHOW REMOVED OBJECTS is set on in ASAP Client. LIKELIHOOD: Unlikely. (SOLN 10-080226-0821) 84. [H03] SYMPTOMS: TMF Mounttime UP events are not generated when a mount is rejected. CONDITIONS: When a tape mount is rejected. LIKELIHOOD: Unlikely. (SOLN 10-071218-9539) 85. [H03] SYMPTOMS: Monitoring processes by their object filename is too resource consumptive. CONDITIONS: When monitoring many processes using their object filename. LIKELIHOOD: Likely. (SOLN 10-070717-6304) 86. [H03] SYMPTOMS: TCP SGP consumes too much virtual memory. CONDITIONS: When TCP max domains settings are too high. LIKELIHOOD: Unlikely. (SOLN 10-070703-5998) 87. [H03] SYMPTOMS: Some forms of TCP sub-entity names and/or abbreviations cause ASAP CI to abend. CONDITIONS: When exotic TCP commands are entered. LIKELIHOOD: Unlikely. (SOLN 10-070624-5781) 88. [H03] SYMPTOMS: Goals could be applied incorrectly to TCP ICMP, IP, QIO, RTE and UDP entity domains. CONDITIONS: When goals are defined against TCP stack sub-entities. LIKELIHOOD: Likely. (SOLN 10-070619-5686) 89. [H03] SYMPTOMS: GOAL/RANK SERVICE , LIST commands could fail when issued from ASAP Client. CONDITIONS: When Service names were too long. LIKELIHOOD: Unlikely. (SOLN 10-070615-5597) 90. [H03] SYMPTOMS: Updater UP events are not always generated for the RDF entity. CONDITIONS: When RDF uses an old version of the ASAP infrastructure SGP_RANKVALUE_ procedure. LIKELIHOOD: Unlikely. (SOLN 10-070605-5272) 91. [H03] SYMPTOMS: ASAPFIL, ASAPPRO and ASAPTCP SGPs can abend if MaxDomains is exceeded. CONDITIONS: When more than the maximum number of domains are found. LIKELIHOOD: Unlikely. (SOLN 10-070507-4628) 92. [H03] SYMPTOMS: Custom event numbers are not generated when used with CPU entity domains. CONDITIONS: When custom event numbers are defined for CPU objectives on subdomains. LIKELIHOOD: Likely. (SOLN 10-070420-4291) 93. [H03] SYMPTOMS: Custom event numbers are not generated when used with TMF entity domains. CONDITIONS: When custom event numbers are defined for TMF objectives on subdomains. LIKELIHOOD: Likely. (SOLN 10-070420-4290) 94. [H03] SYMPTOMS: Objectives (goals) could mistakenly be applied to the wrong domain. CONDITIONS: When a domain matched the objective domain name for the length of the objective domain name. LIKELIHOOD: Unlikely. (SOLN 10-070323-3526) 95. [H03] SYMPTOMS: File SGP gives error message 'NoFile' when a large fileset is added to ASAP and when files are continuously deleted from the fileset. CONDITIONS: When files are deleted after the name is resolved by ASAP but before ASAP has gathered stats on the file. LIKELIHOOD: Unlikely. (SOLN 10-070319-3363) Known Problems Remaining: 1. SYMPTOMS: ASAP CI PROCESS, MEM option may redisplay domain stats from beginning if there are tens of thousands of domains and prompt occurs. CONDITIONS: When there are tens of thousands process domains and there's a prompt. LIKELIHOOD: Likely WORKAROUNDS: For Process configurations with tens of thousands of discrete processes do not use the MEM option. The results are correct without the MEM option. SIDE-EFFECTS: Repeated Display (SOLN 10-130530-7566) 2. SYMPTOMS: When performing a DDL compile for creating a dictionary for running Enform reports, the DDL compile may fail CONDITIONS: DDL/IN ASPDDLDB, OUT $S>#LOC/DICT!, NOLIST LIKELIHOOD: Possible WORKAROUNDS: Do not use DDL Versions T9100^ABX (recalled)or T9100^ABU. SIDE-EFFECTS: If using T9100^ABU or T9100^ABX no record will be created for the TCPIP records. (No SOLN)