READ THIS FILE COMPLETELY BEFORE BEGINNING PRODUCT INSTALLATION Copyright 2006 HP Product Name: ASAP Server Product ID: SE30V2 G-series HSE30V2 H-series Component Products: T0402V02^AAG G-series T0402H01^AAH H-series 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. 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. If you are using the ASAP Extension make a copy of the file $SYSTEM.SYSTEM.ASAPUSER. FUP - VOLUME $SYSTEM.SYSTEM - DUP ASAPUSER, ASAPSAVE.*, SAVEALL 2. If you are upgrading from ASAP 2.4 or an earlier release to ASAP 2.7 then do the following thenthis SPR includes a change to the Objectives database file and also includes EDL changes for several entities. 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 on each node. The objectives database file location is set with the SET OBJECTIVESDB command, or it defaults to $SYSTEM.ZASAP.DBOBJ. 3. Save ASAP CI and all EDL files if you have archived data with the old version of ASAP that you might want to view later. FUP - VOLUME $SYSTEM.SYSTEM - DUP ASAP, ASAPSAVE.*, SAVEALL - DUP ASAP2EDL, ASAPSAVE.*, SAVEALL - DUP ASAP2SYS, ASAPSAVE.*, SAVEALL - DUP ASAP2APP, ASAPSAVE.*, SAVEALL 4. 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. 5. Follow the post-installation instructions in Section B below, if any, after using IPSetup to place and install this product. III. Post-Installation Instructions 1) Invoke the INSTALL^TEMPLATES TACL macro to install this NPV's EMS template file(s) in the running system. This TACL macro and instructions for its use are given in Support Note S92067B. The INSTALL^TEMPLATES TACL macro is distributed on the SUT and can be located in the ISV volume: $.ZINSAIDS.TACLMACS. To print the usage notes, LOAD the file containing the macro and, at the TACL prompt, enter: INSTALL^TEMPLATES /OUT /HELP 2) Run ASAP setup to update the ASAP subsystem with the following commands: a) TACL 1 > VOLUME $.ZASAP b) TACL 2 > 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 saved ASAP database records prior to the install then reload them now. 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. IV. Product Requirements Required Hardware: HP "NonStop" RISC-based servers Minimum OS Release: NonStop Kernel release D42.00 or higher NonStop Kernel release G06.00 or higher Required Software: T0346AAE If using D42-D45.01 T0346AAU If using D46.00-G06.03-G06.22 T6028AAT If using D42.00-D48.01 T6028ABD If using G06.11-G06.26 T6965AAI (see note) T9053AOD If using G06.11-G06.12 T9057AET If using D42.00-D48.02 T9086ACE If using D42.00-D43.01 T9117ABB If using D42.00-D48.02 T9117G06^ABK If using G06.00-G06.26 Note: T6965: The function needed in T6965 is required only if you SET ACTION ON. Disk Space Requirement: ZASAP subvol 9.0MB $System.system run time files 7.0MB ASAP Dictionary files 1.1MB Refer to the section 2 of the ASAP manual for ASAP database file sizes. Memory Requirement: 16MB per cpu minimum. 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 for this CD: To access the documentation for this product, please see the HP NonStop Technical Library at www.hp.com/go/ntl or your NonStop Technical Library CD/DVD disc 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. ADDENDUM Overview: The Availability Stats And Performance (ASAP) provides an availability monitoring infrastructure for an entire network of NonStop servers. ASAP monitors the availability and performance of both system and application objects. System information includes the operational status and performance of NonStop Kernel subsystems. Subsystems monitored include Comm, Cpu, Disk, Expand, File, Process, ProcessBusy, RDF, Spooler, System, Tape, and TMF. Application information can include virtually any user-defined availability statistics. Applications participate in the ASAP environment by using the ASAPX API. New Feature History: ==================== 2.6 No New Features 2.5 [AAE]ASAP now provides support for user defined goals and actions. ASAP can now take corrective actions based on user defined rules associated with RANK/GOAL commands. A new GOAL command is an alias for the RANK command. Thus the commands GOAL and RANK both have the same meaning and can be used interchangably. A new ACTION option on the GOAL/RANK command provides the ability to associate command interpreter commands with actionable goals. For example, the following configures ASAP to automatically run FUP to SECURE the $SYSTEM.SYSTEM.USERID file if its RWEP security vector does not match the security objective for that file. GOAL FILE $SYSTEM.SYSTEM.USERID, RWEP=OOOO ACTION "FUP SECURE <#object>,'<#goal>'" Thus if the RWEP is not OOOO, the following occurs: FUP SECURE $SYSTEM.SYSTEM.USERID,"OOOO" 2.5 [AAE] A new ACTION RULE command allows a user rule library. For example the following creates an action rule named SECURE: ACTION RULE SECURE = FUP SECURE <#object>,"<#goal>" This rule can be used with the goal command above as follows: GOAL FILE $SYSTEM.SYSTEM.USERID, RWEP=OOOO ACTION SECURE More complex recovery actions are also possible using TACL macros and routines. For example: GOAL FILE $SYSTEM.SYSTEM.USERID, RWEP=OOOO ACTION TaclMacro Where TaclMacro is a rule such as: ACTION RULE TaclMacro = TACL MyMacro <#object> <#goal> See HELP RANK and HELP ACTION for more info. 2.5 [AAE] ASAP now supports Communication line monitoring. ASAP now collects both state and performance information for AM3270, ATP6100, CP6100, Envoy, EnvoyACP, Snax, and X.25 lines. The Comm SGP also supports goals and actions. 2.5 [AAE] The ASAP DISK SGP now reports the largest disk space fragment size available on a volume when using the raw command. User goals can be set on the FRAGMENT attribute and actions can be taken. For example the following statement indicates that the largest disk fragment should be at least 10mb in size, if not take corrective ACTION to run DCOM to defragment the volume. GOAL DISK, FRAGMENT > 10 ACTION DCOM <#OBJECT> 2.5 [AAE] The ASAP CPU SGP now reports the number of break points in use when using the raw command. User defined goals can be set on the number of break points. For example the following statement repeatedly generates a critical EMS event if the number of break points set in any CPU exceeds 20. GOAL CPU, BrkPnt <= 20 CRITICAL REPEAT 2.5 [AAE] SGP CPU placement. The ASAP ci SET command now allows you to specify the preferred CPU number where an SGP entity process should execute. Enter HELP SET for more info. Examples: SET DISK, CPU 1 SET EXPAND, CPU 2 SET FILE, CPU 3 2.5 [AAE] Automatic Database Maintenance. A new SET DBMaxDays option allows ASAP to automatically maintain long term database history. Once set long term history is automatically maintained on a per entity basis. The SET DBMaxDays option controls days of history/entity. This option allows days, weeks, months, and even years of ASAP history to be automatically kept. See HELP SET DBMaxDays for more info. Examples: SET DBMaxDays 1 ! default max days SET DBMaxDays APP 14 ! 2 weeks SET DBMaxDays COM 30 ! 1 month SET DBMaxDays CPU 365 ! 1 year SET DBMaxDays DISK 7 ! 1 week SET DBMaxDays EXPAND 7 ! 1 week SET DBMaxDays FILE 7 ! 1 week SET DBMaxDays NODE 7 ! 1 week SET DBMaxDays PROCESS 7 ! 1 week SET DBMaxDays PROCESSBUSY 30 ! 1 month SET DBMaxDays RDF 0 ! 0 none SET DBMaxDays SPOOLER 30 ! 1 month SET DBMaxDays SYSTEM 365 ! 1 year SET DBMaxDays TAPE 7 ! 1 week SET DBMaxDays TMF 7 ! 1 week 2.5 [AAE] Database space analysis. A new DB command provides detailed disk usage analysis of the ASAP database. Per day usage, as well as total usage by entity are provided. The DETAIL option provides detailed info on the Begin and End time for statistics in a given DB file. See HELP DB for more info. Example: +DB 2004 CPU DETAIL $ASAP.ASAP2004.Z* FILENAME Y/M/D LAST-MOD RWEP Begin-Date-Time End-Time -------- -------------- ---- ---------------- ---------------- Z0115CPU 04/01/16 00:00 NUNU 2004/01/15 17:28 2004/01/16 00:00 Z0116CPU 04/01/17 00:00 NUNU 2004/01/16 00:01 2004/01/17 00:00 Z0117CPU 04/01/18 00:00 NNNN 2004/01/17 00:01 2004/01/18 00:00 Z0118CPU 04/01/19 00:00 NNNN 2004/01/18 00:01 2004/01/19 00:00 Z0119CPU 04/01/20 00:00 NNNN 2004/01/19 00:01 2004/01/20 00:00 Z0120CPU 04/01/21 00:00 NNNN 2004/01/20 00:01 2004/01/21 00:00 Z0121CPU 04/01/22 00:00 NNNN 2004/01/21 00:01 2004/01/22 00:00 2.5 [AAE] ASAP node up/down EMS event. A new SET NodeDownAlert ON causes ASAP to generate node up/down EMS alerts. See HELP SET NodeDownAlert for details. Example: 12:03:41 \CENTDIV.$ZOOS *TANDEM.ASAP.V02 004000 ASAP ALERT ZOOS Node \ZERO Status Down 2.5 [AAE] Process entity now allows processes to be monitored by Guardian object filename or by the OSS pathname for OSS processes. You can also use wildcard process names to specify the processes to monitor. MONITOR PROCESS SALES\SERVER\$S* MONITOR PROCESS $SYSTEM.SYS00.TACL MONITOR PROCESS $SYSTEM.SYS00.TACL\## MONITOR PROCESS /home/servers/sales.exe This release also adds two new attributes to Process records: Count is the number of domains; and ACount is the number of attributes that are alerting when viewed at the detail level, or when viewed at the aggregate level is the number of domains that are alerting. 2.5 [AAE] Users can now specify custom event numbers for specific objectives using the RANK command. Custom event numbers in the range 6000-9999 are available for this purpose. For example in the following if the goal for Cpu 0, 1, 2, 3 fails, then the EMS event number for the failed goal would be 9000, 9001, 9002, 9003 respectively. GOAL CPU 0, BUSY < 90 CRITICAL 9000-9100 GOAL CPU 1, BUSY < 80 CRITICAL 9001-9101 GOAL CPU 2, BUSY < 70 CRITICAL 9002-9102 GOAL CPU 3, BUSY < 60 CRITICAL 9003-9103 Likewise if SET OBJECTIVESEVENTUP is ON, then event numbers 9100, 9101, 9102, 9103 would be generated when the goal is met. Enter HELP RANK for more information. 2.5 [AAE] ASAP EMS events that are created when objectives are not met now contain three additional tokens in the event buffer: ZASP-TKN-ASAP-STATE - the current state of the domain ZASP-TKN-ASAP-LASTSTATE - the previous state of the domain ZASP-TKN-ASAP-OBJECTNAME - the physical object name (if any) 2.5 [AAE] ASAP now records and displays the date, time and userid of the last person to modify an objectives record. This information is displayed in all RANK/GOAL statement output. Example: Cpu \ZERO Modified: 2004/06/20 16:43 by user 255,255 Status Critical Repeat Action: TACL Reload <#domain>,Prime Wait: 10 Repeat 2.5 [AAE] The STATUS command in the ASAP command interpreter now provides a timeout option for specifying how long and SGP has to respond to the status request. Enter HELP STATUS for more info. The default timeout has been reduced to 15 seconds. You can select another value, example: STATUS \Sierra TIMEOUT 5 2.5 [AAE] A new SET REMOTESECURITY option has been added to the ASAP command interpreter indicating whether RemotePasswords are checked when shutting down or obtaining status information about remote ASAP monitors. REMOTESECURITY is ON by default, but can be turned off if desired. SET REMOTESECURITY OFF 2.5 [AAE] The AGGREGATE option is now the default when using the APP, FILE and PROCESS commands, so aggregate domains are now automatically displayed. A new NOAGG option has been added to uppress display of aggregate domains when necessary. 2.5 [AAE] The FILE entity now supports the ZLE concepts of logical grouping and aggregation. It also supports wildcard filenames and direct monitoring of OSS files. One to two levels of logical names can preceed a monitored filename to create hierarchical groups of files. Aggregate and aggregate-only domains can then be defined at any level of the grouping. Filenames can now include wildcard characters at the subvolume or filename level, and OSS files can be monitored by specifying the OSS pathname of the file. MONITOR FILE $DATA.SALES*.* MONITOR FILE SALES\DATA\$DATA.SUBV.SALES1 MONITOR FILE SALES\# MONITOR FILE /home/data/salesdata2001.db 2.5 [AAE] New startup parameters, MAXDOMAINS, MAXAGGS and MBYTES, have been added to the FILE and PROCESS SGPs to allow users to monitor many more objects than earlier ASAP versions. MAXDOMAINS controls memory space allocation for the domains read from the objectives database. The default is 999, the maximum is 32766. MAXAGGS controls memory space allocation for aggregate and aggregate-only domains that ASAP creates on your behalf if configured to do so. The default is 199, the maximum is 32766. MBYTES controls the memory space (in megabytes) for the pool used to store domains resolved dynamically at each interval from wildcard specifiers and object filenames. The default is 4, the maximum recommended size is 512. SET FILE PARAM "MAXDOMAINS 10000 MAXAGGS 300 MBYTES 128" SET PROCESS PARAM "MAXDOMAINS 5000 MBYTES 64" An EMS event is generated if space gets depleted from any memory region. 2.5 [AAE] New information is provided about the number of monitored files and processes, and about pool space utilization in the FILE and PROCESS SGPs, in response to the MONITOR , LIST, DETAIL command. +m file,l,d File \Centdiv Num Domains: 41 Max Domains: 20000 Num Files: 17384 Num Aggregates: 12 Pool Entries: 17359 Pool MaxEntries: 111891 Pool High Mark: 28339 RankState: Active Sample Time: 2004/08/04 14:07:00 Last Error: 0 . . . +m process,l,d Process \Centdiv Num Domains: 27 Max Domains: 20000 Num Processes: 839 Num Aggregates: 5 Pool Entries: 834 Pool MaxEntries: 25275 Pool High Mark: 1413 RankState: Active Sample Time: 2004/08/04 14:03:01 Last Error: 0 . . . 2.5 [AAE] When you monitor a FILE or PROCESS domain that contains wildcard names, or a PROCESS domain by referencing the object filename, then ASAP will automatically add an aggregate-only domain. If you do not want aggregate-only to be specified for the wildcard or object filename domain, then you must manually remove the aggregate-only domain after first adding the original domain. Please be sure you understand how many records you will be writing to the historical database before removing the aggregate-only domain, however, to limit the amount of historical data that ASAP saves for each entity. + M FILE + M FILE $DATA.*.* File \Centdiv.$Data.*.*, On + M FILE On - $Data.*.* On - $Data.*.*\## + M FILE $DATA.*.*\##,DEL File $Data.*.*\## deleted. + COMMIT 2.5 [AAE] You can enter two asterisks at the end of a FILE or PROCESS domain name to indicate that the MONITOR or RANK command should be applied to all domains beginning with that name. A single asterisk, which can be used for this purpose when entering commands against other entities, can otherwise be confused with actual wildcard domain name specifiers for the FILE and PROCESS entities. + RANK FILE $DATA** + MONITOR PROCESS $A** 2.4 [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. 2.3 [AAC] No ASAP 2.3 release. 2.2 [AAB] No New Features. 2.1 [AAA] No New Features. 2.0 [V02] ASAP 2.0 includes many new system entities. This includes: Expand, File, Process, ProcessBusy, RDF, Spooler, TMF, and Tape. For complete descriptions, see new LH, File, Process, ProcessBusy, RDF, Spooler, TMF, and Tape commands. 2.0 [V02] ASAP 1.0 System entities such as Cpu, Disk, Expand, ProcessBusy, and System have been enhanced to provide new availability vector information. 2.0 [V02] ASAP 2.0 includes a new Entity Definition Language (EDL). EDL provides a mechanism to define abstract application entities and associated property attributes. Note that EDL is used to define both application and system entities. For example all of the system entities are also defined using the new EDL. For more information, see ASAP Client EDL - Interactive Development Environment, and ASAP Client TIM manual. 2.0 [V02] ASAP 2.0 EDL allows multiple application entity definitions. This allows multiple applications to have totally different entity schemas, property names, and thresholds. 2.0 [V02] Unlike release 1.0, ASAP 2.0 allows you to selectively control which objects or sets of objects are monitored. For Example: MONITOR CPU 0 MONITOR CPU 1 MONITOR DISK $DATA1 MONITOR DISK $DATA2 MONITOR EXPAND $LHCHI MONITOR FILE $SYSTEM.SYSTEM.USERID MONITOR FILE $DATA.SUBVOL MONITOR PROCESS $XYZ MONITOR RDF \CHI->\NYC For more information, see the ASAP command interpreter HELP MONITOR command. 2.0 [V02] ASAP 2.0 includes the ability to set complex Discrete Object Thresholds (DOTs) on individual objects, or on subsets of objects. This capability applies to all ASAP entities, and unlike release 1.0 includes both system and application objects. For more information, see ASAP command interpreter HELP MONITOR and HELP RANK commands. 2.0 [V02] ASAP 2.0 provides new user controlled "Availability" events on all Discrete Object Thresholds (DOTs). For more information, see HELP RANK command. 2.0 [V02] The ASAP database can now be partitioned across multiple volumes on the collection node. New options have also been added to allow user specified primary/secondary extent sizes, and to control the maximum number of extents. For more information, see HELP SET PARTITION. 2.0 [V02] Many ASAP 1.0 features that were only available to the APP entity, now also apply to all system entities. As a result, many ASAP 1.0 ASAPX commands have been moved to the ASAP 2.0 command interpreter. 2.0 [V02] New Burst suppression features have been added to suppress duplicate ASAPLOG and EMS events. 2.0 [V02] Expand now supports the following new Expand transports: ATM, Servernet, and SNA. A new Expand option "IP" was added to display new counters for Expand lines using ATM or TCP/IP as the transport. 2.0 ASAP 1.0 SGP (Stats Gathering Process) data is now supported and automatically remapped into the ASAP 2.0 Database. The Asap 2.0 server can now run in mixed environments with ASAP version 1 and version 2 SGP servers. Note that the ASAP Collector must be version 2.0 in order to run in a mixed environment. 2.0 The ASAP 2.0 CPU SGP now supports 4GB memory modules. Problems Corrected History: =========================== 2.7 [AAG] The canned ASAP rule named SECURE failed to properly re-secure disk files. 2.7 [AAG] The canned ASAP rule named PRIMARY did not work to primary disk paths. 2.7 [AAG] The Process SGP could generate excess activity against the disk process by requesting the program filename at each interval using Process_GetInfoList_ even though it already knew the program filename from a previous request. 2.7 [AAG] The Process SGP would sometimes report incorrect MSent, MRecv and PFaults values for the first interval after a monitored process failed. 2.7 [AAG] The percentage ranking scheme did not work correctly for all ASAP entities when Historical ranking was used. 2.7 [AAG] The MONITOR FILE, LIST, DETAIL and MONITOR PROCESS, LIST, DETAIL commands did not provide useful information about the dynamic object pool size and utilization, and an incorrect default pool size was shown in the help text for HELP SET FILE and HELP SET PROCESS. 2.7 [AAG] The COMM SGP did not report the link level status for X25 lines. The status of the line would be displayed as up when the link status was down or connecting. 2.7 [AAG] The ASAP CI would report an additional comm line from a previous sample whenever a line was no longer being monitored. 2.7 [AAG] The COMM SGP would report Comm lines that were added via SCF when auto-discovery was off. 2.7 [AAG] COMM SGP would not report Comm lines when the IOP was not started. 2.7 [AAG] The DISK SGP would not report the backup path as down for an unmirrored volume when the backup path was downed by the operator or due to a hardware failure. 2.7 [AAG] The EXPAND SGP could report SPI -8 errors when an Expand line is aborted for a long period of time, or could occur if the $zexp is stopped and restarted during an ASAP sample interval. 2.7 [AAG] The ASAP CI could abend after issuing a startup Monitor command. 2.7 [AAG] The DISK SGP reported lines inaccessible on a device subtype 53 when the backup path was being used. 2.7 [AAG] The BUSIEST PROCESS SGP did not display the current priority, but was displaying the intial priority when the process was first started. 2.7 [AAG] The COMM SGP did not display correct rate value, or input/output byte values or input/output data values. Also did not display the correct program object file name for the communication line. Did not always display the correct pin. 2.7 [AAG] The COMM SGP did not always collect line stats when the line was up. 2.6 [AAF] The ASAP Disk SGP was showing invalid flag set for volumes in the up state. 2.6 [AAF] ASAP reported last state plus one for an historically ranked domain when an alert continued into the second interval even if the percentage comparison would have produced a higher state. 2.6 [AAF] The FILE command would output ordinary filenames with backslash characters instead of period characters and ASAP required the characters to be entered when retrieving information about a specific file. 2.6 [AAF] ASAP would fail to automatically create an aggregate-only domain for processes being monitored by a wildcard specifier or object filename if the domain name contained logical prefixes. 2.6 [AAF] The ASAP MONITOR command could allow a FILE domain name containing more than 5 levels to be accepted under certain conditions. 2.6 [AAF] ASAP did not report that files were SQL/MX tables, views and indexes. 2.6 [AAF] ASAP would fail to create obeyform output when the M,OB command was entered. 2.6 [AAF] The ASAP DISK SGP was not returning correct largest fragment state for a down disk. 2.6 [AAF] The ASAP CPU SGP was not displaying correct state value for Breakpoints when the CPU is down. 2.6 [AAF] The ASAP Client was not displaying the correct value for disk block Splits. 2.6 [AAF] The SPOOLER SGP could improperly format the <#OBJECT> token in action strings. 2.6 [AAF] Actions against FILE objects could fail when the file was monitored using a wildcard name. 2.6 [AAF] ASAP would fail to generate an UP event when a TMF transaction duration alert had returned to normal. 2.6 [AAF] In certain cases an ASAP SGP could abend if MaxObjectives, as defined in the entity EDL, was exceeded. 2.6 [AAF] The ASAP DISK SGP could abend. Occurs when more than 33 volumes are monitored and the collector does not reply within 3 minutes to an update request. 2.6 [AAF] The Discrete Objectives Threshold Engine would abend. Would occur when an a disk volume was renamed. 2.6 [AAF] The ASAP DISK SGP did not display the correct disk path to the lient when the -M path is down. Reports that the -MB path is down on the client. Occurs when the Mirror path is down. 2.6 [AAF] The ASAP DISK SGP did not display the correct Operational state for a volume that has a configured backup path, and the mirrored disk did not exist. Would occur when the backup controller is configured and the mirrored disk is not configured. 2.6 [AAF] EXPAND SGP would report down EMS events in a multiline environment when the Path for the multilines was not configured on the node. 2.5 [AAE] The status command can time out. The default for the status reply for each ASAP SGP has been changed from 2 minutes to 15 seconds. 2.5 [AAE] The ASAP EXPAND SGP does not display the correct PIN for any Expand line handler executing with a PIN greater than 255. 2.5 [AAE] The ASAP DISK SGP did not allow decimal values for setting disk queue length objectives. 2.5 [AAE] The ASAP CI Command status does not display SGP's that did not start, due to setting an incorrect object file name or in the unlikely event if an SGP could not start up. 2.5 [AAE] The ASAP monitor process now starts SGP's only during the 15 minute audit interval when an SGP process is stopped or in the unlikely event and SGP abends. 2.5 [AAE] The CPU attributes chit, and disp did not display the correct EMS message when the user specified objective for either attribute was not met. 2.5 [AAE] EDL mistmatch warning when using RANK OBEYFORM. 2.5 [AAE] Aggregate codes AVG and CNT did not compute correctly for the Process Busy, MSent, MRecvd and PFaults attributes. 2.5 [AAE] ASAP CI exhausted available PFS space. 2.5 [AAE] Objective comparisons on the TMF TPS attribute could be incorrect or the TPS value shown in ASAP alert events could be incorrect. 2.5 [AAE] Difficult to know which attributes support objectives. 2.5 [AAE] ASAP Collector process stack overflow abend can occur if the collector is started during cleantime window. 2.5 [AAE] ASAP DISK SGP did not correctly write the correct state when an I/O error occurred on the write to the collector. 2.5 [AAE] The ASAP CPU SGP was not using the percentage of TLE's in use, but was using the actual number of TLE's in use, causing incorrect thresholds to be computed for the TLE attribute. 2.5 [AAE] ASAP and the ASAP modules have not been accelerated. Preventing ASAP and the ASAP modules from executing at the best possible performance levels. 2.5 [AAE] ASAP EXPAND SGP did not report the state correctly for the attribute dframsnt or dframrvd when a configured threshold for either attribute was exceeded. 2.5 [AAE] The ASAP CPU SGP did not report the state correctly for the attribute PCB% or PCBX% when a configured threshold for either attribute was exceeded. 2.5 [AAE] Corrected the DISK SGP not to report path state on non-existent backup controllers. 2.4 [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. 2.4 [AAD] 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. 2.4 [AAD] ASAP CI abended when MONITOR/OUT/ commands were entered. 2.4 [AAD] ASAP did not alert when a TMF auditdump enters the disabled state. 2.4 [AAD] CPU type S7600 or S76000 was not displayed when they were installed. 2.4 [AAD] The DISK SGP could abend when the rate counter overflowed. 2.4 [AAD] Spurious output of the Status attribute name sometimes occurred when using RANK, OBEYFORM option. 2.4 [AAD] MONITOR, RANK, SHOW commands were not always parsed correctly when the domain name contains one or more slash characters. 2.4 [AAD] Break key could cause delays for "MONITOR, LIST" commands. 2.4 [AAD] Unprintable characters sometimes occurred in the MONITOR, LIST, DETAIL. 2.4 [AAD] Corrected spelling of the ASAP information message 1057. The word "suppression" was spelled incorrectly. 2.4 [AAD] The CPU SGP attribute PAGES was not reporting state correctly. 2.4 [AAD] The CPU SGP intermittently did not always report correct process queue length, when the measure subsystem was configured to collect process statistics. 2.4 [AAD] The CPU SGP could abend due to process send or receive counters overflowing. 2.4 [AAD] CPU command did not allow 3 digit queue fields lengths to be displayed on the Asap client, or when using the raw option. 2.4 [AAD] The ASAPLOG file could have a higher than expected I/O rate during each sample interval. 2.4 [AAD] The disk command does not display the previous date when using the sample option. 2.4 [AAD] The disk command could truncate the letter B of the mirror backup (MB) path for disk names containing 7 characters. 2.4 [AAD] 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. 2.4 [AAD] 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. 2.4 [AAD] The ASAP CI would abend when outputting more than 32767 lines. 2.4 [AAD] The ASAP EXPAND SGP did not report the level 4 and level 3 stats: Connect, Ack, Nak, Cancel correctly on a multiline configuration. 2.4 [AAD] The File entity was missing the userid, Security string, Partitions and Last Open time for SQL shorthand view files. 2.4 [AAD] The domain name token is not the event subject token in ASAP alert events. 2.4 [AAD] Difficulties extracting historical ASAP data into CSV files or files intended for input to SQL. 2.4 [AAD] The DISK SGP did not always report the EMS Down volume event when other disk attributes had thresholds set. 2.4 [AAD] The CPU SGP did not display CHIT values greater than 999. 2.3 [AAC] No 2.3 release. 2.2 [AAB] The DISK and EXPAND SGP's now sets the opstate value to zero when Disk or Expand objects are deleted from the NSK configuration. When this occurred the ASAP client could not delete the objects from its cache. 2.2 [AAB] The EXPAND SGP would report errors 1232, and errors 1234 on G series operating systems for any Expand object that was not started. 2.2 [AAB] The EXPAND SGP would report errors 1233,1234,1244,1245 and SPI error -8 when Expand objects were deleted and re-added during the same sample interval. 2.2 [AAB] The DISK SGP does not monitor user added objects when the name is similar to a previously added object. For example the disk SGP would not report on availability information for $DATA1 if $DATA2 was previously defined in the ASAP objectives database. 2.2 [AAB] The DISK SGP was repeating EMS down events against any down volume when the repeat option was not being used. 2.2 [AAB] The ASAP DISK SGP would not monitor disk objects that are 8 characters in length when the node name was also 8 characters in length. 2.2 [AAB] The ASAP command interpreter abended when it was executed on a node numbered zero. 2.2 [AAB] The ASAP PROCESS SGP returned error 13 for all processes being monitored on a D39.02 system. 2.2 [AAB] The ASAP command interpreter failed to load the default EDL file whenever an ASAPCONF configuration file was not found. 2.2 [AAB] The ASAP CPU SGP would not report on the busiest processes after a CPU reload occurred. 2.2 [AAB] The ASAP CPU SGP would not report the correct CPU type for down CPUs. 2.2 [AAB] The TMF SGP failed to properly rank auditdumps, audittrails and transactions when historical ranking was used, and would repeat events for those objects even though repeat was not specified. In addition, the FILE SGP failed to properly rank files when a subvolume was specified for monitoring and historical ranking was used, and would also repeat events even though repeat was not specified. 2.2 [AAB] The ASAP COMMIT command would not work after RANK or MONITOR commands were executed against a node numbered 0. 2.2 [AAB] The SPOOLER SGP would repeat event 4317 at each interval when a Spooler device was configured without a corresponding print process. 2.2 [AAB] RANK and MONITOR commands would output unneeded lines into the output obey file whenever OBEYFORM was specified. 2.2 [AAB] Unexpected OEM states for certain attributes in the FILE and TMF entities when the record represents an empty aggregate set. For example the TMF Transaction record when there are no transactions. 2.2 [AAB] Extraneous spaces in the EMS text token for events 4000, 4001 and 4021 when the domain name exceeds 30-40 characters, depending on the event. 2.2 [AAB] TMF Hung attribute displays Yes/No instead of the actual count of hung transactions when there are hung TMF transactions. 2.2 [AAB] ASAP displays a high value for log messages. 2.1 [AAA] The Monitor writes an information message when log suppress is set OFF. 2.1 [AAA] The EXPAND SGP is not deactivating Phantom lines or ExpandIP entity lines. 2.1 [AAA] The EXPAND SGP would display the operational status text for any Expand line that was deactivated. The status text would display "Exists" on the client, and from the ASAP CI. The proper operational status is now displayed for all deactivated Expand lines. 2.1 [AAA] The EXPANDd SGP does not display the Expand phantom records when the line name is less than 7 characters using the ASAP CI command lh $. 2.1 [AAA] The EXPAND SGP could intermittently write to records to the ASAP database file $dbexp. This would happen during error recovery in the Expand Sgp $ZOOK. 2.1 [AAA] The EXPAND SGP would log error message 1266 after an error 1200 is reported. The Expand line record causing the error 1200 would not be written to the ASAP database file dbexp. 2.1 [AAA] The CPU SGP would not deactivate CPU objects when the Asap CI command rank cpu , deactivate or rank cpu, deactivate was entered. 2.1 [AAA] The DISK SGP would not get the proper state value for the Attributes InKB and OutKB this was due because the ASAP disk SGP was not correctly calculating the actual values of InputKb and OutputKb. 2.1 [AAA] The DISK SGP would display the operational status text for any disk device that was deactivated. The status text would display "Exists" on the client and from the ASAP CI. The proper operational status is now displayed for all deactivated disk devices. 2.1 [AAA] The DISK SGP would fail to get the proper state value for the attribute M. The state value of M was displaying the state value of the P attribute. 2.1 [AAA] When the loginterval value is set to ON the suppressed events summary record would not always be written to the ASAP logfile or generate an EMS event. 2.1 [AAA] Discrete objectives thresholds now generates events for critical or down Statuschanges for all ASAP system entities by default if "Set ObjectivesEvent ON" is set in the ASAPCONF file. One critical EMS event is written per domain. The corresponding "Up" event will be written if "Set ObjectivesEventUp ON" is set in ASAPCONF. To change the event from a critical to an informative event; to repeat it at each interval; or to turn off event generation at the entity or domain level use the RANK command specifying the STATUS attribute. To generate events for warnings or other states use the "Set ObjectivesEventState" option. The ASAP RANK command supports the STATUS attribute to set event Parameters at the entity or domain level for ASAP system and user- defined entities. It also supports a new event parameter, NOEMS, which when specified turns off event generation for Status changes for ASAP system entities. 2.1 [AAA] The RANK command now correctly displays 1-byte character string attribute values without a garbage character on the end. 2.1 [AAA] The PROCESS SGP now reports correct Busy percent for NonStop process pairs that switch or takeover during an interval. It now reports combined values for both processes for Busy, MSent, MRecvd and Pfaults for NonStop process pairs. Other values like Pri and QLen continue to be reported for only the primary process of the pair. The SGP also now reports when NonStop process pairs switch or takeover. 2.1 [AAA] The PROCESS SGP no longer repeats events for failed Pri and BCpu objectives if repeat is not specified. 2.1 [AAA] The CI now properly aligns event keywords in Rank command output for character string attributes. 2.1 [AAA] ASAP now returns accurate alert states for attributes that have alerted then returned to normal with historical ranking mode. 2.1 [AAA] The SPOOLER and TAPE SGP now use the startup RATE parameter correctly. These SGP will now sample at the RATE specified, if specified in the SET SPOOLER PARAMETER or SET TAPE PARAMETER command. 2.1 [AAA] The TAPE SGP now looks explicitly for not found errors and sets the status to NOTFOUND. The corresponding state is DOWN. Similarly, the Spooler SGP now sets the state to DOWN when the status of NOTFOUND is set. 2.1 [AAA] The CPU SGP now monitors non configured Cpu's when they have been added to the objectives database. 2.1 [AAA] The TAPE, TIME