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
» 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
ADV_SERVER ADVANCEDSERVER-V0703-A1-1 Advanced Server for OpenVMS Alpha V7.3A-ECO1 ECO Summary
TITLE: ADV_SERVER ADVANCEDSERVER-V0703-A1-1 Advanced Server for OpenVMS Alpha V7.3A-ECO1 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.

*ADV_SERVER] ADVANCEDSERVER-V0703-A1-1 Advanced Server for OpenVMS Alpha (V7.3A-ECO1) ECO Summary

New Kit Date:       06-FEB-2003
Modification Date:  10-FEB-2003
Modification Type:  Kit updated for Installation Rating
Copyright (c) Compaq Computer Corporation 2002,2003.  All rights reserved.

PRODUCT:    Advanced Server for OpenVMS Alpha (V7.3A-ECO1)

OP/SYS:     OpenVMS Alpha

SOURCE:     Compaq Computer Corporation


     ECO Kit Name:  ADVANCEDSERVER-V0703-A1-1 
     ECO Kits Superseded by This ECO Kit:  None
     ECO Kit Approximate Size:  116928 Blocks 
     Kit Applies To:  OpenVMS Alpha V7.2-2,V7.3,V7.3-1
		      Advanced Server for OpenVMS Alpha V7.3A	
     System/Cluster Reboot Necessary:  Yes
     Rolling Re-boot Supported:  No
     Installation Rating:  INSTALL_1
			   1:  To be installed by all customers
			       running Advanced Server V7.3A	

     Kit Dependencies:

       The following remedial kit(s) must be installed BEFORE
       installation of this kit:


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



An ECO kit exists for Advanced Server for OpenVMS Alpha (V7.3A-ECO1).
This kit addresses the following problems:


     o  Advanced Server Problems with File Access Permissions

         o  Permissions are not inherited properly on a new
       	    directory created in a share that existed prior to
      	    installation of V7.3A. The Advanced Server conforms to
	    the Windows NT Security model, including the inheritance
	    of file and directory security from directories to the
	    contents of directories. It is the Windows NT security
	    inheritance that is not working properly. For more
	    information on Windows NT and Windows 2000 security
	    descriptors and inheritance, see Chapter 12 (Access
	    Control) in Part 2 of the Microsoft Windows 2000 Server
 	    Distributed Systems Guide, at:


         o The Creator Owner ACE might be missing from directories
       	   created after installing V7.3A.

         o %86 ACEs are not being created on some files and
           directories. The Windows NT security descriptor is
           stored in an OpenVMS ACL, specifically in the %86
           ACE. In some cases, the %86 ACE is not being applied
           when it should be. The unsupported registry parameter
           ForceFileAcl affects the creation of %86 ACEs in
           files. In the Advanced Server V7.3A, this parameter
           was inadvertently set to a default value of 0 instead of
           the expected value of 1. With V7.3A-ECO1, ForceFileAcl
           is set to 1 (internally to the Advanced Server) and the
           registry value is ignored.

     These three problems may show up in any of a variety of
     unexpected ways regarding user access to file and directory
     resources. Some problems that have been reported include
     users being able to create files but not being able to
     modify or rename them, and users being unable to access a
     file that they expect to be accessible. For instance, when
     you display the permissions for the problem directories,
     as in the following example (using the ADMINISTRATOR SHOW
     FILES/PERMISSIONS command), the permissions might include
     "Special Access" and "(Not Specified)" instead of the
     expected permissions (such as "Change (RWXD) (RWXD)").

                  Permissions:            Access
                    Administrators        Special Access (All) (Not Specified)
                    Everyone              Special Access (RWXD) (Not Specified)
                    DWilson               Special Access (All) (Not Specified)
                    Server Operators      Special Access (RWXD) (Not Specified)
                    SYSTEM                Special Access (All) (Not Specified)

     Note also that the CREATOR OWNER information is missing
     from this display. The following example shows the
     permissions that might be expected for the directory ACCNTS
     (and here the CREATOR OWNER information is present, as it
     should be):

                  Permissions:            Access
                    Administrators        Full Control (All) (All)
                    CREATOR OWNER         Full Control (All) (All)
                    Everyone              Change (RWXD) (RWXD)
                    DWilson               Special Access (All)* (Not Specified)
                    Server Operators      Change (RWXD) (RWXD)

     o  Wrong Time Set on Client After NET TIME Command Is Used to
   	Synchronize with the Server

        When the NET TIME command is issued from a PC client to
        synchronize its clock with the Advanced Server (V7.3-
        ECO2 or later), as in the following example where the
        server is named TINMAN, the time set on the client might
        be incorrect. The time set on the client will be off by the
        GMT difference (in hours) reported by the server.

        C:\> NET TIME \\TINMAN /SET

     o  File Remains Locked, Access Violation Errors Reported

        In rare circumstances, usually seen in environments that
        include a large number of clients, an attempt to open
        a file in a share on an OpenVMS Cluster can fail with a
        sharing violation. This continues to occur after repeated
        attempts to open the file.

        The problem is seen only on one server node in the cluster.
        The file can be opened from the other server node(s) in the
        cluster. The only way to solve the problem is to restart
        the server on the node that has the problem.

     o  Copying New Files with Certain Names to a Share Might Fail

        Copying new files to an Advanced Server share might fail,
        depending on the names of the files. The following are
        examples of file names that cause the failure (the file
        extension is irrelevant):


        Attempts to copy such files result in an error message
        similar to the following:

        Error Copying File
        Cannot copy filename: Cannot find the specified file.
        Make sure you specify the correct path and filename.

     o  Server Might Crash in Routine RealGetSidOfUnixOwner

        The server might crash in routine NtaclGetSidOfUnixOwner
        of module NTACLMAP, leaving a traceback similar to the
        following in the PWRK$LMSRV log file:

        image       module     routine    line    rel PC           abs PC
        %SYSTEM-F-ACCVIO, access violation, reason mask=00,
        virtual address=0000000000000000, PC=00000000001AC7E0, PS=0000001B
        %TRACE-F-TRACEBACK, symbolic stack dump follows
         image       module   routine      line    rel PC           abs PC
         PWRK$LMSRV  ACLMAP  RealGetSidOfUnixOwner
                                           120640 0000000000000250 0000000000...
         PWRK$LMAPISHR  NTACLMAP  NtaclGetSidOfUnixOwner
                                           89523 00000000000001FC 00000000005...
         PWRK$LMAPISHR  NTACL  get_custom_sd
                                           6385 00000000000000B0 00000000005C...
         PWRK$LMAPISHR  NTACL  NtaclFetchWorkingSD
                                           98211 00000000000016D8 00000000005...

     o  PWRK$LMMCP Hangs with One or More Server Cluster Members in
   	the LEF State

        On an OpenVMS Cluster of four or more cluster members,
        an attempt to start the Advanced Server on the 4th and
        remaining cluster members might result in the PWRK$LMMCP
        process on each of these servers hanging in the LEF (local
        event flag) wait state. Symptoms include clients being
        unable to connect to the servers and ADMINISTER commands
        hanging or timing out.


Advanced Server for OpenVMS uses the POLYCENTER Software Installation (PCSI) 
utility to install.  Refer to the Advanced Server release notes and the Compaq 
Advanced Server for Open VMS Server Installation and Configuration Guide for
complete details on how to install and configure.

Please note the following:

     o  Before attempting to install the Advanced Server,
        HP recommends that you check your system for the
        SYS$UPDATE:PWVN$IVP.DAT file and remove it. Previous
        versions of PWVN$DEINSTAL.COM failed to remove the
        file. If SYS$UPDATE:PWVN$IVP.DAT is present, the
        installation assumes that Netware is still present
        and fails.

     o  In an OpenVMS Cluster, when installing the Advanced
        Server V7.3A for OpenVMS over a previous installation
        of V7.3, V7.3-ECO1, or V7.3-ECO2 of the Advanced Server
        for OpenVMS, you must reboot your system before you
        run the configuration procedure (PWRK$CONFIG.COM). The
        installation procedure will notify you while presenting
        the reboot options that you must reboot your system
        before running PWRK$CONFIG.COM.
        If you do reboot as recommended, you will not have to
        reboot your system again after configuring your server,
        unless you modify configuration parameters affecting
        system resources (such as changes to the physical memory
        to be used by the configuration, client capacity, or the
        data cache size).

For the corrections to take effect, you must reboot the system.

All other trademarks are the property of their respective owners.
Files on this server are as follows:
privacy statement using this site means you accept its terms