****************************
       ECO SUMMARY INFORMATION
    ****************************

    Release Date:  1-JUN-2004
    Kit Name: DEC-AXPVMS-VMS731_TDF-V0500--4.PCSI
    Kit Applies To: OpenVMS ALPHA V7.3-1
    Approximate Kit Size: 1184 blocks
    Installation Rating: INSTALL_3
    Superseded Kits: VMS731_TDF-V0400
    Mandatory Kit Dependencies: VMS731_UPDATE-V0200
                                VMS731_PCSI-V0200
    Optional Kit Dependencies: None.
    VMS731_TDF-V0500.PCSI-DCX_AXPEXE Checksum: 1905158661


    
    =======================================================================
     Hewlett-Packard OpenVMS ECO Cover Letter
    =======================================================================

             ECO NUMBER:     VMS731_TDF-V0500
             PRODUCT:        OpenVMS Alpha OPERATING SYSTEM V7.3-1
             UPDATE PRODUCT: OpenVMS Alpha OPERATING SYSTEM V7.3-1



1  KIT NAME:

     VMS731_TDF-V0500


2  KIT DESCRIPTION:

     2.1  Installation Rating:


     INSTALL_3 : To be installed by customers experiencing the
            problems corrected.


     This installation rating, based upon current CLD information, is
     provided to serve as a guide to which customers should apply this
     remedial kit.  (Reference attached Disclaimer of Warranty and
     Limitation of Liability Statement)


     2.2  Reboot Requirement:

     Reboot Required.

     HP strongly recommends that a reboot is performed immediately after
     kit  installation  to  avoid system instability.  If you have other
     nodes in your OpenVMS cluster, they must also be rebooted in  order
     to  make  use  of  the  new  image(s).   If  it  is not possible or
     convenient to reboot the entire cluster at  this  time,  a  rolling
     re-boot may be performed.


     2.3  Version(s) of OpenVMS to which this kit may be applied:

     OpenVMS Alpha V7.3-1


     2.4  New functionality or new hardware support provided:

     No.


3  KITS SUPERSEDED BY THIS KIT:


      -  VMS731_TDF-V0400



4  KIT DEPENDENCIES:


                                                                Page 2


     4.1  The following remedial kit(s), or  later,  must  be  installed
          BEFORE installation of this, or any required kit:


      -  VMS731_PCSI-V0200

      -  VMS731_UPDATE-V0200



     4.2  In order to receive all the corrections listed  in  this  kit,
          the   following  remedial  kits,  or  later,  should  also  be
          installed:


      -  None.



5  FILES PATCHED OR REPLACED:


      o  [SYSEXE]JBC$JOB_CONTROL.EXE (new image)

         Image Identification Information

         image name: "JBC$JOB_CONTROL"
         image file identification:  "X-27"
         image file build identification:  "X9TD-0060030002"
         link date/time: 12-NOV-2003 11:38:00.45
         linker identification:  "A11-50"
         Overall Image Checksum: 2520637614

      o  [SYSEXE]SYS$DAYLIGHT_SAVING.EXE (new image)

         Image Identification Information

         image name: "SYS$DAYLIGHT_SAVING"
         image file identification:  "TDF  V1.0-0"
         image file build identification:  "     0060030007"
         link date/time: 28-JAN-2004 14:33:49.17
         linker identification:  "A11-50"
         Overall Image Checksum: 548824670

      o  [SYSEXE]SYS$READ_TIME_ZONE_RULE.EXE (new image)

         Image Identification Information

         image name: "SYS$READ_TIME_ZONE_RULE"image file identification:  "X-4A1"
         image file build identification:  "     0060030007"
         link date/time: 28-JAN-2004 14:33:49.44
         linker identification:  "A11-50"
         Overall Image Checksum: 550458474

      o  [SYSEXE]TDF$SET_TIMEZONE.EXE (new image)

         Image Identification Information

                                                                Page 3



         image name: "TDF$SET_TIMEZONE"
         image file identification:  "TDF  V1.0-0"
         image file build identification:  "     0060030007"
         link date/time: 28-JAN-2004 14:33:50.17
         linker identification:  "A11-50"
         Overall Image Checksum: 2913751002

      o  [SYSHLP.EXAMPLES]DAYLIGHT_SAVINGS.COM (new file)

      o  [SYSUPD]DTSS$INSTALL_TIMEZONE_RULE.COM (new file)

      o  [SYSMGR]UTC$TIME_SETUP.COM (new file)



6  NEW FUNCTIONALITY AND/OR PROBLEMS ADDRESSED IN THE VMS731_TDF-V0500
   KIT

     6.1  New functionality addressed in this kit

          None.


     6.2  Problems addressed in this kit

          6.2.1  Missing installation requirement message

               6.2.1.1  Problem Description:

               In order to receive the changes contained in the
               VMS731_TDF-V0400 ECO kit, before rebooting the system,
               users needed to run the [SYSMGR]UTC$TIME_SETUP.COM
               procedure to re-create the UTC time startup file.  The
               VMS731_TDF-V0400 ECO kit did not contain instructions or
               installation messages that detailed this requirement.

               Images Affected:

                -  Installation files



               6.2.1.2  CLDs, and QARs reporting this problem:

                    6.2.1.2.1  CLD(s)

                    None.


                    6.2.1.2.2  QAR(s)

                    None.

                                                                Page 4


               6.2.1.3  Problem Analysis:

               See Problem Description


               6.2.1.4  Release Version of OpenVMS that will contain
                        this change:

               Not Applicable


               6.2.1.5  Work-arounds:

               None.


7  PROBLEMS ADDRESSED IN PREVIOUS KITS

     7.1  Problems addressed in the VMS731_TDF-V0400 kit

          7.1.1  Job controller generates a JBC-W-SYSERROR at boot time

               7.1.1.1  Problem Description:

               Under the following conditions, the job controller
               generates a JBC-W-SYSERROR at boot:

                o  DECnet-Plus installed

                o  DECnet-Plus and DTSS startup are disabled during boot

                o  net$ignore_decnet and net$disable_dtss are defined to
                   true

                o  The SYSGEN parameter auto_dlight_sav is set to 1


               Error messages seen are:

               %% OPCOM 9-JAN-2004 17:47:24.47  %%
               Message from user SYSTEM on AMD6XB
               %JBC-W-SYSERROR, SYS$MANAGER:JBC$DST_COMMAND.COM
               daylight savings time process failed system
               service error at PC 00011EA0

               %% OPCOM 9-JAN-2004 17:47:24.47 %%
               Message from user SYSTEM on AMD6XB
               -JBC-W-NOTIMZONRUL, SYS$TIMEZONE_RULE logical
               not defined, Daylight Savings Time clock
               adjustments are not possible


               Images Affected:

                -  [SYSUPD]DTSS$INSTALL_TIMEZONE_RULE.COM


                                                                Page 5


               7.1.1.2  CLDs, and QARs reporting this problem:

                    7.1.1.2.1  CLD(s)

                    70-10-1108,CFS.105101


                    7.1.1.2.2  QAR(s)

                    None.


               7.1.1.3  Problem Analysis:

               During boot, UTC time is defined by the
               DTSS$UTC_STARTUP.COM or TDF$UTC_STARTUP.COM procedures.
               The TDF$UTC_STARTUP.COM procedure terminates when the
               logical NET$DISABLE_DTSS is defined, but this test should
               only be done when executing the DTSS$UTC_STARTUP.COM
               variant of the startup file.


               7.1.1.4  Release Version of OpenVMS that will contain
                        this change:

               Next release of OpenVMS after V7.3-2


               7.1.1.5  Work-arounds:

               None.


          7.1.2  Error when using SYS$EXAMPLES:DAYLIGHT_SAVING.COM

               7.1.2.1  Problem Description:

               When using the SYS$EXAMPLES:DAYLIGHT_SAVING.COM file to
               manually perform daylight saving time adjustments, the
               following error may be seen:

               Is it O.K. to execute the time sysman now? (Yes/No): YES
               %DCL-E-OPENIN, error opening DISK$name:[somedir.
               somesubdir]DST$CHANGE.COM; as input -RMS

               Images Affected:

                -  [SYSHLP.EXAMPLES]DAYLIGHT_SAVINGS.COM


                                                                Page 6


               7.1.2.2  CLDs, and QARs reporting this problem:

                    7.1.2.2.1  CLD(s)

                    CFS.106916,70-3-7930


                    7.1.2.2.2  QAR(s)

                    None.


               7.1.2.3  Problem Analysis:

               See Problem Description


               7.1.2.4  Release Version of OpenVMS that will contain
                        this change:

               Next release of OpenVMS after V7.3-2


               7.1.2.5  Work-arounds:

               None.


8  PROBLEMS ADDRESSED IN PREVIOUS KITS

     8.1  Problems addressed in the VMS731_TDF-V0300 kit

          8.1.1  Stopping and Starting job controller hangs jobs

               8.1.1.1  Problem Description:

               The VMS731_TDF-V0200 Remedial ECO kit stated that after
               installation of the kit, the job controller could be
               stopped and restarted, alleviating the need for a reboot.
               However, if this is done while jobs are executing in a
               batch queue, those jobs will end normally but will remain
               in the queue with a status of "executing".  This is
               unexpected, incorrect behavior.

               OpenVMS engineering is evaluating this problem.  In the
               meantime, the VMS731_TDF-V0200 ECO kit is being re-issued
               as VMS731_TDF-V0300.  This new kit calls for a re-boot
               rather than simply stopping and starting the controller.

               If you have successfully installed the VMS731_TDF-V0200
               ECO kit there is no need to install the VMS731_TDF-V0300
               kit.  There are no new functional changes in this kit.

               Images Affected:

                                                                Page 7


                -  N/A



               8.1.1.2  CLDs, and QARs reporting this problem:

                    8.1.1.2.1  CLD(s)

                    None.


                    8.1.1.2.2  QAR(s)

                    None.


               8.1.1.3  Problem Analysis:

               See Problem Description


               8.1.1.4  Work-arounds:

               None.


     8.2  Problems addressed in the VMS731_TDF-V0200 kit

          8.2.1  Fix %DCL-W-IVOPER error on systems with DECnet DTSS
                 enabled

               8.2.1.1  Problem Description:

               Running the UTC$TIME_SETUP.COM procedure gives a
               %DCL-W-IVOPER error on systems with DECnet DTSS enabled.

               Images Affected:

                -  [SYSMGR]UTC$TIME_SETUP.COM



               8.2.1.2  CLDs, and QARs reporting this problem:

                    8.2.1.2.1  CLD(s)

                    70-3-6980,CFS.99577


                    8.2.1.2.2  QAR(s)

                    None.

                                                                Page 8


               8.2.1.3  Problem Analysis:

               Misplaced "." in the command procedure.


               8.2.1.4  Work-arounds:

               None.


          8.2.2  Fix SYS$EXAMPLES:DAYLIGHT_SAVINGS.COM to work in
                 OpenVMS Clusters

               8.2.2.1  Problem Description:

               Files written in SYS$SYSROOT cannot be found on other
               nodes in cluster.

               Images Affected:

                -  [DTSS]DAYLIGHT_SAVINGS.COM



               8.2.2.2  CLDs, and QARs reporting this problem:

                    8.2.2.2.1  CLD(s)

                    None.


                    8.2.2.2.2  QAR(s)

                    75-13-1046


               8.2.2.3  Problem Analysis:

               The procedure defaults to using the current directory,
               which is SYS$MANAGER by for the SYSTEM account.  The fix
               is to use the translation of
               SYS$SYSDEVICE:[VMS$COMMON.SYSMGR] as the device/directory
               for DST$CHANGE.COM and DST$SYSMAN.COM.


               8.2.2.4  Work-arounds:

               None.


          8.2.3  System TDF could be set to an incorrect value


                                                                Page 9


               8.2.3.1  Problem Description:

               On systems running DECnet-Plus with DTSS disabled, the
               system TDF could be set to an incorrect value if DECnet
               timezone files exist on the system.

               Images Affected:

                -  [SYSUPD]DTSS$INSTALL_TIMEZONE_RULE.COM



               8.2.3.2  CLDs, and QARs reporting this problem:

                    8.2.3.2.1  CLD(s)

                    CFS.99166,70-10-978


                    8.2.3.2.2  QAR(s)

                    None.


               8.2.3.3  Problem Analysis:

               The procedure did not check to see if DECnet DTSS was
               disabled.  Without this check, DECnet startup could
               overwrite the TDF values set at system startup by VMS.


               8.2.3.4  Work-arounds:

               None.


          8.2.4  Timezone differential factor not preserved across
                 system reboots

               8.2.4.1  Problem Description:

               When setting the time differential factor to a value
               which is not the zone's default and DTSS is not active on
               the system, the differential factor is not preserved
               across system reboots.

               TEST> @SYS$MANAGER:UTC$TIME_SETUP !selecting UTC
                                                  and a differential
                                           factor of 1 hour
               TEST> SHOW LOG *TIMEZONE*

               (LNM$SYSTEM_TABLE)
               "SYS$TIMEZONE_DAYLIGHT_SAVING" = "0"
               "SYS$TIMEZONE_DIFFERENTIAL" = "3600" <The differential
                                                     factor set to
                                              one hour
               "SYS$TIMEZONE_NAME" = "GMT"

                                                               Page 10


               "SYS$TIMEZONE_RULE" = "GMT0"

               After a system reboot:

               TEST> SHOW LOG *TIMEZONE*

               (LNM$SYSTEM_TABLE)
               "SYS$TIMEZONE_DAYLIGHT_SAVING" = "0"
               "SYS$TIMEZONE_DIFFERENTIAL" = "0" <The differential
                                                  factor had been
                                                  set to the zone's
                                           default value
               "SYS$TIMEZONE_NAME" = "GMT"
               "SYS$TIMEZONE_RULE" = "GMT0"

               Images Affected:

                -  [SYSEXE]TDF$SET_TIMEZONE.EXE



               8.2.4.2  CLDs, and QARs reporting this problem:

                    8.2.4.2.1  CLD(s)

                    CFS.102373


                    8.2.4.2.2  QAR(s)

                    None.


               8.2.4.3  Problem Analysis:

               UTC$TIME_SETUP.COM, stores the differential factor in
               SYS$TIMEZONE.DAT.  During a system boot a new version of
               SYS$TIMEZONE.DAT is being created.  The new version
               contains the timezone's default differential factor
               overriding the content of the previous version.


               8.2.4.4  Work-arounds:

               None.


          8.2.5  Using many of the supplied timezone files results in
                 error


                                                               Page 11


               8.2.5.1  Problem Description:

               OpenVMS ships 42 GMT timezone files but can only use 4 of
               the 42 files.  Trying to use 39 of the OpenVMS supplied
               timezone files results in the error:

               $@SYS$MANAGER:UTC$TIME_SETUP

               ... chose a GMT timezone with a non-zero TDF

               %DTSS-E-NOMSG, Message number 0295897A
               %DTSS-E-NOMSG, Message number 0295896A
               ***
               *** The time zone you have chosen produces a
               *** time zone rule that is not usable.  If you
               *** do not correct this your system will not
               *** boot or run correctly.
               ***
               *** Rerun UTC$TIME_SETUP.COM and select a
               *** different time zone.
               ***

               $ SHOW LOGICAL SYS$TIMEZONE
               "SYS$TIMEZONE_RULE" = "Invalid timezone
               rule: GMT-04004"


               Images Affected:

                -  [SYSEXE]SYS$READ_TIME_ZONE_RULE.EXE

                -  [SYSMGR]UTC$TIME_SETUP.COM



               8.2.5.2  CLDs, and QARs reporting this problem:

                    8.2.5.2.1  CLD(s)

                    CFS.102373,CFS.91094,CFS.85381


                    8.2.5.2.2  QAR(s)

                    75-83-162


               8.2.5.3  Problem Analysis:

               The code specifications stated that only POSIX compliant
               timezone rules were supported.  The GMT zones timezone
               names do not conform to the POSIX standard.  Digits,
               commas, plus sign and minus sign are not allowed in the
               standard.

                                                               Page 12


               8.2.5.4  Work-arounds:

               None.


          8.2.6  A PGFIPLHI bugcheck could be seen while booting.

               8.2.6.1  Problem Description:

               A PGFIPLHI bugcheck could be seen while booting.

               Images Affected:

                -  [SYSEXE]SYS$DAYLIGHT_SAVING.EXE

                -  [SYSEXE]TDF$SET_TIMEZONE.EXE



               8.2.6.2  CLDs, and QARs reporting this problem:

                    8.2.6.2.1  CLD(s)

                    None.


                    8.2.6.2.2  QAR(s)

                    75-101-416


               8.2.6.3  Problem Analysis:

               IPL was elevated prior to a call to exe$event_notify but
               the routine issuing the event notification was not locked
               into the working set.


               8.2.6.4  Work-arounds:

               None.


          8.2.7  Remove Daylight Saving time adjustment delay.

               8.2.7.1  Problem Description:

               Daylight saving time adjustments occur one minute and
               thirty seconds after the official DST time adjustment
               moment.  This delay has been removed.

               Images Affected:

                -  [SYSEXE]JBC$JOB_CONTROL.EXE


                                                               Page 13


               8.2.7.2  CLDs, and QARs reporting this problem:

                    8.2.7.2.1  CLD(s)

                    None.


                    8.2.7.2.2  QAR(s)

                    None.


               8.2.7.3  Problem Analysis:

               The delay is no longer needed.


               8.2.7.4  Work-arounds:

               None.


     8.3  Problems addressed in the VMS731_TDF-V0100 kit

          8.3.1  Delay Daylight Savings time adjustment for Java

               8.3.1.1  Problem Description:

               Java applications that run continuously through the
               daylight savings time adjustment incur a two hour clock
               adjustment rather than a one hour clock adjustment.  The
               java application must be stopped and restarted to correct
               the time.

               Images Affected:

                -  [SYSEXE]JBC$JOB_CONTROL.EXE



               8.3.1.2  CLDs, and QARs reporting this problem:

                    8.3.1.2.1  CLD(s)

                    CFS.96221,70-3-6496,CFS.96226


                    8.3.1.2.2  QAR(s)

                    None.

                                                               Page 14


               8.3.1.3  Problem Analysis:

               Java was designed to run 24 hours a day and will adjust
               for daylight savings time automatically, even if the
               OpenVMS system time is not adjusted.  However, if the
               OpenVMS system time is adjusted out from under a Java
               application during the double hour, when the roll over
               hour occurs, Java will be an hour off.

               The Double hour is between 1:00am and 2:01am for ET.  If
               the time is changed after 2:01, Java will have the right
               time.  The fix is to Delay the OpenVMS time adjustment by
               one minute and thirty seconds.  For Eastern US timezone
               the change will occur at 02:01:30AM.


               8.3.1.4  Work-arounds:

               None.


          8.3.2  Multi-threaded process looping at daylight savings
                 forward time change.

               8.3.2.1  Problem Description:

               In the Southern Hemisphere when the time was moved
               forward at the October Daylight Savings Time adjustment,
               multithreaded processes went into a tight CPU loop.
               Examples of applications showing the problem are DCPS
               symbiont, decevent, or anything using the Java runtime.
               Stopping and restarting the processes resolved the
               problem.

               This problem will happen again at the next daylight
               savings time adjustment.

               Images Affected:

                -  [SYSEXE]SYS$DAYLIGHT_SAVING.EXE

                -  [SYSEXE]TDF$SET_TIMEZONE.EXE



               8.3.2.2  CLDs, and QARs reporting this problem:

                    8.3.2.2.1  CLD(s)

                    70-3-6529,CFS.95945

                                                               Page 15


                    8.3.2.2.2  QAR(s)

                    None.


               8.3.2.3  Problem Analysis:

               After adjusting the system time and system TDF value, TDF
               calls exe$event_notify to inform interested parties of
               the change.  TDF did not properly format the notification
               event mask and was signaling a Galaxy member deletion not
               a TDF update.

               DecThreads is registered for TDF change event
               notification so that it can adjust it's timer values.  A
               pthread_delay of 5 seconds should expire in 5 seconds,
               regardless of the time change.  Because threads did not
               receive the TDF change notification, a 5 second delay
               waited 1 hour and 5 seconds, which is at least one cause
               of the looping symptom.


               8.3.2.4  Work-arounds:

               None.


          8.3.3  %LOGIN-F-DISUSER, account is disabled error message

               8.3.3.1  Problem Description:

               Setting the DISUSER flag on the SYSTEM account causes the
               login failure message:

                 %LOGIN-F-DISUSER, account is disabled

               to be displayed when the job controller tries and retries
               creating the daylight savings time adjustment process.

               Images Affected:

                -  [SYSEXE]JBC$JOB_CONTROL.EXE



               8.3.3.2  CLDs, and QARs reporting this problem:

                    8.3.3.2.1  CLD(s)

                    CFS.96940 70-3-6596

                                                               Page 16


                    8.3.3.2.2  QAR(s)

                    None.


               8.3.3.3  Problem Analysis:

               The $CREPRC call didn't specify the PRC$M_UAF flag so the
               process creation was checked against the UAF file.  Since
               the process runs under the JOB_CONTROL process user,
               SYSTEM, the login failure occurred.  Since this process
               creation is an internal VMS operation, it is not
               necessary to check the UAF.


               8.3.3.4  Work-arounds:

               None.


9  INSTALLATION INSTRUCTIONS

     9.1  Compressed File

     This kit is provided as a DCX compressed kit.  To expand this file
     to the installable PCSI file, run the file with a RUN file_name
     command.  When the file is run you will see the following output:

     $ RUN VMS731_LAN-V0500.PCSI-DCX_AXPEXE

     FTSV DCX auto-extractible compressed file for OpenVMS (AXP)
     FTSV V3.0 -- FTSV$DCX_AXP_AUTO_EXTRACT
     Copyright (c) Digital Equipment Corp. 1993

     Options: [output_file_specification] [input_file_specification]

     The decompressor needs to know the filename to use for the
     decompressed file. If you don't specify any, it will use the
     original name of the file before it was compressed, and
     create it in the current directory.  If you specify a
     directory name, the file will be created in that directory.

     Decompress into (file specification):


     If you want the file to be expanded into a different directory,
     enter the directory specification.  DO NOT enter a new file name.
     The expanded file must retain the original name.

     If you want to expand the file via batch, the command file must
     contain an answer to the Decompress into "(file specification)"
     question, either a <CR> or an alternate directory specification

                                                               Page 17


     9.2  Installation Command

     Install this kit with the POLYCENTER Software installation utility
     by logging into the SYSTEM account, and typing the following at the
     DCL prompt:

     PRODUCT INSTALL VMS731_TDF /SAVE_RECOVERY_DATA
     [/SOURCE=location of Kit]

     The /SAVE_RECOVERY_DATA qualifier is optional but highly
     recommended.  Using this qualifier will allow easy removal of the
     kit from the system in the event of problems.

     The kit location may be a tape drive, CD, or a disk directory that
     contains the kit.  The /SOURCE qualifier is not needed if the
     PRODUCT INSTALL command is executed from the same directory as the
     kit location.

     Additional help on installing PCSI kits can be found by typing HELP
     PRODUCT INSTALL at the system prompt.


     9.3  Scripting of Answers to Installation Questions

     During installation, this kit will ask and require user response to
     several questions.  If you wish to automate the installation of
     this kit and avoid having to provide responses to these questions,
     you must create a DCL command procedure that includes the following
     logical name definitions and commands:

      o  To avoid the BACKUP question, define the following:

              $ DEFINE/SYS NO_ASK$BACKUP TRUE

      o  To avoid the REBOOT question, define the following:

              $ DEFINE/SYS NO_ASK$REBOOT TRUE


      o  To save replaced files as *.*_OLD define the following logical
         name as YES.  If you do not wish to save replaced files, define
         the logical name as NO.  Note that if you use the
         /SAVE_RECOVERY_DATA qualifier (recommended) on the PRODUCT
         INSTALL command all replaced files will be saved as part of
         that operation.  There is no need to also save files as
         *.*_OLD:

            $ DEFINE/SYS ARCHIVE_OLD NO

      o  Add the following qualifiers to the PRODUCT INSTALL command and
         add that command to the DCL procedure.

           /PROD=DEC/BASE=AXPVMS/VER=V5.0/SAVE_RECOVERY_DATA


                                                               Page 18


      o  De-assign the logical names assigned

     For example, a sample command file to install the VMS731_TDF-V0500
     kit would be:

     $
     $ DEFINE/SYS NO_ASK$BACKUP TRUE
     $ DEFINE/SYS NO_ASK$REBOOT TRUE
     $ DEFINE/SYS ARCHIVE_OLD NO
     $!
     $ PROD INSTALL VMS731_TDF/PRODUCER=DEC/BASE=AXPVMS-
           /VER=V5.0/SAVE_RECOVERY_DATA
     $!
     $ DEASSIGN/SYS NO_ASK$BACKUP
     $ DEASSIGN/SYS NO_ASK$REBOOT
     $!
     $ exit



     9.4  Special Installation Instructions:

     To assure that the UTC time startup file contains  the  changes  in
     this  kit,  you  must  recreate  the  startup  file  by running the
     [SYSMGR]UTC$TIME_SETUP.COM procedure.  This procedure must  be  run
     after  installation of this kit completes, but before rebooting the
     system.


10  COPYRIGHT AND DISCLAIMER:

     (C) Copyright 2004 Hewlett-Packard Development Company, L.P.

     Confidential computer software.  Valid license from HP and/or its
     subsidiaries required for possession, use, or copying.

     Consistent with FAR 12.211 and 12.212, Commercial Computer
     Software, Computer Software Documentation, and Technical Data for
     Commercial Items are licensed to the U.S.  Government under
     vendor's standard commercial license.

     Neither HP nor any of its subsidiaries shall be liable for
     technical or editorial errors or omissions contained herein.  The
     information in this document is provided "as is" without warranty
     of any kind and is subject to change without notice.  The
     warranties for HP products are set forth in the express limited
     warranty statements accompanying such products.  Nothing herein
     should be construed as constituting an additional warranty.

     DISCLAIMER OF WARRANTY AND LIMITATION OF LIABILITY

     THIS PATCH IS PROVIDED AS IS, WITHOUT WARRANTY OF ANY KIND.  ALL
     EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES,
     INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR
     PARTICULAR PURPOSE, OR NON-INFRINGEMENT, ARE HEREBY EXCLUDED TO THE
     EXTENT PERMITTED BY APPLICABLE LAW.  IN NO EVENT WILL HP BE LIABLE
     FOR ANY LOST REVENUE OR PROFIT, OR FOR SPECIAL, INDIRECT,

                                                               Page 19


     CONSEQUENTIAL, INCIDENTAL OR PUNITIVE DAMAGES, HOWEVER CAUSED AND
     REGARDLESS OF THE THEORY OF LIABILITY, WITH RESPECT TO ANY PATCH
     MADE AVAILABLE HERE OR TO THE USE OF SUCH PATCH.