DECscheduler_for_VMS__________________________ Installation Order Number: AA-PBJ4B-TE January 1991 This guide explains how to install the DECscheduler software for the VMS operating system. Revision/Update Information: This document has been revised for this release. Operating System and Version: VMS Version 5.0 or higher. Software Version: DECscheduler Version 1.1 for VMS Digital Equipment Corporation __________________________________________________________ First Edition, March 1990 Second Edition, January 1991 The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document. The software described in this document is furnished under a license and may be used or copied only in accordance with the terms of such license. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013. © Digital Equipment Corporation 1990, 1991. All rights reserved. The Reader's Comments form supplied with this document requests your critical evaluation to assist in preparing future documentation. The following are trademarks of Digital Equipment Corporation: DECforms, DECscheduler, DECsupport, DECwindows, VAX, VMS, VT, VT100, VT300, and the DIGITAL logo. This document is available on CDROM. This document was prepared with VAX DOCUMENT, Version 1.2. ________________________________________________________________ Contents About This Guide......................................... v 1 Preparing to Install DECscheduler 1.1 Checking the Number and Contents of Your Media........................................ 1-1 1.2 Using Online Release Notes................... 1-1 1.3 General Requirements......................... 1-1 1.3.1 Operating System......................... 1-1 1.3.2 Software License......................... 1-2 1.3.3 VAXcluster Shared Disk................... 1-3 1.4 Installation Procedure Requirements.......... 1-3 1.4.1 Installation Time........................ 1-3 1.4.2 Privileges............................... 1-3 1.4.3 Disk Space............................... 1-4 1.4.4 Process Account Quotas................... 1-4 1.4.5 VMSINSTAL Requirements................... 1-5 1.4.6 System Disk Backup....................... 1-6 2 Installing DECscheduler 2.1 Halting the Installation..................... 2-1 2.2 The Installation Procedure................... 2-1 2.3 Comparing a New Installation with an Update Installation................................. 2-7 2.4 Error Recovery............................... 2-8 iii 3 After Installing DECscheduler 3.1 Starting DECscheduler........................ 3-1 3.2 Editing the System Startup and Shutdown Files........................................ 3-2 3.3 Rebooting the System......................... 3-3 3.4 Starting DECscheduler on a VAXcluster........ 3-3 3.5 Checking Your System Account Minimum Quotas.. 3-4 3.6 Checking the Minimum Privileges for DECscheduler................................. 3-4 3.7 Customizing Your System...................... 3-5 A Example of a New Installation B DECscheduler Logical Names C DECscheduler Installation Kit Files D Determining and Reporting Problems Index Tables B-1 DECscheduler Logicals.................... B-2 C-1 Installation Kit Files................... C-1 iv ________________________________________________________________ About This Guide This guide describes how to install the DECscheduler for VMS software. Audience This document is written for the following personnel: o Data center operations personnel, including system managers, system operators, and schedulers o Production application support personnel o Other VMS users This guide assumes that DECscheduler installers are familiar with the VMS operating system (Version 5.0 or higher) and system management functions such as setting system privileges and process account quotas. The guide also assumes familiarity with processing Digital command language (DCL) commands in both interactive and batch modes. Organization This guide has three chapters and four appendices: 1 - Preparing to Install DECscheduler Describes what you should know and do before you install DECscheduler. 2 - Installing DECscheduler Describes how to install DECscheduler. v 3 - After Installing DECscheduler Describes what you should do after you install DECscheduler. A - Example of a New Installation Provides a sample log of the procedure to install DECscheduler for the first time. B - DECscheduler Logical Names Lists the DECscheduler logical names. C - DECscheduler Installation Kit Files Lists the files provided in the installation kit. D - Determining and Reporting Problems Describes what to do if you discover an error in the DECscheduler software. Related Documents The following documents may be useful to readers of this guide: o Guide to VMS Software Installation Describes how to install layered products on VMS systems. o VMS Backup Utility Manual Describes how to back up your system disk before installing DECscheduler. o VMS License Management Utility Manual Describes how to use the License Management Facility (LMF) to register and load software licenses. o DECscheduler for VMS User Information Explains how to use DECscheduler with the DCL, DECwindows, or DECforms interface. o DECscheduler for VMS Programming Explains how to use the DECscheduler callable routines on the VMS operating system. vi Conventions The following conventions are used in this guide: __________________________________________________________ Convention_Meaning________________________________________ UPPERCASE In command examples, uppercase characters characters represent elements of a command that you should enter exactly as shown. Lowercase In command syntax examples, lowercase characters characters represent elements of a command for which you supply a value. For example: SCHED MODIFY job-specifier Red text In command examples, red text indicates user input. For example: * Products: SCHEDULER [ ] In the installation example, square brackets enclose the default answer for a question. Key names appear in a box. For control key sequences, you hold down the <_x_>_______key_and_press_another_key.______________ vii 1 ________________________________________________________________ Preparing to Install DECscheduler This chapter discusses the preparations and requirements necessary for installing DECscheduler. 1.1 Checking the Number and Contents of Your Media Your bill of materials (BOM) and indented bills report (BIL) specify the number and contents of your media. Make sure you verify the contents of your kit with this information. If you find missing or damaged parts in your kit, contact your Digital Customer Services representative. 1.2 Using Online Release Notes DECscheduler provides online release notes. You can obtain them during the installation or after the installation. To obtain them during the installation, see Section 2.2. To obtain them after the installation, type or print the file: SYS$HELP:SCHEDULER011.RELEASE_NOTES 1.3 General Requirements The following sections list three general requirements for installing and using DECscheduler. 1.3.1 Operating System DECscheduler runs on VMS Version 5.0 or higher. 1-1 Preparing to Install DECscheduler 1.3.2 Software License Before you can use the DECscheduler software, you must register and load your license for DECscheduler. To register and load your license, you use the VMS License Management Facility (LMF), available with Version 5.0 of the VMS operating system. The license registration information that you need is contained in the Product Authorization Key (PAK) shipped with the DECscheduler software. The PAK is a paper certificate that contains information about the software license required to run a particular piece of software. To register a license under VMS, first log in to 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 the PAK. or o Issue the DCL command, LICENSE REGISTER, with the appropriate qualifiers that correspond to information on the PAK. For complete information on using the LMF, see the VMS License Management Utility Manual in the VMS Version 5.0 documentation set. It is best to register your DECscheduler license before you perform the installation. During the installation, the installation procedure asks whether you have registered the DECscheduler license and loaded the appropriate authorization key. If you have not already done so, you can complete the installation; however, you will be unable to run the installation verification procedure (IVP) or use the DECscheduler software. 1-2 Preparing to Install DECscheduler 1.3.3 VAXcluster Shared Disk During the installation, you must specify the device where the product directory is located. Normally, you should accept the default answer of SYS$COMMON; however, if you are installing the DECscheduler in a local area VAXcluster with multiple boot nodes, you should specify a disk that is shared among all nodes in the cluster. 1.4 Installation Procedure Requirements The following sections list the DECscheduler installation procedure requirements. 1.4.1 Installation Time The installation should take from 10 to 20 minutes, depending on the type of media you use and your system configuration. 1.4.2 Privileges To install DECscheduler, you must be logged in to an account that has either the SETPRV privilege or at least the following privileges: o CMKRNL o WORLD o SYSPRV o SYSNAM o CMEXEC o SYSLCK o DETACH Note that VMSINSTAL turns off the BYPASS privilege when the installation starts. 1-3 Preparing to Install DECscheduler 1.4.3 Disk Space Installing DECscheduler requires at least 14,000 blocks of free storage disk space during the installation. After DECscheduler is installed, about 8,000 blocks are used. 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 1.4.4 Process Account Quotas The account you use to install DECscheduler must have sufficient quotas to enable you to perform the installation. VMSINSTAL requires that the installation account have the following quotas: o ASTLM = 24 o BIOLM = 18 o BYTLM = 18,000 o DIOLM = 18 o ENQLM = 30 o FILLM = 20 User account quotas are stored in the file SYSUAF.DAT. Use the VMS Authorize Utility to verify and change user account quotas. The following procedure shows how to do this: 1. Set your directory to SYS$SYSTEM: $ SET DEFAULT SYS$SYSTEM 2. Run the Authorize Utility: $ RUN AUTHORIZE UAF> 3. At the Authorize Utility prompt UAF>, use the SHOW command with an account name to check a particular account. For example: UAF> SHOW SMITH 1-4 Preparing to Install DECscheduler 4. To change a quota, use the MODIFY command at the UAF> prompt. MODIFY has the following format: UAF> MODIFY account-name/quota-name=nnnn The following example changes the FILLM quota for the SMITH account: UAF> MODIFY SMITH/FILLM=50 5. Finally, exit from the Authorize Utility: UAF> EXIT After you exit from the utility, the VMS operating system displays messages indicating whether or not changes were made. After changes are made, you must log out and log in again for the new quotas to take effect. For more information on modifying account quotas, see the description of the VMS Authorize Utility Manual in the VMS documentation on system management. 1.4.5 VMSINSTAL Requirements When invoked, VMSINSTAL checks whether or not : o You have set your default device and directory to SYS$UPDATE. o You are logged in to a privileged account. o You have adequate quotas for installation. o Any users are logged in to the system. If it detects any problems during the installation, VMSINSTAL 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 problem, enter NO or press . After the problem is corrected, restart the installation. 1-5 Preparing to Install DECscheduler 1.4.6 System Disk Backup At the beginning of the installation, VMSINSTAL asks if you have backed up your system disk. Digital recommends that you back up your system disk before installing any software on top of the operating system. Use the backup procedures established at your site. For details on backing up a system, see the VMS Backup Utility Manual in the VMS documentation set. 1-6 2 ________________________________________________________________ Installing DECscheduler This chapter provides step-by-step instructions for installing the DECscheduler software. Use the VMSINSTAL procedure to install and verify the DECscheduler software on the VMS operating system. The VMSINSTAL procedure is automated and self-explanatory. The procedure requires you to mount the software distribution volume when prompted and to respond to questions during the installation. Most questions can be answered with a YES or a NO response. 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 give the default response, press . If you need help with a question, enter a question mark (?) and press . 2.1 Halting the Installation To halt 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. 2.2 The Installation Procedure To install the DECscheduler software, use the following procedure. See Appendix A for a sample installation. 2-1 Installing DECscheduler 1. Invoke VMSINSTAL. To start the installation, invoke the VMSINSTAL command procedure from a privileged account, such as the SYSTEM account. VMSINSTAL is in the directory SYS$UPDATE. Use the following syntax to invoke VMSINSTAL: @SYS$UPDATE:VMSINSTAL product-name device-name product-name The installation name for the component. For DECscheduler, use the following installation name: SCHEDULER device-name The name of the device on which you plan to mount the media. For example, MTA0: is the device name for a tape drive. It is not necessary to use the console drive for this installation. However, if you do use the console drive, you should replace any media you removed once the installation is completed. Example The following example shows the command to invoke VMSINSTAL to install DECscheduler from tape drive MTA0:, as well as the system response: $ @SYS$UPDATE:VMSINSTAL SCHEDULER MTA0: OPTIONS N VAX/VMS Software Product Installation Procedure V5.2 It is 10-MAR-1990 at 11:23. Enter a question mark (?) at any time for help. This example uses the OPTIONS N parameter for printing or displaying release notes. When you invoke VMSINSTAL, use this parameter if you want to print or display the release notes as a part of the installation. You do not have to print the release notes as a part of the installation, and the sample installation in Appendix A does not use this option. See the VMS documentation on VMSINSTAL for more information on VMSINSTAL options. 2-2 Installing DECscheduler If you do not supply the product or the device name, VMSINSTAL prompts you for this information later in the installation procedure. 2. Check your system backup. You should always back up your system disk before performing an installation. VMSINSTAL asks if you are satisfied with your system backup. If you are satisfied with the backup of your system disk, press . Otherwise, enter NO to stop the installation. After you back up your system disk, you can restart the installation: * Are you satisfied with the backup of your system disk [YES]? 3. Mount the distribution media. Mount the first distribution volume on the device that you specified when you invoked VMSINSTAL. The device name appears in the line preceding the question. VMSINSTAL then asks if you are ready to continue with the installation. If you answer YES, VMSINSTAL displays a message that the media containing the DECscheduler 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 MTA0:. * Are you ready? YES %MOUNT-I-MOUNTED, SCHEDULER MOUNTED ON MTA0:. The following products will be processed: SCHEDULER V1.1 Beginning installation of SCHEDULER V1.1 at 11:24 %VMSINSTAL-I-RESTORE, Restoring product saveset A... If you entered the wrong device name when you invoked VMSINSTAL and need to restart the installation, enter NO in response to the Are you ready? question. To halt the installation for other reasons, press . 2-3 Installing DECscheduler 4. Choose the installation verification procedure (IVP). The installation procedure asks if you want to run the IVP: * Do you want to run the IVP after the installation [YES]? The IVP for DECscheduler checks to ensure that the installation is successful. Digital recommends that you run the IVP. To run the IVP, press or enter YES. If you do not want to run the IVP, enter NO. Note that you cannot run the IVP if you have not registered and loaded your authorization key. If you choose not to run the IVP during the installa- tion, you can run it after the installation by entering the command: $ @SYS$TEST:SCHEDULER$IVP.COM The IVP creates a job, runs the job through DECscheduler, reports whether or not the job succeeded, then deletes the job. 5. Purge files. You have the option to purge files from previous versions of DECscheduler that are superseded by this installation. Purging is recommended; however, if you need to keep files from a previous version, enter NO in response to the question: * Do you want to purge files replaced by this installation [YES]? If you answer YES to this question, the DECscheduler- related files will be purged after the installation. 6. Check your license registration. The installation procedure asks if you have registered and loaded your authorization key for DECscheduler, then displays information specific to your particular license. For example: 2-4 Installing DECscheduler Product: DECSCHEDULER Producer: DEC Version: 1.1 Release Date: 16-NOV-1990 7. Restart DECscheduler. (For updated installations only) If you have a previously installed version of the DECscheduler, the installation procedure asks * Do you want to restart the DECscheduler during this installation [YES]? To enable the new version of DECscheduler, you must restart DECscheduler. Answer YES to enable the new version. If you answer NO, the new version of DECscheduler will not be enabled. ________________________Note ________________________ There is a brief time interval between stopping and restarting DECscheduler. If a DECscheduler job completes during this interval, the status of that job is lost. _____________________________________________________ If you do not restart DECscheduler at this time, you can enable the new version of the DECscheduler at a later date by performing the following steps: a. Stop any older versions of DECscheduler by entering $ SCHED STOP/ALL b. Invoke the SYS$STARTUP:SCHEDULER$STARTUP.COM file from the SYSTEM account to start the new DECscheduler: $ @SYS$STARTUP:SCHEDULER$STARTUP.COM If you are not currently logged into the SYSTEM account, but you have an account with CMKRNL privileges, you can start DECscheduler by entering this command: $ SUBMIT/USER=SYSTEM SYS$STARTUP:SCHEDULER$STARTUP.COM 2-5 Installing DECscheduler 8. Choose a product directory location. The installation procedure asks you for the device where the product directory will be located. The default answer is SYS$COMMON; however, if you are installing DECscheduler in a VAXcluster, you should specify a disk that is shared among all nodes in the cluster. Then all nodes in the VAXcluster will have access to the [NSCHED] product directory. * Enter device where [NSCHED] directory is to be located [SYS$COMMON:]: 9. Choose wide-area network support DECscheduler can be built with wide-area network (WAN) support. This allows users to execute DECscheduler commands on remote nodes and to have job dependencies involving remote nodes. You must have a Proxy account on the remote node or use explicit account-and-password access. * Do you want the wide-area network capabilities [YES]? If you want wide-area network support, press or enter YES. Otherwise, enter NO. 10.Choose the callable interface. You can install a callable interface with DECscheduler. * Do you want the callable interface [NO]? If you plan on writing programs that access DECscheduler, answer YES to the question. This places the file NSCHED_SUBS.OLB in the product directory [NSCHED$]. NSCHED_SUBS.OLB is the callable routines library to DECscheduler. This optional installation requires about 800 blocks of additional disk space. 11.Choose the DECwindows interface. (optional) The DECwindows interface provides a graphical, user-friendly interface to DECscheduler. To run the DECwindows interface, you must have a workstation or any X-based display station. The DECwindows interface requires approximately 1300 blocks of disk space. 2-6 Installing DECscheduler * Do you want the DECwindows interface [NO]? 12.Choose the DECforms interface. (optional) The DECforms interface provides a menu-based interface to DECscheduler. The DECforms interface runs on any of the VT100, VT200, or VT300 series of terminals. The DECforms interface requires 800 blocks of disk space. * Do you want the DECforms interface [NO]? 13.Exit the VMSINSTAL procedure. After you answer the previous question, the instal- lation completes on its own. When it has completed, VMSINSTAL prompts you for another product to install: * Products: Exit the procedure by entering the EXIT command or pressing . You can now log out of the privileged account: $ LOGOUT SYSTEM logged out at 10-MAR-1990 11:38:12.32 Note that VMSINSTAL deletes or changes entries in the process symbol tables during the installation. Therefore, if you are going to continue using the system manager's account and you want to restore these symbols, you should log out and log in again. 2.3 Comparing a New Installation with an Update Installation The update installation procedure differs from the new installation procedure in three ways: o The update installation asks * Do you want to restart the DECscheduler during this installation [YES]? This question gives you the option of not enabling the new DECscheduler until a later time. 2-7 Installing DECscheduler o If you answer YES to the restart question, the update procedure later displays the following message when the existing DECscheduler version is stopped: %NSCHED-I-STOPRQST, Stop Requested o After you answer all the installation questions, an update installation displays the message: %CREATE-I-EXISTS, SYS$COMMON:[NSCHED] already exists This message indicates that a previous installation created the directory SYS$COMMON:[NSCHED]. 2.4 Error Recovery If errors occur during the installation, VMSINSTAL displays failure messages. If the installation fails, the following message is displayed: %VMSINSTAL-E-INSFAIL, The installation of SCHEDULER V1.1 has failed. Errors can occur during the installation if any of the following conditions exist: o The operating system version is incorrect. o A version of some prerequisite software is incorrect. o The system does not have the required quotas for a successful installation. o System parameter values are insufficient for a successful installation. o The VMS help library is currently in use. o The product is improperly licensed. For descriptions of the error messages that these conditions generate, see the VMS documentation on system messages, recovery procedures, and VMS software installation. If you are notified that any of these conditions exist, take the appropriate action as described in the message. You may need to change a system parameter or increase an authorized quota value. 2-8 Installing DECscheduler For information on installation requirements, see Chapter 1. 2-9 3 ________________________________________________________________ After Installing DECscheduler After installing DECscheduler, you should do the following: o Start DECscheduler, if you did not start it during the installation procedure. o Edit your system startup and shutdown files. o Reboot your system to verify your edits (optional). o Start DECscheduler on VAXcluster nodes where you want it to run jobs. o Ensure that your system account has the required minimum quotas. o Ensure that the accounts managing DECscheduler have the required privileges. o Customize your DECscheduler installation by mod- ifying the logical name definitions in the file SYS$STARTUP:SCHEDULER$STARTUP.COM. 3.1 Starting DECscheduler If you registered and loaded your authorization key before the installing DECscheduler, the installation procedure has already started DECscheduler. If you did not register and load your authorization key before installing DECscheduler, you must start DECscheduler after the installation procedure. There are two ways to start DECscheduler: o Enter the following command to invoke the SYS$STARTUP:SCHEDULER$STARTUP.COM file from the SYSTEM account: 3-1 After Installing DECscheduler $@SYS$STARTUP:SCHEDULER$STARTUP.COM o If you are not currently logged into the SYSTEM account, you can start DECscheduler by entering this command: $ SUBMIT/USER=SYSTEM SYS$STARTUP:SCHEDULER$STARTUP.COM 3.2 Editing the System Startup and Shutdown Files You must edit your operating system startup and shutdown files: o System startup command file Edit your system startup command file to cause an automatic startup of DECscheduler when your system is rebooted. Add the following command line to the system startup file, SYS$MANAGER:SYSTARTUP_V5.COM: $ @SYS$STARTUP:SCHEDULER$STARTUP.COM You must place this new command line after the line that invokes the network startup command procedure. For example: $ @SYS$MANAGER:STARTNET.COM . . . $ @SYS$STARTUP:SCHEDULER$STARTUP.COM ________________________Note ________________________ For VMS Version 5.0 or higher, the name of the startup command file is SYSTARTUP_V5.COM. _____________________________________________________ o Edit your system shutdown file so that DECscheduler will shut down properly when your system performs an orderly shutdown. 3-2 After Installing DECscheduler Add the following command line to the system shutdown file, SYS$MANAGER:SYSHUTDWN.COM: $ @NSCHED$:SCHEDULER$SHUTDOWN.COM 3.3 Rebooting the System You can reboot your system after you have installed DECscheduler and edited your system startup command file. A system reboot verifies that DECscheduler is ready for use and ensures that the edits to the system startup command file are correct. Rebooting the system is an optional step. 3.4 Starting DECscheduler on a VAXcluster If you have installed DECscheduler on a VAXcluster, you must start DECscheduler on all the nodes that will run DECscheduler jobs. On nodes that will not run jobs, you can install just the DCL interface. You can start DECscheduler on a node in three ways: o Automatically Edit the node's startup command file to start DECscheduler automatically. Section 3.2 describes how to do this. o Interactively Log in to the account from which DECscheduler will run (normally the SYSTEM account), and enter the following command: $ @SYS$STARTUP:SCHEDULER$STARTUP.COM o From batch Enter the following command: $ SUBMIT/USER=SYSTEM SYS$STARTUP:SCHEDULER$STARTUP.COM 3-3 After Installing DECscheduler To install the interface on a node without starting DECscheduler, enter the following commands. You can enter the commands interactively or place them in the system startup file: $ DEFINE/SYSTEM NSCHED$ SYS$COMMON:[NSCHED] $ @NSCHED$:INSTALL_INTERFACE.COM If necessary, substitute the appropriate device for SYS$COMMON. 3.5 Checking Your System Account Minimum Quotas The account from which DECscheduler runs (normally SYSTEM) should be able to execute a detached process with the following minimum quotas: o ASTLM=200 o FILLM=100 o ENQLM=300 o TQELM=200 o DIOLM=200 o BIOLM=10000 o PGFLQUO=10000 3.6 Checking the Minimum Privileges for DECscheduler If you do not choose to start DECscheduler under the SYSTEM account, DECscheduler must start under an account that has the following privileges enabled by default: SYSPRV SYSNAM WORLD SYSLCK CMEXEC DETACH CMKRNL To use DECscheduler, individual accounts must have at least the TMPMBX and NETMBX privileges. Use the VMS Authorize Utility to determine whether users have the privileges that they require. 3-4 After Installing DECscheduler 3.7 Customizing Your System The SYS$STARTUP:SCHEDULER$STARTUP.COM file contains several logical name definitions that you can modify to customize your particular system. Change the values of the logicals as needed, and delete the comments on the appropriate command lines. Table B-1 lists these logicals. 3-5 A ________________________________________________________________ Example of a New Installation This appendix contains an example of the procedure for performing a new installation of the DECscheduler software. The example was run on an operating system that had never had a previous version of DECscheduler installed. There were no users on the system during the installation. Section 2.2 shows the syntax for invoking VMSINSTAL from the SYS$UPDATE directory with the product and device name, using a single command line. This example shows how to do the same thing one step at a time, with VMSINSTAL prompting you for the product and device names. You do not need any VMSINSTAL options to run this installation. Username: SYSTEM Password: Last interactive login on Monday, 03-DEC-1990 10:20 Last non-interactive login on Thursday, 01-DEC-1990 10:28 $ @sys$update:vmsinstal VAX/VMS Software Product Installation Procedure V5.4 It is 3-DEC-1990 at 11:24. Enter a question mark (?) at any time for help. %VMSINSTAL-W-ACTIVE, The following processes are still active: SMITH JONES DAVIS * Do you want to continue anyway [NO]? YES * Are you satisfied with the backup of your system disk [YES]? * Where will the distribution volumes be mounted: DISK1:[JONES] A-1 Example of a New Installation Enter the products to be processed from the first distribution volume set. * Products: SCHEDULER * Enter installation options you wish to use (none): The following products will be processed: SCHEDULER V1.1 Beginning installation of SCHEDULER V1.1 at 11:24 %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. * Do you want to run the IVP after the installation [YES]? * Do you want to purge files replaced by this installation [YES]? Product: DECSCHEDULER Producer: DEC Version: 1.1 Release Date: 16-NOV-1990 * Does this product have an authorization key registered and loaded? YES * Do you want to start DECscheduler after installation [YES]? (C) COPYRIGHT 1989, 1990, 1991 DIGITAL EQUIPMENT CORPORATION, MAYNARD, MASSACHUSETTS ALL RIGHTS RESERVED Enter ? at any prompt if you need additional help. DECscheduler files go into the [NSCHED] directory. You must specify the device for this directory. Usually this will be SYS$COMMON, unless you are installing in a VAXcluster which has separate system disks for various nodes. (in that case you MUST use a shared disk). If you installed DECscheduler previously, the location of your current job database is the default answer and your old job database will be used. * Enter device where [NSCHED] directory is to be located [SYS$COMMON:]: * Do you want the wide-area network capabilities [YES]? If you plan to write programs that use the callable interface, then answer yes to the following question. This will cause the file NSCHED_SUBS.OLB to be placed in your [NSCHED] directory. Disk space requirement approximately 900 blocks. * Do you want the callable interface [NO]? YES * Do you want the DECwindows interface [NO]? YES * Do you want the DECforms interface [NO]? YES %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$COMMON:[NSCHED]. A-2 Example of a New Installation All questions regarding the installation have been asked. The installation will now proceed on its own. Providing wide-area network support... %VMSINSTAL-I-RESTORE, Restoring product save set B ... %VMSINSTAL-I-RESTORE, Restoring product save set C ... Linking Images... Linking the DECwindows interface image (nsched$:scheduler$xui.exe)... Linking the DECforms interface image (nsched$:scheduler$forms.exe)... Linking completed... Providing DCL interface, utilities, and HELP... Please take the following actions after the installation completes: 1 Make sure that your system startup procedure contains the following line $ @SYS$STARTUP:SCHEDULER$STARTUP.COM You may want to edit SCHEDULER$STARTUP.COM to change default values for Max_jobs, or to enable load balancing. Users who are currently logged on must log off and then back on again to gain access to the Scheduler's DCL command interface. 2) Make sure that your site specific system shutdown procedure, SYS$MANAGER:SYSHUTDWN.COM, contains the following line $ @NSCHED$:SCHEDULER$SHUTDOWN This will assure a proper shutdown of DECscheduler. You may run the Installation Verification Procedure at any time by typing the command: $ @SYS$TEST:SCHEDULER$IVP.COM %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... %RUN-S-PROC_ID, identification of created process is 00000305 %RUN-S-PROC_ID, identification of created process is 00000306 Beginning the DECscheduler Installation Verification Procedure. %NSCHED-I-RQSTSUCCSS, Job 1 - Created DECscheduler job 1 (Name: IVP_JOB) Started on node XYZNODE DECscheduler Job 1 (Name: IVP_JOB) Completed on node ZYZNODE %NSCHED-I-FLAGSET, Job IVP_JOB - DELETE Requested DECscheduler has been successfully installed. Installation of SCHEDULER V1.1 completed at 11:38 A-3 Example of a New Installation Enter the products to be processed from the next distribution volume set. * Products:) < Z > VMSINSTAL procedure done at 11:38 $ LO SYSTEM logged out at 3-DEC-1990 11:38:53.70 A-4 B ________________________________________________________________ DECscheduler Logical Names Table B-1 describes the DECscheduler logical names. You can find these names in the SYS$STARTUP:SCHEDULER$STARTUP.COM file, which you can edit. B-1 DECscheduler Logical Names Table_B-1_DECscheduler_Logicals___________________________ Logical________________Description________________________ NSCHED$DEFAULT_JOB_ Defines the maximum number of jobs MAX allowed to run at one time. Default: 6. NSCHED$DEFAULT_JOB_ Sets the priority level at which PRI jobs will run. Default: level 4. NSCHED$DEFAULT_LOG Defines the logging events that will be captured. Default: JOB_EVENT and ABNORMAL_ EVENT. NSCHED$LBAL$CPU_ Weighs the memory rating by WEIGHT multiplying the memory rating by the translation of this logical. A valid range is from 0.0 to 1.0. Default: 0.5. NSCHED$LBAL$INTERVAL Determines the number of seconds between data collection. Default: 30.0 seconds. NSCHED$LBAL$CPU Weighs the CPU rating by mul- WEIGHT tiplying the CPU rating by the translation of this logical. A valid range is from 0.0 to 1.0. Default: 0.5. NSCHED$LOAD_BALANCE Turns load balancing on or off. Default: ON. NSCHED$LOGFILE Names the DECscheduler log file. Default: NSCHED$:VERMONT_ CREAMERY.LOG. NSCHED$NODEPS Suppresses the display of job dependencies. Default: TRUE. NSCHED$SILENT Suppresses the connecting messages B-2 to remote nodes. Default: TRUE. NSCHED$UID Defines the location of the DECwindows user interface _______________________definition_file.___________________ C ________________________________________________________________ DECscheduler Installation Kit Files Table C-1 lists the installation kit files for the DECscheduler software. There are six categories: o DECscheduler executor files o Startup and miscellaneous control files o Callable interface files o DCL interface files o DECwindows interface files o DECforms interface files All files reside in the NSCHED$ directory, unless the table indicates otherwise. Table_C-1_Installation_Kit_Files__________________________ File_______________________Description____________________ DECscheduler_Executor_Files_______________________________ DB_UTILITY.EXE Database compression utility. NSCHED.EXE DECscheduler program image. RETRY.EXE A program image that tries DECscheduler remote operations. SCHEDULER$LBAL.EXE Dynamic load-balancing server. (Run only in a cluster environment.) (continued on next page) C-1 DECscheduler Installation Kit Files Table_C-1_(Cont.)_Installation_Kit_Files__________________ File_______________________Description____________________ DECscheduler_Executor_Files_______________________________ SCHEDULER$LBAL_MGMT.EXE Dynamic load-balancing interface. SCHEDULER$DOO_COMMAND.EXE Run by jobs that are created by DECscheduler. Protection must be set to W:RE. SCHEDULER$SHELL.COM A command shell used to execute jobs. SCHEDULER$SUMMARIZE_ Used to generate a log file LOG.EXE summary. VSS.DAT The job database. VSS_REPORTS.EXE A log file reader/reporter utility. __________________________________________________________ Startup_and_Miscellaneous_Control_Files___________________ INSTALL_DO.COM [*] Installs the job command executor SCHEDULER$DOO_ COMMAND.EXE. INSTALL_INTERFACE.COM[*] Installs all DECscheduler user interfaces. INSTALL_RPCSHARE.COM[*] Installs the components needed for DECscheduler remote features. [*]Invoked_by_SCHEDULER$STARTUP.COM.______________________ (continued on next page) C-2 DECscheduler Installation Kit Files Table_C-1_(Cont.)_Installation_Kit_Files__________________ File_______________________Description____________________ Startup_and_Miscellaneous_Control_Files___________________ LBAL_ROUND_ROBIN.COM Alternative load-balancing procedure that performs round- robin load balancing. LOAD_BALANCE.COM Load-balancing command procedure. Performs dynamic load balancing within a VAXcluster. You can customize this command procedure to meet specific user requirements. SCHEDULER$SHUTDOWN.COM The DECscheduler shutdown procedure that the site- specific system shutdown procedure should call. SCHED_REMOTE.COM[*] Runs the DECscheduler remote network object. SCHED_REMOTE.EXE The DECscheduler remote network object image. SCHED_RUN.COM[*] Runs the DECscheduler program image. SCHEDULER$STARTUP.COM Installs the DECscheduler images and starts them running. Resides in the SYS$STARTUP: directory. SCHEDULER$IVP.COM The DECscheduler installation verification procedure. Resides in the SYS$TEST: directory. [*]Invoked_by_SCHEDULER$STARTUP.COM.______________________ (continued on next page) C-3 DECscheduler Installation Kit Files Table_C-1_(Cont.)_Installation_Kit_Files__________________ File_______________________Description____________________ Startup_and_Miscellaneous_Control_Files___________________ SCHEDULER011.RELEASE_ The DECscheduler release NOTES notes. Resides in the SYS$HELP: directory. __________________________________________________________ Callable_Interface_Files__________________________________ NSCHED_SUBS.OLB A library file containing callable interface routines. __________________________________________________________ DCL_Interface_Files_______________________________________ SCHEDULER.CLD The DECscheduler command language definition file for the DCL interface. SCHEDULER.HLB Thee DECscheduler help file. SCHEDULER$INTERFACE.EXE The DCL interface program image for general command users. SCHEDULER$MANAGER.EXE The DCL interface program image for privileged command users. SCHEDULER$SHELL_ The DCL interface shell for the INTERFACE.EXE DECscheduler subsystem. __________________________________________________________ DECwindows_Interface_Files________________________________ SCHEDULER$XUI.EXE The DECwindows interface image for DECscheduler. SCHEDULER$XUI.UID The user interface database for the DECwindows interface. (continued on next page) C-4 DECscheduler Installation Kit Files Table_C-1_(Cont.)_Installation_Kit_Files__________________ File_______________________Description____________________ DECforms_Interface_Files__________________________________ SCHEDULER$FORMS.EXE The DECforms interface image for DECscheduler. SCHEDULER$FORMS.FORM The DECforms forms definition ___________________________file.__________________________ C-5 D ________________________________________________________________ Determining and Reporting Problems If an error occurs while the DECscheduler software is in use, and you believe that the error is caused by a problem with DECscheduler, take one of the following actions: o If you have a BASIC or DECsupport Software Agreement, call your Customer Support Center. With these services, you receive telephone support that provides high-level advisory and remedial assistance. o If you have a Self-Maintenance Software Agreement, submit a Software Performance Report (SPR). o If you purchased DECscheduler within the past 90 days and you think the problem is caused by a software error, submit a Software Performance Report (SPR). If you find an error in the DECscheduler documentation, fill out and submit the Reader's Comments form for the document that has the error. Include the section and page number where the error was found. D-1 ________________________________________________________________ Index B Disk space, 1-4 ___________________________ checking, 1-4 Backing up your system requirement for disk, 1-6 installation, 1-4 Documentation C__________________________ reporting errors, D-1 Callable interface, 2-6 E files, C-4 ___________________________ Checking your system backup Editing the system startup , 2-3 and shutdown files, 3-2 Comparing new installation Error recovery, 2-8 with update installation Exiting the installation , 2-7 procedure, 2-7 Customizing your system, 3-5 F__________________________ Files D__________________________ callable interface, C-4 DCL interface DCL interface, C-4 files, C-4 DECforms interface, C-5 DECforms interface DECwindows interface, C-4 files, C-5 installation kit, C-1 DECscheduler startup and miscellaneous installation kit files, control, C-2 C-1 to C-5 DECscheduler interface G__________________________ installing on a node General installation without starting requirements, 1-1 DECscheduler, 3-3 operating system, 1-1 DECwindows interface software license, 1-2 files, C-4 VAXcluster shared disk, Determining and reporting 1-3 problems, D-1 Index-1 Installation procedure H__________________________ requirements (Cont.) Halting the installation, system disk backup, 1-6 2-1 time, 1-3 VMSINSTAL, 1-5 I__________________________ Installation verification Installation kit files, C-1 procedure to C-5 choosing, 2-4 Installation procedure, 2-1 running after the to 2-9 installation, 2-4 checking your license Invoking VMSINSTAL, 2-2 registration, 2-4 device-name, 2-2 checking your system product-name, 2-2 IVP backup, 2-3 See Installation choosing a product verification procedure directory location, 2-6 L choosing the callable ___________________________ interface, 2-6 License, 1-2 choosing the installation loading, 1-2 verification procedure, registering, 1-2 2-4 Logical names, B-1 to C-1 choosing wide-area NSCHED$DEFAULT_JOB_MAX, network support, 2-6 B-2 description, 2-1 NSCHED$DEFAULT_JOB_PRI, exiting, 2-7 B-2 getting help, 2-1 NSCHED$DEFAULT_LOG, B-2 halting, 2-1 NSCHED$LBAL$CPU WEIGHT, invoking VMSINSTAL, 2-2 B-2 mounting the distribution NSCHED$LBAL$CPU_WEIGHT, media, 2-3 B-2 postinstallation NSCHED$LBAL$INTERVAL, B-2 activities, 3-1 to NSCHED$LOAD_BALANCE, B-2 3-5 NSCHED$LOGFILE, B-2 purging files, 2-4 NSCHED$NODEPS, B-2 restarting DECscheduler, NSCHED$SILENT, B-2 2-5 NSCHED$UID, B-2 Installation procedure requirements, 1-3 disk space, 1-4 privileges, 1-3 process account quotas, 1-4 Index-2 Preparing to install M__________________________ (Cont.) Mounting the distribution checking contents of media, 2-3 media, 1-1 using online release N__________________________ notes, 1-1 New installation Privileges example, A-1 to A-4 required for installing, 1-3 O Problems, D-1 ___________________________ Process account quotas Online release notes, 1-1 changing, 1-4 obtaining after the minimum, 1-4 installation, 1-1 verifying, 1-4 obtaining during the Product Authorization Key, installation, 2-2 1-2 Operating system, 1-1 Purging files, 2-4 OPTIONS N parameter to print or display R__________________________ release notes during Rebooting the system, 3-3 installation, 2-2 Recovering from errors, 2-8 Reporting problems, D-1 P__________________________ Requirements, 1-1 PAK, 1-2 for installing Postinstallation activities DECscheduler, 1-1 , 3-1 to 3-5 operating system, 1-1 checking your software license, 1-2 DECscheduler minimum VAXcluster shared privileges, 3-4 disk, 1-3 checking your system for the installation account minimum quotas, procedure, 1-3 3-4 disk space, 1-4 customizing your system, privileges, 1-3 3-5 process account quotas editing the system , 1-4 startup and shutdown system disk backup, files, 3-2 1-6 rebooting the system, 3-3 time, 1-3 starting DECscheduler, for VMSINSTAL, 1-5 3-1 Restarting DECscheduler in starting DECscheduler on an update installation, a VAXcluster, 3-3 2-5 Preparing to install, 1-1 Index-3 Restoring process symbol editing, 3-2 tables, 2-7 T__________________________ S__________________________ Time required to install Software license, 1-2 DECscheduler, 1-3 loading, 1-2 registering, 1-2 U__________________________ Specifying the product Update installation directory disk, 1-3 compared to a new Starting a new version of installation, 2-7 DECscheduler, 2-5 Using VMS Authorize utility Starting DECscheduler , 1-4 after installation, 3-1 to change user account on a VAXcluster, 3-3 quotas, 1-4, 1-5 automatically, 3-3 to check user account from batch, 3-3 quotas, 1-4 interactively, 3-3 Stopping an older version V of DECscheduler, 2-5 ___________________________ System disk backup, 1-6 VAXcluster shared disk, 1-3 recommendations, 1-6 VMSINSTAL, 2-2 System startup and shutdown VMSINSTAL requirements, 1-5 files Index-4