Digital Optical Storage Management Software (OSMS)_for_OpenVMS__________________________________ Installation Guide Order Number: AA-QLKMC-TE November 1996 This document contains instructions for the installation of Digital Optical Storage Management Software on the OpenVMS operating system. This document applies to Digital Optical Storage Management 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 Management 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 Optical Storage Management 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 Digital Optical Storage Management 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 A Files Added to System B Sample Installation for OpenVMS VAX Direct Connect C Sample Installation for OpenVMS VAX Address Mode D Sample Installation for OpenVMS VAX LUN Mode E Sample Installation for OpenVMS VAX HSx 1 ______________________________________________________________ Introduction The Digital Optical Storage Management Software package allows members of the VAX[TM] and Alpha[TM] families to access high-capacity optical disk drives incorporated with jukebox mechanisms. Digital Optical Storage Management Software cooperates with the OpenVMS[TM] operating system to provide transparent access to volumes in the jukebox from an OpenVMS host. This document contains instructions for the installation of OSMS on the OpenVMS operating system. Intended Audience This manual is intended for system managers. When to Install OSMS OSMS needs to be installed in the following conditions: o When OSMS is purchased and used for the first time. o When operating system version is changed, upgraded, or downgraded. o When software updates of OSMS are received. Related Manuals For additional information on installing Digital[TM] OSMS, 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 Management Software Jukebox Installation The jukebox and SCSI host adapter, if applicable, must be installed and operating properly before installing the OSMS software. Any problems encountered during the hardware installation phase should be corrected before the OSMS software is installed. Please refer to the OSMS for OpenVMS User's Manual, SCSI bus configuration rules, to ensure the hardware is set up properly before performing the software installation. Also, if connecting to an HSD, or HSJ adapter, make sure the HSD, or HSJ recognizes the jukebox before installing the software. Reference the HSD or HSJ Controller User Guide for further details. If HSJ: To configure a jukebox at the HSJ CLI prompt, For each optical drive in the jukebox, you must type the following two lines: The "PTL" (PORT, TARGET, LUN) format is used. The LUN value is always zero. Information Required for Installation You will need to know specific information about your hardware configuration before you can begin installing the OSMS software. In particular, you must be able to answer the following questions: o What model jukebox is installed? o How many optical disk drives are installed in the jukebox? Preparing to Install Digital Optical Storage Management Software 2-1 Preparing to Install Digital Optical Storage Management Software Information Required for Installation o What are the SCSI Target Ids and Logical Unit Numbers (if any) for the robotics mechanism and the drives installed in the jukebox? o What SCSI adapter in the computer and it's associated PKxy: device designation is being used to interface to the jukebox and drives? If you do not have this information available, refer to the installation information supplied with the equipment or contact your system manager. Registering the License PAK You must register the License Product Authorization Key (PAK) before you begin installing the OSMS software. The installation procedure uses information contained in the PAK to determine some of the characteristics of the installation. If an OSMS PAK (OSMS-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 (OSMS-5) $ $ license load/producer=PERCEPTICS (OSMS-5) The will cause the units to be added together, allowing the system to use the entire capacity of all of your licenses. Preparing to Install Digital Optical Storage Management Software Preparing to Install Digital Optical Storage Management Software 2.4 Installation Procedure Requirements Installation Procedure Requirements The following sections discuss various requirements for installing the OSMS 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. After installation and reboot, cache creation and initialization will take place. Time for cache creation and initialization will vary. For example, for the Digital[TM] RW536 jukebox that supports 144 slots (or 288 optical volumes), if 144 slots are specified and the cache file size is 256 blocks each, the cache creation and initialization process will take approximately 15 minutes. Privileges To install the Digital Optical Storage Management 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 OSMS 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 OSMS 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 Preparing to Install Digital Optical Storage Management Software 2-3 Preparing to Install Digital Optical Storage Management Software Installation Procedure Requirements 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." OSMS requires one cache file for each optical volume that will be made known to OpenVMS. For example, if you have a Digital RW524 jukebox, then 16 optical disks are available, with two optical volumes per disk-one optical volume per side. Therefore, 32 optical volumes will be made known to OpenVMS (JBA0:, JBA1:, . . . , JBA31:) and 32 cache files will be required. 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. ______________________________________________________ Process Account Quotas to Install Software The account you use to install the OSMS 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 Preparing to Install Digital Optical Storage Management Software Preparing to Install Digital Optical Storage Management Software 2.4 Installation Procedure Requirements user account quotas. For information on modifying account quotas, see the description of the Authorize utility in the OpenVMS documentation set. Process Account Quotas to Start Jukebox Software The process quotas, FILLM and BYTLM, and the sysgen parameter, CHANNELCNT may have to be adjusted before the software can be started. The values for all of these items vary based on the jukebox configuration. The FILLM process quota and CHANNELCNT system parameter must be set to a value equal to the number of volumes plus four. The number of volumes for all Digital jukeboxes will be equal to the number of storage slots times two. For example, if a Digital RW536 jukebox is installed and 144 slots are specified then the number of volumes equals 288, (144 slots * 2). Using this volume value then the value for the FILLM process quota and the CHANNELCNT sysgen parameter must be at least 292, (288 plus 4). The OpenVMS Sysgen utility is used to verify and change system parameters. For information on modifying system parameters, see the description of the Sysgen utility in the OpenVMS documentation set. ________________________ Note ________________________ Before any changes to the CHANNELCNT system parameter will become effective, the system must be shutdown and restarted. ______________________________________________________ The BYTLM account quota must be set to at least the number of volumes * 192. The OSMS software creates a cache file for each volume. The OpenVMS operating system allocates memory for a Window Control Block (WCB). that is associated with each cache file. The size allocated for each WCB, for OpenVMS 6.2, is 192 bytes. ________________________ Note ________________________ The values specified for FILLM, BYTLM and CHANNELCNT are minimums. These minimums were determined for a Preparing to Install Digital Optical Storage Management Software 2-5 Preparing to Install Digital Optical Storage Management Software Installation Procedure Requirements system used only to operate the OSMS software. The requirements of your system may be higher. ______________________________________________________ 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 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 Install Digital Optical Storage Management Software Preparing to Install Digital Optical Storage Management Software 2.6 Preparing to Reboot the System Preparing to Reboot the System In general, OSMS will require you to reboot the system before it can start operation. The installation procedure can complete successfully without rebooting the system, but OSMS 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. When the installation is completed, run the Installation Verification Procedure (IVP) using the following command: $ @SYS$TEST:LASERSTAR_IVP Shutting Down OSMS If you have an existing version of OSMS running on the system, you must shut down OSMS 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 JB/MOUNTED). Preparing to Install Digital Optical Storage Management Software 2-7 Preparing to Install Digital Optical Storage Management Software Shutting Down OSMS o Shut down OSMS using the following commands: $ RUN SYS$SYSTEM:JKCONFIG JKCONFIG> REMOVE JBA JKCONFIG> EXIT or $ RUN SYS$SYSTEM:JBCONFIG <-- If version 3.0 or earlier JBCONFIG> REMOVE JBA JBCONFIG> 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:JB*_CACHE_*.WRK;* Preparing to Install Digital Optical Storage Management Software 3 ______________________________________________________________ Installing the Digital Optical Storage Management 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 OSMS 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 OSMS software has been installed, the release notes are located in the following file: SYS$HELP:LASERSTAR034.RELEASE_NOTES Running the Installation Verification Procedure (IVP) The IVP for the OSMS software verifies the installation. After the installation is complete, you should run the IVP to ensure that the OSMS 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:LASERSTAR_IVP Installing the Digital Optical Storage Management Software 3-1 Installing the Digital Optical Storage Management 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 OSMS 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 OSMS on OpenVMS/VAX systems, use the following installation name: OSMSV034 For OSMS on OpenVMS/Alpha (Alpha[TM]) systems, use the following installation name: OSMSA034 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 Management Software Installing the Digital Optical Storage Management Software 3.2 The Installation Procedure The following command invokes VMSINSTAL to install the OSMS 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 OSMSV034 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 OSMS 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 Management Software 3-3 Installing the Digital Optical Storage Management 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 OSMS 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: OSMSV V3.4 Beginning installation of OSMSV 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 Management Software Installing the Digital Optical Storage Management 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:LASERSTAR034.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 Management Software 3-5 Installing the Digital Optical Storage Management Software The Installation Procedure The OSMS 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 various configuration options and their associated startup command files. o Produce additional startup command files, without reinstalling the software, if you have multiple jukeboxes. 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]? Installing the Digital Optical Storage Management Software Installing the Digital Optical Storage Management Software 3.2 The Installation Procedure 9. Specifying which jukebox is being installed The installation will then ask if this is the first jukebox being installed on your system: * Is this the first jukebox installed on your system [YES]? If this is the first (or only) jukebox installed on your system, press . Otherwise, enter NO. If you enter NO, then the installation will ask you to specify which jukebox is being installed: The first jukebox has the device designation JBA, with a controller designation of A; the second jukebox has the device designation JBB, with a controller designation of B; and so forth. You must now enter the one-character controller designation to use for this jukebox. * What is the controller designation for this jukebox [B]? If you are installing your second jukebox, enter B; if you are installing your third jukebox, enter C; and so forth. ________________________ Note ________________________ The jukebox device designation is not related to the SCSI controller's device designation. For example, an installation with two jukeboxes may have JBA and JBB both connected to PKB0:. ______________________________________________________ 10. Specifying the jukebox model The installation will then ask you to select which jukebox model is being installed by presenting a list of the supported configurations. You must answer with the number corresponding to the jukebox being installed. Select which jukebox is being installed from the following list: Installing the Digital Optical Storage Management Software 3-7 Installing the Digital Optical Storage Management Software The Installation Procedure 1. RW504 jukebox (1 drive with 16 slots) 2. RW510 jukebox (2 drives with 32 slots) 3. RW514 jukebox (4 drives with 88 slots) 4. RW516 jukebox (4 drives with 144 slots) 5. RW524 jukebox (1 drive with 16 slots) 6. RW525 jukebox (1 drive with 16 slots) 7. RW530 jukebox (2 drives with 32 slots) 8. RW531 jukebox (2 drives with 32 slots) 9. RW532 jukebox (4 drives with 64 slots) 10. RW534 jukebox (4 drives with 88 slots) 11. RW536 jukebox (4 drives with 144 slots) 12. RW545 jukebox (1 drive with 16 slots) 13. RW546 jukebox (2 drives with 16 slots) 14. RW551 jukebox (2 drives with 32 slots) 15. RW552 jukebox (4 drives with 64 slots) 16. RW554 jukebox (4 drives with 88 slots) 17. RW555 jukebox (4 drives with 128 slots) 18. RW556 jukebox (4 drives with 144 slots) 19. RW557 jukebox (6 drives with 238 slots) * Which jukebox is being installed (1-19): 11. Specifying the number of volumes If the jukebox you specified has more than 20 slots, you are offered the option to configure your system with fewer optical volumes. If you will not be using all of the slots in the jukebox, choosing fewer optical volumes will save some memory in your system and reduce the number of write-behind cache files that will be required. One cache file will be required for each optical volume selected at this point. (See Section 2.4.4.) For example, if you selected item 2 from the previous question (corresponding to a Digital RW510 /RW530 jukebox), you will see the following: Since your disks are double-sided, there are two volumes per optical disk. You have a total of 32 slots (64 volumes) available in your jukebox, corresponding to volumes JBA0: through JBA63:. By default, all volumes will be configured at boot time. If you won't be using all the volumes, you may choose to configure fewer JB devices. The number of volumes that are configured are obvious in the LASERSTAR$STARTUP_A.COM command file, so you can change the value after installation if you desire. Installing the Digital Optical Storage Management Software Installing the Digital Optical Storage Management Software 3.2 The Installation Procedure * Enter the number of volumes to configure at boot time [64]: 12. Setting the default minimum swap interval (MINSWAP) The minimum swap interval (MINSWAP) is the amount of time, in seconds, that a volume is in a drive before it is eligible to be swapped out to let another volume use that drive. The default value is 15 seconds. If infrequent but long I/Os are often performed on the optical volumes, then you may want to make this value larger. If many users need access to different optical volumes for relatively short I/Os, then you may want to make this value smaller. The value you specify here is the default value for MINSWAP, when the system is initialized. It can be changed after startup by using the JBUTIL SET PARAMETER /MINSWAP=n command. The smallest value for MINSWAP is 5 seconds; the largest is 32767. * What should the default minimum swap interval be set to [15]: 13. 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:" Installing the Digital Optical Storage Management Software 3-9 Installing the Digital Optical Storage Management Software The Installation Procedure $ ! $ ! 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 14. 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 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]: 15. 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: Installing the Digital Optical Storage Management Software Installing the Digital Optical Storage Management Software 3.2 The Installation Procedure 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]: 16. Specifying the SCSI addressing mode Some devices support two SCSI addressing modes. The mode is determined via a hardware switch selection. These modes are SCSI Address mode and SCSI Lun mode. If the device you are configuring supports both of these modes then you will be asked to select in which mode the device will operate. This device supports two modes of SCSI bus device addressing: o SCSI Address mode (default) o SCSI Lun mode SCSI bus device addresses are made up of their SCSI bus target id and their logical unit number or Lun. When this device is used in SCSI Address mode, the SCSI bus target id of each individual device may be set by the user but its associated logical unit number will always be set to zero. When this device is used in SCSI Lun mode, the SCSI bus target id and the associated logical unit number of each device may be set by the user. If you chose SCSI Address mode you will only be prompt for the SCSI target ids of the devices. If you chose SCSI Lun mode you will be asked a different set of questions. The only valid answers are ADDRESS, LUN, A, or L. * Which mode do you wish to use for this device [ADDRESS/LUN]" 17. Requesting the same target for all device when in SCSI Lun mode. If your configuration has all the devices associated with the same SCSI bus target id then by answering the next question yes will minimize the amount of SCSI addressing questions asked. * Do you wish to use the same target ids for all devices [Y]? Installing the Digital Optical Storage Management Software 3-11 Installing the Digital Optical Storage Management Software The Installation Procedure Answer this question no if you want to enter both the SCSI target id and SCSI logical unit number for each device. By answering this question yes, you will only be prompt to enter the SCSI target id once, and then you will be prompt for only the logical unit numbers for each device. 18. 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 and the jukebox. There will typically be one SCSI target id for each optical disk drive and another SCSI target id for the jukebox robotic mechanism. 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 associated with the jukebox. Enter or the word EXIT to indicate that the last SCSI target id has been entered. 19. Specifying SCSI device Logical Unit Numbers (LUNs) If the devices you are configuring support address via Logical Unit Numbers, (LUNs), you will also be asked to specify the LUN for each device. An information message appears that describes some of the information mentioned above. The installation procedure displays as follows: A SCSI device has a unique SCSI target id assigned to allow it to 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 entries you have made and restart the prompting for the first SCSI target id. Installing the Digital Optical Storage Management Software Installing the Digital Optical Storage Management Software 3.2 The Installation Procedure If the devices you are configuring support LUNs, then the following message will also appear: Your configuration may also be setup to allow the Logical Unit Number, or LUN of each device to be set. You may chose an addressing method which allows you to set the SCSI target id and the logical unit number for each device. 20. Entering the SCSI target ids and the Logical Unit Numbers After all the text has been displayed, that attempted to explain the SCSI addressing mode that your configuration supports, you will be asked to enter the SCSI address values for your configuration. 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: 3 Creating OpenVMS device unit number 300 for SCSI target id 2 and LUN 0 * Enter the SCSI target id of the fourth optical SCSI device or CTRL/Z if done: The OpenVMS Device unit numbers created are: 100 200 300 * Which OpenVMS device unit number will be used for the jukebox robotics device: 300 21. Specifying OpenVMS devices for each drive Installing the Digital Optical Storage Management Software 3-13 Installing the Digital Optical Storage Management Software The Installation Procedure 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. See the jukebox manufacturer's documentation to determine which drive is considered drive 1, which drive is drive 2, and so on. 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 22. Specifying OpenVMS devices for jukebox robotics mechanism You must now specify which OpenVMS device is associated with the jukebox robotics mechanism. The SCSI addresses, entered earlier, were used to determine the OpenVMS device designation. In the previous example, the SCSI target id 3 was specified for the connection to the SCSI controller PKB0. The OpenVMS device unit number created was shown to be 300, also the value 300 was entered as the unit number to be used for the robotics mechanism. The corresponding device designation based on this information is RZB300. The installation procedure will display the known device designations for the jukebox mechanism. You will only be allowed to select devices shown in the list. Installing the Digital Optical Storage Management Software Installing the Digital Optical Storage Management Software 3.2 The Installation Procedure For example, the installation would proceed as shown below, assuming you have the following configuration: o Digital RW530 jukebox with two drives o Drive 1 has a SCSI target id of 1 o Drive 2 has a SCSI target id of 2 o The jukebox controller has a SCSI target id of 3 o They are connected to the second SCSI controller in your computer (PKB0) You must specify which OpenVMS device is associated with each drive. Select your response to the following questions from this list: WDB100 WDB200 * What OpenVMS device is connected to drive 1: WDB100 * What OpenVMS device is connected to drive 2: WDB200 You must specify which OpenVMS device is associated with the jukebox robotics mechanism. Select your response to the following questions from this list: RZB300 * What RZ device is connected to the jukebox robotic mechanism: RZB300 23. 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 pseudo device, two per slot in jukebox. o All cache files will be the same size for each pseudo device in the same jukebox. Cache file sizes can be different between jukeboxes. 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.) Installing the Digital Optical Storage Management Software 3-15 Installing the Digital Optical Storage Management Software The Installation Procedure 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. One cache file is created for each optical volume that will be made known to OpenVMS. For example, if you have a Digital Model RW504 jukebox, then 16 optical disks are available, with two optical volumes per disk-one optical volume per side. Therefore, 32 optical volumes will be made known to OpenVMS (JBA0:, JBA1:, . . . , JBA31:) and 32 cache files will be required. Specifying cache file size smaller than the default presented at installation time can only be done by editing the LASERSTAR$STARTUP_x.COM file after the installation is complete. Replace the x with the controller letter designation you choose for the jukebox, such as A, B, or C. You must answer the following questions to determine the cache file size and location: * How large should the cache files be [4]: Installing the Digital Optical Storage Management Software Installing the Digital Optical Storage Management Software 3.2 The Installation Procedure 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 OSMSV 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 OSMSV V3.4 has failed. 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. Installing the Digital Optical Storage Management Software 3-17 Installing the Digital Optical Storage Management Software The Installation Procedure 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 OSMS software: o Starting OSMS o Running the installation verification procedure (IVP) o Editing the system startup file o Editing the system shutdown file o Modification if using OpenVMS/Alpha o Modification if using OpenVMS/VAX Starting OSMS After installation is completed and a reboot was performed (if necessary), then you must start OSMS by invoking the following command: $ @SYS$STARTUP:LASERSTAR$STARTUP_x.COM Replace the "x" with the controller letter designation you choose for the jukebox, such as A, B, or C. Running the IVP The IVP for the OSMS software verifies the installation. After the installation is completed, you should run the IVP to ensure that the OSMS software is installed properly. Successful completion of the IVP requires that the jukebox be installed and operational. Installing the Digital Optical Storage Management Software Installing the Digital Optical Storage Management Software 3.3 Post Installation Procedures 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:LASERSTAR_IVP The following is sample output similar to the execution of the IVP: $ @SYS$TEST:LASERSTAR_IVP Starting the Installation Verification Procedure for LASERSTAR If the following display shows any devices that are "Unknown", then the installation may not have been successful. Check the device SCSI target ids, cabling, and proper operation of the device. Checking device _NODE1$WDB100: (device code 46) HP 1716 or DEC RWZ5x multifunction drive Device uses 5-1/4 media Write verify command used by default Device is a multifunction (WORM and M/O) device Device uses the SCSI-2 command set Checking device _NODE1$WDB200: (device code 46) HP 1716 or DEC RWZ5x multifunction drive Device uses 5-1/4 media Write verify command used by default Device is a multifunction (WORM and M/O) device Device uses the SCSI-2 command set Checking device _NODE1$RZB300: (device code 21) HP/DEC Jukebox Device uses 5-1/4 media Device is a jukebox Mode sense determines internal device addresses Disable removing media from the device The following display should show the number of drives in your jukebox. If the number of drives expected is not displayed or there is an error generating the display, contact your system manager. Installing the Digital Optical Storage Management Software 3-19 Installing the Digital Optical Storage Management Software Post Installation Procedures Drive JB unit Drive Number in drive Status ------------------------------------ Drive(0): EMPTY (Online) Drive(1): EMPTY (Online) Installation Verification Procedure for LASERSTAR completed. Editing the System Startup File You must edit the system startup file, SYS$MANAGER:SYSTARTUP_VMS.COM, to enable the OSMS software to function properly after a system reboot. Please add the following command line to the system startup file: $ @SYS$STARTUP:LASERSTAR$STARTUP_x.COM Replace the x with the controller letter designation you choose for the jukebox, such as A, B, or C. Editing the System Shutdown File You must edit the system shutdown file (SYS$MANAGER:SYSHUTDWN.COM) to enable the Digital Optical Storage Management Software to function properly during a system shutdown. Please add the following command line to the system shutdown file: $ @SYS$MANAGER:LASERSTAR$SHUTDOWN.COM 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 Installing the Digital Optical Storage Management Software Installing the Digital Optical Storage Management Software 3.3 Post Installation Procedures 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. 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 Management Software 3-21 A ______________________________________________________________ Files Added to System When installed, the OSMS software adds the following system files on the VAX: SYS$LOADABLE_IMAGES:JKDRIVER.EXE SYS$SHARE:JBUAPI.EXE SYS$SYSTEM:HEADER.EXE SYS$SYSTEM:JBSHOW.EXE SYS$SYSTEM:JKCONFIG.EXE SYS$SYSTEM:JBUTIL.EXE SYS$SYSTEM:ODUTIL.EXE SYS$SYSTEM:SCSI.EXE SYS$SYSTEM:W11AACP.EXE SYS$TEST:LASERSTAR_IVP.COM SYS$MANAGER:LASERSTAR$SHUTDOWN.COM On OpenVMS/Alpha systems, the OSMS software adds the following system files: SYS$LOADABLE_IMAGES:JKDRIVER.EXE SYS$SYSTEM:HEADER.EXE SYS$SHARE:JBUAPI.EXE SYS$SYSTEM:JBSHOW.EXE SYS$SYSTEM:JKCONFIG.EXE SYS$SYSTEM:JBUTIL.EXE SYS$SYSTEM:SCSI.EXE SYS$TEST:LASERSTAR_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: PERCEPTICS$DEVICES.COM PERCEPTICS$OPTICDEF.COM PERCEPTICS$VERSIONS.COM Files Added to System A-1 Files Added to System 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 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 installation for OpenVMS VAX direct connect Enter the products to be processed from the first distribution volume set. * Products: osmsv034 * Enter installation options you wish to use (none): The following products will be processed: OSMSV V3.4 Beginning installation of OSMSV V3.4 at 12:44 %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 installation for OpenVMS VAX direct connect B-1 Sample 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]? * Is this the first jukebox installed on your system [YES]? A file called LASERSTAR$STARTUP_A.COM is required at boot time to initialize LASERSTAR. An existing version of the LASERSTAR$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. Select which jukebox is being installed from the following list: 1. RW504 jukebox (1 drive with 16 slots) 2. RW510 jukebox (2 drives with 32 slots) 3. RW514 jukebox (4 drives with 88 slots) 4. RW516 jukebox (4 drives with 144 slots) 5. RW524 jukebox (1 drive with 16 slots) 6. RW525 jukebox (1 drive with 16 slots) 7. RW530 jukebox (2 drives with 32 slots) 8. RW531 jukebox (2 drives with 32 slots) 9. RW532 jukebox (4 drives with 64 slots) 10. RW534 jukebox (4 drives with 88 slots) 11. RW536 jukebox (4 drives with 144 slots) 12. RW545 jukebox (1 drive with 16 slots) 13. RW546 jukebox (2 drives with 16 slots) 14. RW551 jukebox (2 drives with 32 slots) 15. RW552 jukebox (4 drives with 64 slots) 16. RW554 jukebox (4 drives with 88 slots) 17. RW555 jukebox (4 drives with 128 slots) 18. RW556 jukebox (4 drives with 144 slots) 19. RW557 jukebox (6 drives with 238 slots) * Which jukebox is being installed (1-19): 13 The RW546 jukebox is being configured with 2 drives, 16 slots, and 32 optical disk volumes (JBA0: through JBA31:). The minimum swap interval (MINSWAP) is the amount of time, in seconds, that a volume is in a drive before it is eligible to be swapped out to let another volume use that drive. The default value is 15 seconds. Sample installation for OpenVMS VAX direct connect Sample installation for OpenVMS VAX direct connect If infrequent but long I/O's are often performed on the optical volumes, then you may want to make this value larger. If many users need access to different optical volumes for relatively short I/O's, then you may want to make this value smaller. The value you specify here is the default value for MINSWAP when the system is initialized. It can be changed after startup by using the JBUTIL SET PARAMETER /MINSWAP=n command. The smallest value for MINSWAP is 5 seconds; the largest is 32767. * What should the default minimum swap interval be set to [15]: This software works with the following SCSI interfaces: 1. Any supported Digital Equipment SCSI controller 2. HSC, HSD, or HSJ controller * Which SCSI interface from the above list is being used (1 or 2) [1]: 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]: %OSMSV-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: $ ! $ ! WD$STARTUP_PKB file for OSDSV V3.4 created 11-NOV-1996 17:17:44.93 $ ! $ WRITE SYS$OUTPUT "%WDDRIVER-I-CONNECTWD, connecting WD devices... $ RUN SYS$SYSTEM:SYSGEN CONNECT WDB300/NOADAPTER ! SCSI ID=3 LUN=0 $ EXIT * Do you want to modify this WD$STARTUP_PKB.COM file [N]? Y Sample installation for OpenVMS VAX direct connect B-3 Sample 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: 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: 3 Creating OpenVMS device unit number 300 for SCSI target id 3 and LUN 0 * Enter the SCSI target id of the fourth optical SCSI device or CTRL/Z if done: exit The OpenVMS Device unit numbers created are: 100 200 300 * Which OpenVMS device unit number will be used for the jukebox robotics device: 100 %OSMSV-I-DEFINE, defining device RZB100 for ! SCSI ID=1 LUN=0 %OSMSV-I-DEFINE, defining device WDB200 for ! SCSI ID=2 LUN=0 %OSMSV-I-DEFINE, defining device WDB300 for ! SCSI ID=3 LUN=0 %OSMSV-I-CREATEFILE, created SYS$MANAGER:WD$STARTUP_PKB.COM %OSMSV-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. Sample installation for OpenVMS VAX direct connect Sample installation for OpenVMS VAX direct connect %OSMSV-I-LINK, Linking RZDRIVER for OpenVMS 6.2 %OSMSV-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: WDB200 WDB300 * What OpenVMS device is connected to optical drive 1: wdb200 * What OpenVMS device is connected to optical drive 2: wdb300 You must specify which OpenVMS device is associated with the jukebox robotics mechanism. Select your response to the following questions from this list: RZB100 * What RZ device is connected to the jukebox robotic mechanism: rzb100 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. Sample installation for OpenVMS VAX direct connect B-5 Sample installation for OpenVMS VAX direct connect 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 32 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]: * Where should the cache files be located [SYS$SYSTEM]: LASERSTAR$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. 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:LASERSTAR_IVP %OSMSV-I-LINK, Linking JKDRIVER for OpenVMS 6.2 %OSMSV-I-LINK, Linking JKCONFIG for OpenVMS 6.2 %OSMSV-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 LASERSTAR$SHUTDOWN.COM will be copied to the SYS$MANAGER directory. It should be added to your site shutdown procedure and be invoked every time the system is shutdown. %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 Sample installation for OpenVMS VAX direct connect Sample installation for OpenVMS VAX direct connect Installation of OSMSV V3.4 completed at 12:50 Enter the products to be processed from the next distribution volume set. * Products: ^Z VMSINSTAL procedure done at 12:50 Sample installation for OpenVMS VAX direct connect B-7 C ______________________________________________________________ Sample installation for OpenVMS/VAX, Address Mode Enter the products to be processed from the first distribution volume set. * Products: osmsv034 * Enter installation options you wish to use (none): The following products will be processed: OSMSV V3.4 Beginning installation of OSMSV V3.4 at 12:56 %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 installation for OpenVMS/VAX, Address Mode C-1 Sample installation for OpenVMS/VAX, Address Mode * 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]? * Is this the first jukebox installed on your system [YES]? A file called LASERSTAR$STARTUP_A.COM is required at boot time to initialize LASERSTAR. An existing version of the LASERSTAR$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. Select which jukebox is being installed from the following list: 1. RW504 jukebox (1 drive with 16 slots) 2. RW510 jukebox (2 drives with 32 slots) 3. RW514 jukebox (4 drives with 88 slots) 4. RW516 jukebox (4 drives with 144 slots) 5. RW524 jukebox (1 drive with 16 slots) 6. RW525 jukebox (1 drive with 16 slots) 7. RW530 jukebox (2 drives with 32 slots) 8. RW531 jukebox (2 drives with 32 slots) 9. RW532 jukebox (4 drives with 64 slots) 10. RW534 jukebox (4 drives with 88 slots) 11. RW536 jukebox (4 drives with 144 slots) 12. RW545 jukebox (1 drive with 16 slots) 13. RW546 jukebox (2 drives with 16 slots) 14. RW551 jukebox (2 drives with 32 slots) 15. RW552 jukebox (4 drives with 64 slots) 16. RW554 jukebox (4 drives with 88 slots) 17. RW555 jukebox (4 drives with 128 slots) 18. RW556 jukebox (4 drives with 144 slots) 19. RW557 jukebox (6 drives with 238 slots) * Which jukebox is being installed (1-19): 19 Since your disks are double-sided, there are two volumes per optical disk. You have a total of 238 slots (476 volumes) available in your jukebox, corresponding to volumes JBA0: through JBA475:. Sample installation for OpenVMS/VAX, Address Mode Sample installation for OpenVMS/VAX, Address Mode By default, all volumes will be configured at boot time. If you won't BE using all the volumes, you may choose to configure fewer JB devices. The number of volumes that are configured are obvious in the LASERSTAR$STARTUP_A command file, so you can change the value after installation if you desire. * Enter the number of volumes to configure at boot time [476]: The RW557 jukebox is being configured with 6 drives, 238 slots, and 476 optical disk volumes (JBA0: through JBA475:). The minimum swap interval (MINSWAP) is the amount of time, in seconds, that a volume is in a drive before it is eligible to be swapped out to let another volume use that drive. The default value is 15 seconds. If infrequent but long I/O's are often performed on the optical volumes, then you may want to make this value larger. If many users need access to different optical volumes for relatively short I/O's, then you may want to make this value smaller. The value you specify here is the default value for MINSWAP when the system is initialized. It can be changed after startup by using the JBUTIL SET PARAMETER /MINSWAP=n command. The smallest value for MINSWAP is 5 seconds; the largest is 32767. * What should the default minimum swap interval be set to [15]: This software works with the following SCSI interfaces: 1. Any supported Digital Equipment SCSI controller 2. HSC, HSD, or HSJ controller * Which SCSI interface from the above list is being used (1 or 2) [1]: 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]: %OSMSV-I-PKDEV, devices will be configured on SCSI bus B (PKB0:) Sample installation for OpenVMS/VAX, Address Mode C-3 Sample installation for OpenVMS/VAX, Address Mode 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: $ ! $ ! WD$STARTUP_PKB file for OSMSV V3.4 created 12-NOV-1996 12:47:18.92 $ ! $ WRITE SYS$OUTPUT "%WDDRIVER-I-CONNECTWD, connecting WD devices... $ RUN SYS$SYSTEM:SYSGEN CONNECT RZB100/NOADAPTER ! SCSI ID=1 LUN=0 CONNECT WDB200/NOADAPTER ! SCSI ID=2 LUN=0 CONNECT WDB300/NOADAPTER ! SCSI ID=3 LUN=0 $ EXIT * Do you want to modify this WD$STARTUP_PKB.COM file [N]? Y This device supports two modes of SCSI bus device addressing: o SCSI Address mode (default) o SCSI Lun mode SCSI bus device addresses are made up of their SCSI bus target id and their logical unit number or Lun. When this device is used in SCSI Address mode, the SCSI bus target id of each individual device may be set by the user but its associated logical unit number will always be set to zero. When this device is used in SCSI Lun mode, the SCSI bus target id and the associated logical unit number of each device may be set by the user. If you chose SCSI Address mode you will only be prompt for the SCSI target ids of the devices. If you chose SCSI Lun mode you will be asked a different set of questions. The only valid answers are ADDRESS, LUN, A, or L. * Which mode do you wish to use for this device [ADDRESS/LUN]: ADDRESS 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. Sample installation for OpenVMS/VAX, Address Mode Sample installation for OpenVMS/VAX, Address Mode 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: 0 Creating OpenVMS device unit number 000 for SCSI target id 0 and LUN 0 * Enter the SCSI target id of the second optical SCSI device or CTRL/Z if done: 1 Creating OpenVMS device unit number 100 for SCSI target id 1 and LUN 0 * Enter the SCSI target id of the third 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 fourth optical SCSI device or CTRL/Z if done: 3 Creating OpenVMS device unit number 300 for SCSI target id 3 and LUN 0 * Enter the SCSI target id of the fifth optical SCSI device or CTRL/Z if done: 4 Creating OpenVMS device unit number 400 for SCSI target id 4 and LUN 0 * Enter the SCSI target id of the sixth optical SCSI device or CTRL/Z if done: 5 Creating OpenVMS device unit number 500 for SCSI target id 5 and LUN 0 * Enter the SCSI target id of the seventh optical SCSI device or CTRL/Z if done: 7 ID 7 may conflict with your host controller Creating OpenVMS device unit number 700 for SCSI target id 7 and LUN 0 The OpenVMS Device unit numbers created are: Sample installation for OpenVMS/VAX, Address Mode C-5 Sample installation for OpenVMS/VAX, Address Mode 000 100 200 300 400 500 700 * Which OpenVMS device unit number will be used for the jukebox robotics device: 0 %OSMSV-I-DEFINE, defining device RZB000 for ! SCSI ID=0 LUN=0 %OSMSV-I-DEFINE, defining device WDB100 for ! SCSI ID=1 LUN=0 %OSMSV-I-DEFINE, defining device WDB200 for ! SCSI ID=2 LUN=0 %OSMSV-I-DEFINE, defining device WDB300 for ! SCSI ID=3 LUN=0 %OSMSV-I-DEFINE, defining device WDB400 for ! SCSI ID=4 LUN=0 %OSMSV-I-DEFINE, defining device WDB500 for ! SCSI ID=5 LUN=0 %OSMSV-I-DEFINE, defining device WDB700 for ! SCSI ID=7 LUN=0 %OSMSV-I-CREATEFILE, created SYS$MANAGER:WD$STARTUP_PKB.COM %OSMSV-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. %OSMSV-I-LINK, Linking RZDRIVER for OpenVMS 6.2 %OSMSV-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: WDB100 WDB200 WDB300 WDB400 WDB500 WDB700 Sample installation for OpenVMS/VAX, Address Mode Sample installation for OpenVMS/VAX, Address Mode * What OpenVMS device is connected to optical drive 1: wdb100 * What OpenVMS device is connected to optical drive 2: wdb200 * What OpenVMS device is connected to optical drive 3: wdb300 * What OpenVMS device is connected to optical drive 4: wdb400 * What OpenVMS device is connected to optical drive 5: wdb500 * What OpenVMS device is connected to optical drive 6: wdb700 You must specify which OpenVMS device is associated with the jukebox robotics mechanism. Select your response to the following questions from this list: RZB000 * What RZ device is connected to the jukebox robotic mechanism: rzb000 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 476 cache files will be required for your installation. Sample installation for OpenVMS/VAX, Address Mode C-7 Sample installation for OpenVMS/VAX, Address Mode 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]: * Where should the cache files be located [SYS$SYSTEM]: LASERSTAR$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. 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:LASERSTAR_IVP %OSMSV-I-LINK, Linking JKDRIVER for OpenVMS 6.2 %OSMSV-I-LINK, Linking JKCONFIG for OpenVMS 6.2 %OSMSV-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 LASERSTAR$SHUTDOWN.COM will be copied to the SYS$MANAGER directory. It should be added to your site shutdown procedure and be invoked every time the system is shutdown. %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 OSMSV V3.4 completed at 13:03 Enter the products to be processed from the next distribution volume set. * Products: ^Z VMSINSTAL procedure done at 13:03 Sample installation for OpenVMS/VAX, Address Mode D ______________________________________________________________ Sample installation for OpenVMS/Alpha, Lun Mode Enter the products to be processed from the first distribution volume set. * Products: osmsa034 * Enter installation options you wish to use (none): The following products will be processed: OSMSA V3.4 Beginning installation of OSMSA V3.4 at 12:23 %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 installation for OpenVMS/Alpha, Lun Mode D-1 Sample Installation for OpenVMS/Alpha, Lun Mode * 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]? * Is this the first jukebox installed on your system [YES]? A file called LASERSTAR$STARTUP_A.COM is required at boot time to initialize LASERSTAR. An existing version of the LASERSTAR$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. Select which jukebox is being installed from the following list: 1. RW504 jukebox (1 drive with 16 slots) 2. RW510 jukebox (2 drives with 32 slots) 3. RW514 jukebox (4 drives with 88 slots) 4. RW516 jukebox (4 drives with 144 slots) 5. RW524 jukebox (1 drive with 16 slots) 6. RW525 jukebox (1 drive with 16 slots) 7. RW530 jukebox (2 drives with 32 slots) 8. RW531 jukebox (2 drives with 32 slots) 9. RW532 jukebox (4 drives with 64 slots) 10. RW534 jukebox (4 drives with 88 slots) 11. RW536 jukebox (4 drives with 144 slots) 12. RW545 jukebox (1 drive with 16 slots) 13. RW546 jukebox (2 drives with 16 slots) 14. RW551 jukebox (2 drives with 32 slots) 15. RW552 jukebox (4 drives with 64 slots) 16. RW554 jukebox (4 drives with 88 slots) 17. RW555 jukebox (4 drives with 128 slots) 18. RW556 jukebox (4 drives with 144 slots) 19. RW557 jukebox (6 drives with 238 slots) * Which jukebox is being installed (1-19): 19 Since your disks are double-sided, there are two volumes per optical disk. You have a total of 238 slots (476 volumes) available in your jukebox, corresponding to volumes JBA0: through JBA475:. Sample installation for OpenVMS/Alpha, Lun Mode Sample installation for OpenVMS/Alpha, Lun Mode By default, all volumes will be configured at boot time. If you won't BE using all the volumes, you may choose to configure fewer JB devices. The number of volumes that are configured are obvious in the LASERSTAR$STARTUP_A command file, so you can change the value after installation if you desire. * Enter the number of volumes to configure at boot time [476]: The RW557 jukebox is being configured with 6 drives, 238 slots, and 476 optical disk volumes (JBA0: through JBA475:). The minimum swap interval (MINSWAP) is the amount of time, in seconds, that a volume is in a drive before it is eligible to be swapped out to let another volume use that drive. The default value is 15 seconds. If infrequent but long I/O's are often performed on the optical volumes, then you may want to make this value larger. If many users need access to different optical volumes for relatively short I/O's, then you may want to make this value smaller. The value you specify here is the default value for MINSWAP when the system is initialized. It can be changed after startup by using the JBUTIL SET PARAMETER /MINSWAP=n command. The smallest value for MINSWAP is 5 seconds; the largest is 32767. * What should the default minimum swap interval be set to [15]: This software works with the following SCSI interfaces: 1. Any supported Digital Equipment SCSI controller 2. HSC, HSD, or HSJ controller * Which SCSI interface from the above list is being used (1 or 2) [1]: 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]: %OSMSA-I-PKDEV, devices will be configured on SCSI bus B (PKB0:) Sample installation for OpenVMS/Alpha, Lun Mode D-3 Sample installation for OpenVMS/Alpha, Lun Mode 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: $ ! $ ! WD$STARTUP_PKB file for OSMSA V3.4 created 24-OCT-1996 09:46:47.19 $ ! $ WRITE SYS$OUTPUT "%WDDRIVER-I-CONNECTWD, connecting WD devices... $ RUN SYS$SYSTEM:SYSMAN IO AUTOCONFIG /SELECT=PK* ! Load SCSI Port Driver IO CONNECT RZB000/NOADAPTER ! SCSI ID=0 LUN=0 IO CONNECT WDB100/NOADAPTER ! SCSI ID=1 LUN=0 IO CONNECT WDB200/NOADAPTER ! SCSI ID=2 LUN=0 IO CONNECT WDB300/NOADAPTER ! SCSI ID=3 LUN=0 IO CONNECT WDB400/NOADAPTER ! SCSI ID=4 LUN=0 IO CONNECT WDB500/NOADAPTER ! SCSI ID=5 LUN=0 $ EXIT * Do you want to modify this WD$STARTUP_PKB.COM file [N]? YES This device supports two modes of SCSI bus device addressing: o SCSI Address mode (default) o SCSI Lun mode SCSI bus device addresses are made up of their SCSI bus target ID and their logical unit number or Lun. When this device is used in SCSI Address mode, the SCSI bus target id of each individual device may be set by the user but its associated logical unit number will always be set to zero. When this device is used in SCSI Lun mode, the SCSI bus target id and the associated logical unit number of each device may be set by the user. If you chose SCSI Address mode you will only be prompt for the SCSI target ids of the devices. If you chose SCSI Lun mode you will be asked a different set of questions. The only valid answers are ADDRESS, LUN, A, or L. * Which mode do you wish to use for this device [ADDRESS/LUN]: LUN Sample installation for OpenVMS/Alpha, Lun Mode Sample installation for OpenVMS/Alpha, Lun Mode If your configuration has all of the devices associated with the same SCSI bus target id then answer the next question yes and it will minimize the amount of questions you are asked. If you answer yes, you will only be prompt for the SCSI bus target id once. The remaining questions will be asking you for logical unit numbers associated with the target id. * Do you wish to use the same target id for all devices [Y]? YES A SCSI device has a unique SCSI target id assigned to allow it to 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. Your configuration may also be setup to allow the Logical Unit Number, or LUN of each device to be set. You may chose an addressing method which allows you to set the SCSI target id and the logical unit number for each device. * Enter the SCSI target id of the first optical SCSI device: 2 * Enter the Logical Unit Number (LUN) of the first optical SCSI device [0]: Creating OpenVMS device unit number 200 for SCSI target id 2 and LUN 0 * Enter the Logical Unit Number (LUN) of the second optical SCSI device or CTRL/Z if done [0]: 1 Creating OpenVMS device unit number 201 for SCSI target id 2 and LUN 1 * Enter the Logical Unit Number (LUN) of the third optical SCSI device or CTRL/Z if done [0]: 2 Creating OpenVMS device unit number 202 for SCSI target id 2 and LUN 2 * Enter the Logical Unit Number (LUN) of the fourth optical SCSI device or CTRL/Z if done [0]: 3 Creating OpenVMS device unit number 203 for SCSI target id 2 and LUN 3 * Enter the Logical Unit Number (LUN) of the fifth optical SCSI device or CTRL/Z if done [0]: 4 Sample installation for OpenVMS/Alpha, Lun Mode D-5 Sample installation for OpenVMS/Alpha, Lun Mode Creating OpenVMS device unit number 204 for SCSI target id 2 and LUN 4 * Enter the Logical Unit Number (LUN) of the sixth optical SCSI device or CTRL/Z if done [0]: 5 Creating OpenVMS device unit number 205 for SCSI target id 2 and LUN 5 * Enter the Logical Unit Number (LUN) of the seventh optical SCSI device or CTRL/Z if done [0]: 6 Creating OpenVMS device unit number 206 for SCSI target id 2 and LUN 6 The OpenVMS Device unit numbers created are: 200 201 202 203 204 205 206 * Which OpenVMS device unit number will be used for the jukebox robotics device: 200 %OSMSA-I-DEFINE, defining device RZB200 for ! SCSI ID=2 LUN=0 %OSMSA-I-DEFINE, defining device WDB201 for ! SCSI ID=2 LUN=1 %OSMSA-I-DEFINE, defining device WDB202 for ! SCSI ID=2 LUN=2 %OSMSA-I-DEFINE, defining device WDB203 for ! SCSI ID=2 LUN=3 %OSMSA-I-DEFINE, defining device WDB204 for ! SCSI ID=2 LUN=4 %OSMSA-I-DEFINE, defining device WDB205 for ! SCSI ID=2 LUN=5 %OSMSA-I-DEFINE, defining device WDB206 for ! SCSI ID=2 LUN=6 %OSMSA-I-CREATEFILE, created SYS$MANAGER:WD$STARTUP_PKB.COM %OSMSA-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 %OSMSA-I-CREATEFILE, created SYS$SYSDEVICE:[PERCEPTICS]WD$EXCLUDE_PKB.COM This command file should be invoked one time and the system should be rebooted before you start this software. %OSMSA-I-LINK, Linking RZDRIVER for OpenVMS 6.2 %OSMSA-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 Sample installation for OpenVMS/Alpha, Lun Mode Sample installation for OpenVMS/Alpha, Lun Mode 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 OpenVMS device is associated with each drive. Select your response to the following questions from this list: WDB201 WDB202 WDB203 WDB204 WDB205 WDB206 * What OpenVMS device is connected to optical drive 1: wdb201 * What OpenVMS device is connected to optical drive 2: wdb202 * What OpenVMS device is connected to optical drive 3: wdb203 * What OpenVMS device is connected to optical drive 4: wdb204 * What OpenVMS device is connected to optical drive 5: wdb205 * What OpenVMS device is connected to optical drive 6: wdb206 You must specify which OpenVMS device is associated with the jukebox robotics mechanism. Select your response to the following questions from this list: RZB200 * What RZ device is connected to the jukebox robotic mechanism: rzb200 476 cache files will be required for your installation. 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:. A location on your system disk is required if you plan to MSCP serve your disks to other cluster members. * How large should each cache file be [4]: * Where should the cache files be located [SYS$SYSTEM]: LASERSTAR$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 installation for OpenVMS/Alpha, Lun Mode D-7 Sample installation for OpenVMS/Alpha, Lun Mode 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:LASERSTAR_IVP %OSMSA-I-LINK, Linking JKDRIVER for OpenVMS 6.2 %OSMSA-I-LINK, Linking JKCONFIG for OpenVMS 6.2 %OSMSA-I-LINK, ... ignore LINK-W-MULDEF messages %LINK-W-MULDEF, symbol OTS$DIV_I multiply defined in module OTS$DIV file SYS$COMMON:[SYSLIB]STARLET.OLB;1 %LINK-W-MULDEF, symbol OTS$DIV_L multiply defined in module OTS$DIV file SYS$COMMON:[SYSLIB]STARLET.OLB;1 %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[PERCEPTICS]. %CREATE-I-EXISTS, SYS$SYSDEVICE:[PERCEPTICS] already exists LASERSTAR$SHUTDOWN.COM will be copied to the SYS$MANAGER directory. It should be added to you site shutdown procedure and be invoked every time the system is shutdown. %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... Installation of OSMSA V3.4 completed at 12:26 Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY Creating installation data file: VMI$ROOT:[SYSUPD]OSMSA034.VMI_DATA Enter the products to be processed from the next distribution volume set. * Products: ^Z VMSINSTAL procedure done at 12:27 Sample installation for OpenVMS/Alpha, Lun Mode E ______________________________________________________________ Sample installation for OpenVMS VAX HSx. The following products will be processed: OSMSV V3.4 Beginning installation of OSMSV V3.4 at 14:52 %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. * Will you allow a system shutdown after this product is installed [YES]? no Sample installation for OpenVMS VAX HSx. E-1 Sample installation for OpenVMS VAX HSx. 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]? * Is this the first jukebox installed on your system [YES]? A file called LASERSTAR$STARTUP_A.COM is required at boot time to initialize LASERSTAR. An existing version of the LASERSTAR$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. Select which jukebox is being installed from the following list: 1. RW504 jukebox (1 drive with 16 slots) 2. RW510 jukebox (2 drives with 32 slots) 3. RW514 jukebox (4 drives with 88 slots) 4. RW516 jukebox (4 drives with 144 slots) 5. RW524 jukebox (1 drive with 16 slots) 6. RW525 jukebox (1 drive with 16 slots) 7. RW530 jukebox (2 drives with 32 slots) 8. RW531 jukebox (2 drives with 32 slots) 9. RW532 jukebox (4 drives with 64 slots) 10. RW534 jukebox (4 drives with 88 slots) 11. RW536 jukebox (4 drives with 144 slots) 12. RW545 jukebox (1 drive with 16 slots) 13. RW546 jukebox (2 drives with 16 slots) 14. RW551 jukebox (2 drives with 32 slots) 15. RW552 jukebox (4 drives with 64 slots) 16. RW554 jukebox (4 drives with 88 slots) 17. RW555 jukebox (4 drives with 128 slots) 18. RW556 jukebox (4 drives with 144 slots) 19. RW557 jukebox (6 drives with 238 slots) * Which jukebox is being installed (1-19): 15 Since your disks are double-sided, there are two volumes per optical disk. You have a total of 64 slots (128 volumes) available in your jukebox, corresponding to volumes JBA0: through JBA127:. Sample installation for OpenVMS VAX HSx. Sample installation for OpenVMS VAX HSx. By default, all volumes will be configured at boot time. If you won't BE using all the volumes, you may choose to configure fewer JB devices. The number of volumes that are configured are obvious in the LASERSTAR$STARTUP_A command file, so you can change the value after installation if you desire. * Enter the number of volumes to configure at boot time [128]: The RW552 jukebox is being configured with 4 drives, 64 slots, and 128 optical disk volumes (JBA0: through JBA127:). The minimum swap interval (MINSWAP) is the amount of time, in seconds, that a volume is in a drive before it is eligible to be swapped out to let another volume use that drive. The default value is 15 seconds. If infrequent but long I/O's are often performed on the optical volumes, then you may want to make this value larger. If many users need access to different optical volumes for relatively short I/O's, then you may want to make this value smaller. The value you specify here is the default value for MINSWAP when the system is initialized. It can be changed after startup by using the JBUTIL SET PARAMETER /MINSWAP=n command. The smallest value for MINSWAP is 5 seconds; the largest is 32767. * What should the default minimum swap interval be set to [15]: 30 This software works with the following SCSI interfaces: 1. Any supported Digital Equipment SCSI controller 2. HSC, HSD, or HSJ controller * Which SCSI interface from the above list is being used (1 or 2) [1]: 2 A file called JU$STARTUP.COM is required at boot time to connect the JU devices. An existing version of the JU$STARTUP.COM file has been found on your system. If the devices 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 file is shown below: Sample installation for OpenVMS VAX HSx. E-3 Sample installation for OpenVMS VAX HSx. $ ! $ ! JU$STARTUP file for LSTARV V3.2 created 30-AUG-1994 09:03:39.12 $ ! $ WRITE SYS$OUTPUT "%JUDRIVER-I-CONNJU, connecting JU devices ..." $ ! $ RUN SYS$SYSTEM:SYSGEN CONNECT JUA0/NOADAPTER CONNECT JUA100/NOADAPTER $ ! $ ASSIGN /NOLOG JUA0 PERCEPTICS$JU_DEVICE $ ASSIGN /NOLOG $10$DUA6000 PERCEPTICS$DU_DEVICE $ MCR JUDRIVER_INIT $ ! $ ASSIGN /NOLOG JUA100 PERCEPTICS$JU_DEVICE $ ASSIGN /NOLOG $2$DUA4000 PERCEPTICS$DU_DEVICE $ MCR JUDRIVER_INIT $ ! $ EXIT * Do you want to create a new JU$STARTUP file [N]? Y JU devices are used to connect to an MSCP "command disk" controller, which is typically a SCSI robotic device. The command disk is visible to the system as a standard device designation, such as "HSC001$DUA6000". Note that the device is a "DU" device. The unit number is always 6000 or higher for devices connected to an HSC. The unit number is between 0 and 4095 for devices connected to an HSD or HSJ. For each command disk on your system, enter the DU device designation. Type CTRL/Z when there are no more command disks. * Enter the first DU device designation: $10$DUA6000 * Enter the next DU device or CTRL/Z if done: ^Z %OSMSV-I-DEFINE, defining device JUA0 %OSMSV-I-LINK, Linking JUDRIVER for OpenVMS 6.2 %OSMSV-I-LINK, Linking JUDRIVER_INIT ... %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 JUDRIVER will be copied into the file SYS$TEST:JUDRIVER_IVP.COM. It can be invoked at any time after the installation is completed. Sample installation for OpenVMS VAX HSx. Sample installation for OpenVMS VAX HSx. You must first specify which physical device is associated with each optical disk drive. Since they are connected via an MSCP controller, each drive will have a designation such as "HSC000$DKA100". Assuming the jukebox is connected to the HSC, HSD, or HSJ controller, when asked what OpenVMS device is connected to a drive, you should select the response from this list: $10$DKA100 $10$DKA200 $10$DKA300 $10$DKA400 * What OpenVMS device is connected to optical drive 1: $10$DKA100 * What OpenVMS device is connected to optical drive 2: $10$DKA200 * What OpenVMS device is connected to optical drive 3: $10$DKA300 * What OpenVMS device is connected to optical drive 4: $10$DKA400 You must then specify which OpenVMS device is associated with the jukebox robotics mechanism. Since the jukebox is connected via an HSC, HSD or HSJ controller, the jukebox robotics controller will have a designation such as "JUA0". When asked what OpenVMS device is connected to the jukebox robotic mechanism, you should select the response from this list: JUA0 * What OpenVMS device is connected to the jukebox robotic mechanism: jua0 Only rewritable optical media is supported when the optical subsystem is connected via an HSC, HSD, or HSJ controller. For these configurations the recommended cache file size is 4 blocks. o A cache file exists for each pseudo device. o All cache files will be the same size. o 128 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. * How large should each cache file be [4]: Sample installation for OpenVMS VAX HSx. E-5 Sample installation for OpenVMS VAX HSx. * Where should the cache files be located [SYS$SYSTEM]: LASERSTAR$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. 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:LASERSTAR_IVP %OSMSV-I-LINK, Linking JKDRIVER for OpenVMS 6.2 %OSMSV-I-LINK, Linking JKCONFIG for OpenVMS 6.2 %OSMSV-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 LASERSTAR$SHUTDOWN.COM will be copied to the SYS$MANAGER directory. It should be added to your site shutdown procedure and be invoked every time the system is shutdown. %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 OSMSV V3.4 completed at 15:00 Enter the products to be processed from the next distribution volume set. * Products: ^Z VMSINSTAL procedure done at 15:00 Sample installation for OpenVMS VAX HSx.