\new;poff 8;text off;join off;justify off;head " ";subhead " "
\sect "ASAP SERVER   T0402V02   01NOV2001   Page   "1;center
SOFTWARE RELEASE DOCUMENT ADDENDUM

Product Name:       ASAP SERVER

Product Number:     T0402V02

Date:               01NOV2001

IPM Number:         T0402AAA

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:

   ASAP now generates EMS events for the operational status of an
   object when the operational state changes. ASAP writes an
   information message to the ASAP logfile when logsuppress is set
   off.  The following objects can now be deactivated CPU, ExpandIP,
   Phantom Expand lines. Disk, and Expand objects now display the
   actual status text of the object when the object has been
   deactivated. The ASAP CI was not displaying Phantom Expand lines
   whose name was less than 7 characters. Corrected duplicate Expand
   records being written to the ASAP database. Corrected Expand
   error message 1266. Corrected the disk attributes "InKB",
   "OutKB", and "M" to set their proper state objectives.
   Suppressed ASAP events did not always write a summary record when
   the loginterval expired. The Process SGP no longer computes an
   invalid Busy percent for failing NonStop process pairs, and no
   longer repeats failed Pri and BCpu events when repeat is not
   specified. The RANK command now displays 1-byte strings correctly
   and properly aligns event keywords for string attributes. DOTs
   now computes accurate alerts states for historical ranking mode
   for objects that fail objective comparison then return to normal.
   The Spooler and Tape SGP now use the RATE startup parameter
   correctly. The command SPOOLER $SPLS/PRINT, STATE, DETAIL will
   now print valid Data. Asap now monitors non configured Cpu's.
   The TAPE, TIME <time> command not works properly. The disk SGP
   attempted to write bad records to the DBSYS and DBCPU files when
   the disk object counts were greater than or equal to 37. The TAPE
   SGP will now process tapemount requests from brand new never used
   tape correctly. The TMF SGP has a new NAK param, and can now
   handle long lasting transactions correctly.

Superseded IPMs:    NONE

Requisite IPMs:     NONE

Required Hardware:  NonStop servers
                    Communications controller allowing file transfer
                    from PC to NonStop server

                    PC with 486 or higher processor and all of the
                    following:
                     CD-ROM drive
                     VGA or higher-resolution video adapter and
                     monitor Microsoft Mouse or similar pointing
                     device

Required Firmware:  NONE

Required Software: T6028D42^AAT
                   T9050D42     (RVU D42.00)
                   T9050G05     (RVU G05.00)
                   T9053G06^AMO (if using G06.11)
                   T9057D40^ADE or
                   T9057G02^ADY
                   T9086D40^ACE or
                   T9086G02^ABS
                   T9117D40^AAW or
                   T9117G02^AAV
                   T9550D40
                   T9552D40

                   Microsoft Windows 95, or Windows NT 4.0 or later
                   Microsoft TCP/IP stack and FTP client

Manuals: 425264 ASAP Server TIM manual

Installation Considerations:

Minimal system impact

I. Pre-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 TCP/IP and FTP are unavailable, or if
      you have problems with automatic file placement, use the
      instructions in the IPSetup User Guide section "Manual
      Software Placement Using the IPSetup TACL Program" to manually
      place NonStop Kernel files.

   7. 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: $<ISVvol>.ZINSAIDS.TACLMACS.  To print the usage
         notes, LOAD the file containing the macro and, at the TACL
         prompt, enter: INSTALL^TEMPLATES /OUT <outdev>/HELP

      2) Run ASAP setup to update the ASAP subsystem with the
         following commands:

         a) TACL 1 > VOLUME $<ISV-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

     4) Due to a minor change in the way EDL is interpreted to store
        objectives in the ASAP objectives database, objectives
        previously defined are no longer valid and must be deleted
        and re-added to the database before they can be used.  To
        delete and re-add objectives enter the following ASAP
        commands:

        RANK/OUT outfile/, OBEYFORM
        RANK <entity>, DELETE   (entered twice for each entity)
        OBEY outfile


IV.   Product Requirements

        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.   Manuals Included On this CD

          422770 ASAP SERVER


VI.  CD-ROM Root Directory Contents

AUTORUN.INF     File containing CD AutoRun commands

AXDIST.EXE      Microsoft redistributable libraries file.

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.


CD_DOCS         Subdirectory containing product documentation.

PDF_DOC         Subdirectory of CD_DOCS containing:
                1. Product manuals in PDF format for viewing with
                   Adobe Acrobat Reader

                2. ACROBAT_VIEWERS subdirectory containing Adobe
                   Acrobat Reader for DOS, OS/2, Windows,
                   Windows NT, MacOS, Sun OS, Solaris, HP-UX,
                   IBM AIX, and SGI IRIX.

New Features:  NONE

Problems Corrected:

 1) [AAA] The Monitor writes an information message when log
    suppress is set OFF.

    (SOLN 10-010817-2272)

 2) [AAA] The Expand SGP is not deactivating Phantom lines or
    ExpandIP entity lines.

    (SOLN 10-010817-9658)

 3) [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.

    (SOLN 10-010821-2379)

 4) [AAA] 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 $<linename>.

    (SOLN 10-010821-2382)

 5) [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.

    (SOLN 10-010821-2384)

 6) [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.

    (SOLN 10-010821-2392)

 7) [AAA] The CPU SGP would not deactivate CPU objects when the Asap
    CI command rank cpu <cpunum>, deactivate or rank cpu, deactivate
    was entered.

    (SOLN 10-010821-2398)

 8) [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.

    (SOLN 10-010823-2478)

 9) [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.

    (SOLN 10-010823-2480)

10) [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.

    (SOLN 10-010828-2653)

11) [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.

    (SOLN 10-010831-2801)

12) [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.

    (SOLN 10-010803-1954)

13) [AAA] The RANK command now correctly displays 1-byte character
    string attribute values without a garbage character on the end.

    (SOLN 10-010803-1957)

14) [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.

    (SOLN 10-010820-2312)


15) [AAA] The Process SGP no longer repeats events for failed Pri
    and BCpu objectives if repeat is not specified.

    (SOLN 10-010822-2419)

16) [AAA] The CI now properly aligns event keywords in Rank command
    output for character string attributes.

    (SOLN 10-010822-2421)

17) [AAA] ASAP now returns accurate alert states for attributes that
    have alerted then returned to normal with historical ranking
    mode.

    (SOLN 10-010828-2660)

18) [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.

    (SOLN 10-010821-2393)

19) [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.

    (SOLN 10-010831-2798)

20) [AAA] The CPU SGP now monitors non configured Cpu's when they
    have been added to the objectives database.

    (SOLN 10-010901-2802)

21) [AAA] The TAPE, TIME <time> command was returning an empty data
    list. This has been fixed.

    (SOLN 10-010919-3194)

22) [AAA] The Disk SGP would attempt to write a bad record to the
    ASAP database files DBSYS and DBCPU when the disk device count
    was >= 37. The collector would detect the bad records and
    generate an ASAP error message 2000.
    2000 ZOOS ERR DB^write DBCPU, fe: 666 1 0  \<node>.$ZOOJ
    2000 ZOOS ERR DB^write DBSYS, fe: 666 1 0  \<node>.$ZOOJ

    (SOLN 10-010921-3279)

23) [AAA] The SPOOLER $SPLS/PRINT, DETAIL, STATE now works properly.

    (SOLN 10-010803-1953)


24) [AAA] The TAPE SGP was creating an invalid node tape domain
    entry when a brand new tape which had never been used before,
    was mounted on a tape drive.  The ASAP collector would produce
    error 666 on behalf of the TAPE SGP.  This has been fixed.

    (SOLN 10-010921-3287)

25) [AAA] The Expand SGP would report error 1235 for muliline Expand
    over IP or ATM lines when the IOP was running as a High pin
    process.

    (SOLN 10-011009-3647)

26) [AAA] The TMF SGP now offers a new startup param: NAK <value>,
    where <value> represents the number of consecutive timeouts that
    can be ignored before the TMF SGP raises an alert.  Use this
    param with caution, as it might keep ASAP from alerting you
    about timeout conditions on your system.

    The default behavior of the TMF SGP remains the same: it reports
    timeout errors as soon as they occur.

    (SOLN 10-011009-3650)

27) [AAA] The TMF SGP no longer abends when sampling very long
    lasting transactions. The translation of the delay into seconds
    for the Duration attribute is now done correctly.

    (SOLN 10-011017-3866)

Known Problems Remaining:  NONE

 1) The Disk SGP when using auto discovery of disk devices does not
    remove the device, Opstate value = 0 when disk devices are
    deleted from the NSK configuration. Workaround is to monitor the
    disks with the monitor command and then setting the deleted disk
    device off i.e. Monitor disk $devname,off. This allows the ASAP
    client to remove the disk device from the Clients display.

    (No SOLN)

 2) The Expand SGP when using auto discovery of Expand lines does
    not remove the line, Opstate value = 0 when Expand lines are
    deleted from the NSK configuration. Workaround is to monitor the
    Expand lines with the monitor command and then setting the
    deleted disk device off i.e. Monitor Expand $Linename,off. This
    allows the ASAP client to remove the Expand line from the
    Clients display.

    (No SOLN)

3) The CI will truncate the last character of the disk path in use
   when the Disk device name is 8 characters. For example
   $Diskdev-MB will only display $Diskdev-M.  The Asap client is not
   affected because it only displays the device name and not the
   path that the disk is primaried to.

   (No SOLN)