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

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

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

connection tools
» nameserver lookup
» traceroute
» ping


Find Support Information and Customer Communities for Presario.
Content starts here
OpenVMS VMS73_UPDATE-V0100 Update Alpha V7.3 ECO Summary
TITLE: OpenVMS VMS73_UPDATE-V0100 Update Alpha V7.3 ECO Summary
 
New Kit Date:       22-DEC-2001
Modification Date:  22-FEB-2002 
Modification Type:  Note added regarding modify the PIOPAGES and IMGIOCNT
                    SYSGEN parameters failure.

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, then it can
       be expanded by typing RUN kitname.pcsi-dcx_axpexe.  The resultant
       file will be the PCSI installation file which can be used to install
       the ECO.
 

 

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

OP/SYS:     OpenVMS Alpha V7.3

COMPONENT:  System

SOURCE:     Compaq Computer Corporation

ECO INFORMATION:

     ECO Kit Name:  VMS73_UPDATE-V0100
                    DEC-AXPVMS-VMS73_UPDATE-V0100--4.PCSI
     ECO Kits Superseded by This ECO Kits: 
 
         VMS73_AUDSRV-V0100      VMS73_CLIUTL-V0100
         VMS73_CPU2608-V0100     VMS73_DRIVER-V0100
         VMS73_DTSS-V0100        VMS73_DW_MOT_MUP-V0100
         VMS73_FIBRE_SCSI-V0200  VMS73_IPC-V0100
         VMS73_LAN-V0200         VMS73_LINKER-V0200
         VMS73_MAIL-V0100        VMS73_MOUNT96-V0100
         VMS73_PTHREAD-V0100     VMS73_RMS-V0200
         VMS73_SHADOWING-V0100   VMS73_SYS-V0200
         VMS73_SYSBOOT-V0100     VMS73_SYSLOA-V0100

     ECO Kit Approximate Size:  25056 Blocks
     Kit Applies To:  OpenVMS Alpha V7.3
     System/Cluster Reboot Necessary:  Yes
     Rolling Re-boot Supported:  Yes
     Installation Rating:  INSTALL_1
                           1 - To be installed on all systems running
                                the listed version(s) of OpenVMS.

     Kit Dependencies:

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

         None

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

         None


***************************************************************************
*                              NOTE                                       *
*                                                                         *
* "The post installation command procedure included in this kit to modify *
* the PIOPAGES and IMGIOCNT SYSGEN parameters fails to perform a SYSGEN   *
* "USE CURRENT" prior to writing the changes to the  CURRENT set of       *
* parameters.                                                             *
*                                                                         *
* This may affect the permanent settings of parameters (such as           *
* LGI_CALLOUTS) that you have dynamically changed with the "USE ACTIVE"   *
* and "WRITE ACTIVE" command sequence and/or through an application       *
* since your last system boot.                                            *
*                                                                         *
* If you do not modify dynamic SYSGEN parameters using the above sequence,*
* then there is no need for further action. If you do utilize the above   *
* sequence to dynamically set SYSGEN parameters, then you should review   *
* the permanent (CURRENT) settings of them prior to your next reboot."    *
*                                                                         *
***************************************************************************

ECO KIT SUMMARY:

An ECO kit exists for System Components on OpenVMS Alpha V7.3.  This
kit addresses the following problems:

PROBLEMS ADDRESSED IN VMS73_UPDATE-V0100 KIT:

  o  The VMS73_UPDATE-V0100 kit is a  consolidation  of  previously
     released  OpenVMS  V7.3  ECO kits.  The following ECO kits are
     included:

            VMS73_AUDSRV-V0100               VMS73_CLIUTL-V0100
            VMS73_CPU2608-V0100              VMS73_DRIVER-V0100
            VMS73_DTSS-V0100                 VMS73_DW_MOT_MUP-V0100
            VMS73_FIBRE_SCSI-V0200           VMS73_IPC-V0100
            VMS73_LAN-V0200                  VMS73_LINKER-V0200
            VMS73_SYSLOA-V0100               VMS73_MAIL-V0100
            VMS73_MOUNT96-V0100              VMS73_PTHREAD-V0100
            VMS73_RMS-V0200                  VMS73_SHADOWING-V0100
            VMS73_SYS-V0200                  VMS73_SYSBOOT-V0100

     Following are the problems addressed by the above kits.

PROBLEMS ADDRESSED IN VMS73_AUDSRV-V0100 KIT

  o  Digital command language (DCL) does  not  regain  control
     when  the  SET  SECURITY  command  is  issued.  When this
     occurs, the profile for the object in question may not be
     updated on all nodes in a cluster environment.

         Images Affected:  [SYSEXE]AUDIT_SERVER.EXE


PROBLEMS ADDRESSED IN VMS73_CLIUTL-V0100 KIT:

  o  When a process exists on the system that is in  the  MUTEX  or
     CEF state, SHOW SYSTEM will ACCVIO when the state qualifier is
     used.  For example:

     QUEBIT>  SHOW SYS/STATE=MUTEX
     %SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual
     address=FFFFFFFFC0022A58, PC=0000000000042BE0, PS=0000001B

          Images Affected:  [SYSEXE]SHOW.EXE


  o  When running the Apache WEB server, a system can crash with  a
     SSRVEXCEPT bugcheck in SHOW+61DA0 or SHOW+6205.

          Images Affected:  [SYSEXE]SHOW.EXE


  o  When a SHOW  DEVICE/FULL  command  is  executed,  the  maximum
     blocks  in  extent  cache and blocks currently in extent cache
     fields are not displayed.

          Images Affected:  [SYSMSG]CLIUTLMSG.EXE


  o  When a SHOW PROCESS/ALL/ID=XXXXXXXX command is executed, where
     XXXXXXX  is  the  PID (Process Identifier) of the swapper, the
     following error can occur:

          %LIB-F-BADBLOSIZ, bad block size

          Images Affected:  [SYSEXE]SHOW.EXE


  o  When a SHO QUEUE command is entered, a queue entry number that
     is  over  10,000,000  shows as asterisks rather than the queue
     entry number.

          Images Affected:  [SYSEXE]QUEMAN.EXE
                            [SYSMSG]CLIUTLMSG.EXE


  o  A SET VOLUME/REBUILD command on a volume set may not reset the
     volume  write  count  to  the correct number of writers in the
     cluster.  This can occur when a node that had the  volume  set
     mounted  did  not update the volume write count on dismount or
     on a crash.  A SHOW DEVICE/REBUILD command always  shows  this
     volume  as needing a rebuild.  Even a SET VOLUME/REBUILD=FORCE
     command will not clear this rebuild status.

     Note: In order to receive this full correction, you must also 
           install the VMS73_MOUNT96-V0100 ECO kit.

          Images Affected:  [SYSEXE]SET.EXE


  o  In a SET  FILE/LOG/VERSION  command,  the  /LOG  qualifier  is
     ignored.  For example:

          SYSTEM1 SET FILE/LOG/VER LOGIN.COM;
          SYSTEM1

     The correct behavior is:

          SYSTEM1 SET FILE/LOG/VER LOGIN.COM;

          %SET-I-MODIFIED, WORK:[USER1]LOGIN.COM;2 modified
          SYSTEM1

          Images Affected: [SYSEXE]SET.EXE


  o  An invalid "error opening file" message could be displayed.

          Images Affected:  [SYSEXE]SET.EXE


  o  The  output  of  a  CREATE/DIRECTORY/LOG  command  prints  the
     resulting  directory  name  in  uppercase,  regardless  of the
     actual  on-disk  case.   The  actual  directory   is   created
     correctly,  but the informational message does not reflect the
     actual case of the directory.

     For example:

          $ SET DEFAULT DISK$ODS5:[test]
          $ SET PROCESS/PARSE=EXTENDED
          $ CREATE/DIRECTORY/LOG [test.MixedCaseDir]
          %CREATE-I-CREATED, DISK$ODS5:[TEST.MIXEDCASEDIR] created

          $ dir Mixed*.dir

          Directory DISK$ODS5:[test]

          MixedCaseDir.DIR;1


          Images Affected:  [SYSEXE]CREATE.EXE


  o  A  MTXCNTNONZ  bugcheck  could  occur  during   logical   name
     translation   via   the  DCL  SHOW  LOGICAL  command.

          Images Affected: [SYSEXE]SHOW.EXE


  o  The following shadow qualifiers are being clarified.

      o  If /READ_COST is specified with the virtual unit,  instead
         of an individual member, then all of the existing members'
         read cost is reset to their defaults.  With this change, a
         message is now displayed indicating this.

      o  If /MEMBER_TIMEOUT is specified with a virtual unit or  if
         /MVTIMEOUT   was   specified  to  a  member,  the  command
         succeeded in  changing  the  value.   However,  these  are
         conflicting conditions and should not be allowed.

          Images Affected:  [SYSEXE]SET.EXE


NEW FUNCTIONALITY ADDRESSED IN VMS73_CPU2608-V0100 KIT

  O  The  VMS73_CPU2608-V0100  kit   provides   support   for   the
     AlphaServer ES45

       Images Affected:  [SYS$LDR]SYS$CPU_ROUTINES_2608.EXE

PROBLEMS ADDRESSED IN VMS73_DRIVER-V0100 KIT

  o  If SYSTEM_CHECK is enabled, when a floppy diskette is  removed
     during  a floppy read or write, a MACHINECHK occurs due to use
     of an invalidated DMA scatter/gather register.

     If  SYSTEM_CHECK  is  not  enabled,  there  is  a  theoretical
     possibility  of  random  memory  corruption if the interrupted
     floppy operation was a read and the physical page  pointed  to
     by  the  scatter/gather  register  has  been reallocated for a
     different virtual page.

        Images Affected:  [SYS$LDR]SYS$DVDRIVER.EXE


PROBLEMS ADDRESSED IN VMS73_DTSS-V0100 KIT

  o  The DAYLIGHT_SAVINGS.COM procedure is used to change
     between Daylight Savings Time and Standard Time when
     automatic OpenVMS DST/STD changing and DTSS are  not
     in  use.   The  procedure correctly sets the TDF but
     moves the time the wrong way.

         Images Affected:  [SYSHLP.EXAMPLES]DAYLIGHT_SAVINGS.COM

PROBLEMS ADDRESSED IN VMS73_DW_MOT_MUP-V0100 KIT:

  o  Compaq has determined that systems  running  OpenVMS
     Alpha,  OpenVMS  VAX,  SEVMS VAX or SEVMS Alpha with
     the  DECwindows   MotifServer   installed   have   a
     potential   security  vulnerability  that  could  be
     exploited  to  allow  existing  users   unauthorized
     access  to  data  and  system resources.  To protect
     against this  potential  security  risk,  Compaq  is
     making   available  a  mandatory  update  patch  for
     OpenVMS customers.

     Installation  of  the  DECwindows  Motif  Server  is
     optional  during  the  installation  of  the OpenVMS
     Operating System.  You can verify whether or not the
     DECwindows  Motif  Server has been installed on your
     system using the following command:

             $ DIRECTORY SYS$LIBRARY:DECW$*.EXE

     If no DECW$*.EXE files are present on  your  system,
     the DECwindows Motif Server is not installed on your
     system and you do not need to apply  this  mandatory
     update.

                               NOTE
                               ----

     If the DECwindows Motif Server is not  installed  on
     your   system  you  do  NOT  need  to  install  this
     mandatory update.

     Apply this mandatory update if the  DECwindow  Motif
     Server  is  installed  on  your  system  and you are
     running one of the following versions of OpenVMS  or
     SEVMS:

      o  OpenVMS Alpha Version  6.2  and  all  associated
         hardware releases (for example, Version 6.2-1H1)

      o  SEVMS Alpha Version 6.2

      o  OpenVMS Alpha Version 7.1-2

      o  OpenVMS Alpha Version 7.2-1

      o  OpenVMS Alpha Version 7.2-2

      o  OpenVMS Alpha Version 7.2-1H1

      o  OpenVMS Alpha Version 7.3

      o  OpenVMS VAX Version 6.2

      o  OpenVMS VAX Version 7.1

      o  OpenVMS VAX Version 7.2

      o  OpenVMS VAX Version 7.3

      o  SEVMS VAX Version 6.2


                                 NOTE
                                 ----

     OpenVMS VAX V5.5-2 is not subject to this  potential
     security vulnerability.

     After  completing  the   update,   Compaq   strongly
     recommends  that  you perform an immediate backup of
     your system disk  so  that  any  subsequent  restore
     operations  begin with updated software.  Otherwise,
     you must reapply the update after a  future  restore
     operation.  Also, if at some future time you upgrade
     your system to one of the  versions  of  OpenVMS  or
     SEVMS listed you must reapply the update.

     Also, due to the nature of  the  problem  that  this
     problem,  Compaq  recommends  that  the  five  files
     relpaced buy this fix be deleted and not left on the
     system.

         Images Affected:  [SYSLIB]DECW$TRANSPORT_COMMON.EXE
                           [SYSLIB]DECW$TRANSPORT_DECNET.EXE
                           [SYSLIB]DECW$TRANSPORT_LAT.EXE
                           [SYSLIB]DECW$TRANSPORT_LOCAL.EXE                      -                                                        [SYSLIB]DECW$TRANSPORT_TCPIP.EXE

NEW FUNCTIONALITY INTRODUCED IN VMS73_FIBRE_SCSI-V0200 KIT:

  o  Interrupt and  Response  Coalescing  is  a  functional  option
     implemented  in  KGPSA firmware which allows LP8000 and LP9002
     adapters to reduce the number of interrupts seen  by  a  host.
     Given  a  response count and a delay time (in ms), the adapter
     can defer interrupting the host until that number of responses
     is  available  or  until  that  amount  of  time  has  passed,
     whichever occurs first.  This also makes each  interrupt  seen
     by  the  host  more  cost-effective  because it will generally
     process more responses per interrupt  than  without  Interrupt
     Coalescing.

          Images Affected:  [SYSHLP.UNSUPPORTED]FC$CP.EXE
                            [SYS$LDR]SYS$FGEDRIVER.EXE
                            [SYS$LDR]SYS$PGADRIVER.EXE

  o  You can turn on Interrupt and  Response  Coalescing  with  the
     following command:

       $ MCR SYS$ETC:FC$CP FGx  [] -
       $_ []

       -  FGx :   the  type  of  FG  device  (FGA,  FGB  etc.).   To
          determine  which  FG  devices  are  present,  refer to the
          section titled "Determining FGx Devices"

       -   :  Enables bit 1 = Response Coalescing and bit 0
          = Interrupt Coalescing.

       -   :  Delay is in milliseconds and can range  from
          0 to 255 decimal.

       -  Response count can range from 0 to 63 decimal.

       -  Any negative value leaves a parameter unchanged.

       -  Values returned are those  which  are  current  after  any
          changes.


     The recommended command is:

          MCR SYS$ETC:FC$CP FGA 3 1 8

     You should substitute FGA with whatever FG device you wish  to
     configure.   The  command  must be run once per boot for every
     Emulex FibreChannel adapter on which Interrupt  Coalescing  is
     to  be  enabled.   Once enabled it will persist across adapter
     initializations, path switches, CPU affinity changes, etc., in
     other words, until the next boot.  Interrupt Coalescing can be
     turned off by passing an "enables" value of 0.

  o  In order to tell which FGx device(s) you have on your  system,
     execute the following commands:

          $ ANALYZE/SYSTEM
          SDA>CLUE CONFIG/A

     Following is an excerpt of an example of  the  output  of  the
     above  commands.   Note that all fields are not included, only
     those needed to determine adapter type.

     Adapter Configuration:
     ----------------------

     Port    BusArrayEntry           Device Name / HW-Id
     ----    ----------------        --------------------
     FGA:    FFFFFFFF.810FBC40       KGPSA-CA (Emulex LP8000)
     FGB:    FFFFFFFF.810FBC78       KGPSA-** (Emulex LP9000)

     Interrupt and Response Coalesing will only operate  on  LP8000
     and  LP9002  adapters.   If  the device name is not listed you
     will you will need to EXAMINE the BusArrayEntry entry to  tell
     whether the Adapter is an LP8000, LP9002 or an earlier type of
     adapter.  Following is an example of the EXAMINE command:

     SDA> EXAMINE FFFFFFFF.810FBC40
     FFFFFFFF.810FBC40:  F80010DF.F80010DF   "...."
     SDA> EXAMINE FFFFFFFF.810FBC78
     FFFFFFFF.810FBC78:  F90010DF.F90010DF   "...."

     The field F80010DF.F80010DF  shows  that  the  adapter  is  an
     LP8000 adapter.

     The field F90010DF.F90010DF  shows  that  the  adapter  is  an
     LP9002 adapter.

NEW FUNCTIONALITY INTRODUCED IN VMS73_FIBRE_SCSI-V0100 KIT:

  o  This kit provides support for  the  KZPEA-DB  Ultra  160  SCSI
     Storage Adapter.

     The Compaq KZPEA-DB SCSI Storage Adapter is a high-performance
     dual  channel Ultra 160 SCSI adapter that connects external or
     internal SCSI  storage  devices  to  a  PCI-based  host  Alpha
     system.   The  module provides multimode SCSI support for both
     Single-Ended (SE) and  Low  Voltage  Differential  (LVD)  SCSI
     peripherals in a 33/66 Mhz PCI slot.

     The KZPEA adapter has the following features:

         o  Provides full-featured dual-channel Ultra  160  SCSI  host
            adapter with a 66/33 Mhz 64-bit PCI interface.

         o  Supports Ultra160 data transfer rates up to 160 MB/sec  on
            the 16-bit SCSI bus using LVD SCSI peripherals.

         o  Supports  mixed  SCSI-2,   Ultra2,   and   Ultra160   SCSI
            peripherals on Compaq Storageworks enclosures.

         o  Supports hot-swapping/hot-adding of SCSI peripherals.

         Images Affected:  [SYS$LDR]SYS$PKADRIVER.EXE

PROBLEMS ADDRESSED IN VMS73_FIBRE_SCSI-V0200 KIT:

  o  For 8MM tapes only (eg.  Exabyte, TZK15), a COPY command to  a
     freshly  initialized  tape  results  in  a  fatal  drive error
     whenever the COPY command is issued on a  TMSCP  client  node.
     The  error  log shows that an Illegal Request has been sent to
     the drive.

          Images Affected:  [SYS$LDR]SYS$MKDRIVER.EXE


  o  INCONSTATE crash @SYS$PGADRIVER+AB78.  See crash dump  summary
     below.

     Crashdump Summary Information:
     ------------------------------
     Bugcheck Type:     INCONSTATE, Inconsistent I/O data base
     Current Process:   NULL
     Current Image:     
     Failing PC:        FFFFFFFF.AA7D2B78    SYS$PGADRIVER+0AB78
     Failing PS:        28000000.00000804
     Module:            SYS$PGADRIVER    (Link Date/Time:
                        4-MAY-2001 13:43:31.82)
     Offset:            0000AB78

          Images Affected:  [SYS$LDR]SYS$FGEDRIVER.EXE
                            [SYS$LDR]SYS$PGADRIVER.EXE


PROBLEMS ADDRESSED IN VMS73_FIBRE_SCSI-V0100 KIT:

  o  The system can hang due  to  IO's  Timing  Out,  and  the
     driver  not re-trying the IO command.  The IO timeout can
     be detected      through the error log.

         Images Affected:  [SYS$LDR]SYS$PKADRIVER.EXE

  o  The KZPEA SCSI adapter is  seen  as  a  disk  and  not  a
     device.

         Images Affected:  [SYS$LDR]SYS$PKADRIVER.EXE

  o  When an HSZ/HSG device reports mirror copy status events,
     the  ERRCNT of the device is incremented.  This gives the
     false  impression  that  there  is  a  problem  with  the
     device(s).

         Images Affected:  [SYS$LDR]SYS$DKDRIVER.EXE


  o  MountVerifyTimeouts do resets during heavy IO's.

         Images Affected:  [SYS$LDR]SYS$PKADRIVER.EXE

  o  Add device recognition for the 7892 SCSI Adapter.

         Images Affected:  [SYS$LDR]SYS$PKADRIVER.EXE

  o  Exception conditions, such as those resulting from  power
     surges,  disk  errors  or AUTOGEN operations, can produce
     hangs, crashes or data corruption in an SMP environment.

         Images Affected:  [SYS$LDR]SYS$PKWDRIVER.EXE


  o  Tape drive performance  degrades  significantly  after  a
     tape error.

         Images Affected:  [SYS$LDR]SYS$MKDRIVER.EXE


  o  Odd byte records read from tape to a memory buffer larger
     than the tape record results in one extra byte of data.

         Images Affected:  [SYS$LDR]SYS$PKWDRIVER.EXE


  o  Performance degrades after a bus reset.

         Images Affected:  [SYS$LDR]SYS$PKADRIVER.EXE


  o  A Target negotiates a speed it can't support.

         Images Affected:  [SYS$LDR]SYS$PKADRIVER.EXE


  o  The Emulex FibreChannel adapters support a feature called
     Interrupt  &  Response Coalescing which can significantly
     reduce  the  number  of  host  interrupts   the   adapter
     generates.  To enable this feature the driver must pass a
     response count and a delay in milliseconds to the adapter
     when  it  configures  the FibreChannel link.  This causes
     the adapter to defer interrupting the host until  it  has
     accumulated  the  requested  number of responses or until
     the specified amount of time has passed, whichever occurs
     first.   The feature has the added benefit of making each
     interrupt more cost-effective by driving up  the  average
     number of responses processed for each one.

     This kit adds SYS$ETC:FC$CP.EXE, an application  which  a
     privileged  user  can  run to enable Interrupt & Response
     Coalescing, and a $QIO API to SYS$FGEDRIVER to handle the
     $QIO request.

         Images Affected:  [SYS$LDR]SYS$FGEDRIVER.EXE

  o  An f$getdvi ("tape","mt3_density") command does not  show
     compaction correctly.

         Images Affected:  [SYS$LDR]SYS$MKDRIVER.EXE


  o  If a disk is mounted software write protected,  when  the
     disk enters and completes mount verification, the disk is
     software write enabled.

         Images Affected:  [SYS$LDR]SYS$DKDRIVER.EXE


  o  KZPEA takes too long to reconfigure hot-swapped disks

         Images Affected:  [SYS$LDR]SYS$PKADRIVER.EXE


  o  A system can experience CPUSPINWAIT Crashes.   See  Crash
     dump summary below.

         Crashdump Summary Information:
         ------------------------------
         Bugcheck Type:     CPUSPINWAIT, CPU spinwait timer
                            expired
         Current Process:   NULL
         Current Image:     
         Failing PC:        FFFFFFFF.80088384    SMP$TIMEOUT_C+00064
         Failing PS:        18000000.00000804
         Module:            SYSTEM_SYNCHRONIZATION_MIN    
                            (Link Date/Time: 26-MAY-2001 22 :21:11.81)
         Offset:            00000384

         Images Affected:  [SYS$LDR]SYS$PKQDRIVER.EXE


PROBLEMS ADDRESSED IN VMS73_IPC-V0100 KIT:

  o  A system can crash with an "INCONSTATE, Inconsistent I/O  data
     base"  bugcheck  when  another  node  is rejoining the cluster
     after rebooting, and the ACCEPT fails.

     Crashdump Summary Information:
     ------------------------------
     Bugcheck Type:     INCONSTATE, Inconsistent I/O data base
     Current Process:   NULL
     Current Image:     
     Failing PC:        FFFFFFFF.83350640   SYS$IPC_SERVICES+48640
     Failing PS:        1C000000.00000804
     Module:            SYS$IPC_SERVICES
                        (Link Date/Time: 19-MAY-2001 01:30:51.36)
     Offset:            00048640

          Images Affected:  [SYS$LDR]SYS$IPC_SERVICES.EXE


  o  When processes are communicating via ICC, if process  resource
     wait  is  enabledand the transmitter gets too far ahead of the
     receiver, then the transmitting process goes into MUTEX  wait.
     This  is  expected as the BYTLIM quota is exhausted.  However,
     the transmitter processes hangs  in  MUTEX  wait  waiting  for
     BYTCNT/BYTLM to be returned.

          Images Affected:  [SYS$LDR]SYS$IPC_SERVICES.EXE


  o  A system crash due to a KRNLSTAKNV bugcheck  can  occur.   The
     crash  is  caused  by fork queue corruption.  In order for the
     corruption to occur, all of the following must be true:

           -  Multinet is running

           -  IPC is using the CI

           -  The CI is not running on the primary CPU

           -  There is heavy Multinet  and  IPC  activity,  pushing  the
              timing of fork queue access for both


          Images Affected:  [SYS$LDR]SYS$IPC_SERVICES.EXE
                            [SYSEXE]IPCDEF.STB


PROBLEMS ADDRESSED IN VMS73_LAN-V0200 KIT:

  o  A scatter/gather mapping error can occur.  This is seen  as  a
     machine check bythe system followed by a system crash.

     Crash Dump Summary
     ------------------
     Bugcheck Type:     MACHINECHK, Machine check while in 
                        kernel mode
     Current Process:
     Current Image:     $82$DUA51:[CTM$TMROOT.][CTM_BYTEM]
                        CTM_BYTEM_ALPHA_32.EXE;2
     Failing PC:        FFFFFFFF.80014688
                        EXE$SYSTEM_CORRECTED_ERROR_C+004F8
     Failing PS:        00000000.00001F04
     Module:            SYS$CPU_ROUTINES_2608 (Link Date/Time:
                        17-MAR-2001 03:15:10.47)
     Offset:            00006688

          Images Affected:  [SYS$LDR]SYS$EIDRIVER.EXE


  o  Under the following conditions, the Etherworks  port  will  be
     set  to  100mbs/half-duplex  mode  when  it  should  be set to
     full-duplex mode.

       1.  An XP1000 system  is  connected  to  a  Etherworks  10/100
           switch with a console setting of EIA0_MODE FASTFD

       2.  The Etherworks port is set to Auto-Negotiate.

       3.  OpenVMS is  booted  and  the  Etherworks  switch  is  then
           powered OFF and then ON.

          Images Affected:  [SYS$LDR]SYS$EIDRIVER.EXE


  o  When a DE500 on a satellite  server  node,  which  is  set  to
     auto-negotiate,   is   connected   point-to-point  to  another
     satellite node which is also set to  auto-negotiate,  the  two
     nodes  will  not  synchronize speed/duplex correctly such that
     they cannot complete the  loading  of  OpenVMS  off  a  served
     system disk.

          Images Affected:  [SYS$LDR]SYS$EWDRIVER.EXE
                            [SYS$LDR]SYS$EWDRIVER_DE500BA.EXE


  o  A DE602 installed in an ES40, and configured via  the  console
     as  half-duplex  mode,  will  put  an  Ethernet switch in full
     duplex mode when the switch is  configured  in  auto-negotiate
     mode.

          Images Affected:  [SYSEXE]APB.EXE
                            [SYS$LDR]NET$CSMACD.EXE
                            [SYS$LDR]NET$FDDI.EXE
                            [SYS$LDR]SYS$ECDRIVER.EXE
                            [SYS$LDR]SYS$EIDRIVER.EXE
                            [SYSEXE]SYS$ERBTDRIVER.EXE
                            [SYS$LDR]SYS$ESDRIVER.EXE
                            [SYS$LDR]SYS$EWDRIVER.EXE
                            [SYSEXE]SYS$EWBTDRIVER.EXE
                            [SYS$LDR]SYS$EWDRIVER_DE500BA.EXE
                            [SYS$LDR]SYS$EW1000A.EXE


  o  A system can crash with an INVEXCEPTN, Exception  while  above
     ASTDEL bugcheck after the user issues an NCL SHOW FDDI STATION
     * ALL command.

     Crashdump Summary Information:
     ------------------------------
     Bugcheck Type:     INVEXCEPTN, Exception while above ASTDEL
     Current Process:   SCHED#_563
     Current Image:     DSA2000:[SYS3.SYSCOMMON.][SYSEXE]NCL.EXE;1
     Failing PC:        FFFFFFFF.F793B758    NET$FDDI+0D758
     Failing PS:        20000000.00000804
     Module:            NET$FDDI    (Link Date/Time:
                        18-MAY-2000 00:48:44.06)
     Offset:            0000D758

          Images Affected:  [SYS$LDR]NET$FDDI.EXE


PROBLEMS ADDRESSED IN VMS73_LAN-V0100 KIT:

  o  This kit  adds  boot  support  for  the  Titan  chip  set  for
     AlphaServer  ES45  for  Intel  chips 82558/82559, the DE435 to
     DE500 systems and for the DEFPA.

         Images Affected:  [SYSEXE]APB.EXE
                           [SYS$LDR]SYS$EIBTDRIVER.EXE
                           [SYS$LDR]SYS$EWBTDRIVER.EXE
                           [SYS$LDR]SYS$FWBTDRIVER.EXE


  o  VMS support was incomplete for the  XP1000  embedded  Ethernet
     option  when the XP1000 first shipped.  This kit provides that
     support.

         Images Affected:  [SYSEXE]SYS$APB.EXE
                           [SYS$LDR]SYS$ERDRIVER.EXE
                           [SYS$LDR]SYS$EWDRIVER.EXE
                           [SYS$LDR]SYS$EWDRIVER_DE500BA.EXE
                           [SYS$LDR]SYS$ERBTDRIVER.EXE
                           [SYS$LDR]SYS$EWBTDRIVER.EXE


  o  When using the Auto-Negotiate console  setting  on  an  XP1000
     system, Auto-Negotiation is not done.  Instead, after boot the
     device is in 10mb/half-duplex mode.

         Images Affected:  [SYS$LDR]SYS$EWDRIVER_DE5000BA.EXE


  o  Under heavy  receive  load,  particularly  with  many  receive
     overflow  errors  being recorded, the DE600 NIC DMAs a receive
     descriptor  that  contains  a  stale  pointer  (to  the   next
     descriptor)  which  is  a  -1.  Subsequent use of that pointer
     results in a scatter/gather mapping error which is seen  as  a
     machine check and system crash.

     Crash Dump Summary
     -------------------
     Bugcheck Type:     MACHINECHK, Machine check while in kernel mode
     Current Process:
     Current Image:
     $82$DUA51:[CTM$TMROOT.][CTM_BYTEM]CTM_BYTEM_ALPHA_32.EXE;2
     Failing PC:        FFFFFFFF.80014688
                        EXE$SYSTEM_CORRECTED_ERROR_C+004F8
     Failing PS:        00000000.00001F04
     Module:            SYS$CPU_ROUTINES_2608
                        (Link Date/Time: 17-MAR-2001 03:15:10.47)
     Offset:            00006688

         Images Affected:  [SYS$LDR]SYS$EIDRIVER.EXE

  o  When not doing auto-negotiation, but the link partner is, if a
     link bounce is not done, the link partner may not see a change
     in the link status during system boot or a  LANCP  command  to
     change the speed or duplex mode.  If the link partner does not
     see the change, it does not restart  auto-negotiation.   Since
     auto-negotiation  is not being done, the link partner will not
     succeed  in  doing  auto-negotiation,  but  may  do   parallel
     detection  which  will succeed in setting the speed and duplex
     mode correctly.               

     When one  link  partner  is  not  doing  auto-negotiation  and
     another  link  partner  is,  if a link bounce is not done, the
     link partner that is not doing auto-negotiation may not see  a
     change  in  the  link  status  during  system  boot or a LANCP
     command to change the speed  or  duplex  mode.   If  the  link
     partner   does  not  see  the  change,  it  does  not  restart
     auto-negotiation but may do parallel detection  which  may  or
     may not set the speed and duplex mode correctly.

         Images Affected:  [SYS$LDR]SYS$EIDRIVER.EXE


  o  When not doing auto-negotiation, the  PHY  registers  are  not
     written when they should be in all cases.

         Images Affected:  [SYS$LDR]SYS$EIDRIVER.EXE


PROBLEMS ADDRESSED IN VMS73_LINKER-V0200 KIT:

  o  Static PSECTs (Program Sections) with the EGPS$V_ALLOC_64B are
     not  allocated by the linker in the 64-bit address space.  The
     data is put in the 32-bit P0 space instead.

          Images Affected:  [SYSEXE]LINK.EXE


  o  The Linker creates solitary PSECTs in the P2 space by default.
     This  will  break  any  current application that uses solitary
     PSECTs.

          Images Affected:  [SYSEXE]LINK.EXE


  o  After successful compilation, there can be link warnings  with
     unresolved message-numbers:

            %LINK-W-NOMSG, Message number 0064A120
            %LINK-W-NOMSG, Message number 0064A128
            %LINK-W-NOMSG, Message number 0064A130
            %LINK-W-NOMSG, Message number 0064A128


          Images Affected:  [SYSMSG]PRGDEVMSG.EXE


PROBLEMS ADDRESSED IN VMS73_LINKER-V0100 KIT:

  o  LINKER truncates an image IDENT at the 14th character  with  a
     NULL  in  place  of  the 15th character.  This can be observed
     when a user edits  or  searches  the  '.MAP'  in  the  section
     entitled 'Image synopsis for IDENT string' or when dumping the
     .EXE file.


  o  LINKER omits the solitary attribute, and therefore,  fails  to
     create  separate  sections  for solitary .PSECTs.  See example
     below:

               Option file :
               PSECT_ATTR=B_STRUCT,PAGE,SOLITARY
               PSECT_ATTR=A_STRUCT,PAGE

     A_STRUCT        00040000 00044267 00004268 (      17000.) PAGE
     16 NOPIC,OVR,REL,GBL,NOSHR,NOEXE,  WRT,NOVEC,NOMOD
     PSECT    00040000 00044267 00004268 (      17000.) OCTA
     4

     B_STRUCT        00050000 00054267 00004268 (      17000.) PAGE


PROBLEMS ADDRESSED IN VMS73_MAIL-V0100 KIT:

  o  Sending message from VMSMAIL to Exchange, using TCPIP,  merges
     the  TO:   and  CC:   lines into one TO:  line in the received
     message.  See example below:

         MAIL> Send/CC
         To: SMTP%"A.B@C.COM"
         CC: SMTP%"D.E@F.COM"

     The TO: line in Exchange:
         TO: A.B@C.COM,D.E@F.COM


         Images Affected: [SYSEXE]MAIL.EXE
                          [SYSLIB]MAILSHR.EXE


  o  VMS  Mail  does  not  filter  out  the    character  when
     displaying  certain  types  of information.  A user could send
     any type of VT Escape Sequences to another user's terminal and
     change the receiving terminal's behavior.

         Images Affected:  [SYSEXE]MAIL.EXE


  o  A %MAIL-E-ALTPRIJOB error displays without cause.  See example
     below:

         $ MAIL

           MAIL> 22
                 (Message #22 is displayed)

           MAIL> print

           MAIL>  5
                  (Message #5 is displayed)

           MAIL> print/queue=32$lb2a
           %MAIL-E-ALTPRIJOB, error altering parameters of 
           job 505 queue 32$LB2A
           Job MAIL (queue 34$LB4L, entry 505) started on 34$LB4L

           MAIL> exit
           $
               

     The print job is eventually released to the printer,  but  the
     user is not notified.

         Images Affected:  [SYSEXE]MAIL.EXE


PROBLEMS ADDRESSED IN VMS73_MOUNT96-V0100 KIT:

  o  Roxio CD Creator V5.0 for PCs  creates  a  disk  that  is  not
     compliant  to  the  ISO  standard.   Attempting to mount these
     disks on an OpenVMS system  will  crash  the  system  with  an
     SSRVEXCEPT, Unexpected system service exception bugcheck.

     Crash Dump Summary
     ------------------
     Bugcheck Type:     SSRVEXCEPT,
                        Unexpected system service exception
     Current Process:   DKA400CACP
     Current Image:     $82$DKA0:[SYS0.SYSCOMMON.]
                        [SYSEXE]F11CACP.EXE
     Failing PC:        FFFFFFFF.800ACD10    EXE$QIO_C+00170
     Failing PS:        30000000.00000001
     Module:            IO_ROUTINES    (Link Date/Time:
                                        29-MAR-2000 00:52:23.33)
     Offset:            0001AD10

          Images Affected:  [SYSLIB]MOUNTSHR.EXE
                            [SYSEXE]VMOUNT.EXE


  o  When adding a shadow set member with  /POLICY=MINICOPY  fails,
     the error message output is:

       -SYSTEM-F-INCSHAMEM, incompatible shadow set member
             
     This error message has been changed to  the  more  descriptive
     message:

       -MOUNT-F-REQ_WBM_FAIL, unable to add member using minicopy

          Images Affected:  [SYSLIB]MOUNTSHR.EXE
                            [SYSEXE]VMOUNT.EXE


  o  A SET VOLUME/REBUILD command on a volume set may not reset the
     volume  write  count  to  the correct number of writers in the
     cluster.  This can occur when a node that had the  volume  set
     mounted  did  not update the volume write count on dismount or
     on a crash.  A SHOW DEVICE/REBUILD command always  shows  this
     volume  as needing a rebuild.  Even a SET VOLUME/REBUILD=FORCE
     command will not clear this rebuild status.

     Note: To receive this complete change you must also install
           the VMS721_CLIUTL-V0200 ECO kit.

          Images Affected: [SYSLIB]MOUNTSHR.EXE


  o  The following problems are corrected:

      -  A MOUNT/NOWRITE command on a disk on one cluster will  now
         work  correctly, even if the disk is mounted with a /WRITE
         qualifier on another cluster  in  the  SAN  (Storage  Area
         Network).  Previously, depending on the order in which the
         mount commands were executed, the mount  would  fail  with
         the error message:

         DIFVOLMNT - different volume already mounted on this
                     device.
 
      -  If a disk is  mounted  with  a  /WRITE  qualifier  on  one
         cluster and a /NOWRITE qualifier on another cluster in the
         SAN, mount  verification  will  fail  with  a  WrongVolume
         status  error  on  the  system  which had the disk mounted
         /NOWRITE.   This  change  allows  mount  verification   to
         complete successfully in this configuration.


     Note: To receive this complete correction you must also install
           the VMS721_SYS-V1100 and VMS721_FIBRE_SCSI-V0500 ECO
           kits.        

          Images Affected:  [SYSLIB]MOUNTSHR.EXE
                            [SYSEXE]VMOUNT.EXE


  o  Read failures  during  a  disk  mount  that  were  due  to  an
     inability to read the home block and failures that were due to
     transient errors, such as from  a  path  switch  or  SCSI  bus
     reset, were following the same failure path.  That is, reading
     the alternate home block and if successful, mounting the  disk
     as  read  only.   However,  failures  due  to transient errors
     should not read the alternate home block and should mount  the
     disk as READ/WRITE.

     For transient error failures, this change will now  cause  the
     READ  to  be  re-tried  for 30 seconds (30 re-tries at one per
     second).  If the READ succeeds, the disk will  be  mounted  as
     READ/WRITE.

          Images Affected:  [SYSEXE]VMOUNT.EXE
                            [SYSLIB]MOUNTSHR.EXE


PROBLEMS ADDRESSED IN VMS73_PTHREAD-V0100 KIT:

  o  The threads  library  provides  a  number  of  synchronization
     mechanisms,  one  of  which is readers-writer locks (rwlocks).
     An rwlock may be locked for read, or may be locked for  write.
     A common unlock API is provided.

     In a customer-written exit handler, applications which attempt
     to unlock a write-locked rwlock (presumably after first having
     locked it for write), will  mistakenly  fail  with  the  EPERM
     status return, in images configured with upcalls enabled.

     If a customer does not use exit handlers, this is  irrelevant.
     If they don't use rwlocks, this is irrelevant.  If they do use
     rwlocks in an exit handler, but  have  upcalls  disabled  (the
     default), this is irrelevant.  But if they use rwlocks in exit
     handlers with upcalls enabled, this fix is necessary.  Without
     the  fix,  unlock attempts of a write-locked rwlock in an exit
     handler will fail, leaving the rwlock locked for write.   This
     could  lead  to application deadlocks when subsequently trying
     to operate on the rwlock.

          Images Affected:  [SYSLIB]PTHREAD$RTL.EXE


  o  Threaded applications that  use  mutexes  and  ASTs  and  have
     upcalls enabled may experience the following problems:

        -  a DECthreads bugcheck involving a lock problem, or

        -  an ACCVIO from within  the  threads  library,  referencing
           virtual address xD0.


          Images Affected:  [SYSLIB]PTHREAD$DBGSHR.EXE
                            [SYSLIB]PTHREAD$RTL.EXE


PROBLEMS ADDRESSED IN VMS73_RMS-V0200 KIT:

  o  Fix to increase the directory path cache size  to  accommodate
     larger directories.

     A threaded process may deplete the RMS  directory  path  cache
     when  multiple  process  threads  are  performing simultaneous
     directory lookups.  This can result in  a  race  condition  in
     which  the  threads  end  up in an infinite loop attempting to
     traverse their respective  paths  while  the  cache  is  being
     frequently  flushed.   This  problem  is  aggravated  when the
     directory paths contain long  names  and/or  deep  structures.
     The  directory  path  cache size has been increased to prevent
     this behavior.

          Images Affected:  [SYS$LDR]RMS.EXE


  o  Fix to increase the size of RMS's internal ASB stack.

     RMS's internal ASB stack boundaries may  be  exceeded  due  to
     unanticipated  third  party  EXEC mode activity such as an AST
     delivery  while  RMS  is  operating  on  its  internal  stack.
     Because  the  stack was initially sized for exclusive RMS use,
     the stack  limits  can  overflow  causing  adjacent  RMS  data
     structures  to  become  corrupted.  This can result in various
     aberrant RMS conditions including non-fatal EXEC  mode  System
     Service Exceptions.

          Images Affected:  [SYS$LDR]RMS.EXE


  o  Fix to prevent EXEC mode hangs with EXEC ASTs disabled.

     Under rare circumstances, non-atomic access to an RMS  process
     global data cell could result in status bits being lost during
     concurrent cell access.  A status bit to indicate whether  RMS
     currently  has  ASTs  disabled  could inadvertently be cleared
     through this access resulting in an infinite hang  within  RMS
     waiting for an AST delivery, but with EXEC mode ASTs disabled.
     Atomic access to this cell prevents this from occurring.

          Images Affected:  [SYS$LDR]RMS.EXE


  o  RMS RU journaling  fix  for  an  update  window  when  a  SIDR
     (secondary  index  data  record)  marked  as  RU-DELETE may be
     inappropriately re-marked as deleted while the SIDR  is  still
     part  of  an  active  recovery unit.  If this transaction were
     aborted, this could result in  the  new  secondary  key  value
     being retained in the primary data record.

          Images Affected:  [SYS$LDR]RMS.EXE


  o  Fixes for problems associated with deleting an accessor  of  a
     file with global buffers enabled.

     The probability of these problems occurring increases not only
     with  processes  deleted with a $delprc or stop/id but also if
     they are also accessing a  file  that  is  opened  and  closed
     constantly for only one operation, with brief windows when the

     file has only one accessor (for example, SYSUAF.DAT).

       -  Process hang waiting for exclusive global section  process
          lock  if same file is opened more than once and process is
          deleted during a $connect to  the  same  file  before  the
          section  is  completely initialized.  This could leave one
          stream still holding the exclusive lock when  the  process
          is terminated.

       -  Fatal accvio.  The last accessor of the file  is  deleted,
          and  during  the abort rundown a new process is waiting to
          connect to the global section when the global section lock
          is  released  by  the  last  accessor.  Because the global
          section is a temporary section and doesn't get marked  for
          delete,  there  is  the  possibility  of  a lag before the
          section is deleted by the system.  There was  a  potential
          race  condition  when the new connect might map to the old
          global section before it was deleted.  This  could  result
          in  the  new  mapper  using  some  stale (no longer valid)
          pointers in the old section.


          Images Affected:  [SYS$LDR]RMS.EXE
                            [SYS$LDR]DDIF$RMS_EXTENSION.EXE
                            [SYSLIB]SDARMS$SHARE.EXE
                            [SYS$LDR]RMSDEF.STB


  o  Enhance minimum process quotas that the RMSREC_SERVER detached
     process  is  created with.  This server is dedicated to RMS RU
     journaling detached recovery.

     ENQLM  and  PGFLQUOTA  are  the  process  quotas   that   some
     applications  have  found it necessary to override the minimum
     on their  system  or  cluster  by  increasing  the  associated
     PQL_Mxxxx  sysgen  parameter (e.g.  PQL_MENQLM).  The defaults
     for these quotas are now 1 million for ENQLM and 100  thousand
     for  PGFLQUOTA.  The enhancement also sets WSEXTENT at runtime
     to the WSMAX sysgen parameter.

          Images Affected:  [SYS$LDR]RMS.EXE

  o  Rollback of a remote file transfer change made in V7.2 to  its
     day  1  behavior in order to restore prior performance metrics
     for remote file transfers that request file transfer  mode  by
     setting  the  SQO  (FAB$L_FOP) option.  The change was made to
     ignore the file transfer mode (FTM) request if the remote file
     was write shared.

     This has led to a  number  of  reports  of  applications  that
     previously  had  SQO  specified  for  remote  files  that  are
     experiencing significant  performance  degradations  in  their
     remote  applications  with  the V7.2 family and V7.3.  We have
     reviewed the previous behavior  for  file  transfer  mode  and
     found   that   while   there  is  the  appearance  of  locking
     inconsistencies for readers when FTM  is  used,  there  is  no
     potential  for  data  corruption.  We have concluded that when
     users set the FTM (SQO) option,  they  are  in  effect  giving
     permission  for  the  same kind of inconsistencies that a user
     allows when the read-regardless (RRL) option is set.

     This change  restores  the  pre-V7.2  behavior  for  the  file
     transfer  mode for remote files.  If SQO is set, file transfer
     mode will be used regardless of the sharing specified for  the
     remote  file.   Users  should  expect  to see the same kind of
     inconsistencies  in  reading  data  as  they  see   when   the
     read-regardless (RRL) option is set.  The SQO option should be
     disabled if this is not acceptable for some  application.   In

     addition,  to  avoid  the  possibility  of  a hang that may be
     induced by retrying remote accesses after a record lock error,
     users  should  consider  setting  both  the  no-lock (NLK) and
     read-regardless (RRL) options in the RAB$L_ROP in applications
     that  use  the file transfer mode (SQO) option for remote file
     accesses.  (Note:  The  new  NQL  (no  query  locking)  option
     introduced  in  V7.2-1H1  is not supported by the DAP protocol
     for remote files.)

     An application should  continue  to  work  with  the  restored
     behavior  without  a new change even if a change has been made
     to an existing application to restore the file  transfer  mode
     behavior  since the SQO fix was made in V7.2 (e.g., adding the
     UPI sharing option).

     There is just one potential problem that we need to point out.
     For new applications designed and implemented in V7.2 or later
     that may allow remote accesses to  write  shared  files,  they
     should  check  whether  SQO (FAB$L_FOP) is enabled.  Currently
     the SQO option is being ignored (unless the UPI sharing option
     is  specified),  and  the file transfer mode is not being used
     for any remote accesses.  With the  restore  of  pre-V7.2  SQO
     behavior,  it will start being used and so the behavior of the
     application could change.  Anyone with a new application  that
     has  SQO  set  and the possibility of write shared files being
     remotely accessed by the application should  consider  whether
     the SQO option needs to be disabled.

           Images Affected:  [SYS$LDR]RMS.EXE

  o  Fix to prevent an infinite loop in SDA's SHOW PROCESS/RMS.

     Under rare circumstances, a high  priority  process  utilizing
     the  online System Dump Analyzer (ANALYZE/SYSTEM) to examine a
     low priority process's RMS attributes (SHOW  PROCESS/RMS)  may
     enter  an  infinite  loop.   Since  the  process  is  at  high
     priority, it may have an adverse impact on other processes  on
     the system.

           Images Affected: [SYSLIB]SDARMS$SHARE.EXE


  o  Fix for a user-mode accvio when converting a  sequential  file
     when  the  maximum  record  size  (MRS)  in its file header is
     inappropriately set to zero.

          Images Affected:  [SYSLIB]CONVSHR.EXE
                            [SYSEXE]CONVERT.EXE


PROBLEMS ADDRESSED IN VMS73_RMS-V0100 KIT: 

  o  Fix for potential RMS lock hang with global buffers caused  by
     process deletion (e.g.  STOP/ID).

     This problem involves a race condition that  may  occur  if  a
     process  is interrupted by an abort rundown when it is stalled
     waiting for the convert of a system NL lock  to  a  system  CR
     lock to be granted for a global buffer.  This can result in EX
     lock requests being blocked by an unreleased CR lock.

         Images Affected:  [SYS$LDR]RMS.EXE


  o  Fix for sequential file  corruption  with  global  buffers  in
     cluster.

     The corruption footprint is a  gap  left  by  a  missing  data
     record.   The  gap  contains  a  record's worth of either null
     bytes or residual data in the global buffer  from  some  prior
     use.

     The following conditions are necessary  for  this  problem  to
     occur:

       o  The file must be a sequential file.

       o  The sequential file must have global buffers enabled.

       o  The sequential file must be written to (records  appended)
          simultaneously  from 2 or more nodes in a cluster.  If all
          accesses are from one node, the corruption will not occur.

         Images Affected:  [SYS$LDR]RMS.EXE


  o  Fix to prevent a non-fatal SSRVEXCEPT bugcheck when a wildcard
     network copy completes.

     Attempts to perform wild card file copy operations across  the
     network  may  fail  with  a non-fatal SSRVEXCEPT bugcheck upon
     completion when a  third  party  event  notification  software
     package  is  installed.   Stale information contained within a
     recycled DAP message buffer could cause an invalid path to  be
     executed  during  the  implicit  $DISPLAY of a file during RMS
     rundown.

         Images Affected:  [SYS$LDR]RMS.EXE


  o  Fix to prevent accvio when repeated calls are made to  CONVERT
     utility callable interface.

     When making repeated calls to  the  CONVERT  utility  callable
     interface  from within a user application, an access violation
     or  various  sort  errors  may  be  returned.   The  following
     conditions must exist for this error to occur:

        o  An application  must  be  making  repeated  calls  to  the
           callable CONVERT interface.

        o  The current file being converted must  have  more  than  3
           keys.

        o  At least one of the previously converted files  must  have
           had all compressions disabled.

        o  The  current  file  being   converted   must   have   some
           compression enabled.

         Images Affected:  [SYSEXE]CONVERT.EXE
                           [SYSLIB]CONVSHR.EXE


  o  Fix for a GEM compiler related build problem.  There  are  two
     ways a user may see the effects of this problem:

        o  ORA-482 crashes on Oracle 8.1.6 OPS.

        o  A process can exit with an unhandled exception with the PC
           in SYS$PUT.

     A fix to the GEM compiler is included in OpenVMS Alpha V7.3.

         Images Affected:  [SYS$LDR]RMS.EXE


PROBLEMS ADDRESSED IN VMS73_SHADOWING-V0100 KIT

  o  If System Check is enabled, the first  MOUNT  will  crash  the
     system with a SHADDETINCON bugcheck.

     Crash Information:
     ------------------
     Bugcheck Type:     SHADDETINCON, SHADOWING detects inconsistent 
                        state
     Current Process:   NULL
     Current Image:     
     Failing PC:        FFFFFFFF.8BF41A4C    SYS$SHDRIVER+27A4C
     Failing PS:        24000000.00000804
     Module:            SYS$SHDRIVER    (Link Date/Time:  
                                         3-APR-2001 19:02:11.75)
     Offset:            00027A4C        

        Images Affected:  [SYS$LDR]SYS$SHDRIVER.EXE
                          [SYSEXE]SHADOW_SERVER.EXE


  o  If SYSGEN SYSTEM_CHECK is enabled, the first MOUNT of a system
     disk will crash the system.

        Images Affected:  [SYS$LDR]SYS$SHDRIVER.EXE
                          [SYSEXE]SHADOW_SERVER.EXE

PROBLEMS ADDRESSED IN VMS73_SYS-V0200 KIT:

  o  On a pre-EV56 machine,  STB  R31,xxx(Ry)  sometimes  stores  a
     value  other  than  0.   The  manifestation  of this is that a
     program operates correctly on an EV56 processor, but fails  on
     an EV5 or earlier processor.  The failure depends on the exact
     nature of the program.  It will happen only if some modules in
     the  program were compiled with the /ARCHITECTURE= switch, and
     the processor specified by this switch was EV56 or later.  You
     will usually see a message like:

     %SYSTEM-I-EMULATED, an instruction not implemented on this
     processor was emulated at PC=xxxxx, PS=yyyy

     This message does not mean the problem has occurred,  it  just
     means that some of the conditions are right for it to occur.

         Images Affected: [SYS$LDR]EXCEPTION.EXE
                          [SYS$LDR]EXCEPTION.STB
                          [SYS$LDR]EXCEPTION_MON.EXE
                          [SYS$LDR]EXCEPTION_MON.STB

  o  A system  can  crash  with  a  SSRVEXCEPT,  Unexpected  system
     service exception bugcheck at LOCKING+019CC.

     Crashdump Summary Information:
     ------------------------------
     Bugcheck Type:     SSRVEXCEPT, Unexpected system service exception
     Current Process:   BATCH_3084
     Current Image:     DSA509:[SSEXE.DP]SPCUSERMAINT.EXE;44
     Failing PC:        FFFFFFFF.801619CC    LOCKING+019CC
     Failing PS:        38000000.00000203
     Module:            LOCKING    (Link Date/Time:
                                   29-MAR-2000 00:58:34.67)
     Offset:            000019CC


         Images Affected:  [SYS$LDR]LOCKING.EXE
                           [SYS$LDR]LOCKING.STB

  o  There is no display  of  the  bugcheck  information  during  a
     system crash.

         Images Affected:  [SYS$LDR]EXCEPTION.EXE
                           [SYS$LDR]EXCEPTION.STB
                           [SYS$LDR]EXCEPTION_MON.EXE
                           [SYS$LDR]EXCEPTION_MON.STB

  o  The cluster server Process can hang in a MUTEX wait state.

         Images Affected: [SYS$LDR]PROCESS_MANAGEMENT.EXE
                          [SYS$LDR]PROCESS_MANAGEMENT.STB
                          [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE
                          [SYS$LDR]PROCESS_MANAGEMENT.STB

  o  The user stack can become corrupt through  repeated  issuances
     of  the  DEBUG  command.   The  following sequence of commands
     illustrates the problem:

              LINK/DEBUG FOO (where FOO simply executes an infinite loop)
              $RUN FOO
              DBG> go
              Hit CTRL/Y
              $DEBUG
              DBG> go
              Hit CTRL/Y
              $DEBUG
          %DEBUG-I-TRUNC64, address 0000000200000000 being truncated in
          DBGKREGISTERS\DBG$
          GET_PD_FROM_FP
          %DEBUG-I-TRUNC64, address 0000000200000000 being truncated in
          DBGKREGISTERS\DBG$
          GET_PD_FROM_FP
          DBG> g
          %DEBUG-I-BADSTACKPATCH1, Corrupt stack detected...attempting
          patch STQ
          R27,(SP)
          %DEBUG-W-NORESUME, unable to resume execution, stack or PC
          corrupted in %PROCESS_NUMBER 1
          DBG>

          The user's stack is now corrupt.

         Images Affected: [SYS$LDR]EXCEPTION.EXE
                          [SYS$LDR]EXCEPTION.STB
                          [SYS$LDR]EXCEPTION_MON.EXE
                          [SYS$LDR]EXCEPTION_MON.STB

PROBLEMS ADDRESSED IN VMS73_SYS-V0100 KIT:

  o  The GETTIMEOFDAY() CRTL function returns an  error  in  ORACLE
     Parallel  Server  Version  8.1.6.   This  can occur in several
     ways:

       -  The GETTIMEOFDAY() function returns status code 103DFE0.

       -  The VMS  user  mode  system  services  returns  unexpected
          status  codes,  including C signal status code, SS$_BREAK,
          SS$_IMGDMP or SS$_DEBUG.

       -  An ORA-7211 Oracle 8.1.6 OPS crash could occur.

       -  A severe performance slowdown on Oracle 8.1.6 or 8.1.7 OPS
          could occur.

       -  Oracle 8.1.6 or 8.1.7 OPS might hang.


            Images Affected:  [SYS$LDR]EXCEPTION.EXE
                              [SYS$LDR]EXCEPTION.STB
                              [SYS$LDR]EXCEPTION_MON.EXE
                              [SYS$LDR]EXCEPTION_MON.STB

  o  The  kill()  sys$sigprc  CRTL  functions  return   the   error
     SS$_SUSPENDED  when  the  process  is  neither  suspended  nor
     waiting on a resource.  The processes is simply waiting  on  a
     mutex  or  is  in  the  transient  RWSCS state.  This leads to
     ORA-482 crashes on Oracle 8.1.6 or 8.1.7 OPS could also occur.

            Images Affected:  [SYS$LDR]PROCESS_MANAGEMENT.EXE
                              [SYS$LDR]PROCESS_MANAGEMENT.STB
                              [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE
                              [SYS$LDR]PROCESS_MANAGEMENT_MON.STB

  o  There are several user visible ways this bug can be seen:

      1.  A process ACCVIO's near the symbol exe$altnumtim

      2.  ORA-482 crashes on Oracle 8.1.6 OPS.

      3.  An Oracle process exits with the status code 0C, which  is
          an   ACCVIO.   Since  Oracle  processes  run  as  detached
          processes,  you  would  see  this  status  code   in   the
          accounting log.

           Images Affected:  [SYS$LDR]MESSAGE_ROUTINES.EXE
                             [SYS$LDR]MESSAGE_ROUTINES.STB

PROBLEMS ADDRESSED IN VMS73_SYSBOOT-V0100 KIT:

  o  While booting with greater than 16GB on  an  ES40,  GS140,  or
     other system with a V5 style configuration tree, SYSBOOT fails
     with the following message:

     %SYSBOOT-F-PFNALLOC, slice allocation for PFN DB failed,
     status = 00002334

          Images Affected:  [SYSEXE]SYSBOOT.EXE


PROBLEMS ADDRESSED IN VMS73_SYSLOA-V0100 KIT:

  o  Audit data for non-trusted processes is not captured.

          Images Affected:  [SYS$LDR]SYS$CLUSTER.EXE


  o  Prevent spurious cluster connection failures between nodes.

          Images Affected:  [SYS$LDR]SYS$CLUSTER.EXE

  o  An INVEXCPTN bugcheck occurs when  a  re-init  of  the  RESEND
     queue fails.

          Images Affected:  [SYS$LDR]SYS$CLUSTER.EXE

  o  Changes were made to further reduce SCHED spinlock contention.
     These changes result in system performance improvements.

          Images Affected:  [SYS$LDR]LOCKING.EXE
                            [SYS$LDR]LOCKING.STB
                            [SYS$LDR]SYS$CLUSTER.EXE

INSTALLATION NOTES:

This kit  requires  a  system  reboot.   Compaq  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.

INSTALLATION INSTRUCTIONS:

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

Special Installation Instructions:

  o  SYSGEN Parameter Changes

     As part of the post installation processing for  the
     VMS73_RMS-V0200 kit, two SYSGEN parameters (PIOPAGES
     and  IMGIOCNT)  will  be  modified   in   order   to
     accommodate changes being made within the RMS image.

     The post installation process will make an effort to
     add appropriate lines to the MODPARAMS.DAT files for
     all system roots found on the installation disk  and
     will   perform  a  SYSGEN  write  current  with  the
     modifications on the system from which this  kit  is
     being  installed.   The  installation  process  will
     provide the status of these changes and any  further
     instructions as necessary.


  o  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

         -  $ DEFINE/SYS NO_ASK$REBOOT TRUE

         -  $ DEFINE/SYS ARCHIVE_DW_MOT_MUP TRUE

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

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

         -  De-assign the logicals assigned

     For example, a sample command file  to  install  the
     VMS73_UPDATE-V0100 kit would be:

          $
          $ DEFINE/SYS NO_ASK$BACKUP TRUE
          $ DEFINE/SYS NO_ASK$REBOOT TRUE
          $ DEFINE/SYS ARCHIVE_DW_MOT_MUP TRUE
          $!
          $ PROD INSTALL VMS73_UPDATE/PROD=DEC/BASE=AXPVMS/VER=V1.0
          $!
          $ DEASSIGN/SYS NO_ASK$BACKUP
          $ DEASSIGN/SYS NO_ASK$REBOOT
          $ DEASSIGN/SYS ARCHIVE_DW_MOT_MUP
          $!
          $ exit


          NOTE:

          This kit includes the VS73_DW_MOT_MUP kit.  Defining
          the  logical  ARCHIVE_DW_MOT_MUP  as TRUE will cause
          the installation procedure to  delete  the  previous
          versions  of  the  DECWindows  files  that  this kit
          installs.  Because of the nature of the problem that
          the   VS73_DW_MOT_MUP-V0100   kit  corrects,  Compaq
          recommends that the old files  be  deleted  and  not
          left  on  the  system.   See  section  11  for  more
          information.

All trademarks are the property of their respective owners.
Files on this server are as follows:
»dec-axpvms-vms73_update-v0100--4.README
»dec-axpvms-vms73_update-v0100--4.CHKSUM
»dec-axpvms-vms73_update-v0100--4.pcsi-dcx_axpexe
»vms73_update-v0100.CVRLET_TXT
privacy statement using this site means you accept its terms