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




1  KIT NAME:

     ADAAE05035


2  KIT DESCRIPTION:

     2.1  Installation Rating:

     INSTALL_2: To be installed by all customers using the
                     following feature(s):

      -  Ada


     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:

     No reboot is necessary after installation of this kit.


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

     OpenVMS Alpha V6.2 and up.


     2.4  New functionality or new hardware support provided:

     No.


3  KITS SUPERSEDED BY THIS KIT:


      -  ADAAE04035



4  KIT DEPENDENCIES:

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


      -  HP Ada V3.5A or ADAAE04035.

     This is not a full HP Ada kit.  Installation requires that  one  of
     the above kits is already installed on the system.

                                                                Page 2


     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  NEW FUNCTIONALITY AND/OR PROBLEMS ADDRESSED IN THE ADAAE05035 KIT

     5.1  New functionality addressed in this kit

     None


5.2  Problems addressed in this kit

     5.2.1  Ada Object Module Names Not Unique

          5.2.1.1  Problem Description:

          Ada names for object modules are based off of users'
          compilation unit names.  Long names were truncated at 31
          characters to comply with name length restrictions in the
          object module format.  Multiple long names could collide into
          identically named object modules if they were not unique in
          the first 31 characters.

          This change is compatible with how HP Ada on OpenVMS VAX names
          object modules.  This problem does not effect most HP Ada
          users, unless they require unique object module names.

          Images Affected:

           -  [SYSEXE]ADA.EXE



          5.2.1.2  CLDs, and QARs reporting this problem:

          QXCM1000241083


          5.2.1.3  Problem Analysis:

          The HP Ada target on Alpha was truncating long names, not
          making them unique for object modules.  This change makes the
          object names unique, by changing them when necessary.

                                                                Page 3


          5.2.1.4  Work-arounds:

          Use names unique to the first 31  characters  for  compilation
          units.


     5.2.2  ACS MERGE Error Message Incomplete

          5.2.2.1  Problem Description:

          Errors during ACS MERGE commands give users minimal
          information:

          %ACS-E-CL_NEWVEREXI, Parent library contains a newer
          version of package specification AXTEST_TWELVE_TYPES
          compiled 20-MAY-2003 14:10:39.71 not merged
          %ACS-E-CL_ERRDURMER, Error during merge of
          AXTEST_TWELVE_TYPES;  not merged

          The new message has been improved to help users determine why
          their compilation unit was not merged into their program
          library.

          The improved error message reads:
          %ACS-E-CL_NEWVEREXI, Parent library contains a newer version of
          package specification AXTEST_TWELVE_TYPES
          Destination compiled 20-MAY-2003 14:10:39.71,
          Source compiled 20-MAY-2003 14:10:14.49,
          Destination source file 10-JUN-1996 17:38:02.44,
          Source source file 10-JUN-1996 17:38:02.44;
          not merged

          Note that the error message output was formatted for
          readability.  The destination is the program library where the
          user wants to merge files into.  The source is the program
          library which you want to merge files from.  This example
          shows that the destination library was compiled slightly after
          the source library, so ACS refuses to do the merge.

          Images Affected:

           -  [SYSEXE]ACS.EXE



          5.2.2.2  CLDs, and QARs reporting this problem:

          CFS.100439


          5.2.2.3  Problem Analysis:

          This improved error message is intended to help the user
          figure out why their compilation unit was not getting merged.

                                                                Page 4


          5.2.2.4  Work-arounds:

          Users would need to analyze their two source  and  destination
          libraries  for  the problem compilation unit to get this added
          information.  This could require knowledge of how  Ada  stores
          files in the Ada library to look at file dates within them.


     5.2.3  Ada Biased Record Data Cannot be Debugged

          5.2.3.1  Problem Description:

          HP Ada was generating incorrect debugging information for Ada
          biased types.  Users examining this data in Debug would see
          incorrect results.

          For example:

          type REC_ED40VDA is
              record
                  F1 : INTEGER range 99..102;
                  F2 : INTEGER range 1..8;
              end record;
          for REC_ED40VDA use
              record
                  F1 at 0 range 0..1;
                  F2 at 0 range 2..4;
              end record;
          B : REC_ED40VDA;
          ...
          B.F1 := 101
          B.F2 := 4

          Since the assignments are storing larger numbers than the
          record is able to store as images, the numbers are stored as
          "biased" off a base value.  This value was reported
          incorrectly to DEBUG.

          Images Affected:

           -  [SYSEXE]ADA.EXE



          5.2.3.2  CLDs, and QARs reporting this problem:

          None


          5.2.3.3  Problem Analysis:

          Ada compiler generated debugging information was incorrect.

                                                                Page 5


          5.2.3.4  Work-arounds:

          Users would need to do the bias calculation themselves,  since
          DEBUG  was  getting  incorrect information reported to it from
          Ada.


     5.2.4  Product name change to HP Ada

          5.2.4.1  Problem Description:

          Ada has been rebranded from Compaq Ada to HP Ada.

          Several user visible examples of the product name appear in
          compiler listings, ACS SHOW VERSION command, HELP ADA, HP Ada
          report mapper information.

          The correct product name; HP Ada, will now be used.

          Note that older documentation, such as the DEC Ada Language
          Reference Manual will not be updated.

          Images Affected:

           -  [SYSEXE]ADA.EXE

           -  [SYSEXE]ACS.EXE

           -  [SYSHLP.EXAMPLES.ADA]ADAMAP.EXE



          5.2.4.2  CLDs, and QARs reporting this problem:

          None


          5.2.4.3  Problem Analysis:

          None


          5.2.4.4  Work-arounds:

          None


     5.2.5  Compaq Ada V3.5A Shipped Bad HTML Documentation


                                                                Page 6


          5.2.5.1  Problem Description:

          Several Ada manuals are shipped in HTML format and placed in
          the Ada examples area, defined as ADA$HTML:  after
          installation.

          The V3.5A kit shipped incorrect files.  This kit ships the
          correct HTML files.

          Files Affected:

           -  [SYSHLP.EXAMPLES.ADA.HTML]*.HTML

           -  ADA$EXAMPLES:*.HTML



          5.2.5.2  CLDs, and QARs reporting this problem:

          None


          5.2.5.3  Problem Analysis:

          Incorrect files were shipped


          5.2.5.4  Work-arounds:

          Use .HTML files from Ada  V3.5  kit,  or  manuals  in  another
          format.


6  FILES PATCHED OR REPLACED:


      o  [SYSEXE]ADA.EXE (new image)

         Image Identification Information

         image name: "ADA"
         image file identification: "ADA V3.5A-26"
         image file build identification: ""
         link date/time:  4-APR-2006 17:11:08.16
         linker identification: "A11-12"


      o  [SYSEXE]ACS.EXE (new image)

         Image Identification Information

         image name: "ACS"
         image file identification: "ADA V3.5A-26"
         image file build identification: ""
         link date/time:  4-APR-2006 17:10:50.11
         linker identification: "A11-12"


                                                                Page 7


      o  HP Ada help file ([SYSHLP])

      o  Report Mapper (ADA$EXAMPLES:ADAMAP.HTML)

      o  DEC Ada manuals in HTML format (ADA$HTML:*.HTML)



7  INSTALLATION INSTRUCTIONS

     7.1  Compressed File

     This kit is provided as a Self Extracting ZIPEXE  kit.   To  expand
     this  file  to  the  installable  .PCSI file, run the file with the
     following command:

     $ RUN ADAAE05035.ZIPEXE



     7.2  Installation Command

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

     @SYS$UPDATE:VMSINSTAL ADAAE05035 [location of the saveset]

     The saveset location may be a tape drive, CD, or a disk directory
     that contains the kit saveset.


8  COPYRIGHT AND DISCLAIMER:

     (C) Copyright 2006 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

                                                                Page 8


     EXTENT PERMITTED BY APPLICABLE LAW.  IN NO EVENT WILL HP BE LIABLE
     FOR ANY LOST REVENUE OR PROFIT, OR FOR SPECIAL, INDIRECT,
     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.
