Jump to page titleUNITED STATES
hp.com home products and services support and drivers solutions how to buy
» contact hp


more options
 
hp.com home
End of Jump to page title
HP Services software patches
Jump to content


» software & drivers
» ask Compaq
» reference library
» forums & communities
» support tools
» warranty information
» contact support
» parts
» give us feedback

associated links
» what's new
» contract access
» browse patch tree
» search patch tree
» join mailing list

patches by topic
» DOS
» OpenVMS
» Security
» Tru64 Unix
» Ultrix 32
» Windows
» Windows NT

connection tools
» nameserver lookup
» traceroute
» ping


Find Support Information and Customer Communities for Presario.
Content starts here
OpenVMS VMS73_LINKER-V0400 Alpha V7.3 Linker ECO Summary
TITLE: OpenVMS VMS73_LINKER-V0400 Alpha V7.3 Linker ECO Summary
 
NOTE:  An OpenVMS saveset or PCSI installation file is stored
       on the Internet in a self-expanding compressed file.
 
       For OpenVMS savesets, the name of the compressed saveset
       file will be kit_name.a-dcx_vaxexe for OpenVMS VAX or
       kit_name.a-dcx_axpexe for OpenVMS Alpha. Once the OpenVMS
       saveset is copied to your system, expand the compressed
       saveset by typing RUN kitname.dcx_vaxexe or kitname.dcx_alpexe.
 
       For PCSI files, once the PCSI file is copied to your system,
       rename the PCSI file to kitname.pcsi-dcx_axpexe or
       kitname.pcsi-dcx_vaxexe, then it can be expanded by typing
       RUN kitname.pcsi-dcx_axpexe or kitname.pcsi-dcx_vaxexe.  The
       resultant file will be the PCSI installation file which can be
       used to install the ECO.
 

 
	     ECO NUMBER:     VMS73_LINKER-V0400
             PRODUCT:        OpenVMS Alpha OPERATING SYSTEM V7.3
             UPDATE PRODUCT: OpenVMS Alpha OPERATING SYSTEM V7.3


New Kit Date:       08-SEP-2003
Modification Date:  NONE
Modification Type:  NEW KIT


1  KIT NAME:

     VMS73_LINKER-V0400


2  KIT DESCRIPTION:

     2.1  Installation Rating:


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

      -  OpenVMS Alpha Linker

     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 successful installation of the kit.



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

     OpenVMS Alpha V7.3


     2.4  New functionality or new hardware support provided:

     No.


3  KITS SUPERSEDED BY THIS KIT:


      -  VMS73_LINKER-V0300



4  KIT DEPENDENCIES:

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


      -  VMS73_PCSI-V0100

      -  VMS73_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]LINK.EXE (new image)
          
         Image Identification Information
          
         image name: "LINK"
         image file identification:  "A13-00"
         image file build identification:  "X9UH-0060010010"
         link date/time: 21-AUG-2003 15:22:30.63
         linker identification:  "A11-50"



6  PROBLEMS ADDRESSED IN THIS KIT

     6.1  New problems addressed in the VMS73_LINKER-V0400 kit

          6.1.1  Fortran generates %LINK-W-MULPSC warnings.

               6.1.1.1  Problem Description:

               When using Fortran's ADDRESS64 attribute to allocate
               memory from P2 space, the linker generates %LINK-W-MULPSC
               warnings.

               Images Affected: [SYSEXE]LINK.EXE




          6.1.2  Images not installed resident

               6.1.2.1  Problem Description:

               Alpha image section size is limited to 32MB, the same
               size as VAX image section.  This limitation prevented
               large images, with image sections that spanned more than
               one image section, from being installed resident.  With
               this change, the maximum size of the code image section
               is being increased to 1GB.

               Images Affected: [SYSEXE]LINK.EXE





          6.1.3  Code section binding is not being  disabled,  resulting
                 in image corruption


               6.1.3.1  Problem Description:

               When a code image section spans across more than one
               image section and the image is linked with
               /SECTION_BINDING, code section binding is not being
               disabled.  The resultant image is corrupted and should
               not be installed resident.

               The following example shows an image linked with
               /SECTION_BINDING, the linker left the code section
               binding bit set.

               %LINK-W-BINDFAILS, binding failed, psect INSTRUCTIONS
                  spanned image section located at %X00000000
               %LINK-W-DBINDISABLE, section binding of DATA has been
                  disabled
               %ANALYZE-I-ERRORS, $1$DKB300:[VERIFICATION.LINKER
                                  .LINKER_TESTS]Y.EXE;2 0 errors
               (8)  EIHD$V_BIND_CODE_SEC 1
               (9)  EIHD$V_BIND_DATA_SEC 0

               Images Affected: [SYSEXE]LINK.EXE




     6.2  Problems addressed in the VMS73_LINKER-V0300 kit

          6.3  Increase the RMS I/O related parameters when doing I/O to
               the image file and map.

               6.3.1  Problem Description:

               This change increases the RMS I/O related parameters when
               doing I/O to the image file and map.  This will result in
               an increase in performance and reduce link time.

               Images Affected: [SYSEXE]LINK.EXE





7  INSTALLATION INSTRUCTIONS:

     7.1  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 VMS73_LINKER /SOURCE=[location of Kit]

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

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



     7.2  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
     definitions and commands:

      -  $ DEFINE/SYS NO_ASK$BACKUP TRUE

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

           /PROD=DEC/BASE=AXPVMS/VER=V4.0


      -  De-assign the logicals assigned

     For example, a sample command file to install the
     VMS73_LINKER-V0400 kit would be:

     $
     $ DEFINE/SYS NO_ASK$BACKUP TRUE
     $!
     $ PROD INSTALL VMS73_LINKER/PROD=DEC/BASE=AXPVMS/VER=V4.0
     $!
     $ DEASSIGN/SYS NO_ASK$BACKUP
     $!
     $ exit



8  COPYRIGHT AND DISCLAIMER:

     (C) Copyright 2003 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  COMPAQ  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.

Files on this server are as follows:
»dec-axpvms-vms73_linker-v0400--4.README
»dec-axpvms-vms73_linker-v0400--4.CHKSUM
»dec-axpvms-vms73_linker-v0400--4.pcsi-dcx_axpexe
privacy statement using this site means you accept its terms