ECO NUMBER: OSMSAE02034 ----------- PRODUCT: Digital Optical Storage Management Software (OSMS) for OpenVMS VAX and Alpha -------- UPDATED PRODUCT: Digital Optical Storage Management Software (OSMS) for OpenVMS VAX and Alpha 3.4 ---------------- APPRX BLCK SIZE: 819 ---------------- DIGITAL Cover Letter for DIGITAL Optical Storage Management Software V3.4-2 (ECO 2) for OpenVMS Alpha V6.2 - V6.2-1H3. ECO Kit OSMSAE02034 Description ------------------------------ Below is the description of the problems corrected by this ECO: o Each locally mounted jukebox volume would be placed in a jukebox drive when any node in the cluster was (re)booted. The environment in which this problem can occur is: o OSMS V3.4 and o an Alpha system attached to a RW5xx Series jukebox that is part of a VMScluster and o the SYSGEN parameter MSCP_LOAD is zero and o the system has any locally mounted jukebox volumes The processing of new I/O requests would be delayed until all of the mounted jukebox volumes had been placed into a jukebox drive. This problem was caused due to the OSMS component, JKDRIVER, incorrectly setting the DEV$V_CLU bit in UCB$L_DEVCHAR2. The setting of this bit told the MSCP server that it needed to ensure the unit characteristics are up to date in the server's UCB. The MSCP server issues I/O to each mounted jukebox volume causing each volume to be placed in a jukebox drive. The setting of the DEV$V_CLU bit in UCB$L_DEVCHAR2 is no longer done by the JKDRIVER. This correction is in JKDRIVER with the image file identification of "4.5-0" or higher. o Each clusterwide mounted jukebox volume would be placed in a jukebox drive when any node in the cluster was (re)booted. The environment in which this problem can occur is: o OSMS V3.4 and o an Alpha system attached to a RW5xx Series jukebox that is part of a VMScluster and o the SYSGEN parameter MSCP_LOAD is one and o the system has any jukebox volumes mounted clusterwide The processing of new I/O requests would be delayed until all of the mounted jukebox volumes had been placed into a jukebox drive when any node in the cluster was (re)booted. The problem was caused by the actions of the MSCP server attempting to ensure the unit characteristics are up to date in the server's UCB. Part of the MSCP servers action in performing this task is an issuing of an IO$_NOP request to each cluster-wide mounted volume. This was causing each clusterwide mounted jukebox volume to be placed in a jukebox drive so the I/O could be serviced. The OSMS component JKDRIVER has been modified to detect these IO$_NOP I/O requests and treat these requests as special I/O. This special processing allows the IO$_NOP requests to be serviced without placing each jukebox volume in a jukebox drive. This correction is in JKDRIVER with the image file identification of "4.5-0" or higher. o System failure due to INVEXCEPTN bugcheck at SMP$ACQUIRE_C+00024. The environment in which this problem can occur is: o OSMS/Alpha version prior to V3.4-2 and o a Alpha system attached to a RW5xx Series jukebox via a host based SCSI adapter, not via an HSC, HSD, or HSJ controller. Multiple jukebox configuration may see this problem more frequently. The problem can cause system operation to fail requiring reboot of operating system and restart of all applications. The problem was caused by a coding error in an error path of the OSMS components WDDRIVER.EXE or RZDRIVER.EXE. The code path is invoked when a SCSI command fails due to device busy status. The specific cause of the error was due to the passing of an empty fork block to KP_STALL_FORK_WAIT macro. The OSMS components WDDRIVER and RZDRIVER have been modified to pass the address of a valid fork block. This correction is in WDDRIVER with the image file identification of "4.6-2" or higher and in the RZDRIVER with the image file identification of "1.1-1" or higher. Installation Overview --------------------- Install this kit with the VMSINSTAL command procedure by logging into SYSTEM account, and typing the following at the DCL prompt: @SYS$UPDATE:VMSINSTAL OSMSAE02034 [location of the saveset] The ECO kit checks to ensure that a valid license is installed before proceeding. If one is not found, the installation aborts. The ECO kit checks to ensure that OSMS V3.4 is installed before proceeding. If OSMS V3.4 is not found, the installation aborts. The ECO kit will allow installation if V3.4 ECO 1 is installed or if individually supplied IPMT solutions for these problems are installed. The installation aborts if the images being modified do not meet these requirements. A system reboot IS necessary before this ECO will take affect. Once the system has been rebooted you can restart the software as described in your existing documentation. _______________________________________________________________________ June 1997 © Perceptics Corporation 1988, 1989, 1990, 1991, 1992, 1993, 1994, 1995 Portions © Digital Equipment Corporation, 1996, 1997. All Rights Reserved. The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document. Possession, use, or copying of the software described in this document is authorized only pursuant to a valid written license from Digital, an authorized sublicensor, or the identified licensor. Digital Equipment Corporation makes no representations that the inter- connection of its products in the manner described in this document will not infringe existing or future patent rights, nor do the descriptions contained in this document imply the granting of licenses to make, use, or sell equipment or software in accordance with the description. The following are trademarks of Digital Equipment Corporation: DEC, DECimage, DECnet, Digital, Files-11, OpenVMS, VAX, VMS, and the DIGITAL logo. The following are third party trademarks: LaserStar, LaserWare, and WORMS-11 are trademarks of Perceptics Corporation. Portions of the Source Code, Object Code, and documentation for this product were developed by Perceptics Corporation. All other trademarks and registered trademarks are the property of their respective holders. Copyright Digital Equipment Corporation 1997. All Rights reserved. This software is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. This ECO has not been through an exhaustive field test process. Due to the experimental stage of this ECO/workaround, Digital makes no representations regarding its use or performance. The customer shall have the sole responsibility for adequate protection and back-up data used in conjunction with this ECO/workaround.