Digital Optical Storage Desktop Software (OSDS) for_OpenVMS_________________________________________ Installation Guide Order Number: AA-QLRHC-TE November 1996 This document contains instructions for the installation of Digital Optical Storage Desktop Software on the OpenVMS operating system. This document applies to Digital Optical Storage Desktop Software Version 3.4 and all maintenance updates throughout that version. Operating System & Version: OpenVMS/VAX Version 6.2. OpenVMS/Alpha Version 6.2. Future maintenance releases may require higher versions. Software Version: Digital Optical Storage Desktop Software Version 3.4 ________________________________________________________________ November 1996 © Perceptics Corporation 1988, 1989, 1990, 1991, 1992, 1993, 1994, 1995 Portions © Digital Equipment Corporation, 1996. All rights reserved. The information in this publication 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 publication is authorized only pursuant to a valid written license from Digital Equipment Corporation, an authorized sublicensor, or the identified licensor. Digital Equipment Corporation makes no representations that the use of its products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the agreement. 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. This document was prepared using VAX DOCUMENT Version 2.1. ___________________________________________________________ Contents Introduction 1.1 Intended Audience............................. 1-1 1.2 When to Install OSDS.......................... 1-1 1.3 Related Manuals............................... 1-1 Preparing to Install Digital Opitcal Storage Desktop Software 2.1 Optical Disk Drive Installation............... 2-1 2.2 Information Required for Installation......... 2-1 2.3 Registering the License PAK .................. 2-2 2.4 Installation Procedure Requirements .......... 2-2 2.4.1 Time...................................... 2-2 2.4.2 Privileges................................ 2-3 2.4.3 Disk Space Required for Installation...... 2-3 2.4.4 Disk Space Required for the Cache Files... 2-3 2.4.5 Process Account Quotas to Install Software.................................. 2-4 2.4.6 VMSINSTAL Requirements.................... 2-4 2.5 Backing Up Your System Disk................... 2-5 2.6 Preparing to Reboot the System ............... 2-5 2.7 Shutting Down OSDS ........................... 2-6 Installing the Digital Opitcal Storage Desktop Software 3.1 General Information........................... 3-1 3.1.1 Accessing the Online Release Notes........ 3-1 3.1.2 Running the Installation Verification Procedure (IVP)........................... 3-1 3.1.3 Aborting the Installation................. 3-2 3.2 The Installation Procedure.................... 3-2 3.2.1 Invoking VMSINSTAL........................ 3-2 3.2.2 Answering Installation Questions.......... 3-3 iii 3.2.3 Informational Messages.................... 3-11 3.2.4 Completing the Installation Procedure..... 3-11 3.2.5 Error Recovery............................ 3-11 3.3 Post Installation Procedures.................. 3-12 3.3.1 Starting OSDS ............................ 3-12 3.3.2 Running the IVP .......................... 3-13 3.3.3 Editing the System Startup File........... 3-13 3.3.4 Modification if Using OpenVMS/Alpha....... 3-14 3.3.5 Modification if Using OpenVMS/VAX......... 3-15 Files Added to System Sample Drive Installation for OpenVMS VAX Direct Connect 1 ______________________________________________________________ Introduction The Digital Optical Storage Desktop Software (OSDS) package allows members of the VAX and Alpha families to access high-capacity optical disk drives. OSDS cooperates with the OpenVMS operating system to provide transparent access to volumes in the optical disk drives from an OpenVMS host. This document contains instructions for the installation of OSDS on the OpenVMS operating system. Intended Audience This manual is intended for system managers. When to Install OSDS OSDS needs to be installed in the following conditions: o When OSDS is purchased and used for the first time. o When operating system version is changed, upgraded, or downgraded. o When software updates of OSDS are received. Related Manuals For additional information on installing Digital[TM] OSDS, refer to the OpenVMS system documentation for these topics: o VMSINSTAL procedure o System management and operations Introduction 1-1 2 ______________________________________________________________ Preparing to Install Digital Optical Storage Desktop Software Optical Disk Drive Installation The optical disk drive(s) and SCSI host adapter, if applicable, must be installed and operating properly before installing the OSDS software. Any problems encountered during the hardware installation phase should be corrected before the OSDS software is installed. Please refer to the OSDS for OpenVMS User's Manual, SCSI bus configuration rules, to ensure the hardware is set up properly before performing the software installation. Information Required for Installation You will need to know specific information about your hardware configuration before you can begin installing the OSDS software. In particular, you must be able to answer the following questions: o How many optical disk drives are installed? o What are the SCSI Target Ids and Logical Unit Numbers (if any) for the drives? o What SCSI adapter in the computer and it's associated PKxy: device designation is being used to interface to the drives? If you do not have this information available, refer to the installation information supplied with the equipment or contact your system manager. Preparing to Install Digital Optical Storage Desktop Software 2-1 Preparing to Install Digital Optical Storage Desktop Software Registering the License PAK Registering the License PAK You must register the License Product Authorization Key (PAK) before you begin installing the OSDS software. The installation procedure uses information contained in the PAK to determine some of the characteristics of the installation. If an OSDS PAK (OSDS-5) has not been registered, the installation will terminate. To register a license under OpenVMS, first log into the system manager's account, SYSTEM. You then have a choice of two ways to perform the registration: o Invoke the SYS$UPDATE:VMSLICENSE.COM procedure. When it prompts you for information, respond with data from your License PAK. o At the DCL prompt, enter the LICENSE REGISTER command with the appropriate qualifiers that correspond to the License PAK information. If you are registering multiple licenses for the same product, only load the first license. This may be the case if you purchased multiple sub-systems or additional sub-systems. While using the license utility to enter the additional licenses, specify NO to the question "Do you want to load....". At this point, get out of the license utility and enter the following commands: $ $ license unload/producer=PERCEPTICS (OSDS-5) $ $ license load/producer=PERCEPTICS (OSDS-5) The will cause the units to be added together, allowing the system to use the entire capacity of all of your licenses. Installation Procedure Requirements The following sections discuss various requirements for installing the OSDS software. Time The installation takes approximately 5 to 10 minutes, depending on the type of media and your system configuration. Additional time will be required to shut the system down and reboot if you request a reboot during installation. Preparing to Install Digital Optical Storage Desktop Software Preparing to Install Digital Optical Storage Desktop Software 2.4 Installation Procedure Requirements Privileges To install the Digital Optical Storage Desktop Software, you must be logged in to an account that has SETPRV. It is recommended that you be logged in to the SYSTEM account. ________________________ Note ________________________ VMSINSTAL turns off BYPASS privilege at the start of the installation. ______________________________________________________ Disk Space Required for Installation The installation of the OSDS software requires at least 15,000 blocks of free disk space. After installation, about 4,000 blocks of disk space will be permanently used by the OSDS software. To determine the number of free disk blocks on the current system disk, enter the following command at the DCL prompt: $ SHOW DEVICE SYS$SYSDEVICE Disk Space Required for the Cache Files During the installation, you will be asked to specify the size and location of the "write-behind cache files." OSDS requires one cache file for each optical disk drive installed. The size of the cache file depends on a number of considerations but each cache file must be contiguous on the disk. For additional information, see the item titled, "Specifying the write-behind cache files" in Section 3.2.2. ________________________ Note ________________________ For clustered systems only, the cache files must be on the system disk of the node serving the cluster. Placing the cache file on other disks may cause the cluster to hang during mount verifications caused by cluster transitions. ______________________________________________________ Preparing to Install Digital Optical Storage Desktop Software 2-3 Preparing to Install Digital Optical Storage Desktop Software Installation Procedure Requirements Process Account Quotas to Install Software The account you use to install the OSDS software must have sufficient quotas to enable you to perform the installation. The following table summarizes the process quotas required for the installation account: ___________________________________________________________ ____________Account_Quota_________Value____________________ ASTLM 24 BIOLM 18 BYTLM 18,000 DIOLM 18 ENQLM 30 ____________FILLM_________________20_______________________ User account quotas are stored in the file SYSUAF.DAT. The OpenVMS Authorize utility is used to verify and change user account quotas. For information on modifying account quotas, see the description of the Authorize utility in the OpenVMS documentation set. VMSINSTAL Requirements When you invoke VMSINSTAL, it checks the following: o Whether you have set your default device and directory to SYS$UPDATE o Whether you are logged into a privileged account o Whether you have adequate quotas for installation o Whether any users are logged in to the system VMSINSTAL requires that the installation account have a minimum of the following quotas: ASTLM = 24 BIOLM = 18 BYTLM = 18,000 DIOLM = 18 ENQLM = 30 FILLM = 20 Preparing to Install Digital Optical Storage Desktop Software Preparing to Install Digital Optical Storage Desktop Software 2.4 Installation Procedure Requirements If VMSINSTAL detects any problems during installation, it notifies you of the problem and asks if you want to continue the installation. In some instances, you can enter YES to continue. To stop the installation process and correct the situation, enter NO or press . Then, correct the problem and restart the installation. Backing Up Your System Disk At the beginning of the installation, VMSINSTAL asks if you have backed up your system disk. If you do not have a current backup of you system disk, please create a backup copy of your system disk before installing this software. Use the backup procedures established at your site. For details on performing a system disk backup, see the section on the Backup utility in the OpenVMS documentation set. Preparing to Reboot the System In general, OSDS will require you to reboot the system before it can start operation. The installation procedure can complete successfully without rebooting the system, but OSDS may not start properly until the system is rebooted. You may not need to reboot the system if: o This is a new installation of OpenVMS and associated layered products. o You do not have an existing version of: o Digital OSMS or Digital OSDS o Perceptics LaserStar or Perceptics LaserWare o Digital products that contain the JUDRIVER for controlling robotics mechanisms of tape or optical libraries through an HSD or HSJ. o You have just rebooted and only OpenVMS is operating. In this case, you may answer "NO" when asked if the system should be rebooted. If you have an existing version of any of these products running on the system, you must shut down these products before starting the installation. Refer to the products documentation for specific shutdown procedures. Preparing to Install Digital Optical Storage Desktop Software 2-5 Preparing to Install Digital Optical Storage Desktop Software Preparing to Reboot the System When the installation is completed, run the Installation Verification Procedure (IVP) using the following command: $ @SYS$TEST:LASERWARE_IVP Shutting Down OSDS If you have an existing version of OSDS running on the system, you must shut down OSDS before starting the installation. This involves the following steps: o Dismount all optical volumes (you can determine which volumes are mounted using the DCL command SHOW DEVICE OD/MOUNTED). o Shut down OSDS using the following commands: $ RUN SYS$SYSTEM:JKCONFIG JKCONFIG> REMOVE ODA0: JKCONFIG> REMOVE ODA1: <-- Repeat for all optical disk drives . . . JKCONFIG> EXIT or $ RUN SYS$SYSTEM:ODCONFIG <-- If version 3.0 or earlier ODCONFIG> REMOVE ODA0: ODCONFIG> REMOVE ODA1: <-- Repeat for all optical disk drives . . . ODCONFIG> EXIT o Delete the write-behind cache files using the following command (modify the command as appropriate if the cache files are not located in SYS$SYSTEM): $ DELETE SYS$SYSTEM:OD*_CACHE_*.WRK;* Preparing to Install Digital Optical Storage Desktop Software 3 ______________________________________________________________ Installing the Digital Optical Storage Desktop Software General Information This section includes information about accessing release notes, determining what files are added to your system, running the IVP, and aborting the installation. Accessing the Online Release Notes The OSDS software provides online release notes. When you invoke VMSINSTAL, specify OPTIONS N if you want an opportunity to display or print the online release notes. This choice comes near the beginning of the installation. Review the release notes in case they contain any information about changes in the installation procedure. If you have already reviewed the release notes, you do not need to specify OPTIONS N. After the OSDS software has been installed, the release notes are located in the following file: SYS$HELP:LASERWARE034.RELEASE_NOTES Running the Installation Verification Procedure (IVP) The IVP for the OSDS software verifies the installation. After the installation is complete, you should run the IVP to ensure that the OSDS software is installed properly. Successful completion of the IVP requires that the optical hardware be installed and operational. You may need to reboot the system before running the IVP (see Section 2.6 to determine whether you must reboot). When the installation is completed, run the Installation Verification Procedure (IVP) using the following command: $ @SYS$TEST:LASERWARE_IVP Installing the Digital Optical Storage Desktop Software 3-1 Installing the Digital Optical Storage Desktop Software General Information Aborting the Installation To abort the installation procedure at any time, press . When you press , the installation procedure deletes all files that it has created up to that point and exits. You can then start the installation again. The Installation Procedure The OSDS software installation procedure consists of a series of questions and informational messages. The following sections explain how to invoke VMSINSTAL and answer the installation procedure questions. Invoking VMSINSTAL To start the installation, invoke the VMSINSTAL command procedure from a privileged account, such as the SYSTEM account. VMSINSTAL is in the SYS$UPDATE directory. Use the following syntax to invoke VMSINSTAL: $ @SYS$UPDATE:VMSINSTAL product-name device-name OPTIONS N The product-name is the installation name for the component. For OSDS on OpenVMS/VAX systems, use the following installation name: OSDSV034 For OSDS on OpenVMS/Alpha (Alpha[TM]) systems, use the following installation name: OSDSA034 The device-name is the name of the device on which you plan to mount the media. For example, MUA0: is the device name for a TK50 tape drive. It is not necessary to use the console drive for installation. However, if you do use the console drive, replace any media you removed when the installation is complete. OPTIONS N is an optional parameter that indicates you want to see the release notes question. If you do not include the OPTIONS N parameter, VMSINSTAL does not ask you about the release notes. You can select several other options when you invoke VMSINSTAL. See the OpenVMS documentation on software installation for information on these options. Installing the Digital Optical Storage Desktop Software Installing the Digital Optical Storage Desktop Software 3.2 The Installation Procedure The following command invokes VMSINSTAL to install the OSDS software on an OpenVMS/VAX system from the TK50 tape drive MUA0: and shows the system response. This example uses the OPTIONS N release note parameter. $ @SYS$UPDATE:VMSINSTAL OSDSV034 MUA0: OPTIONS N OpenVMS VAX Software Product Installation Procedure V6.2 It is 15-OCT-1996 at 14:30. Enter a question mark (?) at any time for help. If you do not supply either the product name or the device name, VMSINSTAL prompts you for more information later in the installation procedure. Answering Installation Questions This section discusses the questions that appear during the installation. Each question in the installation is marked with an asterisk (*) at the beginning of the line. Some questions show the default response in brackets, for example [YES]. If you want to use the default response, press the key. 1. Checking for Other Users VMSINSTAL notifies you if there are any other active processes and displays a list of them. It then asks if you want to continue the installation. The installation of OSDS does not require you to shut down DECnet[TM] or remove other users from the system. The default response to the question is NO. %VMSINSTAL-W-ACTIVE, The following processes are still active: _TWA2: _TWA3: * Do you want to continue anyway [NO]? 2. Performing system backup VMSINSTAL asks if you are satisfied with your system backup. Always back up your system disk before performing any installation. If you are satisfied with the backup of your system disk, press . Otherwise, enter NO to discontinue the installation. After you back up your system disk, you can restart the installation. Installing the Digital Optical Storage Desktop Software 3-3 Installing the Digital Optical Storage Desktop Software The Installation Procedure * Are you satisfied with the backup of your system disk [YES]? 3. Mounting the media You should now mount the distribution volume on the device you specified when you invoked VMSINSTAL. The device name appears in the line preceding the question "Are you ready?". VMSINSTAL then asks if you are ready to continue with the installation. If you respond YES to indicate that you are ready, VMSINSTAL displays a message. You are informed that the media containing the OSDS software has been mounted on the specified device and that the installation has begun. For example: Please mount the first volume of the set on MUA0: * Are you ready? YES %MOUNTED-I-MOUNTED, LASERS MOUNTED ON _$$MUA0: The following products will be processed: OSDSV V3.4 Beginning installation of OSDSV V3.4 at 10:00 %VMSINSTAL-I-RESTORE, Restoring product saveset A... 4. Reviewing release notes If you specified OPTIONS N when you invoked VMSINSTAL, you must now choose one of the following options for reviewing the release notes. Release Notes Options: 1. Display release notes 2. Print release notes 3. Both 1 and 2 4. None of the above * Select option [2]: If you select option 1, VMSINSTAL displays the release notes immediately on your terminal. You can terminate the display at any time by pressing . If you select option 2, VMSINSTAL prompts you for the name of the print queue that you want to use: * Queue name [SYS$PRINT]: Installing the Digital Optical Storage Desktop Software Installing the Digital Optical Storage Desktop Software 3.2 The Installation Procedure If you select option 3, VMSINSTAL displays the release notes immediately on the terminal and then prompts you for a queue name for the printed version. Select option 4 if you have already reviewed the release notes. 5. Continuing the installation The installation procedure now asks if you want to continue the installation. To continue, enter YES. Otherwise, press . In either case, the release notes are copied to a file in the SYS$HELP directory. For example: * Do you want to continue the installation [NO]? YES %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. The release notes are located in the following file: SYS$HELP:LASERWARE034.RELEASE_NOTES The installation will now display a copyright notice similar to the following: © 1988,1989,1990,1991,1992,1993,1994,1995 by Perceptics Corporation. ALL RIGHTS RESERVED. Portions © Digital Equipment Corporation, 1996. All rights reserved. This software is furnished under a license and may be used and copied only in accordance with the terms of such license and with the inclusion of the above copyright notice. This software or any other copies thereof may not be provided or otherwise made available to any other person. No title to and ownership of the software is hereby transferred. The information in this software is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital assumes no responsibility for the use or reliability of its software on equipment which is not supplied by Digital. 6. Selecting whether to only configure a system Installing the Digital Optical Storage Desktop Software 3-5 Installing the Digital Optical Storage Desktop Software The Installation Procedure The OSDS software supports a variety of optical hardware configurations. OpenVMS will not automatically configure any of these configurations. The installation procedure and the associated documentation are currently the only tools available that provides any information on configuring optical hardware. By answering YES to the question: * Are you running this procedure only to configure a system [NO]: You will be allowed to do the following: o Learning how to answer the installation procedure prompts without installing the product. o Exploring other configuration options. o Produce additional startup command files, without reinstalling the software, if you have multiple drives. Note, you must answer NO to install the software. 7. Selecting whether to allow a reboot You must next determine whether or not you will allow the system to be rebooted when the installation is completed. (See Section 2.6.) If you decide to reboot the system, you will be asked how soon to shut down and whether an automatic system reboot should be performed. To complete the installation of this product, you should reboot the system. If it is not convenient to reboot at this time, then enter NO to the following question. If you enter NO, the installation procedure will continue. * Will you allow a system shutdown after this product is installed [YES]? * How many minutes for system shutdown [0]: * Do you want to do an automatic system reboot [YES]? 8. Purging files The installation procedure asks if you want to purge files replaced during the installation. To purge files, press . To disable purging of files, enter NO. * Do you want to purge files replaced by this installation [YES]? 9. Specifying the number of disk drives Installing the Digital Optical Storage Desktop Software Installing the Digital Optical Storage Desktop Software 3.2 The Installation Procedure The installation will ask how many optical disk drives you have. You must enter the number of optical disk drives being installed. * How many optical disk drives do you have: 10. Renaming of old WD$STARTUP.COM file to WD$STARTUP_PKx.COM If you have an existing version of the WD$STARTUP command file, you will be told that the file is being renamed. The new command file name appends the port driver controller letter to the existing file name so it is easier to tell which WD devices are created by which command file. The intent of this naming is to help customers support more than one optical sub-system on multiple SCSI adapters. Text similar to this will be shown: An existing version of WD$STARTUP.COM has been found on your system. This version of the product uses a new naming for the WD$STARTUP.COM files to better match the physical configuration. WD$STARTUP.COM will be copied to a new file named, WD$STARTUP_PK"X".COM where the "X" is a letter, such as A,B,C... associated with the SCSI bus controller device. After the file is copied, all versions of WD$STARTUP.COM will be renamed to WD$STARTUP.COM_OLD;*. The old file is shown below:" $ ! $ ! WD$STARTUP file for OSDSV V3.3 created 25-SEP-1995 16:39:04.95 $ ! $ WRITE SYS$OUTPUT "%WDDRIVER-I-CONNECTWD, connecting WD devices... $ RUN SYS$SYSTEM:SYSGEN CONNECT WDB400/NOADAPTER CONNECT WDB500/NOADAPTER $ EXIT 11. Creating a new WD$STARTUP_PKx.COM file If you have an existing version of the WD$STARTUP_ PKx.COM file, you will be asked whether or not you want to create a new file. If you are using the same SCSI devices with the same SCSI addresses, then you do not need to create a new WD$STARTUP_PKx.COM. However, if your configuration has changed, then answer "YES" to the question and you will be prompt for the information Installing the Digital Optical Storage Desktop Software 3-7 Installing the Digital Optical Storage Desktop Software The Installation Procedure needed to create a new file. The previous version of the file will be saved regardless of whether you create a new file or whether you indicated that files should be purged. A file called WD$STARTUP_PKx.COM is required at boot time to connect the WD devices. An existing version of the WD$STARTUP_PKx.COM file has been found on your system. If the SCSI device addressing has not changed, you may use the existing file. The existing version will NOT be purged from the system, regardless of whether you create a new one or not. * Do you want to create a new WD$STARTUP_PKx file [N]: 12. Specifying an SCSI controller An SCSI controller can be identified as a device name starting with "PK", such as PKA0: or PKB0:. Some systems have multiple SCSI controllers available. If more than one SCSI controller is detected during installation, then you will be asked to specify which SCSI controller to use for connecting to the jukebox and drives. For example, if your system has two SCSI controllers connected, the following display will appear: There are 2 SCSI controllers installed on your system. Each controller connects to a separate SCSI bus. You must select which controller is to be used. Select one of the following: A for PKA0: B for PKB0: * Which controller should be used [B]: 13. Specifying SCSI device ids The next part of the installation will require specific information about the device's SCSI target ids assigned to the optical disk drives. There will typically be one SCSI target id for each optical disk drive. The SCSI target id is typically set on the device using switches or a control panel. You must enter the SCSI target id for each SCSI device. Enter or the word EXIT to indicate that the last SCSI target id has been entered. Installing the Digital Optical Storage Desktop Software Installing the Digital Optical Storage Desktop Software 3.2 The Installation Procedure Prompts such as the following will be displayed to allow you to enter the SCSI address information needed to configure your optical subsystem. * Enter the SCSI target id of the first optical SCSI device: 1 Creating OpenVMS device unit number 100 for SCSI target id 1 and LUN 0 * Enter the SCSI target id of the second optical SCSI device or CTRL/Z if done: 2 Creating OpenVMS device unit number 200 for SCSI target id 2 and LUN 0 * Enter the SCSI target id of the third optical SCSI device or CTRL/Z if done: The OpenVMS Device unit numbers created are: 100 200 14. Specifying OpenVMS devices for each drive You must now specify which OpenVMS device is associated with each optical disk drive. The SCSI addresses, entered earlier, were used to determine the OpenVMS device designation. In the previous example, the SCSI target id 2 was specified for the connection to the SCSI controller PKB0. The OpenVMS device unit number created was shown to be 200 and the corresponding device designation was WDB200. The installation procedure will display the known device designations for optical drives. The question is repeated for each optical disk drive. You will only be allowed to select devices shown in the list. Select your response to the following questions from this list: WDB100 WDB200 * What OpenVMS device is connected to optical drive 1: WDB100 * What OpenVMS device is connected to optical drive 2: WDB200 Installing the Digital Optical Storage Desktop Software 3-9 Installing the Digital Optical Storage Desktop Software The Installation Procedure 15. Specifying the write-behind cache files The cache file is used differently depending upon the type of media in use. For WORM optical media, the cache file is used as a consolidation buffer so the number of actual write operations to the media are minimized. For rewritable optical media, the cache file is used to store information needed to handle mount verification issues. o A cache file exists for each drive. o For standalone drives the cache files can be different sizes. o Each cache file has a minimum size of 4 blocks and a maximum size of 32767 blocks and MUST BE CONTIGUOUS ON THE DISK. (The cache files do not need to be contiguous with each other.) o The minimal cache file size needed for use with rewritable optical media is 4 blocks for each cache file. o The minimal cache file size needed for WORM media is: - 256 blocks to allow both "read and write" access. - 4 blocks to allow "read-only" access. o Some applications using WORM media may require even larger cache files: - DECimage Express installations, recommended minimum is 2048 blocks - Database operations (such as Rdb, Ingres, Oracle, etc.) should make the cache files larger -- 2048 to 4096 blocks - Installations doing large amounts of indexed file operations or random block replacements may benefit by making it larger - If very large directories are anticipated (directories with grow larger than 2/3 the cache file size), then make the cache file larger o The cache files should be located on a disk drive which is fast, lightly used, and has sufficient contiguous space for all the cache files. The default location is SYS$SYSTEM:. o A location on your system disk is required if you plan to MSCP serve your optical disks to other cluster members. Note: Only optical volumes containing the Files-11 on-disk structure may be MSCP served. Specifying cache file size smaller than the default presented at installation time can only be done by editing the LASERWARE$STARTUP_A.COM file after the installation is complete. Installing the Digital Optical Storage Desktop Software Installing the Digital Optical Storage Desktop Software 3.2 The Installation Procedure You must answer the following questions to determine the cache file size and location: * How large should the cache files be [4]: A location on your system disk is required if you plan to MSCP serve your optical disks to other cluster members. Note: Only optical volumes containing the Files-11 on-disk structure may be MSCP served. * Where should the cache files be located [SYS$SYSTEM]: All questions have been answered at this point and the installation will proceed. When the installation is completed, the system will reboot if you selected that option. Informational Messages After all the questions have been answered, various informational messages will appear. The sample installations in the appendix show some typical informational messages. Completing the Installation Procedure If you did not agree to allow the system to be rebooted, the following message indicates that the installation procedure has completed: Installation of OSDSV V3.4 completed at 10:40 VMSINSTAL procedure done at 10:41 You can now log out of the privileged account. If you did request a system reboot, it will be invoked at this time in accordance with the parameters you specified. Error Recovery If errors occur during the installation itself, VMSINSTAL displays failure messages. If the installation fails, you see the following message: %VMSINSTAL-E-INSFAIL, The installation of OSDSV V3.4 has failed. Installing the Digital Optical Storage Desktop Software 3-11 Installing the Digital Optical Storage Desktop Software The Installation Procedure Errors can occur during the installation if any of the following conditions exist: o The operating system version is incorrect. o Quotas necessary for successful installation are insufficient. o System parameter values for successful installation are insufficient. For descriptions of the error messages generated by these conditions, see the OpenVMS documentation on system messages, recovery procedures, and software installation. If you are notified that any of these conditions exist, take the appropriate action as described in the message. (You might need to change a system parameter or increase the authorized quota value.) For information on installation requirements, see Chapter 2. Post Installation Procedures The following tasks, if necessary, take place after installing the OSDS software: o Starting OSDS o Running the installation verification procedure (IVP) o Editing the system startup file o Modification if using OpenVMS/Alpha o Modification if using OpenVMS/VAX Starting OSDS After installation is completed and a reboot was performed (if necessary), then you must start OSDS by invoking the following command: $ @SYS$STARTUP:LASERWARE$STARTUP_A.COM Installing the Digital Optical Storage Desktop Software Installing the Digital Optical Storage Desktop Software 3.3 Post Installation Procedures Running the IVP The IVP for the OSDS software verifies the installation. After the installation is completed, you should run the IVP to ensure that the OSDS software is installed properly. Successful completion of the IVP requires that the jukebox be installed and operational. You may need to reboot the system before running the IVP. (See Section 2.6 to determine whether you must reboot.) Then, when the installation is completed, run the Installation Verification Procedure (IVP) using the following command: $ @SYS$TEST:LASERWARE_IVP The following is sample output similar to the execution of the IVP: $ @SYS$TEST:LASERWARE_IVP Starting the Installation Verification Procedure for LASERWARE Channel assigned to "_ODA0:" SCSI Inquiry data returned 56 bytes from device: SCSI Status (00x): Good Device type code: 07x -- Optical memory Response data format: 02x Medium is removable: T Version: 02x, SCSI = 2, ECMA = 0, ISO = 0 Data length: 51 (Length read was 51) Data: "...DEC RWZ52 (C)DEC34043351......" IVP completed for NODE1$ODA0 ... Editing the System Startup File You must edit the system startup file, SYS$MANAGER:SYSTARTUP_VMS.COM, to enable the OSDS software to function properly after a system reboot. Please add the following command line to the system startup file: $ @SYS$STARTUP:LASERWARE$STARTUP_A.COM Installing the Digital Optical Storage Desktop Software 3-13 Installing the Digital Optical Storage Desktop Software Post Installation Procedures Modification if Using OpenVMS/Alpha After the devices physically connected and powered up, but before booting, the device mnemonics can be obtained from the show device console command. The following is an example: >>> SHOW DEVICE BOOTDEV ADDR DEVTYPE NUMBYTE RM/FX WP DEVNAM REV ------- ---- ------- ------- ----- -- ------ --- ESA0 08-00-2B-32-C3-AE, THICK DKA200 A/2/0 DISK 1.05GB FX RZ26 T386 DKA400 A/4/0 RODISK ...... RM WP RRD42 4.5d MKA500 A/5/0 TAPE RM TKZ10 03B8 ..HostId.. A/7 INTR DKB100 B/1/0 DISK 1.05GB FX RZ26 T386 JKB200 B/2/0 OPDISK ...... RM RWZ53 1.28 JKB300 B/3/0 OPDISK ...... RM RWZ52 3404 The system may incorrectly configure the DKDRIVER for use with the optical disk drives if the devices are not excluded during the autoconfigure phase of the system startup. This will prevent the use of your optical subsystem because the WDDRIVER cannot be connected. For the OpenVMS/Alpha systems running Version 6.2 or higher, it is required to issue a SYSMAN IO SET EXCLUDE = (device) to prevent the optical disks from being incorrectly configured as magnetic disks. This only has to be done when the configuration of a SCSI bus changes or when the OpenVMS operating system is upgraded. The change will have no effect until the next reboot. The installation procedure will create a command file to execute the SYSMAN IO SET EXCLUDE commands needed to allow the configuration to function. This command file is named WD$EXCLUDE_PK(x).COM, where (x) is a letter associated with the SCSI bus on which to exclude the devices. The file WD$EXCLUDE_PK(x).CONFIGURE will be created if you execute the installation procedure using the configuration option. In this case the (x) is still the letter associated with the SCSI bus on which to exclude the devices. Installing the Digital Optical Storage Desktop Software Installing the Digital Optical Storage Desktop Software 3.3 Post Installation Procedures Modification if Using OpenVMS/VAX A new value may be set for the SCSI_NOAUTO SYSGEN parameter by the installation procedure. This value is set in order to reserve the SCSI target ids during the SYSGEN AUTOCONFIG phase of a system startup. The value should also be changed in the SYS$SYSTEM:MODPARAMS.DAT file to make the change permanent. The change will have no effect until the next reboot. Installing the Digital Optical Storage Desktop Software 3-15 A ______________________________________________________________ Files Added to System When installed, the OSDS software adds the following system files on the VAX: SYS$LOADABLE_IMAGES:JKDRIVER.EXE SYS$SYSTEM:HEADER.EXE SYS$SYSTEM:JKCONFIG.EXE SYS$SYSTEM:ODUTIL.EXE SYS$SYSTEM:SCSI.EXE SYS$SYSTEM:W11AACP.EXE SYS$TEST:LASERWARE_IVP.COM On OpenVMS/Alpha systems, the OSDS software adds the following system files: SYS$LOADABLE_IMAGES:JKDRIVER.EXE SYS$SYSTEM:HEADER.EXE SYS$SYSTEM:JKCONFIG.EXE SYS$SYSTEM:SCSI.EXE SYS$TEST:LASERWARE_IVP.COM SYS$TEST:WDDRIVER_IVP.COM The following files are added to the SYS$MANAGER directory on both OpenVMS for VAX and Alpha systems: LASERWARE$STARTUP_x.COM LASERWARE$STARTUP_A.COM PERCEPTICS$DEVICES.COM PERCEPTICS$OPTICDEF.COM PERCEPTICS$VERSIONS.COM If a direct SCSI connection is used to attach the optical sub-system to the host, the following files are added on both OpenVMS for VAX and Alpha systems: SYS$LOADABLE_IMAGES:WDDRIVER.EXE SYS$LOADABLE_IMAGES:RZDRIVER.EXE SYS$TEST:WDDRIVER_IVP.COM SYS$MANAGER:WD$STARTUP_PKx.COM Files Added to System A-1 Files Added to System SYS$MANAGER:WD$EXCLUDE_PKx.COM (Alpha only) If an HSD or HSJ is used to connect the optical sub-system to the host, the following files are added: SYS$LOADABLE_IMAGES:JUDRIVER.EXE SYS$MANAGER:JU$STARTUP.COM SYS$TEST:JUDRIVER_IVP.COM A directory on SYS$SYSDEVICE called [PERCEPTICS] is created to store files that may be required for field service or other purposes. The following files are stored there on both OpenVMS for VAX and Alpha systems: FID_TO_SPEC.EXE JKDRIVER.STB JUDRIVER.STB (HSx only) JUDRIVER.MAP (HSx only) JUDRIVER_INIT.STB (HSx only) KIT_VERSION.TXT POKE.EXE RESET_ERRCNT.EXE W11ACP.STB (VAX only) WDDRIVER.STB Files Added to System B ______________________________________________________________ Sample Drive Installation for OpenVMS VAX Direct Connect Enter the products to be processed from the first distribution volume set. * Products: OSDSV034 * Enter installation options you wish to use (none): The following products will be processed: OSDSV V3.4 Beginning installation of OSDSV V3.4 at 17:14 %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. © 1988,1989,1990,1991,1992,1993,1994,1995 by Perceptics Corporation. ALL RIGHTS RESERVED. Portions © Digital Equipment Corporation, 1996. All rights reserved. This software is furnished under a license and may be used and copied only in accordance with the terms of such license and with the inclusion of the above copyright notice. This software or any other copies thereof may not be provided or otherwise made available to any other person. No title to and ownership of the software is hereby transferred. The information in this software is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital assumes no responsibility for the use or reliability of its software on equipment which is not supplied by Digital. * Are you running this procedure only to configure a system [NO]: To complete the installation of this product, you should reboot the system. If it is not convenient to reboot at this time, then enter NO to the following question. If you enter NO, the installation procedure will continue. Sample Drive Installation for OpenVMS VAX Direct Connect B-1 Sample Drive Installation for OpenVMS VAX Direct Connect * Will you allow a system shutdown after this product is installed [YES]? no During this installation, new files will be provided to replace existing versions. You may purge these older versions to save disk space, or keep them if you feel they may be of use. Purging is recommended. * Do you want to purge files replaced by this installation [YES]? A file called LASERWARE$STARTUP_A.COM is required at boot time to initialize LASERWARE. An existing version of the LASERWARE$STARTUP_A.COM file has been found on your system. A new version of this file will now be created. The existing version will NOT be purged, so you may wish to manually purge this file when the installation is completed. * How many optical disk drives do you have: 1 There are 2 SCSI controllers installed on your system. Each controller connects to a separate SCSI bus. You must select which controller is to be used. Select one of the following: A for PKA0: B for PKB0: * Which controller should be used [B]: %OSDSV-I-PKDEV, devices will be configured on SCSI bus B (PKB0:) An existing version of WD$STARTUP_PKB.COM has been found on your system. WD$STARTUP_PKB.COM issues the commands required to connect devices to the B SCSI bus. If the device SCSI target ids have not changed, you may use the existing file. The existing version will NOT be purged from the system, regardless of whether you create a new one or not. The existing file is shown below: $ RUN SYS$SYSTEM:SYSGEN CONNECT RZB000/NOADAPTER CONNECT WDB300/NOADAPTER CONNECT WDB400/NOADAPTER CONNECT WDB500/NOADAPTER CONNECT WDB700/NOADAPTER $ EXIT * Do you want to modify this WD$STARTUP_PKB.COM file [N]? Y Sample Drive Installation for OpenVMS VAX Direct Connect Sample Drive Installation for OpenVMS VAX Direct Connect A SCSI device has a unique SCSI target id assigned to allow it to be be addressed separately from all other devices on the same SCSI bus. Some devices also use logical unit numbers (LUN's), although this is typically zero. You must specify the SCSI target id for the devices to be connected to the SCSI bus. If you are not sure what the SCSI target ids of your devices are, type CTRL/Y to exit the installation and contact your system manager. Entering CTRL/Z or "EXIT" will terminate the prompting for SCSI target. ids. Entering "OVER" will discard the entrys you have made and restart the prompting for the first SCSI target id. * Enter the SCSI target id of the first optical SCSI device: 3 Creating OpenVMS device unit number 300 for SCSI target id 3 and LUN 0 * Enter the SCSI target id of the second optical SCSI device or CTRL/Z if done: exit %OSDSV-I-DEFINE, defining device WDB300 for ! SCSI ID=3 LUN=0 %OSDSV-I-CREATEFILE, created SYS$MANAGER:WD$STARTUP_PKB.COM %OSDSV-I-ADDSTARTUP, add @SYS$MANAGER:WD$STARTUP_PKB to SYSTARTUP_VMS.COM %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[PERCEPTICS]. %CREATE-I-EXISTS, SYS$SYSDEVICE:[PERCEPTICS] already exists This command file should be invoked one time and the system should be rebooted before you start this software. %OSDSV-I-LINK, Linking WDDRIVER for OpenVMS 6.2 %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[PERCEPTICS]. %CREATE-I-EXISTS, SYS$SYSDEVICE:[PERCEPTICS] already exists The Installation Verification Procedure (IVP) for WDDRIVER will be copied into the file SYS$TEST:WDDRIVER_IVP.COM. It can be invoked at any time after the installation is completed. You must specify which physical SCSI device is associated with each drive. Select your response to the following questions from this list: WDB300 * What OpenVMS device is connected to optical drive 1: wdb300 Sample Drive Installation for OpenVMS VAX Direct Connect B-3 Sample Drive Installation for OpenVMS VAX Direct Connect The cache file is used differently depending upon the type of media in use. For WORM optical media, the cache file is used as a consolidation buffer so the number of actual write operations to the media are minimized. For rewritable optical media, the cache file is used to store information needed to handle mount verification issues. o A cache file exists for each pseudo device. o All cache files will be the same size. o Each cache file has a minimum size of 4 blocks and a maximum size of 32767 blocks and MUST BE CONTIGUOUS ON THE DISK. (The cache files do not need to be contiguous with each other.) o The minimal cache file size needed for use with rewritable optical media is 4 blocks for each cache file. o The minimal cache file size needed for WORM media is: - 256 blocks to allow both "read and write" access. - 4 blocks to allow "read-only" access. o Some applications using WORM media may require even larger cache files: - DECimage Express installations, recommeded minimum is 2048 blocks - Database operations (such as Rdb, Ingres, Oracle, etc.) should make the cache files larger -- 2048 to 4096 blocks - Installations doing large amounts of indexed file operations or random block replacements may benefit by making it larger - If very large directories are anticipated (directories with grow larger than 2/3 the cache file size), then make the cache file larger o 1 cache files will be required for your installation. o The cache files should be located on a disk drive which is fast, lightly used, and has sufficient contiguous space for all the cache files. The default location is SYS$SYSTEM:. o A location on your system disk is required if you plan to MSCP serve your optical disks to other cluster members. Note: Only optical volumes containing the Files-11 on-disk structure may be MSCP serverd. * How large should each cache file be [4]: 256 * Where should the cache file be located [SYS$SYSTEM]: LASERWARE$STARTUP_A.COM will be copied to the SYS$MANAGER directory. It should be added to SYSTARTUP_VMS.COM to be invoked every time the system is rebooted. Sample Drive Installation for OpenVMS VAX Direct Connect Sample Drive Installation for OpenVMS VAX Direct Connect The Installation Verification Procedure (IVP) will be copied into the SYS$TEST directory. After installation is completed and the system has been re-booted, you may run the IVP by typing the following command: @SYS$TEST:LASERWARE_IVP %OSDSV-I-LINK, Linking JKDRIVER for OpenVMS 6.2 %OSDSV-I-LINK, Linking JKCONFIG for OpenVMS 6.2 %OSDSV-I-LINK, Linking the WORMS-11 ACP for OpenVMS 6.2 ... %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[PERCEPTICS]. %CREATE-I-EXISTS, SYS$SYSDEVICE:[PERCEPTICS] already exists %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... %REGISTER-I-DUP ODUTIL, (ODUTIL, XX3.4-0) already in registry %REGISTER-I-SUMMARY images examined: 1, dependent images: 1 Installation of OSDSV V3.4 completed at 17:19 Enter the products to be processed from the next distribution volume set. * Products: ^Z VMSINSTAL procedure done at 17:20 Sample Drive Installation for OpenVMS VAX Direct Connect B-5