DIGITAL Optical Storage Desktop Software (OSDS) and DIGITAL Optical Storage Management Software (OSMS) for OpenVMS _______________________________________________ Release Notes July 1997 These release notes are common between the Alpha and VAX variants of the DIGITAL Optical Storage Desktop Software and DIGITAL Optical Storage Management Software products. Revision Information: Operating System & Version: OpenVMS/VAX Version 7.1 OpenVMS/Alpha Version 7.1 Revision Information: Software Version: DIGITAL Optical Storage Desktop Software Version 3.4A Optical Storage Management Software Version 3.4A ________________________________________________________________ July 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 interconnection 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. This document was prepared using VAX DOCUMENT Version 2.1. _________________________________________________________________ Contents 1 General....................................... 1 2 Enhancements.................................. 1 2.1 General................................... 1 3 Bug Fixes..................................... 1 4 Known Problems................................ 3 5 Known Limitations-Hardware.................... 4 6 Known Limitations-Software.................... 5 7 Documentation Errata.......................... 7 8 Media for Use in RWZ52........................ 7 9 Media for Use in RWZ53........................ 8 iii 1 General The OSDS and OSMS Version 3.4A products contain references (such as command file names) that use the names LaserWare, LaserStar, and Perceptics. The use of these names in our products should not cause you any concern. HSOF software V2.7J or higher is required for use with optical products connected via an HSD30, HSJ30, or HSJ40 controllers. The Software Product Description (SPD) has been added to the product distribution kit. To extract the SPD (text or postscript) from your distribution kit use one of the following commands: (For OSDS/Alpha text version) $ BACKUP/SELECT=SPD_OSDS.TXT OSDSA0A034.A/SAVE SPD_OSDS.TXT (For OSDS/Alpha postscript version) $ BACKUP/SELECT=SPD_OSDS.PS OSDSA0A034.A/SAVE SPD_OSDS.PS (For OSDS/VAX) $ BACKUP/SELECT=SPD_OSDS.PS OSDSV0A034.A/SAVE SPD_OSDS.PS $ BACKUP/SELECT=SPD_OSDS.TXT OSDSV0A034.A/SAVE SPD_OSDS.TXT (For OSMS/Alpha) $ BACKUP/SELECT=SPD_OSMS.PS OSMSA0A034.A/SAVE SPD_OSMS.PS $ BACKUP/SELECT=SPD_OSMS.TXT OSMSA0A034.A/SAVE SPD_OSMS.TXT (For OSMS/VAX) $ BACKUP/SELECT=SPD_OSMS.PS OSMSV0A034.A/SAVE SPD_OSMS.PS $ BACKUP/SELECT=SPD_OSMS.TXT OSMSV0A034.A/SAVE SPD_OSMS.TXT 2 Enhancements 2.1 General The product has been modified to operate with the OpenVMS V7.1 operating system. The installation procedure and the names of the startup files have been modified slightly, as compared to releases prior to V3.4. Refer to the Installation Guides for OSDS and OSMS for additional information. JKDRIVER: (VAX only) Added a two second delay after loading media into a jukebox drive but before issuing a I/O. This prevents the logging of medium offline errors associated with media loaded into a jukebox drive. 3 Bug Fixes RZDRIVER: (OSMS/Alpha only) 1 Modification to prevent RZ devices from being MSCP served. Correction of a coding error in an error path 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. WDDRIVER: (Alpha only) Modification to prevent RZ devices from being MSCP served. Correction of a coding error in an error path 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. JKDRIVER: (Alpha only) Problem one: The JKDRIVER has been modified to detect 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 changes prevents each clusterwide mounted jukebox volume from being placed in a jukebox drive when any node in the cluster is (re)booted. This 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. Problem two: The setting of the DEV$V_CLU bit in UCB$L_DEVCHAR2 is no longer done by the JKDRIVER. This changes prevents each locally mounted jukebox volume from being placed in a jukebox drive when any node in the cluster is (re)booted. This problem was caused by the 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. 2 This problem was causing the processing of new I/O requests to be delayed until all of the mounted jukebox volumes had been placed into a jukebox drive. For systems with a small number of mounted jukebox volumes this action may not even be noticeable. For system with a large number of mounted jukebox volumes this process could take over two hours. 4 Known Problems You must create or use a WD$STARTUP_PKx.COM file that associates a RZ device with the robotics mechanism. If you use an existing WD$STARTUP.COM file, created by a previous release, that does not create a RZ device then the installation may become trapped in a loop asking you for the RZ device associated with the robotics mechanism. Termination of the install procedure requires the stopping of the process in this event. Volumes created on a drive connected to an HSD or HSJ controller may be configured with a different disk geometry than disk connect via a host interface such as a KZPSA and vice versa. This may lead to problems if the primary home block became unreadable as recovery is based upon the geometry information provided by the controller. No reported cases of this exist but code review shows the possibility that this is a potential problem. Workaround are to do any required recovery efforts using the same controller that created the volumes data set or try the MOUNT qualifier /OVERRIDE=LIMITED_SEARCH. Rewritable disk cannot be initialized for FILES-11[TM] use by issuing multiple calls to the SYS$INIT_VOL system service from a single image. The first call will execute correctly but all other calls will not produce the desired results. The problem is characterized by "MAPAREA, file ('file- id') 'file_name' invalid map area" error message being displayed during an ANALYZE/DISK. The workaround is to use the DCL INIT command or spawn separate processes to make the SYS$INIT_VOL calls for your applications. A coding problem exists between JBUTIL and JBUAPI which can cause a JBU INSERT or JBU REMOVE command to report successful completion when no operation has been performed. Command retry or disabling swapping of media while the JBU INSERT or JBU REMOVE operation is in progress are workarounds. 3 Various condition may lead to the following error statement from the mount utility; "Failed to create or access SECURITY.SYS". The workaround for this type of failure is to use the /OVERRIDE=SECURITY qualifier with the MOUNT command. The JKCONFIG SET command for OD or JB devices that do not exist may cause a system failure. Do not issue this command to devices that do not exist. The JKCONFIG SHOW JUA0 command may cause a system failure. This is an invalid command, as the only valid device designation is a jukebox pseudo-device. The DCL command INIT/ERASE cannot be used to initialize a WORM disk. The command will never complete. If this command did complete the WORM disk would be full of the ERASE data pattern and be useless. Do not issue this command while using WORM disks. Mount operations will fail if the previous dismount was of a WORMS-11[TM] disk that had become full but the WORMS-11 Storage Control Block could not be flushed from the cache file. The workaround for this problem is to use JKCONFIG REMOVE command to break the connection between the OD device or JB devices and the cache file or files, delete the cache file or files, execute the product startup command file, and mount the disk. If the disk to be mounted is the WORMS-11 disk that is full, then this disk may need to be physically write- protected via the tab on the media cartridge before the mount is attempted. The SYSMAN IO CONNECT of RZ or WD devices on non-existent PK devices may cause system failure on ALpha systems. Verify that the PK device associated with the RZ or WD device controller designation has been created before attempting the SYSMAN IO CONNECT command. 5 Known Limitations-Hardware The OSMS/Alpha software will not work correctly with the PB2HA SCSI host controller due to a coding limitation with the WDDRIVER and RZDRIVER. Many variations of problems exist involving the use of the JBUTIL INSERT and JBUTIL REMOVE commands. This host controller is not supported for use with OSDS or OSMS Version 3.4A. 4 OSDS/OSMS Version 3.4A does not support 12-inch WORM products that were supported with prior releases of these products. OSMS Version 3.4A does not support the HSC family of controllers that were supported with a prior release of the product. Customers with such products are recommended to use the Version 3.3-1 release of OSMS. OSMS Version 3.4A was not qualified on a VAX with over 512 MB of memory because no functional changes were made that would affect the execution of the product in this environment. Only configurations consisting of a VAX with over 512 MB of memory and a jukebox connected via an HSD or HSJ can be affected. The HSD and HSJ controllers do not support SCSI Logical Unit Number addressing. This means that the RW551, RW552, and RW557 model jukeboxes cannot be configured using SCSI LUN MODE. When these jukeboxes are connected via HSD or HSJ controllers the jukebox must be set in SCSI ADDRESS MODE. Please note the OSMS installation procedure only allows you to configure these jukeboxes in SCSI ADDRESS MODE when used with HSD or HSJ controllers. When a differential to single-ended SCSI converter (DWZZA- xx) is used within the path from the host to an optical subsystem, it may become necessary to power-cycle the DWZZA-xx to recover from some error conditions. DIGITAL recommends that if you power cycle an optical subsystem connected to a DWZZA-xx as part of a trouble-shooting effort that you power cycle the DWZZA-xx also. 6 Known Limitations-Software The RW531, RW532, RW551, and RW552 are mechanically able to carry two optical cartridges at time in the robotics mechanism. This feature allows these jukeboxes to insert a new cartridge into the drive and to place the cartridge in the drive back into a storage slot as one operation instead of two operations. This "exchange" operation is slightly quicker than two "move" operations. The OSMS software does not use the "exchange" operation, at this time, because the overall improvement impact to system throughput is not sufficient to warrant the risk to data integrity. This feature may be added in the future when the risk to data 5 integrity can be shown to be as good or better than the present implementation using the "move" operations. The OSDS and OSMS for OpenVMS Alpha products do not support the use of WORM media containing the WORMS-11 file structure. WORM media containing the FILES-11 file structure may be used. The implementation of directory management via the WORMS-11 file system has been shown to lose directory entries in very large directory files, those over 4000 blocks. Also the performance of the current implementation is very poor as compared to a similarly populated FILES-11 file system directory for directories over 500 blocks. Users of WORM disk containing the WORMS-11 file structure are advised to define a directory hierarchy that prevents directories from growing larger than 500 blocks. The installation procedure may not correctly identify all of the PK devices on your system. When answering the question regarding which PK device to use, you should choose the PK device that you have configured the optical subsystem with even if it is not listed by the installation procedure. The use of the JBU SET DRIVE 0/OFFLINE command will incorrectly disable swapping of volumes to/from all drives. If want to associate a volume with a drive and prevent it from swapping while allowing other volumes to swap you must use the highest numbered drive. If you wish to do this with more than one volume then you must use the highest numbered drives. Always leave the lowest numbered drives in the online state to allow for normal jukebox swap operation. The following sequence of events may lead to a volume appearing as write-locked when it is not. A write protected volume is dismounted but not removed from a drive in a jukebox. The volume is removed from the jukebox while it is still in the drive. Another volume is inserted into the jukebox using the same JB device designation. A mount attempt is made of this new volume. The workaround to this problem is to always unload write protected disk from a jukebox drive, or to MOUNT and DISMOUNT/UNLOAD the disk before removal from the jukebox. 6 7 Documentation Errata Page 3-3 of the DIGITAL Optical Storage Management Software User's Guide references RVxxx in a table. This is a 12-inch WORM device and is not supported by OSMS Version 3.4A. OSMS Version 3.4A does not support the HSC family of controllers. In the OSMS Installation Guide, there are sample installations that reference HSC controllers. These references do not apply to this version of the product. The qualifiers for the JBUTIL SHOW ERROR command are not applicable to 5 1/4-inch devices (see Page 5-19). The JBU-E-SOURCEEMPTY message described on Page 5-26 is not applicable to DIGITAL optical devices. 8 Media for Use in RWZ52 OSDS and OSMS V3.4A requires that media to be used in RWZ52 optical disk drives have the following characteristics: o Rewritable media must have a sector size of 512 Byte /Sector. o Rewritable media must have a sector capacity of 576999 or 1163337. o WORM media must have a sector size of 512 Byte/Sector. o WORM media must have a sector capacity of 576999 or 1163337. Digital Equipment Corporation supports the following media which meets the above requirements: o DIGITAL RWX1K-01 Rewritable Optical disk o DIGITAL RWX1K-02 WORM Optical disk o DIGITAL RWX5K-01 Rewritable Optical disk o DIGITAL RWX5K-02 WORM Optical disk Please note: o Non-DIGITAL media that has the same characteristics should work but cannot be guaranteed to work with OSDS or OSMS products. 7 o Only Rewriteable Optical disks can be used when the path to the optical subsystem includes an HSD or HSJ. 9 Media for Use in RWZ53 OSDS and OSMS V3.4A requires that media to be used in RWZ53 optical disk drives have the following characteristics: o Rewritable media must have a sector size of 512 Byte /Sector. o Rewritable media must have one of the following sector capacities: 576999 1163337 2244957 o WORM media must have a sector size of 512 Byte/Sector. o WORM media must have one of the following sector capacities: 576999 1163337 2244957 Digital Equipment Corporation supports the following media which meets the above requirements: o DIGITAL RWX1K-01 Rewritable Optical disk o DIGITAL RWX1K-02 WORM Optical disk o DIGITAL RWX5K-01 Rewritable Optical disk o DIGITAL RWX5K-02 WORM Optical disk o DIGITAL RWX6K-01 Rewritable Optical disk o DIGITAL RWX6K-02 WORM Optical disk Please note: o Non-DIGITAL media that has the same characteristics should work but cannot be guaranteed to work with OSDS or OSMS products. o Only Rewriteable Optical disks can be used when the path to the optical subsystem includes an HSD or HSJ. 8 The following restrictions also apply to the use of any media with the RWZ53 drive. All media with the sector capacity of 576999 can be read but not written by the RWZ53. This includes the DIGITAL RWX1K-01 Rewritable Optical disk and DIGITAL RWX1K-02 WORM Optical disk media. 9