DIGITAL Optical Storage Management Software (OSMS) and DIGITAL Optical Desktop Software (OSDS) Version 1.6 for DIGITAL UNIX V4.0b Product Release Notes September, 1997 ________________________________________________________ September 1997 (c) Perceptics Corporation 1988, 1989, 1990, 1991, 1992, 1993, 1994, 1995 Portions (c) 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. DIGITAL OSMS and DIGITAL OSDS Version 1.6 features Correction to Documentation: Please note, the hardcopy Installation and Users guides references support for DIGITAL OSMS and DIGITAL OSDS versions 1.5 and DIGITAL UNIX V3.2c through V3.2g in the title page. Please disregard this information. Both guides provide support for Version 1.6 of DIGITAL OSMS and DIGITAL OSDS as well as for version 1.5. There are separate release notes for each product version of DIGITAL OSMS and Digital OSDS. Please review all release notes appropiate to the version installed on your system. DIGITAL OSDS/DIGITAL OSMS Installation Verification Procedure The Installation Verification Procedure (IVP) verifies that all files required for OSDS operations are copied to the appropriate directories and that the these files have had the correct permissions assigned. For IVP test to succeed, ALL option must have been selected at Digital OSDS or Digital OSMS install time. The script file that performs IVP is osmsivp. It is copied to the /usr/sbin directory during installation and may be run at any time after installation. It is recommended, however, that the IVP be run immediately following installation. (In the example input and output below, square brackets [a/b] indicate that either character may apply. For example: os[d|m]sivp may be entered as either as osdssivp or osmssivp depending on the upon the product.) To run the IVP from anywhere in the system, simply invoke the command: # os[d|m]sivp The IVP will search all target directories for those files copied during installation and, if found, will verify that those files have the correct owner, group and permissions. The IVP generates no disk output nor creates any files. While checking files, the IVP will display the message: Checking File: When all files have been verified, the IVP terminates with a beep and the message: OSDS[D|M]SIVP Passed When this message is seen, the OS[D|M]S files have been correctly installed. There are two conditions that may cause the IVP to fail. First, if a file that is expected to exist is not found, the IVP will display the message: File not found directly under the 'Checking File' line. Second, if a file is found that does not possess the correct owner, group or permissions, the IVP will display the message: File has incorrect permissions, owner or group In either case, any error (whether missing file or incorrect owner, group or permissions on an existing file) will terminate the IVP immediately with a beep and the message: OS[D|M]S IVP Failed If the IVP does fail, perform the following uninstall procedure: # setld -i | grep OS[D|M]S then, using the output from grep, if any: # setld -d [ ... ] This will uninstall any subsets. Check for any .preOS[D|M]S files in the system and their status. For a list of .preOS[D|M]S files refer to the User's Guide. Reinstall the product and run IVP. If the problem persists, contact the local DIGITAL office for support. Product Performance Notes 1. Using DIGITAL OSMS, changer-based volumes mounted nfs may exhibit the following behaviors due to the latency of platter-swapping in the changer. These behaviors are seen with large numbers of concurrent accesses to nfs-mounted optical volumes; ie., a request from client2 is issued before the request from client1, for a volume not physically in a drive, completes: + I/O and/or Device Busy errors seen at the client. + In extreme cases, local processes may be suspended indefinitely waiting for access to some platters. + Also in extreme cases, the nfs server may exhibit nfs resource exhaustion. In DIGITAL UNIX, nfs requests are cached on timeout and, before any requests can be satisfied, the cache becomes full. Timeout at the client is a limitation of the nfs architecture. For these reasons, avoid large numbers of concurrent accesses to optical volumes mounted nfs unless all volumes are physically in drives. 2. Occasionally, files created using DIGITAL OSMS and DIGITAL OSDS 1.4 will not be readable. If 1.4 files must be read, copy to the 1.6 mounted volume via an intermediate storage device, such as a hard disk or tape. 3. Certain scripts running DIGITAL UNIX-C Shell (csh) may crash the system with kernel memory fault or unaligned memory access exceptions while accessing an optical disk under DIGITAL UNIX V4.0b. Appropriate DIGITAL UNIX V4.0b patches (not DIGITAL OSMS or DIGITAL OSDS patches) must be applied to eliminate this problem. Consult the DIGITAL UNIX V4.0b patch information for additional details. 4. Avoid copying files from one side of a platter to the other; buffering is insufficient. If copies need to be made from one side of a platter to the other, first copy the data from the source side to another platter or device and then copy to the desination. 5. Avoid omount when the device (optical filesystem) does not exist. When using OSMS (jukebox support) run the jbc utility and determine which slots are empty to avoid this action. Do this after insertion/removal of platters.