\new;poff 8;text off;join off;justify off;head " ";subhead " " \sect "ASAP Server T0402V02 29JUN2001 Page "1;center SOFTWARE RELEASE DOCUMENT Product Name: ASAP SERVER Product Number: T0402V02 Date: 29JUN2001 Copyright Notice: COMPAQ CONFIDENTIAL: NEED TO KNOW ONLY Copyright 2001 Compaq Computer Corporation Protected as an unpublished work. The computer program listings, specifications and documentation herein are the property of Compaq Computer Corporation or a third party supplier and shall not be reproduced, copied, disclosed, or used in whole or in part for any reason without the prior express written permission of Compaq Computer Corporation. Summary: Compaq 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 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.0 provides numerous additional features. For details, see below. Required Hardware: NonStop RISC-based servers Required Firmware: NONE Required Software: D42.00 onward G05.00 onward T6028D42^AAT (see note) T9053G06^AMO (G06.11 onward, see note) Note: These IPMs, or superseding IPMs, must be installed on the RVUs with which they are usable and in which they are not already included Manuals: 425264 ASAP Server TIM manual Migration Considerations: NONE Installation Considerations: NONE New Features: 1) Use of D-Series Enhancements: Can be created by a high PIN process Y D42.00 Can communicate with a high PIN requester Y D42.00 Notes: Only applicable to ASAP Can communicate with a high PIN server N Can create a high PIN process N Can run at a high PIN N Defaults to run at a high PIN N (HIGHPIN on) Has a new (since C30 FCS) maximum of OPENS N on a device, process name, or subdevice Issues new (since C30 FCS) operator messages Y D42.00 Issues new (since C30 FCS) tokens Y D42.00 Recognizes high PIN process IDs N Recognizes new (since C30 FCS) tokens N Recognizes remote 8-character N (including $) device/volume/file names Recognizes remote 6-character N (including $) process names Recognizes variable-length-string N file names 2) [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. (No SOLN) 3) [V02] ASAP 1.0 System entities such as Cpu, Disk, Expand, ProcessBusy, and System have been enhanced to provide new availability vector information. (No SOLN) 4) [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. (No SOLN) 5) [V02] ASAP 2.0 EDL allows multiple application entity definitions. This allows multiple applications to have totally different entity schemas, property names, and thresholds. (No SOLN) 6) [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. (No SOLN) 7) [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. (No SOLN) 8) [V02] ASAP 2.0 provides new user controlled "Availability" events on all Discrete Object Thresholds (DOTs). For more information, see HELP RANK command. (No SOLN) 9) [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. (No SOLN) 10) [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. (No SOLN) 11) [V02] New Burst suppression features have been added to suppress duplicate ASAPLOG and EMS events. (No SOLN) 12) [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. (No SOLN) 13) [V02] 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. (No SOLN) 14) [V02] The ASAP 2.0 CPU SGP now supports 4GB memory modules. (No SOLN) Problems Corrected: 1) [V02] ASAP CI corrected a possible formatting problem with data counters rolling over to an adjacent field. (No SOLN) 2) [V02] Corrected Expand multiline IP problems. (No SOLN) 3) [V02] Processbusy corrected to display $disk device name instead of DP2 object "TSYSDP2" (No SOLN) 4) [V02] CPU,RAW,AVG and CPU,AVG,TYPE corrected to display correct cputype and correct CPU state. (No SOLN) Known Problems Remaining: 1) Burst suppression report summary does not always report after the suppression interval (Loginterval) has expired. (No SOLN) 2) The children nodes of a TMF distributed transaction are not displayed. (No SOLN) 3) Status monitor command can time out when SGP's take too long to report status information. (No SOLN) 4) Asap 2.0 does not support multiple collector access to the same database. (No SOLN)