OpenVMS VAXINIT01_070 VAX V5.5-2 - V7.0 INIT$SHR ECO Summary

 
NOTE:  An OpenVMS saveset or PCSI installation file is stored
       on the Internet in a self-expanding compressed file.
       The name of the compressed file will be kit_name-dcx_vaxexe
       for OpenVMS VAX or kit_name-dcx_axpexe for OpenVMS Alpha.
 
       Once the file is copied to your system, it can be expanded
       by typing RUN compressed_file.  The resultant file will
       be the OpenVMS saveset or PCSI installation file which
       can be used to install the ECO.

Copyright (c) Digital Equipment Corporation 1994, 1996. All rights reserved.

PRODUCT:     OpenVMS VAX

COMPONENTS:  INIT$SHR.EXE
             Media Management Extensions (MME)

SOURCE:      Digital Equipment Corporation

ECO INFORMATION:

     ECO Kit Name:  
     ECO Kits Superseded by This ECO Kit:   VAXINIT03_061
                                            VAXINIT02_061    (CSCPAT_1153)
                                            VAXINIT01_U2055  (CSCPAT_1172)
     ECO Kit Approximate Size:  587 Blocks
                    Saveset A -  72 Blocks
                    Saveset B -  90 Blocks
                    Saveset C -  90 Blocks
                    Saveset D - 108 Blocks
                    Saveset E - 108 Blocks
                    Saveset F - 108 Blocks
                 Cover Letter -  11 Blocks
                         Total of 4 files - 360 Blocks

     Kit Applies To:  OpenVMS VAX 5.5-2, V5.5-2H4, V5.5-2HF,
                                  V6.0, V6.1, V6.2, V7.0
     System Reboot Necessary:  No


ECO KIT SUMMARY:

An ECO kit exists for INIT$SHR on OpenVMS VAX V5.5-2 through V7.0.
This kit addresses the following problems:

Problems addressed in the VAXINIT01_070 kit for OpenVMS VAX
  V6.1, V6.2, and V7.0:

  o  A part of the global variable space in the INIT$SHR.EXE image
     is not initialized to zero each time the $INIT_VOL System
     Service is called from a program.  This causes the INIT$SHR.EXE 
     image to remain active.  Therefore, the first call in a series 
     will be correct, but all subsequent calls will pick up values 
     from the first call which can result in disk corruption.

Problems addressed in the VAXINIT03_061 kit for OpenVMS VAX V6.1:

  o   An INIT of a brand new tape can go into an infinite loop. This
      also causes the IO count to steadily increase on some tape
      drives.

      This problem is corrected in OpenVMS VAX V6.2.


Problems addressed in the VAXINIT03_061 kit for OpenVMS VAX V5.5-1,
V5.5-2, V5.5-2H4, V5.5-2HF, V6.0, and V6.1:

  o   When initializing a tape without MME running, if the
      expiration date of the first file on the tape has not been
      reached, and no user over-ride flag is set, INIT will ignore
      this and initialize the tape anyway.
 
      This problem is corrected in OpenVMS VAX V6.2.


  o   The item_list parameter to the $INIT_VOL system service is
      documented as being optional, and if not specified a zero must
      be passed. If a zero is passed, $INIT_VOL returns with an
      ACCVIO status.

      This problem is corrected in OpenVMS VAX V6.2.


Problems addressed in VAXINIT02_061 kit for OpenVMS VAX V6.1:

  o  The VAXINIT01_061 kit checks for the existence of
     SYS$SHARE:MMESHR.EXE and fails the installation if the
     file is found. OpenVMS VAX V6.1 includes the file in
     the B saveset. The VAXINIT01_061 kit installation fails.

     This problem is corrected in OpenVMS VAX V6.2.

Problems addressed in VAXINIT01_061 kit for OpenVMS VAX V6.1:

  o  MME_UCB, used by the Media Management routines to identify
     the device name and context, was not initialized to point
     at the current device UCB.  Therefore, the device name
     returned to the Media Manager is zero.

     This problem is corrected in OpenVMS VAX V6.2.


Problems addressed in VAXINIT01_U2055 kit for OpenVMS VAX V5.5-2:

  o  The command "INITIALIZE/OVERRIDE=ACCESSIBILITY tape: label"
     fails with the error :

          %INIT-F-NORMAL, normal successful completion

     if the user has the VOLPRO privilege enabled.

     This problem is corrected in OpenVMS VAX V6.0.


INSTALLATION NOTES:

The system does not need to be rebooted after this kit is installed.
However, if you have other nodes in your OpenVMS VAXcluster, they
should be rebooted or you should install this kit on each system
in order to make use of the new image(s).

Colorado Site
Georgia Site

vaxinit01_070.README
vaxinit01_070.CHKSUM
vaxinit01_070.CVRLET_TXT
vaxinit01_070.a-dcx_vaxexe
vaxinit01_070.b-dcx_vaxexe
vaxinit01_070.c-dcx_vaxexe
vaxinit01_070.d-dcx_vaxexe
vaxinit01_070.e-dcx_vaxexe
vaxinit01_070.f-dcx_vaxexe