READ THIS FILE COMPLETELY BEFORE BEGINNING PRODUCT INSTALLATION Copyright 2003 HP Product Name: ASAP Server Product ID: SE30V2.4 Component Products: T0402AAD 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 need Adobe Acrobat Reader (available on this CD) to read or print the IPSetup User Guide. 4. Decide whether you will use DSM/SCM to move files to Installation Subvolumes (ISVs) after files are placed on the workstation. Using DSM/SCM is optional, but is recommended when DSM/SCM is available. 5. 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 you have problems with automatic file placement, use the instructions in the IPSetup User Guide section "Manual Software Placement Using FTP & SETUPRUN" 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. IMPORTANT: Always reinstall this product after using the Install product to install a Site Update Tape (SUT). Installing a SUT using the Install product can result in overwriting this Independent Product with older versions of software. This problem does not occur when using DSM/SCM to install SUTs. 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. For example from a Tacl prompt enter the following command: Fup Dup $System.System.Asapuser,$System.Asaptemp.*,saveall,purge 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. 3) If you are using the ASAP Extension copy the duplicated file from the Pre-Installation instructions Step 1 to $System.System.Asapuser. For example from a Tacl prompt enter the following command: Fup dup $System.Asaptemp.Asapuser,$System.Asaptemp.Asapuser,saveall, purge IV. Product Requirements Required Hardware: NonStop System Minimum OS Release: NonStop Kernel release D42.00 or higher NonStop Kernel release G06.00 or higher Required Software: T0346AAE if using D42.00-onward or G06.03-onward or T0346AAU if using D46.00-onward or G06.03-onward T6028AAT if using D42.00-onward or G05.00-onward (see note) T9053ANU if using G06.11-G06.12 (see note) T9057AET if using D42.00-onward or T9057AEH if using G05.00-G05.01 (see note) T9086ACE if using D42.00-D43.01 T9117ABB if using D42.00-D48.02 or T9117ABG if using G06.00-G06.14 (see note) Note: T6028^AAT: The function needed is included in G06.09 and G06.10. T9053^AMO: Fixes a problem introduced in G06.11 with the Dfreq queue counter. T9057^AEH: The function needed in T9057 is included in G06.00-G06.15. T9086^ACE: The function needed in T9086 is included in D43.02-D48.03 and G05.00-G06.15. T9117^ABG: The function in this SPR that depends on T9117ABG is not used on G05.xx. 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 SPR ABG or superseding SPR (for releases D31.00 to D40.00) T9552D40 TCP/IP FTP with SPR ABJ or superseding SPR (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 Included On this CD 422770 ASAP SERVER 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. CD_DOCS Subdirectory containing product documentation in the following two subdirectories: TIM_COLL Subdirectory of CD_DOCS containing product manuals formatted for the Total Information Manager (TIM) viewer. PDF_DOCS Subdirectory of CD_DOCS containing: 1. Product manuals in PDF format for viewing with Adobe Acrobat Reader 2. ACROBAT_VIEWERS subdirectory containing Adobe Acrobat Readers. ADDENDUM Overview: Availability Stats And Performance (ASAP) software 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 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. ASAP 2.4 provides additional features. For details, see below. New Feature History: ==================== 2.4 Process ZLE. ASAP now provides support for super-scalar ZLE systems with tens of thousands of monitored process domains. A) Process ZLE provides the ability to hierarchically group processes. For example, all the Spooler collector processes might be grouped into a group called "Spooler\Collectors". Use the MONITOR command to specify the logical portion of the name preceding the actual process name to monitor a process as part of a hierarchical group. For example: MONITOR PROCESS SPOOLER\COLLECTOR\$S MONITOR PROCESS SPOOLER\COLLECTOR\$S2 MONITOR PROCESS SPOOLER\COLLECTOR\$S3 MONITOR PROCESS SPOOLER\PRINT\$SPLP MONITOR PROCESS SPOOLER\PRINT\$SPLP2 Logical process domain names can be 64 bytes in length and can contain up to 5 levels of hierarchy separated by a backslash. The actual process name must be the last level in the hierarchy. B) Process ZLE provides the capability to create aggregate domains, at any level of the logical hierarchy, that contain summary information for all domains beneath the aggregate domain in the hierarchy. For example the domain "Spooler\Collector\#" would contain aggregate information for all Spooler collector processes, and the domain "Spooler\#" would contain aggregate information about all Spooler processes. To define an aggregate process domain use the MONITOR command and the "#" character to identify the level at which to create the aggregate. For example: MONITOR PROCESS SPOOLER\COLLECTOR\# MONITOR PROCESS SPOOLER\PRINT\# MONITOR PROCESS SPOOLER\# C) Process ZLE allows you to set objectives on aggregate domains and their metric properties. For example to set an objective that the total process busy used by all Spooler Collector processes should be less than 10% and the total Spooler busy for all Spooler processes should be less than 20%, you would enter the following commands: RANK PROCESS SPOOLER\COLLECTOR\#, BUSY < 10 RANK PROCESS SPOOLER\#, BUSY < 20 D) Process ZLE lets a user control the amount of historical data being written to the ASAP database by limiting historical data to only aggregate domains. ASAP still processes each detail domain, computing statistics, and creating alerts when objectives aren't met, but can be setup to only write the aggregate summary records to disk. Use the MONITOR command and the "##" indicator to specify of an aggregate-only domain at a specific level in the hierarchy. For example: MONITOR PROCESS SPOOLER\COLLECTOR\## MONITOR PROCESS SPOOLER\PRINT\## MONITOR PROCESS SPOOLER\## E) Advanced ASAP users are given complete control over the content of aggregate records by externalizing the aggregate or propagate function for each attribute into the MetricRule formula in ASAP's Entity Definition Language (EDL). For example the Process Busy attribute defaults to summarize all the Busy attribute values into the aggregate record, so the aggregate represents the total Process Busy for all processes in the group. This default behavior is defined in the MetricRule for the Busy attribute, and it can be changed to show the average Busy for all processes, or the minimum or maximum Busy values found, or by removing the MetricRule formula ASAP will propagate the Busy value from the domain with the highest alert state for Busy. The Process MetricRule formula is defined as follows: METRICRULE "" is: SUM|AVG|MIN|MAX|CNT The default varies by attribute: Pri - MIN MRecv - SUM Busy - SUM QLen - MAX MPages - SUM MQLen - MAX MSent - SUM PFaults - SUM Attributes not in the list have no default MetricRule defined therefore the aggregate value is determined by propagating the value with the worst ASAP state to the aggregate domain. F) The state at which the Process SGP considers a domain to be alerting has been externalized into a new Process parameter. The MINSTATE parameter is used to set a state other than the default state of low alert (3). In addition, the MINONLY and NORECS parameters are added to provide additional levels of control over records written to the ASAP historical database. G) Process ZLE adds the ability to retrieve detail data for alerting domains directly from ASAP memory. This lets a user configure an aggregate-only domain but still see the alerting domains when errors occur without incurring disk I/O overhead for all the detail records. The Process EDL can now also define a detail command that uses the MEMORY, MINSTATE and COUNT command options to retrieve alerting detail domains whenever a users right-mouse's on an aggregate-only domain and chooses "Show Object Details". H) The PROCESS command now supports the AGGREGATE and AGGREGATEONLY options, in addition to the AGGONLY and AO abbreviations for AGGREGATEONLY. In summary, Process ZLE lets a user monitor tens of thousands of detail domains while reducing disk I/O to the historical database by writing only aggregate records to disk. Please see the new version of the ASAP Server Manual that ships with this release for more information on the Process ZLE enhancement. (SOLN 10-030822-9097) 2.0 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 ASAP 1.0 System entities such as Cpu, Disk, Expand, ProcessBusy, and System have been enhanced to provide new availability vector information. 2.0 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 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 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 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 ASAP 2.0 provides new user controlled "Availability" events on all Discrete Object Thresholds (DOTs). For more information, see HELP RANK command. 2.0 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 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 New Burst suppression features have been added to suppress duplicate ASAPLOG and EMS events. 2.0 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.4 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 The Monitor command defaults to add. Some ASAP users expect the behavior to act as the information function list, info. A new option SET MONITORADD allows you to control the default behavior of the MONITOR command. 2.4 ASAP CI abended when multiple MONITOR/OUT/ commands were entered. 2.4 ASAP did not alert when a TMF auditdump enters the disabled state. 2.4 CPU type S7600 or S76000 was not displayed when they were installed. 2.4 Disk SGP could abend when a rate counter overflowed. 2.4 Spurious output of the Status attribute name somtimes occurred when using the RANK, OBEYFORM option. 2.4 MONITOR, RANK, SHOW commands might not work when the domain name contains one or more slash characters. 2.4 Break key could cause delays for "MONITOR, LIST" commands. 2.4 Unprintable characters sometimes occurred in the MONITOR, LIST, DETAIL. 2.4 Corrected spelling of the ASAP information message 1057 the word suppression was incorrect. 2.4 CPU SGP attribute PAGES was not reporting state correctly. 2.4 CPU SGP intermittently did not always report correct process queue length, when the measure subsystem is configured to collect process statistics. 2.4 CPU SGP could abend due to process send or receive counters overflowing. 2.4 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 The ASAPLOG file could have a higher than expected I/O rate during each sample interval. 2.4 The Disk command does not display the previous date when using the sample option. 2.4 The disk command would truncate the letter B of the mirror backup (MB) path for disk names containing 7 characters. 2.4 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 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 The ASAP CI would abend when outputting more than 32767 lines. 2.4 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 The file entity was missing the userid, security string, partitions and last open time for SQL shorthand view files. 2.4 The domain name token is not the event subject token in ASAP alert events. 2.4 Difficulties extracting historical ASAP data into CSV files or files intended for input to SQL. 2.4 The Disk SGP did not always report the EMS Down volume event when other disk attributes had thresholds set. 2.3 No 2.3 release. 2.2 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 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 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 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 The Disk SGP was repeating EMS down events against any down volume when the repeat option was not being used. 2.2 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 The ASAP command interpreter abended when it was executed on a node numbered zero. 2.2 The ASAP Process SGP returned error 13 for all processes being monitored on a D39.02 system. 2.2 The ASAP command interpreter failed to load the default EDL file whenever an ASAPCONF configuration file was not found. 2.2 The ASAP CPU SGP would not report on the busiest processes after a CPU reload occurred. 2.2 The ASAP CPU SGP would not report the correct CPU type for down CPUs. 2.2 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 The ASAP COMMIT command would not work after RANK or MONITOR commands were executed against a node numbered 0. 2.2 The Spooler SGP would repeat event 4317 at each interval when a Spooler device was configured without a corresponding print process. 2.2 RANK and MONITOR commands would output unneeded lines into the output obey file whenever OBEYFORM was specified. 2.2 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 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 TMF Hung attribute displays Yes/No instead of the actual count of hung transactions when there are hung TMF transactions. 2.2 ASAP displays a high value for log messages. 2.1 The Monitor writes an information message when log suppress is set OFF. 2.1 The Expand SGP is not deactivating Phantom lines or ExpandIP entity lines. 2.1 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 The Expand 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 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 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 The CPU SGP would not deactivate CPU objects when the Asap CI command rank cpu , deactivate or rank cpu, deactivate was entered. 2.1 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 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 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 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 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 The RANK command now correctly displays 1-byte character string attribute values without a garbage character on the end. 2.1 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 The Process SGP no longer repeats events for failed Pri and BCpu objectives if repeat is not specified. 2.1 The CI now properly aligns event keywords in Rank command output for character string attributes. 2.1 ASAP now returns accurate alert states for attributes that have alerted then returned to normal with historical ranking mode. 2.1 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 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 The CPU SGP now monitors non configured Cpu's when they have been added to the objectives database. 2.1 The TAPE, TIME