*******************************************************************************
* *
* This is a newly released patch... *
* *
* Online links can be found at *
* http://ftp.support.compaq.com/patches/public/vms/axp/v7.1-2/dec-axpvms-vms712_cliutl-v0100--4.README
*******************************************************************************

TITLE: OpenVMS VMS712_CLIUTL-V0100 Alpha V7.1-2 CLIUTL ECO Summary

Modification Date: 17-JAN-2001
Modification Type: New Kit
 
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-dcx_axpexe.pcsi, then it can
       be expanded by typing RUN kitname-dcx_axpexe.pcsi. The resultant
       file will be the PCSI installation file which can be used to install
       the ECO.
 

Copyright (c) Compaq Computer Corporation 2000. All rights reserved.

OP/SYS: OpenVMS Alpha

COMPONENT: CLIUTL

SOURCE: Compaq Computer Corporation

ECO INFORMATION:

     ECO Kit Name: VMS712_CLIUTL-V0100
                    DEC-AXPVMS-VMS712_CLIUTL-V0100--4.PCSI
     ECO Kits Superseded by This ECO Kit: None
     ECO Kit Approximate Size: 2048
     Kit Applies To: OpenVMS Alpha V7.1-2
     System/Cluster Reboot Necessary: No
     Rolling Re-boot Supported: Information Not Available
     Installation Rating: 3

     Kit Dependencies:

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

           VMS712_UPDATE-V0300
           VMS62TO71U2_PCSI-V0200

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

         VMS712_RMS-V0100

ECO KIT SUMMARY:

An ECO kit exists for CLIUTL on OpenVMS Alpha V7.1-2. This kit addresses
the following problems:

Problems Addressed In VMS712_CLIUTL-V0100:

   o A SET DEVICE/SERVED <TAPEDEV> command may fail with a
       %SYSTEM-F-IVDEVNAM error. This problem could occur when an
       ALPHA system is mistakenly booted with a SYSGEN parameter
       TMSCP_SERVE_ALL = 0. As a result, none of the tape drives are
       served to the cluster clients. Consequently, typing the SET
       DEVICE/SERVED <TAPEDEV> command fails. Since the SYSGEN
       parameter is not dynamic, a reboot of the server is necessary
       to make the tape devices available to the client nodes.

       This change extends functionality of the SET DEVICE/SERVED on
       ALPHA servers to include tape devices.

           Images Affected: [SYSEXE]SET.EXE

 
   o If the $SET AUDIT/SERVER=START command fails, the system
       STARTUP process will hang in a loop waiting for the
       AUDIT_SERVER process to start.

           Images Affected: [SYSEXE]SETAUDIT.EXE

   o When an unprivileged user attempts to access a queue and is
       denied, the event is not alarmed or audited.

           Images Affected: [SYSEXE]SUBMIT.EXE

   o Add a new /CONTENTION_POLICY qualifier to SET RMS_DEFAULT to
       address locking fairness issues.

       The new Alpha global buffer read-mode lock support introduced
       in V7.2-1H1 is functionally compatible with both VAX and older
       Alpha releases. Operations in mixed clusters produce correct
       results. However, there is a locking fairness issue that may
       arise with mixed cluster operations.

       In a mixed cluster environment with very high contention for
       specific buckets, it is possible for accesses to write-shared
       files on nodes using read-mode bucket locking to dominate
       access to a bucket. Nodes without this support might be
       unable to access the bucket for a protracted period of time.
       It is also possible to observe comparable behavior on all
       OpenVMS versions when dealing with accesses to write-shared
       files without global buffers enabled -- even on a standalone
       system. A similar fairness issue between lock conversions and
       new lock requests may be observed in which the new lock
       requests may remain un-granted for an extended period of time.

       This kit provides an interface for RMS support for a new
       option to improve fairness under high contention conditions
       for write-shared files. The option is controlled using the
       /CONTENTION_POLICY qualifier to the DCL command SET
       RMS_DEFAULT. The option may be set at a process or system
       level. Since selecting this option may noticeably increase
       locking overhead and since many applications will never
       encounter this issue, the default system behavior leaves this
       option disabled. A future lock management enhancement should
       make this fairness workaround unnecessary for later releases.

       The following are valid PROCESS keywords (/SYSTEM not
       specified) for SET RMS_DEFAULT/CONTENTION_POLICY:

          NEVER Never use the higher overhead option to
                          improve fairness for any write-shared files
                          accessed by this process; minimal
                          overhead.

          SOMETIMES Use this option for fairer bucket access
                          (but higher overhead) to any write-shared
                          files with global buffers enabled that are
                          accessed by this process.

          ALWAYS Use this option for fairer bucket access
                          (but higher overhead) to all write-shared
                          files accessed by this process.

          SYSTEM_DEFAULT Use system setting. Note that this keyword
            (Default) is disallowed with /SYSTEM.

       The following are valid SYSTEM keywords (/SYSTEM specified):

          NEVER (Default) Never use the higher overhead
                          option to improve fairness for any
                          write-shared files accessed on the system;
                          minimal overhead.

          SOMETIMES Use this option for fairer bucket access
                          (but higher overhead) to any write-shared
                          files with global buffers enabled that are
                          accessed on the system.

          ALWAYS Use this option for fairer bucket access
                          (but higher overhead) to all write-shared
                          files accessed on the system.

          Images Affected: [SYSEXE]SET.EXE

   o SHOW LOGICAL allocates virtual address space based on pagesize
        rather than pagelet size for Alpha only. De-allocation of
        used virtual memory was incorrect.

           Images Affected: [SYSEXE]SHOW.EXE

   o If the virtual-circuit (PB$ path-block) count exceeds four
        times the SCS-node count, a SHOW CLUSTER command will hang on
        startup on cluster nodes with many SCS ports, e.g., CIPCA,
        CIXCD, MC:... or Pxx0: devices. An "SCS-node" is defined as
        any SCS-speaking node, such as HSJxx/HSCxx Storage
        Controllers, RFxx DSSI disk controllers, or VMS nodes, etc.

           Images Affected: [SYSEXE]SHWCLSTR.EXE

 
INSTALLATION NOTES:

No reboot is necessary after successful installation of this kit.
However, users must log out and log back in to use the new features
provided by this kit.

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 VMS712_CLIUTL /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

All trademarks are the property of their respective owners.

---

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]