OpenVMS System Manager’s Manual, Volume 1: Essentials Order Number: AA–PV5MF–TK April 2001 This manual is part one of a task-oriented guide to managing a Compaq OpenVMS system. Revision/Update Information: This manual supersedes the OpenVMS System Manager’s Manual, Volume 1: Essentials, OpenVMS Version 7.2 Software Version: OpenVMS Alpha Version 7.3 OpenVMS VAX Version 7.
© 2001 Compaq Computer Corporation Compaq, VAX, VMS, and the Compaq logo Registered in the U.S. Patent and Trademark Office. OpenVMS is a trademark of Compaq Information Technologies Group, L.P in the United States and other countries. Microsoft, Windows, and Windows NT are trademarks of Microsoft Corporation in the United States and other countries. Motif, Open Software Foundation, OSF/1, and UNIX are trademarks of The Open Group in the United States and other countries.
Contents Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiii 1 Overview of This Manual 1.1 1.2 1.3 1.4 Using the OpenVMS System Manager’s Manual . . . . . . . . . . . How This Manual Relates to Other System Management Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Finding Information About Managing Complex Environments Finding Information About Managing Small Systems . . . . . . . .
2.4 Using OPCOM to Communicate with System Users . . . . . . . . . . . . 2.4.1 Understanding OPCOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.4.2 Starting OPCOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.4.3 Sending Messages to Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.4.4 Controlling the Use of OPA0: as an Operator Terminal . . . . . . . 2.4.5 Designating Operator Terminals . . . . . . . . . . . . . . . . . . . . . . . . 2.4.
3.7.5 Using a Product Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.7.5.1 Adding Information to the Database . . . . . . . . . . . . . . . . . 3.7.5.2 Registering a Noncompliant Product . . . . . . . . . . . . . . . . . 3.7.5.3 Detecting and Tracking Software Dependencies . . . . . . . . . 3.8 Installing with the POLYCENTER Software Installation Utility . . 3.8.1 Performing Preliminary Steps . . . . . . . . . . . . . . . . . . . . . . . . . 3.8.1.1 Specifying Locations . . . . . . . . .
Solving Booting Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Writing a New Boot Block on the System Disk . . . . . . . . . . . . . . . . . Shutting Down the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performing an Orderly Shutdown with SHUTDOWN.COM . . . . . Understanding the Order of Shutdown Events . . . . . . . . . . . . . . Customizing SHUTDOWN.COM to Perform Site-Specific Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.4.6 Adding Startup Files to a Startup Database . . . . . . . . . . . . . . . . . . . 5.4.7 Changing Information Associated with a Startup File . . . . . . . . . . . . 5.4.8 Deleting a Record from a Startup Database . . . . . . . . . . . . . . . . . . . . 5.4.9 Preventing a Startup File from Executing . . . . . . . . . . . . . . . . . . . . . 5.4.10 Allowing a Previously Disabled Startup File to Execute . . . . . . . . . . 5.5 Registering Images that Have System Version Dependencies . . . . . . . . . 5.5.
6.8 Saving Your Customization . . . . . . . . . . . . . . . . 6.9 Using SYSMAN to Manage System Time . . . . . . 6.9.1 Modifying the System Time . . . . . . . . . . . . . 6.9.1.1 Resetting System Time After January 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–23 6–24 6–24 6–25 Understanding the User Authorization File . . . . . . . . . . . . . . . . . . . Priority . .
7.9.4 Creating Network Proxy Authorization Files 7.9.5 Adding Proxy Accounts . . . . . . . . . . . . . . . . 7.9.6 Removing Proxy Accounts . . . . . . . . . . . . . . 7.9.7 Displaying Proxy Accounts . . . . . . . . . . . . . . 7.9.8 Controlling Proxy Logins . . . . . . . . . . . . . . . 7.10 Managing Mail . . . . . . . . . . . . . . . . . . . . . . . . . . 7.10.1 Modifying a User Record . . . . . . . . . . . . . . . 7.10.2 Removing a User Record . . . . . . . . . . . . . . . 7.10.
8.8.2 Using Spooled Printers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.8.2.1 Spooling Printers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.8.2.2 Despooling a Spooled Printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.8.2.3 Testing a Spooled Printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.9 Managing Tape Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.9.
9.5.3 Assisting Users in Mounting Volumes . . . . . . . . . . . . . . . . . . . . . . . . . 9.5.4 Mounting a Volume with Protected Subsystems . . . . . . . . . . . . . . . . . 9.5.5 Converting an Existing Volume from One ODS Format to Another . . . 9.5.5.1 Converting from ODS-2 to ODS-5 . . . . . . . . . . . . . . . . . . . . . . . . . 9.5.5.2 Converting from ODS-1 to ODS-2 . . . . . . . . . . . . . . . . . . . . . . . . . 9.5.5.3 Converting from ODS-5 Files to ODS-2 . . . . . . . . . . . . . . . . . . . .
9.12.3 Recovering Lost Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.12.4 Erasing Old Home Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.12.5 Creating a Disk Usage File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.13 Using Mount Verification for Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.13.1 Understanding Mount Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.13.
. . . . . 10–28 10–31 10–33 10–33 10–33 11.1 Overview of BACKUP Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.2 Understanding Types of Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.3 Formulating a Backup Strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.4 Understanding the Backup Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.4.1 The BACKUP Command Line . . . . . . . . . . . . . . . . . . . . .
11.15.7 Backing Up Your Workstation Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.15.7.1 Using a Command Procedure for Nightly Image Backups . . . . . . . 11.15.7.2 Using a Command Procedure for Nightly Incremental Backups . . 11.15.7.3 Using an Interactive Command Procedure for Backups . . . . . . . . . 11.15.8 Backing Up Volume Shadow Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.15.8.1 Mounting a Disk in a Host-Based Shadow Set . . . . . . . . . . . . . . . . 11.15.8.
. . . . . . . . 12–11 12–12 12–12 12–13 12–13 12–13 12–13 12–14 13.1 Understanding the Queue Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.2 Understanding the Queue Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.3 Specifying the Location of the Queue Database . . . . . . . . . . . . . . . . . . . . . 13.3.1 Specifying the Location of the Queue Master File . . . . . . . . . . . . . . . . 13.3.2 Specifying the Location of Queue and Journal Files . . . . . . .
If You See Inconsistent Queuing Behavior on Different OpenVMS Cluster Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.11.6.1 Investigating the Problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.11.6.2 Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.11.6.3 Correcting the Problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.12 Reporting a Queuing System Problem to Compaq . . . . . . . .
14.6.2 Using Job Retention Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.6.2.1 Setting Job Retention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.6.2.2 Specifying Timed Job Retention . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.6.2.3 Changing Job Retention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.6.3 Specifying Queue Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.6.3.
Managing Jobs in Queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Monitoring Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying Job Processing Options . . . . . . . . . . . . . . . . . . . . . . . . . Holding and Releasing a Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Requeuing an Executing Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Requeuing a Pending Job . . . . . . . . . . . . . . . . . . . . . . . .
13–1 13–2 13–3 14–1 14–2 14–3 14–4 14–5 14–6 14–7 14–8 14–9 14–10 14–11 14–12 14–13 OpenVMS Batch and Print Queuing System . . . . . . . . . . . . . . . Queue Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Locations of Queue Database Files . . . . . . . . . . . . . . . . . . . . . . Default Batch Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Multiple Batch Queues with Special Resource and Performance Options . . . . . . . . . . . . . . . . . . .
7–1 7–2 7–3 7–4 7–5 7–6 7–7 7–8 7–9 8–1 8–2 8–3 8–4 8–5 8–6 8–7 8–8 8–9 9–1 9–2 9–3 9–4 9–5 9–6 9–7 9–8 9–9 9–10 9–11 9–12 9–13 9–14 9–15 9–16 9–17 10–1 10–2 10–3 10–4 10–5 10–6 10–7 11–1 11–2 11–3 11–4 xx Resource Type Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Login Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System-Supplied UAF Accounts . . .
11–5 11–6 11–7 11–8 11–9 12–1 14–1 14–2 14–3 14–4 14–5 14–6 14–7 14–8 Sample Process Quotas for Efficient Backups . . . . . . . . . . . . Methods of Volume Initialization . . . . . . . . . . . . . . . . . . . . . . Number of Shadow Sets Supported . . . . . . . . . . . . . . . . . . . . Valid Standalone BACKUP Qualifiers . . . . . . . . . . . . . . . . . . BACKUP Error Options and Results . . . . . . . . . . . . . . . . . . . Kinds of Security Events OpenVMS Can Report . . . . . . . . . .
Preface Intended Audience The intended audience for this manual is Compaq OpenVMS system managers.
Related Documents The following books are helpful when used in conjunction with the OpenVMS System Manager’s Manual: • OpenVMS System Management Utilities Reference Manual • OpenVMS User’s Manual • OpenVMS Software Overview • The current version of the Upgrade and Installation Manual for your system • OpenVMS Guide to System Security • OpenVMS Performance Management • OpenVMS Cluster Systems and Guidelines for OpenVMS Cluster Configurations • The following networking manuals: Compaq TCP/IP Se
Conventions The following conventions are used in this manual: Ctrl/x A sequence such as Ctrl/x indicates that you must hold down the key labeled Ctrl while you press another key or a pointing device button. PF1 x A sequence such as PF1 x indicates that you must first press and release the key labeled PF1 and then press and release another key or a pointing device button. Return In examples, a key name enclosed in a box indicates that you press a key on the keyboard.
Monospace text Monospace type indicates code examples and interactive screen displays. In the C programming language, monospace type in text identifies the following elements: keywords, the names of independently compiled external functions and files, syntax summaries, and references to variables or identifiers introduced in an example. xxvi - A hyphen at the end of a command format description, command line, or code line indicates that the command or statement continues on the following line.
1 Overview of This Manual Together, the two parts of this manual explain tasks and concepts related to managing a Compaq OpenVMS system. This chapter describes this manual and how to use it. The OpenVMS System Manager’s Manual explains system management tasks for new and experienced system managers. However, before performing these tasks, you should be familiar with the following items: • User-level tasks such as creating and editing files and command procedures.
Overview of This Manual 1.1 Using the OpenVMS System Manager’s Manual The Task Table The first table lists the major tasks described in the chapter. If you need to perform a task quickly, go directly to the section that explains that task. For example, in this chapter the task table lists the following tasks: Task Section Using the OpenVMS System Manager’s Manual Section 1.1 Finding information about managing complex environments Section 1.3 Finding information about managing small systems Section 1.
Overview of This Manual 1.4 Finding Information About Managing Small Systems Table 1–2 lists the tasks you are likely to perform, and where to find instructions for performing these tasks. Table 1–2 Documentation for Managing Small Standalone Systems Chapter, Section, or Other Manual Task Installing and upgrading the operating system The Upgrade and Installation Manual Installing layered products Section 3.2 Loading software licenses Section 3.3.2 Booting the system Section 4.1.3.
2 Using OpenVMS System Management Utilities and Tools This chapter provides general information about system management utilities and tools that are provided with the Compaq OpenVMS Operating System. Procedures for using utilities and tools to perform specific tasks are provided in the respective chapters that describe those tasks. For example, this chapter contains a general description of the System Management utility (SYSMAN). Section 9.11.2 describes how to use SYSMAN to manage disk quotas. Section 15.
Using OpenVMS System Management Utilities and Tools Concept Section System Management utility (SYSMAN) Section 2.3.1 Understanding a SYSMAN management environment Section 2.3.3 Understanding a SYSMAN profile Section 2.3.5 Understanding OPCOM Section 2.4.1 2.1 Understanding OpenVMS System Management Tools Compaq supplies the following software tools to monitor and control system operations and resources: Tool For More Information OpenVMS Management Station Section 2.1.
Using OpenVMS System Management Utilities and Tools 2.1 Understanding OpenVMS System Management Tools Figure 2–1 Sample OpenVMS Management Station Screen X ManageWORKS − OpenVMS User Account Zoom OpenVMS Account Name: General Flags Mail USER on SYS5 Network Proxies Passwords Quotas Security Time Restrictions Contact Information Owner: Joe J User Location: Big Office Phone: x234 ID: Argus State Disabled Enabled 200 , [ 200 ] Account Expiration Expires On: 0 / 0 / 0 0: 0 Advanced...
Using OpenVMS System Management Utilities and Tools 2.1 Understanding OpenVMS System Management Tools The OpenVMS Management Station consists of two components: • The client. This is Microsoft Windows based software that you install on a PC and use to perform management operations. • The server. This software must be installed on all OpenVMS systems to be managed. You do not interact directly with the server, the client does that.
Using OpenVMS System Management Utilities and Tools 2.1 Understanding OpenVMS System Management Tools • Displaying user account attributes 2.1.2 DCL Commands You perform many system management tasks by entering DCL (DIGITAL Command Language) commands. For example, enter the DCL command MOUNT to make disks and tapes available to the system. Most of the DCL commands used by system managers require special privileges (such as OPER privilege).
Using OpenVMS System Management Utilities and Tools 2.1 Understanding OpenVMS System Management Tools When you execute this command procedure with the command @GO_WORK, you set your default directory to [PERRY.WORK] and display a list of files in that directory. With complex command procedures, you can use DCL instead of a highlevel programming language. For more information about creating command procedures, refer to the OpenVMS User’s Manual. 2.1.4.
Using OpenVMS System Management Utilities and Tools 2.1 Understanding OpenVMS System Management Tools 2.1.4.2 Using Compaq-Supplied Command Procedures for System Management Compaq provides several command procedures for managing a system. Table 2–1 lists some commonly used command procedures. Table 2–1 System Management Command Procedures Command Procedure Function SYS$SYSTEM:STARTUP.
Using OpenVMS System Management Utilities and Tools 2.1 Understanding OpenVMS System Management Tools Table 2–2 System Management Utilities and Tools Utility Purpose Accounting utility (ACCOUNTING) To produce reports of resource use. ACL editor (access control list editor) To create and maintain ACLs. Analyze/Disk_Structure utility (ANALYZE/DISK_STRUCTURE) To check the validity of Files–11 Structure Levels 1, 2, and 5 disk volumes, and to report errors and inconsistencies.
Using OpenVMS System Management Utilities and Tools 2.1 Understanding OpenVMS System Management Tools Table 2–2 (Cont.) System Management Utilities and Tools Utility Purpose System Generation utility (SYSGEN) To create and install page, swap, and dump files and to manage system parameters. †On VAX systems, to load and connect device drivers. System Management utility (SYSMAN) To centralize system management. Allows you to perform system management tasks simultaneously on one or more nodes.
Using OpenVMS System Management Utilities and Tools 2.2 Logging In to the SYSTEM Account 2.2 Logging In to the SYSTEM Account To use system management utilities and perform system management functions, log in to the system manager’s account (SYSTEM). Caution Compaq recommends that you change the password for the SYSTEM account frequently to maintain system security. Because the SYSTEM account has full privileges by default, exercise caution when using it.
Using OpenVMS System Management Utilities and Tools 2.3 Using SYSMAN to Centralize System Management Feature For More Information Enable a system to execute SYSMAN commands from remote nodes Section 2.3.2 Define your SYSMAN management environment Section 2.3.4 Adjust your SYSMAN profile to set privileges, default device and directory, and DCL verification Section 2.3.6 Execute DCL commands from SYSMAN Section 2.3.8 Create SYSMAN command procedures Section 2.3.
Using OpenVMS System Management Utilities and Tools 2.3 Using SYSMAN to Centralize System Management • Enough identifiers removed from your current account so that the total number of rights falls within the appropriate range 2.3.1.3 Tools and Commands SYSMAN uses many of the same software tools that you traditionally use to manage a system. It can process most DCL commands, such as MOUNT and INITIALIZE.
Using OpenVMS System Management Utilities and Tools 2.3 Using SYSMAN to Centralize System Management 2.3.3 Understanding a SYSMAN Management Environment When you use SYSMAN, you must define the management environment you will be working in. The management environment is the node or nodes on which subsequent commands will execute. By default, the management environment is the local node (the node from which you execute SYSMAN).
Using OpenVMS System Management Utilities and Tools 2.3 Using SYSMAN to Centralize System Management 2.3.4 Defining the SYSMAN Management Environment To define the management environment, use the SYSMAN command SET ENVIRONMENT. Whenever you redefine an environment, SYSMAN displays the new context. You can always verify the current environment with the SHOW ENVIRONMENT command. When you are not working on your local node or within your own cluster, your environment is a nonlocal environment.
Using OpenVMS System Management Utilities and Tools 2.3 Using SYSMAN to Centralize System Management 3.
Using OpenVMS System Management Utilities and Tools 2.3 Using SYSMAN to Centralize System Management 2.3.4.3 Defining an OpenVMS Cluster Environment To define your management environment to be an OpenVMS Cluster system, use the SET ENVIRONMENT/CLUSTER command.
Using OpenVMS System Management Utilities and Tools 2.3 Using SYSMAN to Centralize System Management • If the environment is an OpenVMS Cluster systen and does not have common SYSUAF and RIGHTSLIST databases, SYSMAN checks the SYSUAF on the target nodes to see if you are an authorized user. If you are an authorized user, SYSMAN copies your profile from the SYSUAF on the target nodes to the SMISERVER process on the target nodes.
Using OpenVMS System Management Utilities and Tools 2.3 Using SYSMAN to Centralize System Management SYSMAN> SET PROFILE/PRIVILEGES=SYSPRV SYSMAN> SHOW PROFILE %SYSMAN-I-DEFDIR, Default directory on node NODE21 -- WORK1:[MAEW] %SYSMAN-I-DEFPRIV, Process privileges on node NODE21 -TMPMBX OPER NETMBX SYSPRV 2.3.6.2 Changing Your Default Device and Directory Use the SET PROFILE/DEFAULT command to reset the default device and directory specification for your process and all server processes in the environment.
Using OpenVMS System Management Utilities and Tools 2.3 Using SYSMAN to Centralize System Management In an OpenVMS Cluster environment, SYSMAN executes DO commands sequentially on all nodes in the cluster. After a command completes or times out on one node, SYSMAN sends it to the next node in the environment. Any node that is unable to execute a command returns an error message. For more information about using the DO command to manage an OpenVMS Cluster system, see Section 22.6.
Using OpenVMS System Management Utilities and Tools 2.3 Using SYSMAN to Centralize System Management $ TYPE SYSMANINI.INI DEFINE/KEY/TERMINATE KP0 "SET ENVIRONMENT/CLUSTER/NODE=(NODE21,NODE22)" DEFINE/KEY/TERMINATE KP1 "CONFIGURATION SHOW TIME" DEFINE/KEY/TERMINATE KP2 "SHOW PROFILE" . . . 2.4 Using OPCOM to Communicate with System Users The operator communication manager (OPCOM) is a tool for communicating with users and operators on the system.
Using OpenVMS System Management Utilities and Tools 2.
Using OpenVMS System Management Utilities and Tools 2.4 Using OPCOM to Communicate with System Users OPCOM Components OPCOM uses the following components: For More Information Component Description OPCOM process The system process that manages OPCOM operations. Unless you disable it, the OPCOM process starts automatically at system startup time. Section 2.4.2 Operator terminals Terminals designated to display messages broadcast by OPCOM.
Using OpenVMS System Management Utilities and Tools 2.4 Using OPCOM to Communicate with System Users 2.4.2 Starting OPCOM The OPCOM process starts automatically during system startup, unless it is disabled. You might need to start OPCOM interactively if a software problem causes the process to fail and prevents OPCOM from restarting automatically.
Using OpenVMS System Management Utilities and Tools 2.4 Using OPCOM to Communicate with System Users Examples The REPLY command in the following example sends a message to all users logged in to node WLDWND. When the message is displayed, a bell rings at the terminal. $ REPLY/ALL/BELL/NODE=WLDWND "Please log off" The REPLY command in the following example sends a message to the user logged in at terminal TTC1. When the message is displayed, a bell rings at that terminal.
Using OpenVMS System Management Utilities and Tools 2.4 Using OPCOM to Communicate with System Users The following table describes each keyword: Keyword Description CARDS Displays messages sent to the card readers. CENTRAL Displays messages sent to the central system operator. CLUSTER Displays messages from the connection manager pertaining to OpenVMS Cluster system state changes. DEVICES Displays messages pertaining to mounting disks.
Using OpenVMS System Management Utilities and Tools 2.4 Using OPCOM to Communicate with System Users 2.4.6 Sending Requests to an Operator In sites where operators are assigned to assist users by mounting volumes and changing printer forms, users can communicate with operators by entering the DCL command REQUEST and the following qualifiers: Qualifier Description /REPLY Sends a request and requests a reply to the message.
Using OpenVMS System Management Utilities and Tools 2.4 Using OPCOM to Communicate with System Users Qualifier Description /STATUS Reports which classes are enabled, and all outstanding user requests for the terminal from which this command was entered. The current terminal must be enabled as an operator terminal. /TO=identificationnumber Replies to the request specified by the identification number and completes the request. The current terminal must be enabled as an operator terminal.
Using OpenVMS System Management Utilities and Tools 2.5 Using VMSKITBLD.COM to Modify a System Disk Disk Description Source disk The disk from which you copy system files. The source disk must be an existing system disk. Target disk The disk to which you move the system files. Caution Do not attempt to use VMSKITBLD with the current system disk as the target disk. VMSKITBLD.COM deletes files that are required for a running system. 2.5.1 Using VMSKITBLD.
Using OpenVMS System Management Utilities and Tools 2.5 Using VMSKITBLD.COM to Modify a System Disk b. In response to the following prompt, enter the top-level system directory for the source disk: * Enter SOURCE disk top-level system directory [default = SYS0]: In most cases, you can choose the default value [SYS0]. c. In response to the following prompt, enter the name of the target disk: * Enter TARGET disk name (ddcu:): d.
Using OpenVMS System Management Utilities and Tools 2.5 Using VMSKITBLD.COM to Modify a System Disk * * * * * Enter mounted SOURCE disk name (ddcu:): SYS$SYSDEVICE: Enter SOURCE disk top level system directory [default = SYS0]: Enter TARGET disk name (ddcu:): DUA0: Return Enter the TARGET disk’s label [default = VAXVMSRL5]: Return Enter TARGET disk top level system directory [default = SYS0]: The target disk will be initialized.
Using OpenVMS System Management Utilities and Tools 2.5 Using VMSKITBLD.COM to Modify a System Disk Example SYSBOOT> USE DEFAULT SYSBOOT> SET STARTUP_P1 "MIN" SYSBOOT> CONTINUE . . . $ SET DEFAULT SYS$COMMON:[SYSEXE] $ RUN AUTHORIZE UAF> CREATE/RIGHTS UAF> CREATE/PROXY UAF> EXIT $ @SYS$UPDATE:AUTOGEN SAVPARAMS REBOOT CHECK_FEEDBACK . . . 2.5.2 Using VMSKITBLD.
Using OpenVMS System Management Utilities and Tools 2.5 Using VMSKITBLD.COM to Modify a System Disk b. In response to the following prompt, enter the top-level system directory for the source disk: * Enter SOURCE disk top level system directory [default = SYS0]: In most cases, you can choose the default value [SYS0]. c. In response to the following prompt, enter the name of the target disk: * Enter TARGET disk name (ddcu:): d.
Using OpenVMS System Management Utilities and Tools 2.5 Using VMSKITBLD.COM to Modify a System Disk 4. Enter the following command to invoke VMSKITBLD: $ @SYS$UPDATE:VMSKITBLD VMSKITBLD prompts you to choose one of the following options: Operation [BUILD,ADD,COPY]? 5. Enter ADD and press Return. VMSKITBLD displays messages that either prompt you for information needed to complete the operation or inform you of the procedure’s status. a.
Using OpenVMS System Management Utilities and Tools 2.5 Using VMSKITBLD.COM to Modify a System Disk 2.5.3.1 Configuring a System Root Added with VMSKITBLD After you use VMSKITBLD to add an alternate system root directory to a system disk, you must configure system parameters for the new root. Perform the following steps: 1. Shut down the system and halt your computer. For instructions on shutting down your system, see Section 4.8.1. 2.
3 Installing, Upgrading, and Updating Software This chapter describes the concepts related to installing, upgrading, and updating OpenVMS operating system software and layered products. Two methods are available for installing or upgrading software: the POLYCENTER Software Installation utility and the VMSINSTAL.COM command procedure. Operating System Software To install or upgrade the OpenVMS VAX or Alpha operating system, refer to the current OpenVMS VAX or Alpha Upgrade and Installation Manual.
Installing, Upgrading, and Updating Software 3.1 Installing, Upgrading, and Updating the Operating System 3.1 Installing, Upgrading, and Updating the Operating System The installation of software can mean a complete installation, an upgrade, or an update. The terms have the following meanings: Installation Used to install a completely new version of the operating system. Upgrade Used to make major changes to an existing version of the operating system.
Installing, Upgrading, and Updating Software 3.3 Preparing Your System to Run VMSINSTAL.COM 3.3 Preparing Your System to Run VMSINSTAL.COM This section provides guidelines for preparing your system for using VMSINSTAL.COM. Note that each software product that you install might not require you to follow all of the guidelines listed in this section. 3.3.1 Performing Preliminary Operations Before you use VMSINSTAL.
Installing, Upgrading, and Updating Software 3.3 Preparing Your System to Run VMSINSTAL.COM At the UAF prompt ( UAF> ), enter the following command: UAF> SHOW SYSTEM See Section 7.1.2 for details. • If necessary, use the Authorize utility to modify the SYSTEM account limits. Changes you make do not take effect until you log out and log in again. For example, to increase the DIOLM limit to 100, enter the following command: UAF> MODIFY SYSTEM/DIOLM=100 See Section 7.1.2 for details.
Installing, Upgrading, and Updating Software 3.3 Preparing Your System to Run VMSINSTAL.COM 3.3.3 Preventing Nodes from Sharing PAKs The /NO_SHARE qualifier for the LICENSE MODIFY command lets you add the NO_SHARE option to a PAK registered in a license database (LDB). NO_ SHARE PAKs are assigned to a single node in an OpenVMS Cluster system. A NO_SHARE PAK cannot be shared with other OpenVMS Cluster nodes.
Installing, Upgrading, and Updating Software 3.4 Running VMSINSTAL.COM The following sections explain required and optional parameters in the VMSINSTAL.COM command line: Parameter Section Product list Section 3.4.1 Source Section 3.4.2 Options Section 3.4.3 Destination Section 3.4.4 Backup qualifiers Section 3.4.5 and Section 3.6.3.3 Section 3.4.6 explains how to complete an installation. 3.4.
Installing, Upgrading, and Updating Software 3.4 Running VMSINSTAL.COM command; the distribution media then finds and displays the products that are included. How to Perform This Task To obtain the product list, enter commands in the following format: MOUNT/OVERRIDE=ID device: DIRECTORY device:[0,0] where device is the drive that holds the distribution media.
Installing, Upgrading, and Updating Software 3.4 Running VMSINSTAL.COM You can also use a logical name to specify the source. If you do not specify the source, VMSINSTAL.COM asks you for it, as follows: * Where will the distribution volumes be mounted: 3.4.3 Selecting Options The VMSINSTAL.COM command procedure permits the use of six options. Table 3–2 briefly describes each option. Section 3.6 contains a detailed description of each option. Table 3–2 VMSINSTAL.
Installing, Upgrading, and Updating Software 3.4 Running VMSINSTAL.COM 3.4.4 Selecting the Destination The destination parameter is optional. By default, VMSINSTAL.COM assumes that the product is to be installed in the system common directory SYS$COMMON on the system disk. However, you must use this parameter in the following two instances: • To install the product in an alternate root. The product is installed on a system disk other than that on which the target system is running.
Installing, Upgrading, and Updating Software 3.5 Recovering from a System Failure • The system disk or a library used by the installation was corrupted. In this case, VMSINSTAL.COM instructs you to restore either the system disk or the corrupted library from the backup copy and to restart the installation. • VMSINSTAL.COM continues the installation. In this case, the procedure performs most of the installation. In addition, VMSINSTAL.
Installing, Upgrading, and Updating Software 3.6 Selecting VMSINSTAL.COM Options You can use the Alternate Working Device option to specify an alternate working device for the temporary working directory (defined as the logical name VMI$KWD). This option allows you to perform an installation with fewer free blocks on the system disk than are otherwise required. If you do not specify this option, VMSINSTAL.COM creates the temporary working directory in the following location: SYS$SPECIFIC:[SYSUPD.
Installing, Upgrading, and Updating Software 3.6 Selecting VMSINSTAL.COM Options Examples If you specify just one option, enter the disk directory name immediately after the OPTIONS G parameter, leaving a space between G and the disk directory. For example, if you are storing save sets for a product named NEWAID010 from the console drive into disk directory USER1:[PRODUCTS], enter the following command: $ @SYS$UPDATE:VMSINSTAL.
Installing, Upgrading, and Updating Software 3.6 Selecting VMSINSTAL.COM Options Qualifier Explanation /CONFIRM Displays a prompt on your terminal before each file is processed. To process the file, enter Y or YES and press the Return key. The system interprets any other response, including simply pressing the Return key, as NO. Refer to the OpenVMS System Management Utilities Reference Manual for more information about the BACKUP command and its qualifiers. 3.6.
Installing, Upgrading, and Updating Software 3.6 Selecting VMSINSTAL.COM Options If the product does not supply release notes, VMSINSTAL.COM displays two error messages. It also asks whether you want to continue or to end the installation, as follows: %VMSINSTAL.COM-W-NOFILE, New File facvvu.RELEASE_NOTES does not exist. %VMSINSTAL.COM-W-NORELNOTE, unable to locate release notes.
Installing, Upgrading, and Updating Software 3.7 Using the POLYCENTER Software Installation Utility To run the POLYCENTER Software Installation utility as a batch job, see Section 3.8.6. Table 3–3 lists DCL commands the POLYCENTER Software Installation utility can perform and describes each of them.
Installing, Upgrading, and Updating Software 3.7 Using the POLYCENTER Software Installation Utility Table 3–4 Privileges Required by the POLYCENTER Software Installation Utility Operations Privileges Required COPY, EXTRACT, FIND, LIST, PACKAGE None CONFIGURE, SHOW SYSLCK REGISTER SYSLCK and SYSPRV (or a system UIC) INSTALL, RECONFIGURE, REMOVE SYSLCK, SYSPRV (or a system UIC), TMPMBX, and CMKRNL Note that commands you execute from the kit you are installing might require additional privileges.
Installing, Upgrading, and Updating Software 3.7 Using the POLYCENTER Software Installation Utility • Reference copy format. In this form, the PDF, the PTF, and all files that comprise the product are placed in a directory tree on a random-access device. OpenVMS is distributed in reference copy format on CD–ROM. 3.7.3 Software Product Name Conventions A software product kit packaged in sequential copy format has a container file named in the following format: producer-base-product-version-kit_type.
Installing, Upgrading, and Updating Software 3.7 Using the POLYCENTER Software Installation Utility 3.7.3.1 Version Identification Format The version of the software product kit is in the format tmmnn-ue. This format is described in Table 3–6. Table 3–6 Format of tmmnn-ue Version Identification t The type of version (a single uppercase alphabetic character). mm The major version number (decimal integer 01 through 99). nn The minor version number (decimal integer 00 through 99).
Installing, Upgrading, and Updating Software 3.7 Using the POLYCENTER Software Installation Utility • A product description file in a reference copy format kit for OpenVMS Alpha has the following format: DEC-AXPVMS-VMS-V0601-1H2-2.PCSI$DESCRIPTION This format shows that the producer is DEC (DIGITAL), the base is AXPVMS (OpenVMS Alpha), the product is OpenVMS, and the version is V6.1-1H2.
Installing, Upgrading, and Updating Software 3.7 Using the POLYCENTER Software Installation Utility • Preventing a question from being asked again. If you do not defer a question when you create a PCF, the response recorded in the PCF is used during future installations. The installer is not prompted for the information. This reduces the length and complexity of the actual installation procedure. 3.7.4.2 Configuration Commands To create a PCF, use the PRODUCT CONFIGURE command.
Installing, Upgrading, and Updating Software 3.7 Using the POLYCENTER Software Installation Utility Example 3–1 Sample Procedure for Creating a PCF $ PRODUCT CONFIGURE VMS/SOURCE=SYS$SYSDEVICE:[VMS$COMMON]/LOG _$ /CONFIGURATION=(OUTPUT=MYPCF) Return The following product has been selected: DEC AXPVMS VMS V7.2 [Available] Do you want to continue [YES] Return Configuration phase starting ...
Installing, Upgrading, and Updating Software 3.7 Using the POLYCENTER Software Installation Utility The callouts in the example mark the following actions: ! Chooses to select values for individual options instead of accepting default values for all of the options. " Requests (by using the defer key, F17) that the installer be given the choice of whether or not to install the optional example files. # Toggles the defer option (twice to illustrate the toggle effect).
Installing, Upgrading, and Updating Software 3.7 Using the POLYCENTER Software Installation Utility 3.7.5 Using a Product Database The POLYCENTER Software Installation utility automatically stores information about product installation, configuration choices, and objects, such as files and directories, that make up the product in the product database. The product database is useful for recalling information about products installed on your system and for detecting and tracking product dependencies. 3.7.5.
Installing, Upgrading, and Updating Software 3.7 Using the POLYCENTER Software Installation Utility 3.7.5.3 Detecting and Tracking Software Dependencies Some software products depend on other software products to work correctly. For example, a product might work only when a specific version of another product is installed on the system. The POLYCENTER Software Installation utility detects and tracks the dependencies of the products that you install.
Installing, Upgrading, and Updating Software 3.8 Installing with the POLYCENTER Software Installation Utility Logical name PCSI$SOURCE defines the location of the software kits you want to install. Logical name PCSI$DESTINATION defines the location where you want to install the software.
Installing, Upgrading, and Updating Software 3.
Installing, Upgrading, and Updating Software 3.8 Installing with the POLYCENTER Software Installation Utility 3.8.4.1 Requesting an Explanation to Questions To request a full description of all product options and information, use the /HELP qualifier with PRODUCT INSTALL. To request help about an individual question, press the Help key or PF2 in response to the question.
Installing, Upgrading, and Updating Software 3.8 Installing with the POLYCENTER Software Installation Utility 3.8.5 Confirming Your Answers After you respond to questions about product options, the POLYCENTER Software Installation utility can display a summary of your answers. For example: Do you want to review the options? [YES] Return DEC TCP/IP Services for OpenVMS Optional example files may be installed...: NO Optional NFS files may be installed...: NO Optional applications may be installed...
Installing, Upgrading, and Updating Software 3.8 Installing with the POLYCENTER Software Installation Utility The last message indicates that some files might have been moved to their target directories, but the product has not been completely installed. Installation of the product at a later time will delete the files from the aborted installation and will then perform a full installation. 3.8.
Installing, Upgrading, and Updating Software 3.9 Performing Other Operations on Installed Software Products To change the configuration choices for an installed product, use the PRODUCT RECONFIGURE command. The product kit must be present in the user’s default directory or specified by the /SOURCE qualifier or by the PCSI$SOURCE logical name. 3.9.2 Recording a Change in Volume Label in the Product Database To record a changed volume label in the product database, enter the PRODUCT REGISTER VOLUME command.
Installing, Upgrading, and Updating Software 3.9 Performing Other Operations on Installed Software Products Table 3–8 SHOW OBJECT Command: Displaying Managed Object Information Question Command What files or other objects did this product create? PRODUCT SHOW OBJECT * /PRODUCT=productname What product created this file or other object? PRODUCT SHOW OBJECT object-name/FULL 3.9.5.
4 Starting Up and Shutting Down the System This chapter describes various ways to start up and shut down your system. To initiate startup of your system, you boot it. Many systems have unique booting commands. For detailed booting instructions for your system, refer to the following manuals: • On VAX systems, refer to the most recent versions of the OpenVMS VAX Upgrade and Installation Manual and the upgrade and installation supplement for your VAX computer.
Starting Up and Shutting Down the System Concept Section System shutdown procedures Section 4.8 The order of shutdown events Section 4.8.2 4.1 Understanding Booting and System Startup Booting is the process of loading system software from the system disk into processor memory. When you boot your system, it automatically performs a series of tasks to start up your system. These tasks are collectively known as system startup.
Starting Up and Shutting Down the System 4.1 Understanding Booting and System Startup 7. The boot process finishes, and you can log in to the operating system. 4.1.2 Deferring Memory Testing on AlphaServer 4100 Computers To speed up the time between system power-on and user login, you can now defer a portion of memory testing on AlphaServer 4100 computers. When you choose this option, the console tests a minimum amount of memory and leaves the rest for the operating system to test.
Starting Up and Shutting Down the System 4.1 Understanding Booting and System Startup 4.1.3.1 Nonstop Boot: The Most Common Booting Operation The most common boot operation is a nonstop boot from the system disk. You perform a nonstop boot after changing certain system parameters or installing certain layered products, or after a standalone backup.
Starting Up and Shutting Down the System 4.1 Understanding Booting and System Startup 4.1.4 System Startup and STARTUP.COM Immediately after your system boots, it runs the site-independent command procedure SYS$SYSTEM:STARTUP.COM to start up the system and control the sequence of startup events. This section describes STARTUP.COM. Caution Do not modify SYS$SYSTEM:STARTUP.COM. This file is deleted and replaced each time you upgrade your system to the next version of the operating system. Leaving STARTUP.
Starting Up and Shutting Down the System 4.1 Understanding Booting and System Startup 2. A short time later (up to a few minutes), the system displays a message similar to the following message: The OpenVMS system is now executing the site-specific system startup commands. This message indicates that the system is executing SYSTARTUP_VMS.COM. You can modify this file to perform various operations at startup time. For more information, see Section 5.2.7. 3.
Starting Up and Shutting Down the System 4.2 Booting with Modified System Parameter Values 4.2.1 Booting After Showing or Modifying Individual System Parameter Values In a conversational boot operation, you can show and modify values for individual parameters.1 The system modifies the values both in memory and in the system parameter file. How to Perform This Task 1.
Starting Up and Shutting Down the System 4.2 Booting with Modified System Parameter Values 2. At the SYSBOOT> prompt, enter a command in the following format: USE file-spec where file-spec specifies the file name and type of the alternate parameter file. The file must be in SYS$SYSTEM. You cannot specify a device name. For example: SYSBOOT> USE ALTPARAMS.DAT 3. Enter the CONTINUE command to continue booting: SYSBOOT> CONTINUE Example SYSBOOT> USE ALTPARAMS.DAT SYSBOOT> CONTINUE 4.
Starting Up and Shutting Down the System 4.4 Booting in an Emergency 4.4.1 Booting with Default System Parameters If the current values stored in the parameter file have been incorrectly modified, these incorrect values might cause the system to become unbootable. With a conversational boot operation, you can reset the active values for all system parameters to the default value. Note that in most cases, Compaq recommends that you use AUTOGEN to modify system parameters.
Starting Up and Shutting Down the System 4.4 Booting in an Emergency $ EDIT SYS$SYSTEM:MODPARAMS.DAT . . . [Insert the following line in MODPARAMS.DAT:] MIN_NPAGEDYN = 2999808 . . . $ @SYS$UPDATE:AUTOGEN SAVPARAMS REBOOT 4.4.2 Booting Without Startup and Login Procedures If the system does not complete the startup procedures or does not allow you to log in, bypass the startup and login procedures. The startup and login procedures provided by Compaq should always work.
Starting Up and Shutting Down the System 4.4 Booting in an Emergency $ RUN SYS$SYSTEM:SYSMAN SYSMAN> PARAMETERS USE CURRENT SYSMAN> PARAMETERS SET/STARTUP SYS$SYSTEM:STARTUP.COM SYSMAN> PARAMETERS WRITE CURRENT SYSMAN> EXIT $ 8.
Starting Up and Shutting Down the System 4.4 Booting in an Emergency Field Value Privileges All The process name is usually set to the name of the device on which you logged in (for example, _OPA0:). How to Perform This Task 1. Perform a conversational boot by following the instructions in one of the following manuals: • On VAX systems, refer to the most recent versions of the OpenVMS VAX Upgrade and Installation Manual and the upgrade and installation supplement for your VAX computer.
Starting Up and Shutting Down the System 4.4 Booting in an Emergency 11. Shut down and reboot the system. Example SYSBOOT> SET UAFALTERNATE 1 SYSBOOT> SET WINDOW_SYSTEM 0 SYSBOOT> CONTINUE Username: Return Password: Return Password: Return $ DEFINE/SYSTEM/EXECUTIVE_MODE SYSUAF SYS$SYSTEM:SYSUAF.
Starting Up and Shutting Down the System 4.5 Booting with Controlled Startup You can also perform site-specific startup events by adding commands to the site-specific startup command procedures. For more information, see Section 5.2. How to Perform This Task 1.
Starting Up and Shutting Down the System 4.5 Booting with Controlled Startup How to Perform This Task 1. Edit the file SYS$SYSTEM:MODPARAMS.DAT. AUTOGEN uses this file to modify parameters. 2. Add a line to MODPARAMS.DAT assigning the name of your alternate procedure to the symbol STARTUP. For example: STARTUP = "SYS$SYSTEM:MY_STARTUP.COM" 3. At a convenient time, invoke AUTOGEN. When the system reboots, the procedure specified in step 2 becomes the default startup command procedure.
Starting Up and Shutting Down the System 4.
Starting Up and Shutting Down the System 4.5 Booting with Controlled Startup 4.
Starting Up and Shutting Down the System 4.5 Booting with Controlled Startup Qualifiers can be any of the options specified in Table 4–2. These options take effect the next time you boot the system. Example $ RUN SYS$SYSTEM:SYSMAN SYSMAN> STARTUP SET OPTIONS/VERIFY=FULL/OUTPUT=FILE/CHECKPOINTING This example requests startup logging with: Full verification Output to the STARTUP.
Starting Up and Shutting Down the System 4.7 Writing a New Boot Block on the System Disk 4.7 Writing a New Boot Block on the System Disk Block 0 on a system disk is the boot block. It contains the size and location of the primary bootstrap image, which is used to boot the system. On VAX systems, the primary bootstrap image is VMB.EXE. On Alpha systems, the primary bootstrap image is APB.EXE. Certain processors must read the boot block to obtain the location of the primary bootstrap image.
Starting Up and Shutting Down the System 4.7 Writing a New Boot Block on the System Disk Use the device name format described in the upgrade and installation documentation for your processor. If you want to boot using a bootstrap image other than the default, you must specify the full file specification of the image, including device and directory. 3.
Starting Up and Shutting Down the System 4.7 Writing a New Boot Block on the System Disk This message means that access to the target device is limited. Check the WRITE PROTECT button on the disk drive. • ‘‘Boot file is not contiguous.’’ This message means that the primary bootstrap image, VMB.EXE or APB.EXE, is not contiguous on disk. Perform one of the following actions: On VAX systems, enter the following command: $ COPY/CONTIGUOUS device:[VMS$COMMON.SYSEXE]VMB.EXE; _$ device:[VMS$COMMON.
Starting Up and Shutting Down the System 4.8 Shutting Down the System For More Information Procedure Purpose OPCCRASH.EXE An emergency shutdown program. Run the OPCCRASH emergency shutdown program if you are unable to perform an orderly shutdown with SHUTDOWN.COM. Section 4.8.5 Shutdown using console commands Emergency shutdown commands. Use these console shutdown commands only if OPCCRASH.EXE fails. Section 4.8.6 4.8.1 Performing an Orderly Shutdown with SHUTDOWN.COM Use SYS$SYSTEM:SHUTDOWN.
Starting Up and Shutting Down the System 4.8 Shutting Down the System Enter an integer. If you have defined the system logical name SHUTDOWN$MINIMUM_MINUTES, its integer value is the minimum value that you can enter. For example, if the logical name is defined as 10, you must specify at least 10 minutes to final shutdown or an error message is returned. If you do not enter a value, SHUTDOWN.COM uses the logical name value. Caution The default is 0 minutes.
Starting Up and Shutting Down the System 4.8 Shutting Down the System 8.
Starting Up and Shutting Down the System 4.
Starting Up and Shutting Down the System 4.8 Shutting Down the System SHUTDOWN message on AVALON, from user SYSTEM at _AVALON$OPA0: 12:10:00.20 AVALON will shut down in 0 minutes; back up 12:30. Please log off node AVALON. MONTHLY PREVENTIVE MAINTENANCE 17 terminals have been notified on AVALON %SHUTDOWN-I-SITESHUT, The site-specific shutdown procedure will now be invoked. %SHUTDOWN-I-STOPUSER, All user processes will now be stopped. %SHUTDOWN-I-REMOVE, All installed images will now be removed.
Starting Up and Shutting Down the System 4.8 Shutting Down the System 9. SHUTDOWN.COM dismounts all mounted volumes and, if you requested it, spins down the disks. If you defined SHUTDOWN$VERBOSE, the procedure lists each disk as it is dismounted. The procedure does not spin down the system disk, nor does it dismount or spin down the quorum disk (if one exists on your system). 10. SHUTDOWN.COM closes the operator log file. 11. SHUTDOWN.COM runs the program SYS$SYSTEM:OPCCRASH.EXE to shut down the system.
Starting Up and Shutting Down the System 4.8 Shutting Down the System Logical Name Description SHUTDOWN$MINIMUM_MINUTES Defines the minimum number of minutes you can specify as number of minutes to shutdown. For example, if your users require 30 minutes’ notice before a system shutdown, define this logical name to be 30. This logical must be defined with the /SYSTEM qualifier.
Starting Up and Shutting Down the System 4.
Starting Up and Shutting Down the System 4.8 Shutting Down the System Qualifier Function [NO]SPIN_DOWN_DISKS Spins down disks. The default is NO. You cannot spin down the system disk. [NO]INVOKE_SYSHUTDOWN Invokes the site-specific shutdown procedure. The default is INVOKE_SYSHUTDOWN. [NO]AUTOMATIC_REBOOT Reboots the system automatically when the shutdown is complete. The default is NO. [NO]REBOOT_CHECK Checks for basic operating system files and notifies you if any are missing. The default is NO.
Starting Up and Shutting Down the System 4.8 Shutting Down the System • Writes the modified page list back to disk. This ensures that all writable section files are updated to their correct state before the system crashes and all in-memory data is lost. • Unless the logical name OPC$NODUMP is defined, creates a crash dump by writing physical memory to the system dump file. For more information about the system dump file, see Section 16.1. In an emergency, if you cannot invoke SHUTDOWN.
Starting Up and Shutting Down the System 4.8 Shutting Down the System On VAX systems, the following message is also displayed: USE CONSOLE TO HALT SYSTEM Halt the system when you see this message. 4.8.6 Performing an Emergency Shutdown Using Console Commands Certain computer consoles have an additional emergency CRASH command. If your computer has the CRASH command, it is located on the console media; you can execute it only from the console prompt on the console terminal.
5 Customizing the Operating System After you install the operating system, you can customize it for site-specific requirements. Information Provided in This Chapter This chapter describes the following tasks: Task Section Adding and deleting optional files Section 5.1 Modifying site-specific startup command procedures Section 5.2 Modifying login command procedures Section 5.3 Customizing startup databases Section 5.4 †Registering images that have system version dependencies Section 5.
Customizing the Operating System 5.1 Adding and Deleting Optional Files Depending on the system you are using, you can add or delete files in one of the following ways: • On VAX systems, you can use the OpenVMS Tailoring utilities, VMSTAILOR and DECW$TAILOR: VMSTAILOR—applies to optional system files DECW$TAILOR—applies to support for DECwindows Delete files from and add files to the system disk by identifying classes and subclasses of operating system files that you want to add or delete.
Customizing the Operating System 5.2 Modifying Site-Specific Startup Command Procedures Term Definition Site-specific startup command procedures Startup command procedures that you can modify to perform operations specific to your site. Use any text editor to add or modify commands in these procedures. STARTUP.COM executes several site-specific startup command procedures that Compaq provides. These procedures are listed in Table 5–1.
Customizing the Operating System 5.2 Modifying Site-Specific Startup Command Procedures version of the file because your .COM version is damaged, copy the .TEMPLATE file to a file with the .COM file type, and edit the copy. 5.2.1.2 Rules for Modifying Startup Command Procedures When modifying site-specific startup command procedures, be sure to follow these rules: • Conform to the rules of command procedures, as described in the OpenVMS User’s Manual. • Keep the files in the SYS$MANAGER directory.
Customizing the Operating System 5.2 Modifying Site-Specific Startup Command Procedures 4. Adds any new drivers by executing one of the following commands: • On VAX systems, the SYSGEN command AUTOCONFIGURE ALL. This command automatically configures the device driver database, locates all standard devices attached to the system, and loads and connects their device drivers. • On Alpha systems, the SYSMAN command IO AUTOCONFIGURE.
Customizing the Operating System 5.2 Modifying Site-Specific Startup Command Procedures 5.2.3 Modifying SYPAGSWPFILES.COM to Install Page and Swap Files When the system boots, it automatically installs the primary page and swap files, if they are present in the SYS$SYSTEM directory. If the page and swap files are not in SYS$SYSTEM, or if secondary page and swap files are located on a disk other than the system disk, you must install these files each time the system boots.
Customizing the Operating System 5.2 Modifying Site-Specific Startup Command Procedures 3. If necessary, add a MOUNT command to mount the disk or disks that are to hold the secondary page and swap files. Disks other than the system disk are not yet mounted at the time SYPAGSWPFILES.COM is invoked. For information about the MOUNT command, refer to the MOUNT section of the OpenVMS System Management Utilities Reference Manual. 4.
Customizing the Operating System 5.2 Modifying Site-Specific Startup Command Procedures Example To connect a nonstandard device called the QQ device, add the following commands to SYCONFIG.COM: $ SYSGEN := $SYSGEN $ SYSGEN CONNECT QQA0 5.2.4.
Customizing the Operating System 5.2 Modifying Site-Specific Startup Command Procedures Table 5–2 (Cont.) Commonly Defined System Logical Names Logical Name For More Information NETPROXY OpenVMS Guide to System Security †NET$PROXY OpenVMS Guide to System Security QMAN$MASTER Section 13.3 RIGHTSLIST OpenVMS Guide to System Security SYS$ERRORLOG Section 20.4.1 SYS$MONITOR Section 20.8.
Customizing the Operating System 5.2 Modifying Site-Specific Startup Command Procedures 5.2.6 Modifying SYSECURITY.COM to Set Up Security Auditing SYSECURITY.COM runs prior to starting the security audit server process. You can add commands to this file to mount or define any disks that you want to hold security auditing log files or local security archive files. For more information about security auditing, see Section 20.7. Ordinarily, the system turns on auditing in VMS$LPBEGIN just before SYSTARTUP_VMS.
Customizing the Operating System 5.2 Modifying Site-Specific Startup Command Procedures 2. To prevent the command procedure from exiting if it invokes an error, include the DCL command SET NOON at the beginning of the file. This command disables error checking after the execution of each command in the procedure. For more information about error checking, refer to the OpenVMS User’s Manual. 3. Add commands to perform site-specific operations. Sections 5.2.7.1 to 5.2.7.
Customizing the Operating System 5.2 Modifying Site-Specific Startup Command Procedures that operator-assisted mounts are disabled. To enable this feature during SYSTARTUP_VMS.COM, specify /ASSIST with each MOUNT command. For a DSA disk, you must also insert a WAIT statement in the command procedure prior to the first MOUNT statement. The wait time is controller-dependent. If you omit a WAIT statement, the MOUNT request might fail with a ‘‘no such device’’ status.
Customizing the Operating System 5.2 Modifying Site-Specific Startup Command Procedures 5.2.7.5 Installing Known Images You can install commonly used programs as known images to reduce the I/O overhead in activating those images and to assign attributes or privileges to the images. Use the Install utility (INSTALL) to install known images, which you must reinstall each time the system boots. STARTUP.COM includes a series of INSTALL commands that install certain system programs as known images.
Customizing the Operating System 5.2 Modifying Site-Specific Startup Command Procedures Example The following commands, executed in SYSTARTUP_VMS.COM, invoke SDA, save and analyze the crash dump, and print a listing file: $ ANALYZE/CRASH_DUMP SYS$SYSTEM:SYSDUMP.DMP COPY SYS$SYSTEM:SAVEDUMP.DMP ! Save dump file SET OUTPUT DISK1:SYSDUMP.
Customizing the Operating System 5.2 Modifying Site-Specific Startup Command Procedures For example, you could include the following command in SYSTARTUP_ VMS.COM: $ DEFINE/SYSTEM SYS$ANNOUNCE "SIRIUS OPENVMS CLUSTER AT ANDROMEDA, INC." Or you might prefer to print a file by including the following command: $ DEFINE/SYSTEM SYS$ANNOUNCE "@SYS$MANAGER:ANNOUNCE.TXT" If you do not define SYS$ANNOUNCE, the system does not display an announcement.
Customizing the Operating System 5.2 Modifying Site-Specific Startup Command Procedures 5.2.7.13 Starting a DECnet or TCP/IP Network Before starting the network, you must register your DECnet license and configure your network. See Chapter 23 for information about setting up DECnet network. If your system participates in a DECnet network, you might need to start the DECnet software each time your system boots: • If you are running DECnet for OpenVMS on your system, edit SYSTARTUP_ VMS.
Customizing the Operating System 5.2 Modifying Site-Specific Startup Command Procedures The maximum number of interactive users influences the service rating that the LAT software assigns to a service node. The LAT software uses a ratio of current users to maximum users in calculating a rating. An artificially high user limit results in a high service rating, indicating—erroneously—that the service node is more able to provide services. For information about LAT software, see Section 26.1.
Customizing the Operating System 5.3 Modifying Login Command Procedures to Customize User Environments in to a captive account, the process is terminated because the system environment might not have been set up properly. If you expect SYLOGIN.COM to cause an error, you must use either SET NOON or ON ERROR commands, and explicitly exit the command procedure with a successful status so that the user’s login command procedure can be executed. LOGIN.
Customizing the Operating System 5.4 Customizing Startup Databases with SYSMAN File Description VMS$PHASES.DAT Determines the order of the phases of startup in a sequential list. This file includes a series of four basic phases (INITIAL, CONFIGURE, DEVICE, and BASEENVIRON) needed to bring the operating system up to a basic working environment, followed by a series of phases for layered products. STARTUP.COM uses this list of phases for startup. Do not modify this file. VMS$VMS.
Customizing the Operating System 5.4 Customizing Startup Databases with SYSMAN Each phase must meet the prerequisites of the following phase; therefore, the order of the phases is extremely important. Components that occur in a phase cannot have dependencies on components that are in the same phase or in subsequent phases. When installing layered products using SYSMAN, be sure that all requisite components occur in a previous phase. • Mode (or method) by which the component file is to run.
Customizing the Operating System 5.4 Customizing Startup Databases with SYSMAN 5.4.5 Showing the Contents of a Startup Database To display the contents of the current database, enter the STARTUP SHOW FILE command. You can specify various qualifiers for this command to control the amount of information displayed. For more information, refer to the OpenVMS System Management Utilities Reference Manual. Example $ RUN SYS$SYSTEM:SYSMAN SYSMAN> STARTUP SHOW FILE/FULL 5.4.
Customizing the Operating System 5.4 Customizing Startup Databases with SYSMAN Example $ RUN SYS$SYSTEM:SYSMAN SYSMAN> STARTUP ADD/MODE=DIRECT/PHASE=LPMAIN FOR$LPMAIN_043_STARTUP.COM SYSMAN> STARTUP SHOW FILE/NODE SYSMAN> STARTUP MODIFY FILE FOR$LPMAIN_043_STARTUP.COM/NODE=ZNODE 5.4.8 Deleting a Record from a Startup Database Deleting a record from a startup database prevents a product from starting up. To delete a record, use the STARTUP REMOVE FILE command.
Customizing the Operating System 5.4 Customizing Startup Databases with SYSMAN To enable a previously disabled file, enter the STARTUP ENABLE FILE command in the following format: STARTUP ENABLE FILE filespec where filespec specifies the name of the file to be enabled. Example $ RUN SYS$SYSTEM:SYSMAN SYSMAN> STARTUP ENABLE FILE FOR$LPMAIN_043_STARTUP.COM/NODE=ZURICH 5.
Customizing the Operating System 5.5 Registering Images that Have System Version Dependencies When you upgrade your system to a new version of the operating system, an image might fail because the new version no longer matches the image’s version requirements. However, an image might continue to be compatible with the new operating system version, even if it fails the version check. Note In OpenVMS VAX Version 6.
Customizing the Operating System 5.5 Registering Images that Have System Version Dependencies filename Specifies the name and location of the image you want to register. The filename parameter accepts wildcard characters. Table 5–3 REGISTER_PRIVILEGED_IMAGE.COM Keywords Keyword Action ANALYZE Displays version-dependent image names and their subsystem dependencies. REGISTER Registers images on the local system. DEREGISTER Deletes images from the registry on the local system.
Customizing the Operating System 5.6 Customizing the Help Message Database for a description of the files that you must manipulate to customize the Help Message database. Note Currently, user-supplied comments or additions to Compaq supplied .MSGHLP$DATA files are not preserved through the next upgrade. However, your own .MSGHLP$DATA files are not affected by future releases. You can reuse .MSGHLP files to insert your own messages into future Compaq supplied database files.
Customizing the Operating System 5.6 Customizing the Help Message Database Thereafter, if Help Message cannot translate a status code and the SYS$LIBRARY:MSGHLP$MESSAGE_SECTION.EXE image exists, Help Message activates it and searches all message section files to which it points. The impact on Help Message search time depends upon the number of files searched. 2.
Customizing the Operating System 5.6 Customizing the Help Message Database 5. When your .OLB file reflects the message section files you want Help Message to search, copy the final .EXE file from your account to SYS$LIBRARY:. Example The following example demonstrates this sequence of events: 1. Link all OpenVMS supplied message section files. 2. Review the resulting .OLB file. 3. Delete the VVIEFMSG module from the .OLB file. 4. Add the file USERS:[TOOLS]NEW_MSGS.EXE to the list in the .OLB file. 5.
Customizing the Operating System 5.6 Customizing the Help Message Database by MSGHLP$LIBRARY, or you can create specialized search paths to include different configurations of .MSGHLP$DATA files. A search path definition can include individual file names or can point to one or more directories. If you specify a directory with no file name, Help Message searches all .MSGHLP$DATA files currently found in that directory. Pointing to a directory instead of individual files can minimize your bookkeeping when .
Customizing the Operating System 5.6 Customizing the Help Message Database Use this syntax to extract one or more messages specified by the search string: HELP/MESSAGE/EXTRACT=filename.MSGHLP search-string 2. Check the contents of the resulting .MSGHLP file to be sure that it contains only the data that you want to delete from the database. Edit out any messages that you do not want to delete from the database. 3. Use /DELETE to delete the contents of the .MSGHLP file from the database.
Customizing the Operating System 5.6 Customizing the Help Message Database supplied message descriptions do not change during the upgrade, you can reuse .MSGHLP files to reinsert comments after the upgrade. How to Perform This Task 1. Extract the message to which you want to add a comment. The following example extracts hypothetical message NOSNO: $ HELP/MESSAGE/EXTRACT=NOSNO.MSGHLP NOSNO 2. Edit the .MSGHLP file to add your comment. The .
Customizing the Operating System 5.6 Customizing the Help Message Database • The message you modify subsequently displays with change bars to designate it as unsupported, user-supplied data. Note Currently, the Compaq supplied message is reinserted into the database at the next upgrade and the user-supplied text is overwritten. How to Perform This Task 1. Extract the message having the text or description you want to change: HELP/MESSAGE/EXTRACT=filename.MSGHLP search-string 2. Check the .
Customizing the Operating System 5.6 Customizing the Help Message Database How to Perform This Task 1. Create a .MSGHLP file with your message descriptions in it. (Section 5.6.4 includes an example of the .MSGHLP file format.) 2. Specify your .MSGHLP file as input to update the Compaq supplied .MSGHLP$DATA file. Assuming that MSGHLP$LIBRARY.MSGHLP$DATA is the default, all you must enter is: HELP/MESSAGE/INSERT=filename.MSGHLP Example $ HELP/MESSAGE/INSERT=MYMESSAGES.MSGHLP 5.
Customizing the Operating System 5.7 Customizing Mail On VAX systems, if neither 8 nor 16 is in the value for MAIL$SYSTEM_FLAGS, the system checks to see whether DECnet for OpenVMS or DECnet-Plus is running on the system and operates as if the appropriate bit were set. If MAIL$SYSTEM_FLAGS accidently specifies both DECnet and DECnet-Plus, the Mail utility defaults to DECnet-Plus. MAIL$INTERNET_MODE Certain network addresses can be interpreted by the Mail utility as either DECnet-Plus names or SMTP names.
Customizing the Operating System 5.8 Setting Up the Multipurpose Internet Mail Extension (MIME) Utility 5.8.1 Defining a Foreign Command Your only installation work is to define a foreign command to run the utility, for example: MIME:== $SYS$SYSTEM:MIME.EXE You can establish systemwide defaults for displaying MIME-encoded messages by creating two files: MIME$MAILCAP.DAT and MIME$FILETYPES.DAT. MIME$MAILCAP.
6 Setting System Time This chapter describes how to control system time on OpenVMS systems, describes how system time relates to Universal Coordinated Time (UTC), and tells how to ensure that local system time remains correct when local time changes, as for daylight saving time. This chapter describes the following tasks: Task System Setting time zone information OpenVMS Alpha Version 7.3 Section 6.2 Setting time zone information OpenVMS Alpha before Version 7.3 and OpenVMS VAX Section 6.
Setting System Time 6.1 Setting Correct Time Zone Information on Your System 6.1.2 Understanding Time-Setting Concepts Understanding some time concepts will help you see the importance of setting correct time zone information on your system. 6.1.2.1 Coordinated Universal Time Coordinated Universal Time (UTC) is similar in most respects to Greenwich Mean Time (GMT). Under the UTC time standard, zero hours occurs when the Greenwich Meridian is at midnight.
Setting System Time 6.1 Setting Correct Time Zone Information on Your System Some time zones do not have full-hour TDFs. In these cases, find the specific value on the map itself. For example, if you live in Adelaide, Australia, your TDF is +9:30. In a time zone with daylight saving time, the TDF for daylight saving time is typically +1:00 from the standard time.
+10:00 +9:00 +11:00 +12:00/ 12:00 11:00 10:00 8:00 9:00 6:00 7:00 4:00 5:00 2:00 3:00 0:00 1:00 +2:00 +1:00 +4:00 +3:00 +6:00 +5:00 ARCTIC OCEAN ARCTIC OCEAN 80¡ 80¡ 3 ASIA 60¡ 60¡ NORTH AMERICA ASIA EUROPE 3h 30m 40¡ NORTH PACIFIC OCEAN +6h 30m +4h 30m NORTH ATLANTIC OCEAN 1 DAY +1 DAY 20¡ 20¡ +3h 30m AFRICA +7 +7h 30m +5h 30m INDIAN OCEAN 3h 30m +8 0¡ 40¡ 0¡ +5h 30m SOUTH AMERICA +6h 30m 20¡ 20¡ AUSTRALIA +9h 30m SOUTH PACIFIC OCEAN +2 40¡ 40¡ SOUTH ATLANTIC OCEAN
Setting System Time 6.1 Setting Correct Time Zone Information on Your System OpenVMS Version Architecture See 7.3 Alpha Section 6.2 7.3 VAX Section 6.3 7.2 and earlier VAX or Alpha Section 6.3 All OpenVMS Cluster Section 6.4 6.2 Setting Time Zone Information on OpenVMS Alpha Version 7.3 and Later This section contains instructions for setting time zone information on OpenVMS Alpha Version 7.3 and later. For instructions on setting time sone information on OpenVMS Alpha prior to Version 7.
Setting System Time 6.2 Setting Time Zone Information on OpenVMS Alpha Version 7.3 and Later This results in the following (or similar) display: AUTO_DLIGHT_SAV is set to "1". OpenVMS will automatically change to/from Daylight Saving Time. (in timezones that use Daylight Saving Time) LOCAL TIME ZONE LOCAL SYSTEM TIME = EASTERN / US -- DAYLIGHT TIME = 4-OCT-2000 11:14:00.51 (EDT) TIME DIFFERENTIAL FACTOR = -4:00 TIME ZONE RULE = EST5EDT4,M4.1.0/02,M10.5.
Setting System Time 6.2 Setting Time Zone Information on OpenVMS Alpha Version 7.
Setting System Time 6.2 Setting Time Zone Information on OpenVMS Alpha Version 7.3 and Later If you answer Yes or press Return to accept the default, time zone information is set.
Setting System Time 6.2 Setting Time Zone Information on OpenVMS Alpha Version 7.3 and Later If you answer Yes, the following is displayed: Enter the time adjustment value you would like to add to the local time. You can enter hours only (hh) or hours and minutes (hh:mm) The value can be positive (hh:mm or +hh:mm) or negative (-hh:mm). You are then asked to enter the time adjustment, usually either -1:00 or +1:00.
Setting System Time 6.3 Setting Time Zone Information on OpenVMS VAX Systems 3. Press Return to accept the default of BOTH or enter one of the other choices in answer to the following question: Configure which time parameter (TIMEZONE/TDF/BOTH/NONE)? [BOTH] Note Compaq recommends that you set both the time zone and the TDF. If you set the TDF without setting the time zone, the procedure cannot provide default TDF values.
Setting System Time 6.3 Setting Time Zone Information on OpenVMS VAX Systems 3. The system displays areas with different time zones and asks you to select your area. Enter a number, for example, 6: US Time Zone Menu 1) Alaska 2) Aleutian 3) Arizona 4) Central 5) East-Indiana 6) Eastern 7) Hawaii 10) Mountain 8) Indiana-Starke 11) Pacific 9) Michigan 12) Samoa 0) None of the above Select the number above that best describes your location: 6 4.
Setting System Time 6.3 Setting Time Zone Information on OpenVMS VAX Systems 2. Select option 1 to verify the TDF displayed or to enter a new one: Configuring the Time Differential Factor (TDF) Enter ? anytime for help [0] [1] [2] Exit Set the Time Differential Factor Display the Time Differential Factor Please pick an option number [2]: 1 The system then displays the following information: The Time Differential Factor (TDF) is the difference between your system time and Coordinated Universal Time (UTC).
Setting System Time 6.4 Setting Time in an OpenVMS Cluster Environment 6.4 Setting Time in an OpenVMS Cluster Environment The local time, the TDF, and the time zone must be the same on all nodes in an OpenVMS Cluster environment. You can use the System Management utility (SYSMAN) DO command to invoke the command procedure SYS$MANAGER:UTC$TIME_SETUP.
Setting System Time 6.5 Adjusting for Daylight Saving Time If AUTO_DLIGHT_SAV is set to 1, an OpenVMS Alpha Version 7.3 (and later) system automatically sets the time forward or back when local time changes between daylight saving time and standard time. If AUTO_DLIGHT_SAV is set to 0 (the default), OpenVMS does not automatically change between daylight saving time and standard time.
Setting System Time 6.5 Adjusting for Daylight Saving Time You can run DAYLIGHT_SAVINGS.COM interactively and respond to prompts for input, or run the command procedure with parameters. To run DAYLIGHT_SAVINGS.
Setting System Time 6.5 Adjusting for Daylight Saving Time • Queue a batch job to make the changes at a future time. (This is the most common use of this command procedure.) The following example of DAYLIGHT_SAVINGS.COM shows answers that cause the procedure to queue a batch job, DST_CHANGE, which will execute when the time changes from standard time to daylight saving time. Many of the questions are similar to those explained in Section 6.3.2. In the example, the initial TDF value is -5:00.
Setting System Time 6.6 Setting Time Using the Battery-Backed Watch (BBW) (Alpha Only) 6.6 Setting Time Using the Battery-Backed Watch (BBW) (Alpha Only) The OpenVMS Alpha architecture maintains the current date and time in the Battery-Backed Watch (BBW) across power failures and system downtime. The BBW is functionally equivalent to the Time of Day Register (TODR) that the VAX architecture uses. One difference, however, is the BBW’s constraint on the date range.
Setting System Time 6.7 Choosing Languages, and Date and Time Formats Later, users can override the system defaults set up by the system manager and select their own date and time formats. Steps to Change Languages, and Dates and Times For languages other than English or date/time formats other than the defaults, you must complete these steps. Note Compaq recommends that you include these steps within the command procedure SYS$MANAGER:SYSTARTUP_VMS.COM. 1.
Setting System Time 6.7 Choosing Languages, and Date and Time Formats 6.7.2 Invoking LIB$DT_STARTUP.COM The SYS$MANAGER:LIB$DT_STARTUP.COM command procedure defines the possible choices for the following logicals: • SYS$LANGUAGES The system loads the languages you have selected using the SYS$LANGUAGES (plural) logical. Users can later select their own choice of languages by defining the SYS$LANGUAGE (singular) logical, as explained in Section 6.7.4.
Setting System Time 6.7 Choosing Languages, and Date and Time Formats 6.7.3.1 Defining Your Own Format To define your own format, define LIB$DATE_FORMAT_nnn and LIB$TIME_ FORMAT_nnn, using the mnemonics shown in Table 6–2. Replace nnn with a number of your choice. Note For user-defined formats, Compaq recommends that you use values of _500 and above for _nnn.
Setting System Time 6.7 Choosing Languages, and Date and Time Formats Table 6–2 (Cont.
Setting System Time 6.7 Choosing Languages, and Date and Time Formats Table 6–3 (Cont.) Predefined Output Date Formats Date Format Logical Format Example LIB$DATE_FORMAT_014 !MN0-!D0-!Y2 01-13-98 LIB$DATE_FORMAT_015 !MN0.!D0.!Y2 01.13.98 LIB$DATE_FORMAT_016 !MN0 !D0 !Y2 01 13 98 LIB$DATE_FORMAT_017 !D0/!MN0/!Y2 13/01/98 LIB$DATE_FORMAT_018 !D0/!MN0-!Y2 13/01-98 LIB$DATE_FORMAT_019 !D0-!MN0-!Y2 13-01-98 LIB$DATE_FORMAT_020 !D0.!MN0.!Y2 13.01.
Setting System Time 6.7 Choosing Languages, and Date and Time Formats Table 6–4 (Cont.) Predefined Output Time Formats Time Format Logical Format Example LIB$TIME_FORMAT_006 !H04.!M0 09.13 LIB$TIME_FORMAT_007 !H04 !M0 09 13 LIB$TIME_FORMAT_008 !HH4:!M0 9:13 LIB$TIME_FORMAT_009 !HH4.!M0 9.
Setting System Time 6.9 Using SYSMAN to Manage System Time 6.9 Using SYSMAN to Manage System Time You can manage system time for an OpenVMS Cluster system with SYSMAN CONFIGURATION commands. Table 6–5 summarizes these CONFIGURATION commands and their functions. Table 6–5 SYSMAN CONFIGURATION Commands Command Function CONFIGURATION SET TIME Updates system time CONFIGURATION SHOW TIME Displays current system time 6.9.
Setting System Time 6.9 Using SYSMAN to Manage System Time 2. The next example sets the environment to NODE21, NODE22, and NODE23, sets privilege, and modifies the system time on all three nodes: SYSMAN> SET ENVIRONMENT/NODE=(NODE21,NODE22,NODE23) SYSMAN> SET PROFILE/PRIVILEGE=LOG_IO SYSMAN> CONFIGURATION SET TIME 12:38:00 3.
Setting System Time 6.9 Using SYSMAN to Manage System Time In an OpenVMS Cluster system (or for a node that is not part of the cluster), when you set the time, the TODR and the base time in the system image are reset with the values for the new year. However, multiple systems might share the system image. This does not normally cause a problem except after the first day of a new year. Note The system issues the SET TIME command when it boots and as a part of the normal SHUTDOWN command procedure.
Setting System Time 6.9 Using SYSMAN to Manage System Time If you are running the DIGITAL Distributed Time Service (DECdts) on your system, you must use it to set the time.
7 Managing User Accounts This chapter describes how to grant access to users on your system. It tells you how to add and maintain user accounts, and it describes the privileges that you can give and the resources that you can allocate to the users on your system. It also describes the system management features of the OpenVMS Mail utility (MAIL). Information Provided in This Chapter This chapter describes the following tasks: Task Section Managing system-supplied UAF accounts Section 7.
Managing User Accounts 7.1 Understanding the User Authorization File 7.1 Understanding the User Authorization File The system user authorization file (UAF), SYS$SYSTEM:SYSUAF.DAT, contains user account records. Each record consists of fields that provide information about the account’s user name, login characteristics, login restrictions, and resource control attributes.
Managing User Accounts 7.1 Understanding the User Authorization File Table 7–1 Resource Type Limits Resource Type Description of Limit Pooled A process and its subprocesses share the resource on a firstcome, first-served basis until the limit is reached. Nondeductible A subprocess receives the same limit on the resource as the creator receives. The creator’s limit is not affected. Deductible A subprocess receives a portion of the creator’s resource. That portion is deducted from the creator’s limit.
Managing User Accounts 7.1 Understanding the User Authorization File Table 7–2 (Cont.
Managing User Accounts 7.2 Understanding the Protection of Authorization Files The primary proxy database that the system uses is the NET$PROXY.DAT file. NETPROXY.DAT is maintained: For use by DECnet for OpenVMS For backward compatibility See Section 7.9.3 for more details about network proxy accounts. • Rights database file, RIGHTSLIST.DAT The RIGHTSLIST.DAT authorization file is created with the following default protection: RIGHTSLIST.
Managing User Accounts 7.3 Understanding UAF Login Checks Table 7–3 (Cont.) System Login Flow Step Action Result 4. System checks whether SYS$LOGIN is defined. If SYS$LOGIN is defined, the logical name is translated (in the case of DCL, to SYS$MANAGER:SYLOGIN.COM) and that procedure executes. If SYS$SYLOGIN is not defined, no system login is run. If a command procedure is specified in the LGICMD field and that procedure exists, it executes.
Managing User Accounts 7.4 Managing System-Supplied UAF Accounts Table 7–4 describes system-supplied UAF accounts. Table 7–4 System-Supplied UAF Accounts UAF Record Description DEFAULT Serves as a template for creating new user accounts. A new user account is assigned the values of the DEFAULT account except where you explicitly override those values. Thus, whenever you add a new account, you need only specify values for fields that you want to be different.
Managing User Accounts 7.4 Managing System-Supplied UAF Accounts 7.4.2.1 Creating Field Service Accounts (Alpha Only) On Alpha systems, you can use CREATE_SPECIAL_ACCOUNTS.COM to create accounts for Compaq support representatives. In creating these accounts, follow these guidelines: • Create an account for each Compaq support (Field Service) representative rather than just one account called FIELD for all the representatives. Note that you must use the command procedure for each account you want to create.
Managing User Accounts 7.4 Managing System-Supplied UAF Accounts For example: UAF> MODIFY JOHN_JONES/FLAGS=NODISUSER 7.4.2.2 Creating SYSTEST and SYSTEST_CLIG Accounts (Alpha Only) The following example shows typical dialogue with CREATE_SPECIAL_ ACCOUNTS.COM when it is used to create SYSTEST and SYSTEST_CLIG accounts: $ @CREATE_SPECIAL_ACCOUNTS.COM This procedure creates accounts.
Managing User Accounts 7.4 Managing System-Supplied UAF Accounts To enable the account when it is needed, run AUTHORIZE and enter the command in the following format: MODIFY username /FLAGS=NODISUSER 2. Optionally, change fields in the DEFAULT account. For example: UAF> MODIFY DEFAULT/DEVICE=DISK$USER/WSQUO=750 In this example, the default device is set to the name most commonly used for user accounts that will be added.
Managing User Accounts 7.4 Managing System-Supplied UAF Accounts How to Perform This Task 1. Set your default to the directory that contains the SYSUAF.DAT file, typically, SYS$SYSTEM. 2. Gain access to a specific user record by running AUTHORIZE. 3. Enter the SHOW command (see example) to display a specific user record. 4. Enter AUTHORIZE commands such as ADD and MODIFY to create or change the information in the fields of the UAF record. See Section 7.
Managing User Accounts 7.4 Managing System-Supplied UAF Accounts • Name of the command procedure to be executed automatically at login time. If the field is blank, the system uses the default CLI (DCL), and executes SYS$LOGIN:LOGIN.COM by default. • Command language interpreter tables (if blank, same as CLI field). • Device and directory names for default file access.
Managing User Accounts 7.5 Preparing to Add User Accounts Table 7–5 (Cont.) Account Types Account Type Characteristics Limited Access This account provides controlled login to the system and, in some cases, has only a subset of user software available. Limited-access accounts ensure that the system login command procedure (SYLOGIN.COM) and the process login command procedure (specified by the /LGICMD qualifier in the UAF), as well as any command procedures they call, are executed.
Managing User Accounts 7.5 Preparing to Add User Accounts For interactive accounts, it is best to let the person using the account control the password. Initially, provide a password that is not easy to guess. The user will be forced to change the password at first login. Only the person using the account should know the password.
Managing User Accounts 7.5 Preparing to Add User Accounts Assign accounts the same group number if their owners perform similar work, access the same files frequently, or use many of the same logical names. See the OpenVMS Guide to System Security for a detailed discussion of the user identification code. Note Compaq reserves UIC group 1 and groups 300–377. 7.5.2.3 Adding a Disk Quota Entry Disk quotas limit the amount of disk space available to individual users on a particular volume.
Managing User Accounts 7.5 Preparing to Add User Accounts 7.5.2.5 Setting the User Default Device for a Captive Account For a captive account, whether you create a top-level directory depends on the nature of the user system. If people use files in a particular directory, make that directory the default directory specification. For example, if the inventory system uses the files DISK$DATA:[INV]STOCK1.DAT and DISK$DATA:[INV]STOCK2.
Managing User Accounts 7.6 Adding User Accounts 7.6 Adding User Accounts The following sections explain how to use two different methods for adding user accounts: • The Authorize utility (AUTHORIZE) • A command procedure 7.6.1 Adding a User Account with AUTHORIZE Once you analyze the purpose of a user account and decide which attributes and resources it requires, you can use the Authorize utility (AUTHORIZE) to create the account. How to Perform This Task 1.
Managing User Accounts 7.6 Adding User Accounts Table 7–6 (Cont.) Qualifiers Used with AUTHORIZE Priority2 /PRIORITY Privileges /DEFPRIVILEGES /PRIVILEGES Login Access Controls 3 /ACCESS /FLAGS4 /PRIMEDAYS /DIALUP /INTERACTIVE /REMOTE /EXPIRATION /LOCAL 2 Default values are usually adequate for accounts not running real-time processes. 3 By default, users are allowed to log in at any hour of any day. To override the setting of a particular day, use the DCL command SET DAY.
Managing User Accounts 7.6 Adding User Accounts The UIC must be unique for the system. For example, each account in the UIC group 200 must have a unique member number. You can list the UICs currently assigned to users by entering a question mark ( ? ) after the UIC member number prompt. The account is not created until you have answered all of the questions in the procedure.
Managing User Accounts 7.7 Maintaining User Accounts In establishing login command procedures for interactive accounts, you have the following choices: Login Command Procedure Description System As system manager, you normally create and maintain a standard login command procedure in the system directory (the file is usually named SYS$MANAGER:SYLOGIN.COM). You then assign the logical name SYS$SYLOGIN to the name of the file so that whenever a user logs in, the procedure is executed.
Managing User Accounts 7.7 Maintaining User Accounts Example 7–1 Sample Systemwide SYS$MANAGER:SYLOGIN.COM Login Command Procedure $ V = F$VERIFY(0) $START: $ ! $ SET NOCONTROL=Y ! Do not allow Ctrl/Y to exit procedure $ SET NOON $ ! $ ! Allow network jobs to start faster $ ! $ IF F$MODE() .EQS.
Managing User Accounts 7.7 Maintaining User Accounts Example 7–2 Sample Login Command Procedure (LOGIN.
Managing User Accounts 7.7 Maintaining User Accounts How to Perform This Task 1. Create a systemwide logout command procedure that executes whenever a user logs out. (The file is usually named SYS$MANAGER:SYLOGOUT.COM.) 2. To ensure that this command procedure executes, include a command in SYS$MANAGER:SYLOGIN.COM that equates the most commonly used abbreviation of the LOGOUT command (often LO) to the execution of the logout command procedure.
Managing User Accounts 7.7 Maintaining User Accounts 7.7.3 Listing User Accounts Use the AUTHORIZE command LIST to create the file SYSUAF.LIS, containing a summary of all user records in the UAF.
Managing User Accounts 7.7 Maintaining User Accounts • What to name the default records How to Perform This Task Once you define a user category and establish which record attributes are needed, you can create the default record. Examples 1.
Managing User Accounts 7.7 Maintaining User Accounts When you run AUTHORIZE to remove a user’s UAF record, AUTHORIZE also removes the user’s connections as a holder of identifiers in the rights database. However, if a departed user is the only remaining holder of a given identifier, remove that identifier to avoid future confusion. See the OpenVMS Guide to System Security. 5. Remove the user’s disk quota entry from the disk quota file, if one existed, with SYSMAN. 6.
Managing User Accounts 7.7 Maintaining User Accounts 7.7.6 Using BACKUP to Remove User Files If each user has a unique UIC, you can use the Backup utility (BACKUP) to remove the user’s files, even if the files are scattered throughout the directory structure. See the Backup utility section in the OpenVMS System Management Utilities Reference Manual for more information. Examples 1. The following example of a BACKUP command is used to remove files: $ BACKUP/DELETE PUBLIC:[...
Managing User Accounts 7.8 Restricting the Use of Accounts 7.8.1 Setting Day Types You can restrict the use of certain accounts by defining the days of the week as either PRIMARY or SECONDARY, and then assigning login restrictions to these day types. For example, if you define the days Saturday and Sunday as SECONDARY days, then any restrictions you assign to the SECONDARY day type apply to both.
Managing User Accounts 7.8 Restricting the Use of Accounts Note that network connections are treated differently than interactive connections and batch jobs. See the documentation for the network software you are running for information about disconnecting established network connections. 7.8.3 Restricting CPU Time OpenVMS Version 7.3 and later enables you to perform class scheduling using the SYSMAN interface.
Managing User Accounts 7.
Managing User Accounts 7.8 Restricting the Use of Accounts Keyword Meaning [NO]DISNEWMAIL [Do not] suppress ‘‘New Mail . . . ’’ announcements. [NO]DISPWDDIC [Do not] disable automatic screening of new passwords against a system dictionary. [NO]DISPWDHIS [Do not] disable automatic checking of new passwords against list of user’s old passwords. [NO]DISRECONNECT [Do not] disable automatic reconnection to an existing process when a terminal connection has been interrupted.
Managing User Accounts 7.8 Restricting the Use of Accounts semicolon (;) vertical bar ( | ) and double vertical bar ( | | ) • Use the DCL command READ/PROMPT in captive account login command procedures because the INQUIRE command is not allowed. • Set the subprocess limit to 0 to prevent the user from spawning out of the account. Set both the /PRCLM qualifier and the SYSGEN parameter PQL_MPRCLM.
Managing User Accounts 7.8 Restricting the Use of Accounts Example 7–4 Sample Captive Command Procedure $ deassign sys$input $ previous_sysinput == f$logical("SYS$INPUT") $ on error then goto next_command $ on control_y then goto next_command $ set control=(y,t) $ $next_command: $ on error then goto next_command $ on control_y then goto next_command $ $ if previous_sysinput .nes.
Managing User Accounts 7.8 Restricting the Use of Accounts In the user’s account record of the UAF, the default value of a user’s priority is 4; for practical purposes, the minimum value is 0. Ensure that the priority for timesharing users remains at the default. Note that if you give some users an advantage over other users by raising their priorities, ragged performance results, because the system reacts sharply to even small base priority differences. 7.
Managing User Accounts 7.9 Setting Up Special Accounts /PROXY causes SYSMAN to check that device is in the NODE::USERNAME format, which can be up to 63 characters in length. /LOG causes SYSMAN to display a message that the device and user have been added to the ALF database. To protect automatic login accounts, set the AUTOLOGIN flag in the account’s UAF record. This flag makes the account available only by autologin, batch, and network proxy.
Managing User Accounts 7.9 Setting Up Special Accounts $ RUN SYS$SYSTEM:AUTHORIZE UAF> ADD/IDENTIFIER KITE_FLYING/ATTRIBUTES=RESOURCE {message} UAF> GRANT/IDENTIFIER KITE_FLYING GEORGE/ATTRIBUTES=RESOURCE {message} UAF> GRANT/IDENTIFIER KITE_FLYING LINDORF/ATTRIBUTES=RESOURCE {message} UAF> EXIT 3. Create the disk quota authorization for the project identifier.
Managing User Accounts 7.9 Setting Up Special Accounts • The process creating the file does not have system privileges. See the OpenVMS System Management Utilities Reference Manual and the OpenVMS Guide to System Security for more information about the Creator ACE. 7.9.3 Understanding Network Proxy Accounts A network proxy account allows users on a remote node in a network to access data by way of a local account on your system.
Managing User Accounts 7.9 Setting Up Special Accounts • On systems running DECnet-Plus: NET$PROXY.DAT contains proxy information stored using DECnet-Plus full names. NETPROXY.DAT contains proxy information stored using DECnet-Plus node synonyms. Note Deleting either NETPROXY.DAT or NET$PROXY.DAT will result in incorrect functioning of proxy access on systems running DECnet for OpenVMS Phase IV. Also, many applications such as ALL-IN-1 rely on NETPROXY.DAT. The SYSUAF.
Managing User Accounts 7.9 Setting Up Special Accounts either PROXY2 or PROXY3, WALTER must specify the desired proxy account in the access control string of the DCL command used to perform network file operations. Caution Because the remote user receives the same privileges as the local user, do not set up proxy accounts associated with local accounts that have special privilege. Granting remote users such access powers poses a threat to the security of your system. 2.
Managing User Accounts 7.9 Setting Up Special Accounts 7.9.7 Displaying Proxy Accounts To display proxy accounts, use the AUTHORIZE command SHOW/PROXY. This command displays only the first 255 characters of the node name, although the command can handle a maximum of 1024 characters. The following examples assume that proxy access from RUBY::DELAPORT to the local account DELAPORT has been added to the network proxy authorization file as the default.
Managing User Accounts 7.10 Managing Mail 7.10 Managing Mail When managing user accounts, you might have to manage a user’s mail account.
Managing User Accounts 7.11 Managing System Resources In most cases, Alpha systems present to users, and accept from users, units of memory in a 512-byte quantity called a pagelet. Thus, one pagelet is the same size as one VAX page. Also, on an Alpha 8KB computer, 16 pagelets equal 1 Alpha page.
Managing User Accounts 7.11 Managing System Resources Table 7–8 (Cont.
Managing User Accounts 7.11 Managing System Resources Table 7–9 (Cont.) Descriptions of SYSTEM and DEFAULT Accounts Account Description Buffered I/O Count Limit (BIOlm) Limits the number of outstanding buffered I/O operations permitted for a user’s process. In a buffered I/O operation, the data transfer takes place from an intermediate buffer in the system pool, not from a process-specified buffer.
Managing User Accounts 7.11 Managing System Resources Table 7–9 (Cont.) Descriptions of SYSTEM and DEFAULT Accounts Account Description Enqueue Quota (Enqlm) Limits the number of locks a process (and its subprocesses) can own. OpenVMS Record Management Services (RMS) uses the Lock Management facility to synchronize shared file access, global buffers, and record locks.
Managing User Accounts 7.11 Managing System Resources Table 7–9 (Cont.) Descriptions of SYSTEM and DEFAULT Accounts Account Description Maximum Detached Processes Limit (Maxdetach) Specifies the maximum number of detached processes with the cited user name that can be active at one time. MAXDETACH can also be used to control the number of virtual terminals a user can have. To prevent the user from creating detached processes, specify the keyword NONE.
Managing User Accounts 7.11 Managing System Resources Table 7–9 (Cont.) Descriptions of SYSTEM and DEFAULT Accounts Account Description Working Set Quota (WSquo) Specifies the working set quota. This is the maximum amount of physical memory a user process can lock into its working set.
8 Managing Peripheral Devices System managers are often responsible for setting up and managing peripheral devices such as terminals and printers. This chapter describes these tasks. For information about managing storage media such as disks and tapes, see Chapter 9. Information Provided in This Chapter This chapter describes the following tasks: Task Section Getting information about devices on the system Section 8.2 Setting security protection characteristics on devices Section 8.
Managing Peripheral Devices 8.1 Understanding Device Names • All local DSA tape devices are named MUAn, where n is a unique tape unit number. Use of a single controller letter requires that the unit number for each local DSA device be unique. Duplicate unit numbers are possible if the local disks reside on different controllers.
Managing Peripheral Devices 8.2 Getting Information About Devices on the System If you specify a device name with the SHOW DEVICE command, the system displays information about the device you specified. If you use certain qualifiers with SHOW DEVICES, information is displayed about those devices that currently have volumes mounted or that have been allocated to processes. Refer to the OpenVMS DCL Dictionary for a list of qualifiers that can be used with the SHOW DEVICES command.
Managing Peripheral Devices 8.
Managing Peripheral Devices 8.2 Getting Information About Devices on the System 8.2.1 Determining If Volumes Need Rebuilding If a volume was improperly dismounted, it may require rebuilding. Volumes are improperly dismounted when, for example, the system crashes. Use the /REBUILD_STATUS qualifier with the SHOW DEVICES command to determine if a volume needs rebuilding. Do not use the /REBUILD_STATUS qualifier with any other SHOW DEVICES qualifiers, except the /OUTPUT qualifier.
Managing Peripheral Devices 8.2 Getting Information About Devices on the System Volume label Cluster size Free blocks Extend quantity Mount status "VOLUME_1" 0 0 0 Process Relative volume number Transaction count Maximum files allowed Mount count ACP process name 1 1 0 1 "DKA1CACP" Volume status: ISO 9660. Members of this volume set are $1$DKA1: (rvn 1), $1$DKA7: (rvn 64), $1$DKA16: (rvn 65535). 8.
Managing Peripheral Devices 8.3 Setting Security Protection Characteristics on Devices This command procedure applies the protection specified in the security template to all current devices. 8.4 Connecting Devices and Loading Device Drivers The system uses a software component called a device driver to control I/O operations for a particular device type. For a device to function on a system, the device must be connected, and the device driver must be loaded into memory.
Managing Peripheral Devices 8.4 Connecting Devices and Loading Device Drivers Topic For More Information † Manually connecting devices and loading drivers Section 8.4.1 ‡ Manually connecting devices and loading drivers Section 8.4.2 Suppressing autoconfiguration Section 8.4.3 †VAX specific ‡Alpha specific 8.4.
Managing Peripheral Devices 8.4 Connecting Devices and Loading Device Drivers Network Communication Device To connect the network communications logical device on VAX systems, run the appropriate startup files for the particular network protocol.
Managing Peripheral Devices 8.4 Connecting Devices and Loading Device Drivers Caution Exercise great care in issuing IO CONNECT and IO LOAD commands. Incorrect use of these commands could cause the system to fail. Network Communication Device To connect the network communications logical device on Alpha, run the appropriate startup files for the particular network protocol.
Managing Peripheral Devices 8.4 Connecting Devices and Loading Device Drivers To suppress autoconfiguration, and still configure HSCs and MSCPserved devices on remote nodes, add the following lines to the end of SYCONFIG.COM: $ STARTUP$AUTOCONFIGURE_ALL == 0 $ @SYS$SYSTEM:STARTUP CONFIGURE $ EXIT These commands suppress autoconfiguration but still execute the CONFIGURE phase of STARTUP.COM. However, if you add the command @SYS$SYSTEM:STARTUP CONFIGURE to SYCONFIG.
Managing Peripheral Devices 8.5 Automatically Configuring Devices for OpenVMS Alpha Systems Prior to OpenVMS Alpha Version 7.1, configuration tables were built into the OpenVMS kernel and could not be modified without replacing a system image. As of OpenVMS Alpha Version 7.1, the configuration tables are constructed from ASCII text files on the system disk. A system file (SYS$SYSTEM:SYS$CONFIG.DAT) is provided for all OpenVMS supported devices, and a user file (SYS$SYSTEM:SYS$USER_CONFIG.
Managing Peripheral Devices 8.5 Automatically Configuring Devices for OpenVMS Alpha Systems where the value is a string, a quoted string, or a numeric value. The END_ DEVICE keyword has no associated value.
Managing Peripheral Devices 8.5 Automatically Configuring Devices for OpenVMS Alpha Systems SDA> CLUE CONFIG . . . Adapter Configuration: ---------------------TR Adapter ADP Hose Bus BusArrayEntry Node Device Name/HW-Id -- ----------- -------- ---- -------------------- ---- ----------------. . .
Managing Peripheral Devices 8.5 Automatically Configuring Devices for OpenVMS Alpha Systems The FLAGS keyword shows optional information about how to load the driver. More than one flag may be specified, separated by a comma (,). Example: FLAGS = NOVECTOR, CASE_BLIND, EXTENDED_ID, ISA_ON_ EISA NOVECTOR Device has no interrupt vector. CASE_BLIND Causes the ID to be treated as an ASCII string and converted to uppercase.
Managing Peripheral Devices 8.5 Automatically Configuring Devices for OpenVMS Alpha Systems must be converted to BEGIN_PRIVATE "some data" END_PRIVATE The USER_PARAM keyword in ISA_CONFIG.DAT passes the quotation marks, so PRIVATE_DATA cannot be used to do the conversion. An ISA driver can retrieve the data between BEGIN_PRIVATE and END_ PRIVATE by calling IOC$NODE_DATA with the function code IOC$K_ISA_ USER_PARAM.
Managing Peripheral Devices 8.5 Automatically Configuring Devices for OpenVMS Alpha Systems The MC SYSMAN IO REBUILD/VERIFY command causes SYSMAN to read and process the SYS$SYSTEM:SYS$USER_CONFIG.DAT and SYS$SYSTEM:CONFIG.DAT files, but not to rebuild the configuration files for OpenVMS. Messages will be displayed for any errors that are encountered. This command can be used by developers to test new changes to SYS$SYSTEM:SYS$USER_CONFIG.DAT without modifying the current system. 8.5.
Managing Peripheral Devices 8.5 Automatically Configuring Devices for OpenVMS Alpha Systems 8.5.4 SYS$MANAGER:ISA_CONFIG.DAT Unsupported Support for using the SYS$MANAGER:ISA_CONFIG.DAT file to configure ISA devices was discontinued in OpenVMS Alpha Version 7.2. If you use this file, you should convert to using the ISACFG utility from the console and the file-based autoconfiguration method described in the following sections. Table 8–2 contains a list of keywords from ISA_CONFIG.
Managing Peripheral Devices 8.5 Automatically Configuring Devices for OpenVMS Alpha Systems Descriptions of the conversion for each parameter in ISA_CONFIG.DAT are as follows: NAME = xx Use the NAME keyword in SYS$USER_CONFIG.DAT. Use the same value, where xx is the device code. (The device code is usually 2 letters.) Example: NAME = ER DRIVER = driver_name Use the DRIVER keyword in SYS$USER_CONFIG.DAT. Use the same value for file-based autoconfiguration.
Managing Peripheral Devices 8.5 Automatically Configuring Devices for OpenVMS Alpha Systems EISA_IO_PORT to obtain the length in the upper word of the returned longword should stop examining the upper word. With ISA_CONFIG.DAT, the length was returned; but with ISACFG, the length is always 8. Example: >>>isacfg -slot 3 -dev 0 -mk -enadev 1 -etyp 1 -handle AAA321 -irq0 10 -iobase0 2F8 This example assigned port 2F8 to the device. MEM = (ee:f, gg:h, ...
Managing Peripheral Devices 8.5 Automatically Configuring Devices for OpenVMS Alpha Systems The following keywords do not have equivalents in ISA_CONFIG.DAT: -enadev a_number Takes the numbers 0 (disabled) and 1 (enabled). It allows you to disable a device so that it will not be used in resource allocation calculations. -etyp a_number Defines an entry type for this entry. OpenVMS supports only the values 0 and 1. It should always be specified as a 1.
Managing Peripheral Devices 8.6 Managing Terminals 8.6.1.2 Setting Characteristics in System Startup To execute SET TERMINAL commands each time your system boots, add these commands to a site-specific startup command procedure. If your configuration is simple, you can add the commands to SYSTARTUP_VMS.COM. If your configuration requires a large number of commands, create a separate command procedure (for example, TERM_SETUP.COM) and execute it from the SYSTARTUP_VMS.COM.
Managing Peripheral Devices 8.6 Managing Terminals Virtual terminals are identified by the VTAn: device name. After the SYSGEN or IOGEN command is entered, any terminal with the TT2$M_DISCONNECT characteristic set prior to login is treated as a virtual terminal. Note LAT terminals (LTAn:) can be disconnected if the TT2$M_DISCONNECT characteristic is set, but remote terminals (RTAn:) cannot be disconnected.
Managing Peripheral Devices 8.6 Managing Terminals See the DECnet-Plus for OpenVMS Applications Installation and Advanced Configuration for a detailed description of the procedure for setting up dynamic asynchronous DECnet lines. 8.6.2.2 Determining the Physical Terminal Type of a Virtual Terminal You can determine the physical terminal type associated with a virtual terminal.
Managing Peripheral Devices 8.7 Managing Modems • Troubleshooting modems 8.7.1 Understanding Modems A modem converts a digital signal to an analog signal by modulating the digital information on a carrier signal; a modem converts analog to digital signals by demodulating—or extracting—digital information from analog signals on an analog transmission facility such as a telephone line. The two words MOdulator and DEModulator form the basis for the device name: modem.
Managing Peripheral Devices 8.7 Managing Modems Table 8–3 Related Modem Documentation Reference Description DECnet-Plus for OpenVMS Network Management Explains the use of modems to establish a dynamic asynchronous DECnet connection between two nodes. Asynchronous DECnet is a protocol that can operate over a modem datalink. Compaq TCP/IP Services for OpenVMS Management Explains the use of modems to establish a serial connection using the PPP (Alpha only) and SLIP protocols and TCP/IP Services.
Managing Peripheral Devices 8.7 Managing Modems Figure 8–2 depicts direct and indirect modem configurations. The remote devices T1 and T2 are indirectly connected to both Host1 and Host2 host computers using the DECserver and the LAT protocol; T3 is connected directly to Host2.
Managing Peripheral Devices 8.7 Managing Modems Table 8–4 Common Pinouts on the EIA-232 DB23 Connection Pinout Description Data Terminal Equipment (DTE) Transmit information through pin 2, and receive information through pin 3, among other standardized pin assignments. Data Communications Equipment (DCE) Transmit information through pin 3, and receive information through pin 2, among other EIA-232 pin assignments.
Managing Peripheral Devices 8.7 Managing Modems Table 8–6 Connector Applications Connector and Pinout Example Adapter1 A DB9 9-pin connector with an EIA-574 PC-compatible pinout The DB9 connectors found on most PC, AlphaStation, and AlphaServer systems Use the H8571-J or compatible MMJ adapter. A DB9 9-pin connector that predates the EIA-574 pinout The console connector on various MicroVAX systems uses a pinout that predates the EIA-574 pinout Use the H8575-B or compatible MMJ adapter.
Managing Peripheral Devices 8.7 Managing Modems Table 8–7 (Cont.) DECconnect Accessories Order Number Description H8571-C 25-pin male EIA-232 to DEC-423 DECconnect adapter. H8571-E DEC-423 DECconnect 25-pin adapter with jack screws. H8571-J 9-pin MMJ adapter. Used with the PC-compatible EIA-574 DB9 wiring. H8572-00 MMJ cable extender. Allows the direct connection of two BC16E cables. H8575-A Female 25-pin DEC-423 DECconnect MMJ to EIA-232 general-purpose adapter.
Managing Peripheral Devices 8.7 Managing Modems Table 8–8 Types of Modem Control That Devices Support Type of Modem Control No modem control Description The host and the modem cannot intercommunicate the status of the host or the modem. It is possible to use a modem on this port; however, this type of port is not recommended for a modem.
Managing Peripheral Devices 8.7 Managing Modems 3. Determine the command set used by the modem. The command set includes the commands used to request that the modem place a telephone call, the telephone number to be called, and the commands used to configure the modem. Examples of command sets follow: • AT command set: ATDT phone-number where: AT indicates ‘‘attention’’—to get the attention of the modem DT indicates ‘‘dial tone’’; (PT would indicate ‘‘pulse tone’’).
Managing Peripheral Devices 8.7 Managing Modems • On a DECserver, configure the port using the following commands: DECserver> SET PORT n MODEM ENABLE DECserver> SET PORT n FLOW CONTROL XON ENABLE DECserver> SET PORT n AUTOBAUD ENABLE where n is the port number. The commands enable the modem, XON, and autobaud. These commands require privileges on the DECserver. 5. Ensure security with your modems. Dial-in lines allow remote, unauthorized users access to your system.
Managing Peripheral Devices 8.7 Managing Modems Table 8–9 Troubleshooting Communications Problems Problem Considerations Modem does not answer Check that the telephone number being called is correct. Check that the modem has power. Check that the host system or device has power and is operating. If possible, directly connect a standard terminal in place of the modem, and test the operation directly. Check that the host modem control signals are present, and correctly wired.
Managing Peripheral Devices 8.8 Managing Printers 8.8.1 Setting Printer Characteristics Printer characteristics must be set prior to starting queues for the printers. The DCL command SET PRINTER establishes characteristics for a line printer. The DCL command SET TERMINAL sets characteristics for a printer connected to a terminal or LAT port. In addition, if you want to spool your printers, you must do so before starting the queues to be associated with those printers.
Managing Peripheral Devices 8.8 Managing Printers If your system runs application programs that might write output directly to a printer, Compaq recommends that you spool your printers. Compaq recommends that you also spool your LAT printers to prevent privileged users from writing directly to a LAT printer. Writing directly to a LAT printer can cause problems for output queues that use the printer. Figure 14–9 illustrates a sample configuration using spooled printers. Section 8.8.2.
Managing Peripheral Devices 8.
Managing Peripheral Devices 8.9 Managing Tape Drives 8.9 Managing Tape Drives When managing tape drives, perform the following tasks: Task For More Information Get information about tape drives Section 8.9.1 Change tape drive characteristics Section 8.9.2 For information about managing volumes on tape drives, see Section 9.2. For information about managing Fibre Channel tape devices, see Guidelines for OpenVMS Cluster Configurations. 8.9.
Managing Peripheral Devices 8.10 Managing a Card Reader (VAX Only) 8.10 Managing a Card Reader (VAX Only) On VAX systems, the Compaq CR–11 card reader reads computer card decks. Users can submit the two following types of card decks for processing: • Batch job card decks • Data card decks To ensure that card decks are processed efficiently, you must understand their characteristics and the use of the card reader.
Managing Peripheral Devices 8.10 Managing a Card Reader (VAX Only) 8.10.1.2 Data Card Deck (VAX Only) A data deck contains data that will be either read by a program or copied to a file for later use. The process that reads the data deck is usually associated with an interactive user at a terminal or with a batch job submitted by an interactive user. Since the user and process already are logged in to the system, the first card can contain any data the user specifies.
9 Managing Storage Media This chapter discusses the following subjects: • Storage media terms and concepts • Volumes and volume sets Tasks related to setting up both disks and magnetic tape drives: initializing and mounting • Disks Tasks related to disk maintenance: the management of disk space and methods for detecting and repairing disk errors Information Provided in This Chapter This chapter describes the following tasks: Task Section Allocating and deallocating disk and tape drives Section 9.
Managing Storage Media Concept Section Tape and disk volume protection Section 9.4 Disk volume sets Section 9.6.1 Disk quotas Section 9.11.1 Mount verification Section 9.13.1 9.1 Understanding Storage Media Concepts The following list contains concepts related to storage media in general: Term Definition Device (or Drive) Hardware that allows access to storage media. Media Physical items on which you can store data. Volume Logical unit of data storage; one or more media units.
Managing Storage Media 9.1 Understanding Storage Media Concepts Table 9–1 Disk and CD–ROM Terminology Term Definition Sector Uniquely addressable unit. Each sector on a CD–ROM comprises a sequence of 2048 8-bit bytes; on most disks, a sector is equivalent to a block (512 bytes). Logical block Organizational unit of volume space containing 512 8-bit bytes. A CD–ROM sector comprises 4 blocks. Logical block numbering Logical blocks are numbered from 0 to n-1.
Managing Storage Media 9.1 Understanding Storage Media Concepts Figure 9–1 On-Disk Structure Hierarchy of a File File Extent 1 Cluster 1A Cluster 1B Extent 2 Cluster 2A Cluster 1C Block Block Block Block Block Block Block Block Extent 3 Cluster 3A Cluster 3B Block Block Block Block ZK−0739−GE OpenVMS File Structure Options On-Disk Structures include Levels 1, 2, and 5. (Levels 3 and 4 are internal names for ISO 9660 and High Sierra CD formats.
Managing Storage Media 9.1 Understanding Storage Media Concepts Table 9–2 (Cont.) File Structure Options on OpenVMS Systems Structure Disk or CD Description Foreign Both Unknown file structure. When you specify a foreign structure, you make the contents of a volume known to the system, but the system makes no assumptions about its file structure. The application is responsible for supplying a structure.
Managing Storage Media 9.1 Understanding Storage Media Concepts Beginning with OpenVMS Version 7.2, the limits of storage and index file bitmaps have been increased as follows: Type of Bitmap Limit Storage bitmap 65535 blocks Index file bitmap 4095 blocks The increased bitmap limits have the following advantages: • They allow you to use space more efficiently with small files. • They increase the number of files allowed on a volume to the architectural maximum of approximately 16 million.
Managing Storage Media 9.1 Understanding Storage Media Concepts Table 9–4 (Cont.) Comparison of ODS-1, ODS-2, and ODS-5 Formats Characteristic ODS-1 (VAX only) ODS-2 ODS-5 2 Directories No hierarchies of directories and subdirectories; directory entries are not ordered1 Alpha: 255 VAX: 8 (with rooted logical, 16) Alpha: 255 VAX: 8 (with rooted logical, 16) System disk Cannot be an ODS-1 volume Can be an ODS-2 volume ODS-5 volume not supported for Version 7.
Managing Storage Media 9.1 Understanding Storage Media Concepts 9.1.1.4 The ISO 9660 Standard for CD–ROMs The OpenVMS implementation of On-Disk Structure conforms to the file structures defined by the ISO 9660 standard. Table 9–5 defines terms related to the ISO 9660 standard. Table 9–5 ISO 9660 Terms Term Description Volume space Set of all logical blocks on a volume containing information about the volume.
Managing Storage Media 9.1 Understanding Storage Media Concepts 9.1.2.1 System and User Disk Support Restrictions and suggestions for using Extended File Specifications on your system are as follows: • You can mount an ODS-5 volume only on an OpenVMS VAX or an Alpha Version 7.2 or later system. Most applications can access only traditionally named files on a VAX system. • Compaq does not support creating the system disk as (or changing it to) an ODS-5 volume. 9.1.2.
Managing Storage Media 9.1 Understanding Storage Media Concepts BACKUP Limitations On an OpenVMS VAX system, users cannot successfully create or restore an ODS5 image save set. However, these users can successfully restore ODS-2-compliant file names from an ODS-5 save set. Users can also perform a disk-to-disk copy from ODS-5 to ODS-2 as long as they do not specify /IMAGE. For more information, refer to the OpenVMS Guide to Extended File Specifications. 9.1.2.4 Network Support For OpenVMS Version 7.
Managing Storage Media 9.1 Understanding Storage Media Concepts Table 9–6 (Cont.) Terms Related to Magnetic Tapes Term Definition bpi Bits per inch; measure used for characters of data on tape on OpenVMS systems. Also called density. IRG Interrecord gap; interval of space between blocks. Record blocking Grouping of individual records into a block, thereby reducing wasted space. Sequential Organization of magnetic tape data; that is, data is organized in the order in which it is written to the tape.
Managing Storage Media 9.1 Understanding Storage Media Concepts Figure 9–2 Record Blocking Without Record Blocking Record Record Record IRG IRG Record Record IRG IRG Record Record IRG IRG Record Record IRG IRG Record IRG IRG With Record Blocking All 10 Records IRG ZK−0741−GE Assume that a 1600-bits-per-inch magnetic tape contains 10 records that are not grouped into a block. Each record is 160 characters long (0.1 inch at 1600 bits per inch) with a 0.
Managing Storage Media 9.1 Understanding Storage Media Concepts Refer to the OpenVMS System Management Utilities Reference Manual for details about using the /DENSITY qualifier with these utilities. Also refer to Chapter 11 for details about using the /DENSITY qualifier with BACKUP. Example $ INITIALIZE/DENSITY=tk85 MKA500: TEST The command in this example initializes the media in the MKA500: drive to tk85 density with a label of TEST.
Managing Storage Media 9.1 Understanding Storage Media Concepts 9.1.4.1 Public Disk Volumes A public volume is a file-structured disk volume that can contain both private and public files. Public volumes can be either of the following ones: Type of Volume Description System volumes Available to all the users on a system Group volumes Available to all the users in a group As long as file protections permit it, all users have access to public volumes and to the files on them.
Managing Storage Media 9.1 Understanding Storage Media Concepts In large configurations, you can place secondary paging and swapping files on other devices to balance disk load. See Section 16.16 for more information. The OpenVMS Performance Management provides detailed information about redistributing system files and achieving a balanced disk load. 9.1.4.2 Private Disk Volumes A private volume is a file-structured volume that contains only private files.
Managing Storage Media 9.2 Allocating and Deallocating Drives 2. $ ALLOCATE/GENERIC RA90 MYDISK This example shows how to use the /GENERIC qualifier with the ALLOCATE command to allocate a particular type of device. In this case, the system allocates the first available RA90 drive to your process. For further discussion of the /GENERIC qualifier and other qualifiers that you can use with the ALLOCATE command, refer to the OpenVMS DCL Dictionary.
Managing Storage Media 9.3 Initializing Volumes Before you or any user can write files or data to a disk or a tape volume, you must initialize a volume. Caution Initializing a disk volume removes links to existing files on the volume, which, in effect, deletes (but does not erase) the files. To erase the data in a file, use the INITIALIZE/ERASE command. Do not initialize a volume that contains data that users want to keep. (Initializing a volume each time you use it is not necessary.
Managing Storage Media 9.3 Initializing Volumes 9.3.1 Using the INITIALIZE Command Use the DCL command INITIALIZE to format and write a label to the volume. To initialize a disk or tape volume, enter the INITIALIZE command using the following format: INITIALIZE device-name[:] volume-label where: device-name Specifies the name of the device on which the volume is to be physically mounted and then initialized. To prevent initializing another user’s volume, allocate a device before you initialize the volume.
Managing Storage Media 9.3 Initializing Volumes Table 9–8 (Cont.) INITIALIZE Command Qualifiers Qualifier Description /HEADERS= number-of-headers Specifies the number of file entries, called file headers, that you expect to have in INDEXF.SYS, the index file. It controls how much space is initially allocated to INDEXF.SYS for headers. (The system accesses the index file each time it locates a file on disk.
Managing Storage Media 9.3 Initializing Volumes 3. $ INITIALIZE/WINDOWS=10 DUA3: This example shows how to cite a large number of pointers for a large disk of 500 MB. 9.3.3 Initializing a New Volume with ODS-5 Format You can initialize a new volume as an ODS-5 volume by entering the INITIALIZE command using the following format. Note that once you initialize the volume, the current contents of the volume are lost.
Managing Storage Media 9.3 Initializing Volumes 9.3.4 Assisting Users in Accessing and Initializing Volumes Initializing volumes for users might be necessary in some circumstances: • If the volume previously contained data, the protection code might prevent users from accessing and initializing the volume. • If the first file section on the volume has not reached its expiration date, users might not be able to initialize a tape volume.
Managing Storage Media 9.4 Protecting Volumes Table 9–9 (Cont.) Access Types for Disk and Tape Volumes Access Type Gives you the right to... Control Change the protection and ownership characteristics of the volume. Users with the VOLPRO privilege always have control access to a disk volume, with the following exceptions: • Mounting a file-structured volume as foreign requires control access or VOLPRO privilege. • Mounting a volume containing protected subsystems requires SECURITY privilege.
Managing Storage Media 9.4 Protecting Volumes You can also specify protection when you mount disk volumes, but you ordinarily do not do so because the protection that you specify is in effect only while the volume is mounted. For details, refer to the Mount utility (MOUNT) in the OpenVMS System Management Utilities Reference Manual. • Use the DCL command SET VOLUME after you mount a volume to change UIC-based volume protection.
Managing Storage Media 9.4 Protecting Volumes Table 9–10 (Cont.) INITIALIZE Command Qualifiers for Protection Qualifier Explanation /GROUP System, owner, and group processes have read, write, create, and delete access to the volume. World users have no access. /NOSHARE System and owner processes have read, write, and delete access to the volume. World users have no access. Group users also have no access unless you specify the /GROUP qualifier.
Managing Storage Media 9.4 Protecting Volumes You can enable the protection fields by specifying either of the following items: • XAR mount option, using the following format: MOUNT/PROTECTION=XAR When you specify the XAR option for a file that has an associated XAR, the protection fields in the XAR are enabled.
Managing Storage Media 9.4 Protecting Volumes 9.4.2 Protecting Tape Volumes The system protects magnetic tapes only at the volume level. You establish protection when you initialize tape volumes; after that, the Mount utility (MOUNT) enforces the protection that you have established.
Managing Storage Media 9.4 Protecting Volumes 9.4.2.1 Using the /PROTECTION Qualifier with Tape Volumes If you use the /PROTECTION qualifier when you initialize tape volumes, the protection code is written to a system-specific volume label. With the /PROTECTION qualifier, the system applies only read (R) and write (W) access restrictions. (Execute [E] and delete [D] access do not apply.
Managing Storage Media 9.5 Mounting Volumes File-Structured and Foreign Volumes Ordinarily, when you mount volumes, the system imposes a format on each volume that allows you to read, write, create (or execute), and delete files. These mounted volumes have the format of the OpenVMS operating system. If you specify the /FOREIGN qualifier when you mount a volume, the system does not impose a format on the media, and you cannot access the files on the mounted volume.
Managing Storage Media 9.5 Mounting Volumes The following sections explain how to perform these tasks: Task Section Use MOUNT command qualifiers when you mount disks Section 9.5.1 Use MOUNT command qualifiers when you mount tapes Section 9.5.2 Assist users with mounting Section 9.5.3 Mount a volume with a protected subsystem Section 9.5.4 Convert an existing volume from one ODS format to another Section 9.5.5 Modify disk volume characteristics Section 9.5.6 9.5.
Managing Storage Media 9.5 Mounting Volumes Table 9–13 (Cont.) MOUNT Command Qualifiers for Mounting Disks Qualifier Description /CLUSTER Requires SYSNAM privilege; specifies that after a volume is successfully mounted on the local node, or if it is already mounted with the /SYSTEM qualifier on the local node, it is to be mounted on every other node in the existing OpenVMS Cluster environment (that is, the volume is to be mounted clusterwide).
Managing Storage Media 9.5 Mounting Volumes Table 9–13 (Cont.) MOUNT Command Qualifiers for Mounting Disks Qualifier Description /SHARE Specifies that other users can access the volume. (However, you must use the /SYSTEM qualifier to mount public volumes.) Two users can access a private volume simultaneously if they both use MOUNT/SHARE.
Managing Storage Media 9.5 Mounting Volumes Table 9–14 MOUNT Command Qualifiers for Mounting Tapes Qualifier Description /BLOCKSIZE=n Specifies the block size for the magnetic tape. The range of valid values for n varies, depending on the density of the volume, whether the data is for input or output, and whether the operation uses OpenVMS RMS. By default, the system writes 2048-byte blocks.
Managing Storage Media 9.5 Mounting Volumes Table 9–14 (Cont.) MOUNT Command Qualifiers for Mounting Tapes Qualifier Description /PROCESSOR=keyword For magnetic tapes and Files–11 Structure Level 1 disks, requests that the MOUNT command associate an ancillary control process (ACP) to process the volume. You must have the operator user privilege OPER to use the /PROCESSOR qualifier.
Managing Storage Media 9.5 Mounting Volumes 9.5.3 Assisting Users in Mounting Volumes Large sites often have operators assigned to assist users with mounting volumes. Section 2.4.6 explains how users can send requests to operators. Section 2.4.7 briefly explains how operators reply to those requests.
Managing Storage Media 9.5 Mounting Volumes 2. Enter the REPLY command in one of the following forms: REPLY Command Qualifiers Description /ABORT=identification-number ‘‘message-text’’ Indicates that the user request is canceled. (The user’s MOUNT command exits with an error status.) /PENDING=identificationnumber ‘‘message-text’’ Indicates that the request has been put in a wait state until it can be completed.
Managing Storage Media 9.5 Mounting Volumes Unprivileged users can build and manage protected subsystems. You must be involved at two points in the process: • To create the necessary identifiers for the subsystem. Refer to the OpenVMS Guide to System Security for details. • To mount the volume with the protected subsystem, which is explained in this section. Caution Anyone who mounts a subsystem is responsible for knowing what is on the volume being mounted.
Managing Storage Media 9.5 Mounting Volumes You can check that the volume is ODS-2 by entering a SHOW DEVICE/FULL command and seeing a display like the following: $ SHOW DEVICE DKA200:/FULL Disk $10$DKA200:, device type RZ47, is online, allocated, deallocate on dismount, mounted, file-oriented device, shareable. Error count . . . 0 Operations completed 232 Volume Status: ODS-2, subject to mount verification, file high-water marking, write-back caching enabled.
Managing Storage Media 9.5 Mounting Volumes If the volume fails this test, the system displays a message similar to the following: %SET-E-NOTMOD, DKA300: not modified -SET-W-NOTPRIVATE, device must be mounted privately • The mount count must indicate that the device was mounted only once, which protects against anyone mounting the device over a cluster.
Managing Storage Media 9.5 Mounting Volumes To recover from the error condition, reenter the SET VOLUME/STRUCTURE_ LEVEL=5 command, and then dismount and remount the disk. As a last resort, you can restore the backup you made. 9.5.5.2 Converting from ODS-1 to ODS-2 To convert from ODS-1 format to ODS-2 format: 1. Back up the entire disk or disks. 2. Initialize the disk or disks as ODS-2 file structure. 3. Restore the disk or disks. 9.5.5.
Managing Storage Media 9.5 Mounting Volumes In the following example, DKA500: is an ODS-5 disk, and IMAGE.BCK is an ODS-2 save set on the DKA200: disk. $ BACKUP/LOG/CONVERT/IMAGE DKA500: DKA200:[000000]IMAGE.BCK/SAVE %BACKUP-I-ODS5CONV, structure level 5 files will be converted to structure level 2 on DKA200: -BACKUP-I-ODS5LOSS, conversion may result in loss of structure level 5 file attributes %BACKUP-S-COPIED, copied DKA200:[000000]000000.DIR;1 %BACKUP-S-COPIED, copied DKA200:[000000]BACKUP.
Managing Storage Media 9.5 Mounting Volumes In the following example, DKA500: is the ODS-5 disk, and DKA200: is the ODS-2 disk. $ BACKUP/LOG/CONVERT DKA500:[*...]*.*;* DKA200:[*...]*.*;* %BACKUP-I-ODS5CONV, structure level 5 files will be converted to structure level 2 on DKA200: -BACKUP-I-ODS5LOSS, conversion may result in loss of structure level 5 file attributes %BACKUP-S-CREDIR, created directory DKA200:[TEST_FILES.SUB$$DIR$] %BACKUP-S-CREATED, created DKA200:[TEST_FILES.SUB$$DIR$]SUB$_$_FILE_$.
Managing Storage Media 9.5 Mounting Volumes Examples 1. $ SET VOLUME/DATA_CHECK=(READ,WRITE) DKA100: This command requests that data checks be performed following all read and write operations to the DKA100: volumes. 2. $ SET VOLUME/LABEL=LICENSES DKA100: This command encodes the label LICENSES on the DKA100: volume. Note that, if characters in labels are entered in lowercase, the /LABEL qualifier changes them to uppercase. 9.5.7 Speeding Up Disk Mounting The DISKMOUNT.
Managing Storage Media 9.6 Setting Up Disk Volume Sets 9.6.1 Understanding Disk Volume Sets A volume set is a collection of disk volumes bound into a single entity by the DCL command MOUNT/BIND. To users, a volume set looks like a single, large volume. Volume sets have the following characteristics: • Files are automatically located anywhere on the volume set that space is available. • Disk quotas are enforced over the entire set. • A single directory structure covers the whole volume set.
Managing Storage Media 9.6 Setting Up Disk Volume Sets • Enter the MOUNT/BIND command only once to bind a volume set; thereafter, the volume set association is recorded on the volumes. (See Section 9.5 for details.) • Once you bind two or more volumes into a volume set, you cannot separate them. The only way to separate a volume set is to use the Backup utility (BACKUP) to copy sets of directories selectively. (See Section 11.13 for more information.
Managing Storage Media 9.6 Setting Up Disk Volume Sets system files move or extend to other volumes in the set, the system might fail to boot. You do not need special privileges to create volume sets. However, you must have write access to the index file on all volumes you are attempting to bind into a volume set; this usually means you also must have a system UIC, have the user privilege SYSPRV, or be the owner of the volumes.
Managing Storage Media 9.6 Setting Up Disk Volume Sets PAYVOL1, which is listed first in the list of labels, becomes the root volume of the set. The master file directory (MFD) for PAYVOL1 contains the directory structure for the entire volume set. 2. $ MOUNT DUA1:,DUA2:,DUA3: PAYVOL1,PAYVOL2,PAYVOL3 This example illustrates the use of one MOUNT command to mount a previously created volume set. 9.6.
Managing Storage Media 9.6 Setting Up Disk Volume Sets volumes are unusable as a volume set because the directory structures are not properly bound. 9.6.5 Adding Volumes to an Existing Disk Volume Set You can add volumes to an existing volume set at any time. The maximum number of volumes in a volume set is 255. This section contains examples that show how to add volumes to an existing volume set. Examples 1.
Managing Storage Media 9.7 Mounting ISO 9660 Volume Sets and Groups For more information about ISO 9660 volume structure on CD–ROM media, refer to the Guide to OpenVMS File Applications. 9.7.1 Mounting ISO 9660 Volume Sets ISO 9660 supports volume sets of up to 65,535 volume set members. At any one time, users can mount a 255-member subset of the total volume set of 65,535.
Managing Storage Media 9.7 Mounting ISO 9660 Volume Sets and Groups 9.7.4 Mounting ISO 9660 Volumes Using SVDs All ISO 9660 volumes contain a Primary Volume Descriptor (PVD) that uses ASCII (ISO 646-IRV) as the character set. Both ISO 9660 and OpenVMS file naming conventions use the same subset of ASCII characters when displaying the directories and file names of a volume.
Managing Storage Media 9.7 Mounting ISO 9660 Volume Sets and Groups Table 9–15 ISO 9660 Restrictions Media Affected Description and Resolution Volume Labels These can contain from 1 to 32 characters. The first 12 characters are used to produce a unique volume identity.
Managing Storage Media 9.8 Mounting Tape Volume Sets other words, when you mount a tape volume set, you can specify more volume identifiers than device names or more device names than volumes. The number of devices you specify directly affects the action taken by the tape file system when processing continuation volumes in a volume set.
Managing Storage Media 9.8 Mounting Tape Volume Sets 4. You can check the densities, volume labels, UICs, and relative volume numbers of the volumes that are mounted on devices. To do so, specify the SHOW DEVICES/FULL command. If you specify a generic device code for the tape drives, such as MU, information is displayed for all drives of that type configured in the system.
Managing Storage Media 9.8 Mounting Tape Volume Sets The operating system supports the continuous processing of mounted volumes in a tape volume set through automatic volume switching and automatic volume labeling (AVL). 9.8.2.
Managing Storage Media 9.8 Mounting Tape Volume Sets 2. $ INITIALIZE MUA0: MAIN $ MOUNT/OVERRIDE=IDENTIFICATION/INITIALIZE=CONTINUATION MUA0:,MUA1: This example shows the use of the /INITIALIZE=CONTINUATION qualifier for mounting volume sets. It also shows how the system creates volume identifiers for continuation volumes. The volume labeled MAIN is mounted on the MUA0: drive. The second volume in the set receives the volume identifier MAIN02 and is mounted on the MUA1: drive.
Managing Storage Media 9.8 Mounting Tape Volume Sets 9.8.2.4 Sending Messages Back to Users After loading the continuation volume on the drive specified in the mount request, mount the volume by entering the REPLY command with one of the three qualifiers shown in Table 9–16. For more information about these qualifiers, refer to the OpenVMS DCL Dictionary.
Managing Storage Media 9.8 Mounting Tape Volume Sets Once the tape file system receives the REPLY command, the system performs checks on the continuation volume to ensure that the volume is the correct one. If it is the correct volume with proper access codes, the system mounts the volume and reissues pending read or write requests to the continuation volume. If the volume fails any of these access checks, the system does not mount the volume (or initialize and mount it in the case of a blank tape). 9.8.
Managing Storage Media 9.9 Dismounting Volumes and Volume Sets 9.9 Dismounting Volumes and Volume Sets When you finish processing the files or data on a disk or tape volume, use the DISMOUNT command to explicitly dismount a single volume or an entire volume set. Use the following format when you enter the DISMOUNT command: DISMOUNT device-name where: device-name Name of the device containing the volume—either a logical name or a physical name.
Managing Storage Media 9.9 Dismounting Volumes and Volume Sets The system writes the information in the caches to the disk when you dismount the disk or shut down the system. If you remove a disk from a drive before the caches are written to disk, the information in the caches is lost. Therefore, you must follow these guidelines: • Avoid write-locking a volume while it is mounted. • Do not remove a volume from a drive before it has been dismounted.
Managing Storage Media 9.9 Dismounting Volumes and Volume Sets You can access all the files that precede the file whose file-trailer labels have not been written. However, you cannot access the file that does not have file-trailer labels. 9.9.1.2 Dismounting Allocated Devices If the device you are dismounting was allocated with an ALLOCATE command, it remains allocated after you dismount it with the DISMOUNT command.
Managing Storage Media 9.9 Dismounting Volumes and Volume Sets 9.9.4 Dismounting a Volume in an OpenVMS Cluster System You can use the DISMOUNT command to dismount a volume throughout an OpenVMS Cluster system by using the /CLUSTER qualifier. The following command, which requires SYSNAM privilege, dismounts a volume in an OpenVMS Cluster system: $ DISMOUNT/CLUSTER $10$DJA100: The DISMOUNT/CLUSTER command first checks for conditions that prevent the volume from dismounting on the local node.
Managing Storage Media 9.10 Using Command Procedures for Media Setup 3. To execute the SETUP.COM command procedure, enter the following command: $ @SETUP 9.10.2 Sample Command Procedure for Setting Up Tape Volumes The command procedure shown in Example 9–1, which is more complex and detailed than the previous example, is designed to set up a magnetic tape for processing. The ALLOCATE and MOUNT/FOREIGN commands are included in this command procedure.
Managing Storage Media 9.10 Using Command Procedures for Media Setup Example 9–1 (Cont.) Command Procedure to Set Up Tape Volumes $ ! $ L2: INQUIRE/NOPUNC TO "Where do you want the file(s)? ( RET for current directory)" $ IF TO .EQS. "" THEN GOTO REPLACE $ LINE := ’LINE’ ’TO’ $ GOTO L3 $ REPLACE: LINE := ’LINE’ [] $ ! $ L3: INQUIRE/NOPUNC NEW "Create a new version if file already exists? " $ IF .NOT.
Managing Storage Media 9.11 Managing Disk Space Method Section Purge files Section 9.11.3 Set version limits on files Section 9.11.4 Set file expiration dates Section 9.11.5 Analyze and repair error conditions Section 9.12 9.11.1 Understanding Disk Quotas A disk quota is a method for maintaining and enforcing limits on the amount of disk space available to users on a public volume.
Managing Storage Media 9.11 Managing Disk Space $ Number of blocks by which a user can exceed the quota. Each entry in a quota file includes the information shown in Table 9–17.
Managing Storage Media 9.11 Managing Disk Space 9.11.2 Establishing Disk Quotas Disk quota operations are enabled by default. However, you can use SYSMAN DISKQUOTA commands to control disk usage. You can assign disk quotas to users and maintain an accurate record of disk use for ODS Level 2 or 5 disks. You create a quota file for each disk except the system disk. The quota file records the current usage and the maximum disk usage for all users.
Managing Storage Media 9.11 Managing Disk Space The first SYSMAN command in this example sets the environment for all nodes in the cluster. The second SYSMAN command sets up the quota file, QUOTA.SYS, in directory [000000] on the DUA12: device. The quota file has one entry, UIC [0,0], that stores default values for quotas and overdrafts. 2.
Managing Storage Media 9.11 Managing Disk Space 3. $ SHOW QUOTA/USER=[DOCUMENTATION,ELAINE] User [DOCUMENTATION,ELAINE] has 27305 blocks used, 2305 OVERDRAWN, of 25000 authorized and permitted overdraft of 4000 blocks on DISK$ This SHOW QUOTA command indicates that a user has an overdrawn quota. 9.11.2.
Managing Storage Media 9.11 Managing Disk Space Examples 1. $ PURGE/LOG $DISK1:[JONES...] The command in this example purges all files in the directory [JONES] and all the subdirectories below [JONES] on the $DISK1: device. It logs the files that are deleted (displaying their names on the terminal as they are deleted). 2. $ PURGE/KEEP=3 $DISK1:[*...] This example uses wildcard characters to perform global purges and uses the /KEEP qualifier to retain only three versions of each file. 9.11.
Managing Storage Media 9.11 Managing Disk Space The expiration date of a frequently accessed file fluctuates between the minimum and maximum period plus the current date. When you set a suitable interval between minimum and maximum retention periods, you can balance between accuracy and efficiency in maintaining expiration dates. Be careful about setting expiration dates; either be very specific, or set the expiration date in the simplest way.
Managing Storage Media 9.11 Managing Disk Space Example $ SET VOLUME DUA0:/RETENTION=(15-0:0,20-0:0) In this example, the command sets the minimum retention period to 15 days and the maximum to 20 days. 9.12 Using the Analyze/Disk_Structure Utility to Check and Repair Disks You can reclaim disk space by using the Analyze/Disk_Structure utility (ANALYZE/DISK_STRUCTURE) to identify and delete lost files and files marked for deletion.
Managing Storage Media 9.12 Using the Analyze/Disk_Structure Utility to Check and Repair Disks 9.12.1 Reporting Errors By default, ANALYZE/DISK_STRUCTURE reports errors but does not make repairs. In this mode, ANALYZE/DISK_STRUCTURE runs through eight stages of data collection and then, by default, prints a list of all errors and lost files to your terminal. One type of problem that ANALYZE/DISK_STRUCTURE locates is an invalid directory backlink.
Managing Storage Media 9.12 Using the Analyze/Disk_Structure Utility to Check and Repair Disks For complete descriptions of all errors and recommended actions, refer to the OpenVMS Command Definition, Librarian, and Message Utilities Manual. 9.12.3 Recovering Lost Files A lost file is not linked to a directory. Under normal circumstances, files are not lost. However, files occasionally lose their directory links because of disk corruption, hardware problems, or user error.
Managing Storage Media 9.12 Using the Analyze/Disk_Structure Utility to Check and Repair Disks 9.12.4 Erasing Old Home Blocks When you initialize a volume, the initialize operation might not erase old home blocks. These are blocks that were created by previous initialize operations. If a volume that has old home blocks is damaged, you might not be able to recover the volume without erasing the blocks.
Managing Storage Media 9.13 Using Mount Verification for Recovery %%%%%%%%%%% OPCOM, %%%%%%%%%%% Device is offline. Mount verification in progress. When a device goes off line or is write-locked, mount verification sends two messages: • One message goes to OPCOM. • The other message, distinguished by the prefix %SYSTEM-I-MOUNTVER, goes directly to the system console (OPA0:), bypassing OPCOM.
Managing Storage Media 9.13 Using Mount Verification for Recovery Task Section Control timeout periods for mount verification Section 9.13.2.2 Recover from offline errors Section 9.13.2.3 Recover from write-lock errors Section 9.13.2.4 Cancel mount verification using the DISMOUNT command Section 9.13.2.5 9.13.2.1 Enabling Mount Verification Mount verification is enabled by default when you mount a disk or tape.
Managing Storage Media 9.13 Using Mount Verification for Recovery %%%%%%%%%%% OPCOM, %%%%%%%%%%% Device contains the wrong volume. Mount verification in progress. 2. Once mount verification completes, the disk is marked as valid, and OPCOM issues a message in the following format: %%%%%%%%%%% OPCOM, %%%%%%%%%%% Mount verification completed for device . 3.
Managing Storage Media 9.13 Using Mount Verification for Recovery 9.13.2.5 Canceling Mount Verification You can cancel a mount verification request in one of the following ways: • Dismount the volume with the DCL command DISMOUNT from a process that is not hung. • If the device is off line, allow mount verification to time out. The default time limit for tapes is 600 seconds (10 minutes); for disks, it is 3600 seconds (1 hour).
Managing Storage Media 9.14 Using Interrupt Priority Level C (IPC) The IPC program converts lowercase letters to uppercase, issues the terminal bell character whenever it receives illegal characters (such as most control characters), compresses multiple spaces, and ignores leading spaces. How to Invoke IPC 1. On both OpenVMS VAX and Alpha systems, enter the following command from the console terminal: $ Ctrl/P This command does not echo.
Managing Storage Media 9.14 Using Interrupt Priority Level C (IPC) 9.14.2 Canceling Mount Verification To cancel mount verification using IPC, enter the following command from the console terminal in response to the IPC> prompt: IPC> C device-name This command cancels any pending mount verification on the device specified. (A warning is given if no mount verification was in progress for that device.
Managing Storage Media 9.14 Using Interrupt Priority Level C (IPC) 9.14.3 Entering the Debugger To use the XDELTA debugger, enter the following commands from the console terminal: IPC> X You are now in the debugger. The X command transfers control to the debugging tool XDELTA (provided it was loaded with the system by setting the appropriate value in the boot file). If XDELTA has not been loaded, the prompt IPC> is reissued.
Managing Storage Media 9.15 Using the Bad Block Locator Utility to Detect Media Errors How to Perform This Task To use BAD, perform the following steps: 1. Allocate the device with the DCL command ALLOCATE (to ensure that the device is not accessed by any other programs). 2. Enter the DCL command MOUNT/FOREIGN. When the device is mounted as foreign, the system does not recognize it as a Files–11 volume, and BAD can execute. 3. Enter the DCL command ANALYZE/MEDIA.
10 Using Files and Directories This chapter discusses concepts and tasks related to file protection, file manipulation, and data transfer. Information Provided in This Chapter This chapter describes the following tasks: Task Section Using Extended File Specifications features Section 10.1.1 Controlling access to ODS-5 volumes Section 10.2 Getting file information Section 10.4 Protecting disk files Section 10.5.3 Protecting disk directories Section 10.5.
Using Files and Directories 10.1 Understanding Extended File Specifications Features Feature Description New on-disk structure Extended File Specifications support the latest volume OnDisk Structure (ODS): Level 5 (ODS-5). This volume structure provides the basis for creating and storing files with extended file names. Additional character set support A broader set of characters is available for naming files on OpenVMS.
Using Files and Directories 10.1 Understanding Extended File Specifications Features 10.1.2 Setting Users’ Expectations of Extended File Specifications A system manager can help users become accustomed to Extended File Specifications by explaining the differences between ODS-2 and ODS-5 file names. These differences become most apparent when users change from ODS-2 to ODS-5 styles. If you pass the following usage notes along, users might find them helpful.
Using Files and Directories 10.1 Understanding Extended File Specifications Features Case Is Determined by the First Instance of an Extended File Name On an ODS-5 volume, the case for all versions of a file name is identical; the case is preserved as the file name was first created. In the following example, the disk is ODS-5. $ SET DEFAULT DKA500:[TEST] $ SET PROCESS /PARSE_STYLE=EXTENDED $ CREATE myfile.txt Ctrl/Z $ CREATE MYFILE.TXT Ctrl/Z $ DIRECTORY Directory DKA500:[TEST] myfile.txt;2 myfile.
Using Files and Directories 10.1 Understanding Extended File Specifications Features The following example shows the output when you run the program: $ @test Search returns DKA300:[FISHER]test.txt;1 Did not find file matching TEST $ @test case-blind Search returns DKA300:[FISHER]test.
Using Files and Directories 10.1 Understanding Extended File Specifications Features Use Traditional File Names in a Mixed-Volume Environment To avoid ODS-2 and ODS-5 file name incompatibility when working with both ODS-2 and ODS-5 volumes, and to assure backward compatibility with prior versions of OpenVMS, use only ODS-2 traditional file names. Error Messages Can Vary Depending on Parse Style Error messages displayed to users might vary depending on the parse style.
Using Files and Directories 10.1 Understanding Extended File Specifications Features $ SET PROCESS /PARSE_STYLE=TRADITIONAL " $ OPEN /WRITE FILE z.z.z.z %DCL-W-PARMDEL, invalid parameter delimiter - check use of special characters \.Z\ # $ SET PROCESS /PARSE_STYLE=EXTENDED $ $ OPEN /WRITE FILE z.z.z.z %DCL-E-OPENIN, error opening -RMS-E-CRE, ACP file create failed % -SYSTEM-W-BADFILEVER, bad file version number ! The volume is ODS-2. " The parse style is set to TRADITIONAL. # DCL returns an error message.
Using Files and Directories 10.1 Understanding Extended File Specifications Features $ SHOW DEFAULT DKA200:[DOREO] $ DUMP /OUTPUT DKA500:[DOREO]This^_is^_a^_file.Dat %DUMP-E-OPENOUT, error opening DKA200:[DOREO]THIS^_IS^_A^_FILE.DMP;as output -RMS-E-CRE, ACP file create failed -SYSTEM-W-BADFILENAME, bad file name syntax The output file specified with the /OUTPUT qualifier defaults to the same name as the input file, with .DMP as the file type, in the default directory.
Using Files and Directories 10.1 Understanding Extended File Specifications Features In addition, the directory depth on a VAX is limited to 8 (or 16, using rooted logicals). Physical Backups of ODS-5 Volumes on VAX Systems On OpenVMS VAX systems, BACKUP supports ODS-5 volumes only when you specify the /PHYSICAL qualifier to back up a volume. The BACKUP /PHYSICAL command causes BACKUP to make a block-by-block physical backup of the disk, ignoring the structured contents of the disk.
Using Files and Directories 10.2 Controlling Access to ODS-5 Volumes 10.2.2 Preventing an Untested Application from Accessing an ODS-5 Volume Follow these steps to prevent an untested application from accessing an ODS-5 volume: 1. Define an identifier (for example, ODS5_UNSAFE) to identify applications that you do not want to access an ODS-5 volume, for example: UAF> ADD /IDENTIFIER ODS5_UNSAFE /ATTR=SUBSYSTEM %UAF-I-RDBADDMSG, identifier ODS5_UNSAFE value %X80010039 added to rights database 2.
Using Files and Directories 10.3 Using DCL Commands with Files 10.3 Using DCL Commands with Files You use the DIGITAL Command Language (DCL) to perform a number of operations on files, as shown in the following table.
Using Files and Directories 10.4 Getting File Information The DIRECTORY command in this example lists all file types of the AVERAGE file and the version number of each file. The command would also list all versions of these files; however, only one version of each file exists. 2. $ DIRECTORY/SIZE/DATE/VERSIONS=1/PROTECTION AVERAGE Directory DISK$DOCUMENT:[MALCOLM] AVERAGE.EXE;6 AVERAGE.FOR;6 AVERAGE.LIS;4 AVERAGE.
Using Files and Directories 10.4 Getting File Information Effective: Recording: File organization: Sequential Shelved state: Shelved File attributes: Allocation: 36, Extend: 36, Global buffer count: 0 No version limit Record format: Variable length, maximum 255 bytes Record attributes: Carriage return carriage control Journaling Enabled : None File protection: System:RWED, Owner:RWED, Group:RE, World: Access Cntrl List: None Total of 1 file, 36/36 blocks.
Using Files and Directories 10.5 Protecting Files Type of Protection For More Information UIC-based protection codes Chapter 12 Access control lists (ACLs) Chapter 12 ISO 9660-formatted media protection Section 9.4.2 ANSI-standard accessibility protection (magnetic tape only) Section 9.4.2 For the most part, file protection is transparent. Tools exist, however, to adjust the protection of a file.
Using Files and Directories 10.5 Protecting Files tape volume. See the description of initializing magnetic tape volumes in Section 9.3. The next example illustrates how you can use the SHOW PROTECTION command to display the default protection characteristics for disk files. Example $ SHOW PROTECTION SYSTEM=RWED, OWNER=RWED, GROUP=RE, WORLD=NO ACCESS In this example, the SHOW PROTECTION command requests a display of the current protection defaults. 10.5.
Using Files and Directories 10.5 Protecting Files specify the proper protection both for the directory that lists the file and for the file itself. See Section 10.5.4 for instructions on protecting directories. The following sections explain how to perform these tasks: Task Section Set default disk file protection Section 10.5.3.1 Set explicit disk file protection Section 10.5.3.2 Modify disk file protection characteristics Section 10.5.3.3 10.5.3.
Using Files and Directories 10.5 Protecting Files Examples 1. $ SHOW PROTECTION SYSTEM=RWED, OWNER=RWED, GROUP=RE, WORLD=NO ACCESS The SHOW PROTECTION command displays the current default protection. In this example, the response shows the system default protection, which indicates that the system and owner have all types of access, group users have read and execute access, and world users have no access. 2. $ SHOW SECURITY IMAGES.DIR DBA1:[SADAMS]IMAGES.
Using Files and Directories 10.5 Protecting Files 10.5.3.3 Modifying Disk File Protection Characteristics Table 10–3 shows the DCL commands that you can use to establish and modify the protection characteristics of files. Table 10–3 DCL Commands to Modify File Protection Characteristics Command Description For More Information SET DIRECTORY Modifies the characteristics of one or more directories. The directory protection can override the protection of individual files within the directory.
Using Files and Directories 10.5 Protecting Files In this example, the file INCOME.DAT;3 is protected against deletion. The SET SECURITY/PROTECTION command changes only the owner’s delete access for the file INCOME.DAT;3. Now the owner can delete the file. 2. $ SET SECURITY/PROTECTION=(SYSTEM:R,OWNER:RWED,GROUP:RW) PAYROLL.LIS In this example, the SET SECURITY/PROTECTION command changes the protection codes applied to the PAYROLL.LIS file.
Using Files and Directories 10.5 Protecting Files 10.5.4 Protecting Disk Directories Each directory has a protection associated with it. Directory protection can override the protection of individual files within the directory. For example, if a directory denies world access, world users cannot look up files in that directory even though the files permit world access. For directory protection, you can use the access types shown in Table 10–4.
Using Files and Directories 10.5 Protecting Files Note To protect sensitive files, the directory protection alone is not adequate. You must also protect each individual file contained within the directory. Section 10.5.3 contains instructions for protecting disk files. By default, top-level directories receive UIC-based protection (S:RWE,O:RWE,G:RE,W:E) and no ACL. A newly created subdirectory receives the same protection as its parent directory, but delete access is removed from all categories.
Using Files and Directories 10.5 Protecting Files 10.5.5 Protecting Magnetic Tape Files Because tapes are single-user devices, tape protection is only at the volume level. The protection codes for magnetic tape volumes are usually assigned with the INITIALIZE command. You cannot use DCL commands to change protection characteristics on magnetic tape volumes. See Section 9.5.1 for more information. 10.
Using Files and Directories 10.6 Accessing Disk Files The contents of HISFILE are displayed on your terminal. 10.7 Accessing Tape Files This section describes file-level access for tapes. When you request access to a standard-labeled volume or a file, the operating system checks at the volume and file level to ensure that your process can access the volume or file. The level at which the system checks access depends on the operation you request and the type of access the operation requires.
Using Files and Directories 10.7 Accessing Tape Files Table 10–5 (Cont.) Comparison of OpenVMS Extended Names and Standard Names Characteristic OpenVMS Extended Names Standard Names Format filename.type;version filename.;version (Version is optional.) Length 39.39; 17.; Valid Characters A through Z; 0 through 9; ampersand (&), hyphen (-), underscore ( _ ), and dollar sign ($); wildcard characters asterisk (*) and percent sign (%) ASCII ‘‘a’’1 characters enclosed in quotation marks (" ").
Using Files and Directories 10.7 Accessing Tape Files 10.7.3 Using Wildcard Characters with Tape Volumes The OpenVMS operating system supports a limited use of wildcard characters in file specifications for tape volumes. Table 10–6 explains the use of wildcard characters with OpenVMS extended names and with standard names.
Using Files and Directories 10.7 Accessing Tape Files In this example, the DIRECTORY command instructs the system to search for files with both standard names and OpenVMS extended names that do not have a file type. 10.7.4 Reading Files on Tape Volumes When you access a tape file for a read operation, the tape is positioned at the beginning of the file section after the file header labels.
Using Files and Directories 10.7 Accessing Tape Files c. Writes the trailer labels d. Writes two tape marks to denote the logical end-of-volume (EOV) All files following the newly created file are lost. To close a tape file that was opened for write access, the tape file system issues commands to the driver to write the labels, followed by a double tape mark that indicates the logical EOV. 10.7.5.
Using Files and Directories 10.8 Copying and Transferring Files 10.8 Copying and Transferring Files With the OpenVMS operating system, you can copy files on disks and tapes both within the system and across other operating systems. The OpenVMS operating system provides a number of facilities to assist you in both types of information transfer. Table 10–7 summarizes the methods you can use to transfer information.
Using Files and Directories 10.8 Copying and Transferring Files 2. Because disks are random-access devices, and because files must be listed in directories, you must create a directory to contain your files on the disk volume after you initialize the volume. Copying from Disks The default format for files on disk volumes is Files–11 Structure Level 2.
Using Files and Directories 10.8 Copying and Transferring Files For this example, assume that the disk device DMA5: has been allocated to your process and that a disk volume has been initialized and mounted on that device. Also assume that you have a directory called PRIVATE already created on that volume. 3. $ COPY/LOG MTA1:"%&*?!SKI! """ SEASON.DAT %COPY-S-COPIED, MTA1:[]"%&*?!SKI! """.;1 copied to WRKD:[MANUAL]SEASON.
Using Files and Directories 10.8 Copying and Transferring Files 10.8.2 Copying Files to Tape Volumes You can use the COPY command to copy files from a disk volume to a tape volume. The procedures are similar to those for copying files from one disk volume to another. One difference, however, is that magnetic tapes are sequential-access devices and do not have directories. You must set up (initialize and mount) a tape device before copying disk files to a tape volume.
Using Files and Directories 10.8 Copying and Transferring Files 3. Enter the MOUNT command to mount the volume and write files to it, as in the following example: $ MOUNT TAPE_DEVICE: GMB001 %MOUNT-I-MOUNTED, GMB001 mounted on _MTA2: $ COPY *.* TAPE_DEVICE: The MOUNT command specifies the device name and volume label of the volume on the device. The COPY command copies the highest version of each file in your default directory onto the tape.
Using Files and Directories 10.8 Copying and Transferring Files 3. $ COPY/LOG OPENVMS_LONG$FILE_NAME.LONG_EXT MTA1: %COPY-S-COPIED, WRKD:[MANUAL]OPENVMS_LONG$FILE_NAME_EXT;1 copied to MTA1:OPENVMS_LONG$FILE_NAME.LONG_EXT;1 (80 records) In this example, a long file name with a long file type is copied to the tape volume MTA1: with the same file name and type as on the disk volume. 4. $ COPY/LOG %%.JOU;* MTA1:*.* %COPY-S-COPIED, WRKD:[MANUAL]C6.JOU;1 copied to MTA1:[]C6.
Using Files and Directories 10.8 Copying and Transferring Files Use the EXCHANGE/NETWORK command to perform the following operations: • Transfer files between an OpenVMS node and a node that is not OpenVMS. • Transfer a group of input files to a group of output files. • Transfer files between two nodes that are not OpenVMS, provided those nodes share DECnet connections with the OpenVMS node that issues the EXCHANGE/NETWORK command.
11 Using BACKUP You can guard against data loss or corruption by using the OpenVMS Backup utility (BACKUP) to create copies of your files, directories, and disks. In case of a problem—for example, a disk drive failure—you can restore the backup copy and continue your work with minimal disruption. Information Provided in This Chapter This chapter describes the following tasks: Task Section Formulating a BACKUP strategy Section 11.3 Setting process quotas for efficient backups Section 11.
Using BACKUP 11.1 Overview of BACKUP Tasks 11.1 Overview of BACKUP Tasks For BACKUP to effectively guard against data loss, you must back up important data on a regular basis and be familiar with how to restore the data when necessary. Besides backing up your own files, directories, and disks, you should also back up your system disk. If you have a standalone workstation, backing up your system disk is probably your responsibility.
Using BACKUP 11.2 Understanding Types of Backups 11.2 Understanding Types of Backups The following table lists the types of backup operations. Operation Description File operation Processes individual files or directories. Section 11.13 describes file operations. Selective operation Processes files or volumes selectively, according to criteria such as version number, file type, UIC, date and time of creation, expiration date, or modification date.
Using BACKUP 11.3 Formulating a Backup Strategy 11.3 Formulating a Backup Strategy When formulating a backup strategy, keep in mind the specific requirements of your site and the advantages and disadvantages of the different types of backups. Your backup strategy also depends on the following factors: • The resources you can devote to backups • The importance of the data • The volatility of the data For example, if you have a standalone workstation, a nightly image backup might be your best approach.
Using BACKUP 11.3 Formulating a Backup Strategy file entries. (The primary file, which uses the same file header but allocates different data storage blocks, is also restored.) However, despite the error message, note that there is no BACKUP error or loss of data. You do not have to change tapes or disks during a backup if any of the following statements is true: • All of the files fit on a single piece of storage media. • Your site uses a tape loader. • You have several disk or tape drives available.
Using BACKUP 11.4 Understanding the Backup Interfaces 11.4.1.1 Using Extended Character Sets Beginning with OpenVMS Version 7.2, which introduces Extended File Specifications, BACKUP can process file names that have extended character sets. Included are the following formats: • ODS-2 standard file name • ISO Latin-1 • Unicode (UCS-2) For additional information about extended character sets, refer to the OpenVMS Guide to Extended File Specifications. 11.4.1.
Using BACKUP 11.4 Understanding the Backup Interfaces • Context-sensitive hints You are prompted for input by a one-line ‘‘hint’’ about the field where the display cursor is currently located. • Pull-down help Choose the pull-down Help menu bar item for more extensive help on a variety of Backup Manager topics. 11.4.2.
Using BACKUP 11.5 Understanding Save Sets When restoring data from tape, if you do not include a save-set name with an input magnetic tape, BACKUP reads the next save set it encounters on the tape. (If you specify the input save-set qualifier /REWIND, BACKUP rewinds the tape and reads the first save set on the tape.) 11.5.2 Files–11 Disk Save Sets To write save sets on a Files–11 disk, you must include the output save-set qualifier /SAVE_SET.
Using BACKUP 11.5 Understanding Save Sets 11.5.4 Sequential-Disk Save Sets Sequential-disk save sets allow you to treat a Files–11 disk volume sequentially, (like a magnetic tape volume). The primary advantage of using sequential-disk save sets is that you can mount multivolume save sets one volume at a time. This is particularly useful on systems without tape drives that have a large fixed-media disk and a small removable disk. When one sequential disk is full, BACKUP prompts you to mount another disk.
Using BACKUP 11.5 Understanding Save Sets BACKUP can read a sequential-disk save set either as a sequential-disk save set or as a Files–11 save set: • When BACKUP reads a save set as a sequential-disk save set, the save set can be mounted one volume at a time. The default directory for the save set file specification is the master file directory [000000] on the disk. • When BACKUP reads a save set as a Files–11 save set, all volumes of the save set must be mounted.
Using BACKUP 11.7 Setting Process Quotas for Efficient Backups $ SET DEFAULT SYS$SYSTEM $ RUN AUTHORIZE UAF> SHOW SYSTEM 3.
Using BACKUP 11.
Using BACKUP 11.7 Setting Process Quotas for Efficient Backups ASTLM 24 BIOLM 18 BYTLM 32768 ENQLM 200 2.
Using BACKUP 11.8 Using Disks and Tapes 11.8.1 Understanding Volume Initialization Initializing a volume completes the following actions: • Formats it in the OpenVMS Files–11 format • Assigns it an ANSI label • Removes links to any existing files (effectively erasing them) • Writes a tape expiration date and volume protection data to the volume header record of the tape Caution Initializing a volume removes links to existing files on the volume, effectively erasing the files.
Using BACKUP 11.8 Using Disks and Tapes Magnetic tape volume labels can contain a maximum of six characters. You can use any ANSI ‘‘a’’ character in a magnetic tape volume label. The ANSI ‘‘a’’ characters include numbers, uppercase letters, and any of the following nonalphanumeric characters: ! "%’()*+,_. /: ;<=>? If you use any nonalphanumeric characters, you must enclose the volume label with quotation marks. Label your magnetic tapes according to the data contained on the tapes.
Using BACKUP 11.8 Using Disks and Tapes How to Perform This Task The two ways to initialize a disk during a backup operation are: • When you perform an image copy to disk, BACKUP automatically initializes the output disk, effectively erasing any existing files and volume-initialization data on the disk. To preserve volume-initialization data on the output disk, use the /NOINITIALIZE qualifier. • When you create a sequential disk save set, BACKUP does not initialize the output volume (by default).
Using BACKUP 11.8 Using Disks and Tapes • If a save set will be written in sequential-disk format (for example, if the save set occupies more than one disk), the target disk must be mounted as a foreign device by specifying the command qualifier /FOREIGN to the DCL command MOUNT. How to Perform This Task 1. Enter the SHOW DEVICES command in the following format to check whether the device is already mounted: SHOW DEVICES device-name 2.
Using BACKUP 11.9 Understanding OPCOM and Volumes 11.9 Understanding OPCOM and Volumes If you have a standalone workstation or easy access to disk and tape drives at your facility, you probably can mount and initialize your own volumes. At some sites, however, an operator performs these tasks. Using the services of an operator might be necessary because the drive you want to use is located remotely or because you do not have the necessary privileges to manipulate a volume.
Using BACKUP 11.9 Understanding OPCOM and Volumes Examples 1. To request the operator to mount a tape, enter a command similar to the following one: $ REQUEST/REPLY "Is anyone using drive MUA12?" %OPCOM-S-OPRNOTIF, operator notified, waiting...12:21:12.46 %OPCOM-S-OPREPLY, PLEASE DIRECT YOUR REQUEST TO THE TAPE OPERATOR 2-APR-2000 12:26:13.12. request 2 completed by operator OPA0 $ The /REPLY qualifier assigns your request a unique number (in this case, 2) to which the operator can respond.
Using BACKUP 11.10 Listing the Contents of a BACKUP Save Set To list the contents of save sets does not require you to know the names of save sets on magnetic tape. Enter the device specification of the drive in which the tape is inserted with the BACKUP/LIST command. BACKUP reads the next save set it encounters on the magnetic tape and stops processing when it reaches the end of that save set.
Using BACKUP 11.11 Understanding Multivolume BACKUP Operations 11.11 Understanding Multivolume BACKUP Operations When you save data with BACKUP, the save set often spans more than one volume, creating a multivolume save set. When this occurs, BACKUP fits as much data as it can on the first volume, then dismounts it.
Using BACKUP 11.11 Understanding Multivolume BACKUP Operations a label, the first tape is labeled BACKUP, the second BACK02, and the third BACK03. • If you specified a single label on the command line using the /LABEL qualifier and it matches the label of the first volume, BACKUP labels subsequent volumes with the first four characters of the label from the first volume plus the number of the volume in the sequence.
Using BACKUP 11.12 Understanding BACKUP Tape Label Processing • Compares the volume label specified in the BACKUP command line (either explicitly with the /LABEL qualifier or implicitly through the save-set name) to the volume label of the tape to prevent you from creating a save set on the wrong magnetic tape. BACKUP uses the following guidelines when processing tape labels: If you specify a label that is longer than six characters, BACKUP truncates the label to six characters.
Using BACKUP 11.12 Understanding BACKUP Tape Label Processing Assuming the volume labels of the tapes you use match the corresponding labels on the command line, BACKUP continues processing until it completes the operation or runs out of volume labels. If you do not specify enough labels on the command line to complete the operation or if the tape loaded does not have an ANSI label, BACKUP prompts you to enter a label for the tape in the drive.
Using BACKUP 11.13 Backing Up Files and Directories $ BACKUP [LYKINS...]*.*;* [OWLCR...]*.*;* Note Disk-to-disk copy operations initiated using the /VERIFY qualifier might attempt to verify files that are not copied.
Using BACKUP 11.13 Backing Up Files and Directories 3. You can also specify a list of files that you want to back up: $ BACKUP _From: DUA0:[MGR]EMPLOYEES.DAT,USER1:[RECORDS]DOOHAN.DAT,EVANS.DAT _To: MUA1:MONTHLY_AUG.BCK/LABEL=TAPE1 4. If you are backing up large amounts of data, you can also specify more than one output device: $ BACKUP _From: DUA0:[000000]*.* _To: MTA1:BACKUP.
Using BACKUP 11.13 Backing Up Files and Directories 10. If you are backing up more data than the output volume can contain, mount the output volume using the /FOREIGN qualifier and create a sequential disk save set. For example: $ MOUNT DUA1: PAYROLL %MOUNT-I-MOUNTED, PAYROLL mounted on _DUA1: $ MOUNT/FOREIGN DJA21: %MOUNT-I-MOUNTED, WEEKLY mounted on _DJA21: $ BACKUP From: DUA1:[PAYROLL] To: DJA21:[PAYROLL_BACKUPS]PAY22MAY2000.
Using BACKUP 11.13 Backing Up Files and Directories An image compare operation may not work correctly when you create two disks with identical files by incrementally backing up and restoring the files from one disk to the other disk. This is because BACKUP does not ensure that the incrementally restored files have the same FIDs as the incrementally saved files. This is true regardless of whether the /OVERLAY, /NEW_VERSION, or /REPLACE qualifiers are used in the restore command. Examples 1.
Using BACKUP 11.13 Backing Up Files and Directories Example This example shows how to create a BACKUP journal file and list the contents of the BACKUP journal file: $ BACKUP/JOURNAL/LOG/IMAGE DRA2: MIA0:3OCT.FUL %BACKUP-S-COPIED, copied DRA2:[COLLINS]ALPHA.DAT;4 %BACKUP-S-COPIED, copied DRA2:[COLLINS]EDTINI.EDT;5 . . . %BACKUP-I-RESUME, resuming operation on volume 2 %BACKUP-I-READYWRITE, mount volume 2 on _MIA0: for writing Press return when ready: Return %BACKUP-S-COPIED, copied DRA2:[LANE]MAIL.
Using BACKUP 11.14 Restoring Files and Directories How to Perform This Task To restore files, use the BACKUP command in the following format: BACKUP save-set-specifier [/SAVE_SET] /SELECT=[dir...] output-specifier:[dir...] Use the /SAVE_SET qualifier if the save set is on a disk or diskette. The /SELECT qualifier lets you specify the exact file you want to restore.
Using BACKUP 11.14 Restoring Files and Directories $ BACKUP _From: MIA0:NOV2SAVE.BCK/SELECT=[LYKINS.GLENDO]STRAT1.DAT;5 _To: STRAT1.DAT;5 $ DIRECTORY STRAT1.DAT Directory [LYKINS.GLENDO] STRAT1.DAT;5 Total of 1 file. $ 5. Suppose you deleted the entire [REPORTS] directory, which previously contained the following subdirectories: $ SET DEFAULT [REPORTS] $ DIRECTORY *.DIR Directory USER3:[REPORTS] INTERNAL.DIR PUBLIC.DIR SUMMARIES.DIR TEST.DIR WEEKLY.DIR 2 5 1 3 2 Total of 5 files, 13 blocks.
Using BACKUP 11.15 Backing Up User Disks 11.15 Backing Up User Disks This section explains performing incremental and image backups to disk and tape. Note Do not use the menu system (which displays when you boot the OpenVMS VAX operating system CD–ROM) to back up user disks. Use the menu system to back up system disks only. In addition, if you back up large user disks on VAX systems, BACKUP might need to page and thereby cause the operation to fail.
Using BACKUP 11.15 Backing Up User Disks How to Perform This Task If several users are on your system, notify them that a disk backup is about to take place.
Using BACKUP 11.15 Backing Up User Disks causes BACKUP to check the contents of the output specifier against the input specifier after the files are written to the volume. The /LABEL qualifier indicates the label of the tape. 2. If you are backing up a large disk, you may want to use several tape drives for the backup.
Using BACKUP 11.15 Backing Up User Disks Examples 1. For example, if you want to create an image backup save set of the disk named DUA1: on a disk named DUA2:, you could enter the following commands: $ MOUNT DUA1: USER1 %MOUNT-I-MOUNTED, USER1 mounted on _DUA1: $ MOUNT DUA2: USER2 %MOUNT-I-MOUNTED, USER2 mounted on _DUA2: $ BACKUP/IMAGE/RECORD _From: DUA1: _To: DUA2:[USER.BACKUPS]USER1.SAV/SAVE_SET 2. You can also specify multiple disk drives as the output specifier in the BACKUP command line.
Using BACKUP 11.15 Backing Up User Disks date fields are not as recent as the last image backup or incremental backup in which the /RECORD qualifier was used. 3. Enter the BACKUP command in the following format: BACKUP/RECORD/SINCE=BACKUP input-specifier output-specifier[/LABEL=label] [/REWIND] The /RECORD qualifier records the current date and time in the file header record of each file that is backed up. This information is essential for future incremental backups.
Using BACKUP 11.15 Backing Up User Disks $ DIRECTORY/FULL LOGIN.COM Directory WORK204:[HIGGINS] LOGIN.COM;31 File ID: (23788,1,0) Size: 7/9 Owner: [ACC,HIGGINS] Created: 30-APR-2000 14:37:33.98 Revised: 30-APR-2000 14:37:34.44 (1) Expires: Backup: 30-APR-2000 20:20:57.
Using BACKUP 11.15 Backing Up User Disks 2. You can also specify multiple disk drives as the output device in the BACKUP command line. For example: $ MOUNT DUA0: USER1 %MOUNT-I-MOUNTED, USER1 mounted on _DUA0: $ MOUNT/FOREIGN DUB24: %MOUNT-I-MOUNTED, DISK2 mounted on _DUB24: $ MOUNT/FOREIGN DUB25: %MOUNT-I-MOUNTED, DISK3 mounted on _DUB25: $ BACKUP/RECORD/SINCE=BACKUP _From: DUA0:[000000...] _To: DUB24:USER1.SAV,DUB25/SAVE_SET 11.15.
Using BACKUP 11.15 Backing Up User Disks $ BACKUP/RECORD/IGNORE=(INTERLOCK) _$ disk:[000000...]*.DIR;* _$ NLA0:DUMMY.BCK/SAVE/NOCRC/GROUP_SIZE=0 $ $ BACKUP/VERIFY/FAST/RECORD/IGNORE=(INTERLOCK) _$ /NOASSIST/COMMENT="Incremental backup of DISK:" _$ disk:[000000...]*.*;*/SINCE=BACKUP _$ tape:incr.bck/LABEL=incr/SAVE In this example, the first BACKUP command performs the dummy backup operation, and the second command performs the actual incremental backup.
Using BACKUP 11.15 Backing Up User Disks $! $ REPLY/ALL "Full Backup About to Begin. Open Files Will Not Be Saved" $! $ BACKUP /IMAGE DUA2: MUA0:FULL_BACKUP.SAV /REWIND /IGNORE=LABEL_PROCESSING $ DISMOUNT MUA0: $ EXIT $! $FAILURE: $ WRITE SYS$OUTPUT "---> Backup failed" $ WRITE SYS$OUTPUT "" $ DISMOUNT MUA0: $ EXIT 3. Edit the command procedure to reflect: • The name of the disk that you want to back up. To back up more than one disk, list each of the devices in the BACKUP command line.
Using BACKUP 11.15 Backing Up User Disks 11.15.7.2 Using a Command Procedure for Nightly Incremental Backups You can use a similar command procedure to perform nightly incremental backups of your disks. It might be more convenient to perform nightly incremental backups and weekly image backups if either of the following conditions applies: • Interactive users are on your system at all times, and system performance is noticeably affected by backups.
Using BACKUP 11.15 Backing Up User Disks • The day of the week (if any) to be omitted in the incremental backup In this example, the incremental backup will not be performed on Friday, reserving that day for an image (full) backup. 3. Be sure that an image backup has been made and also be sure that you continue to make regular image backups. When you make your image backups, be sure to use the /RECORD qualifier (as well as the /IMAGE qualifier) in your BACKUP command line. 4.
Using BACKUP 11.15 Backing Up User Disks the tape’s volume label with the label you specified and ensures that the tape is expired. If the tape is not expired or the label does not match, the command procedure exits. If the tape is expired and the label matches, BACKUP writes the expiration date you specified to the volume header record and initializes the tape.
Using BACKUP 11.15 Backing Up User Disks Volume shadowing checks for geometries and maximum logical block numbers (LBNs) on devices. This enables devices such as the RZ28 and the RZ28B to operate in the same shadow set. Even though their device IDs differ, their geometries and maximum LBNs will match when configured on like controllers (two HSJ controllers, for example). When you create a shadow set, individual users access it as a virtual unit.
Using BACKUP 11.15 Backing Up User Disks 11.15.8.1 Mounting a Disk in a Host-Based Shadow Set To mount a disk in the StorageWorks RAID Array 110 Subsystem in a host-based shadow set, you must use the /OVERRIDE=NO_FORCED_ERROR qualifier with the MOUNT command. The StorageWorks RAID Array 110 Subsystem does not support the READ/WRITE LONG SCSI commands that are necessary for implementing the FORCED ERROR function in SCSI. Without FORCED ERROR, you must override that check by the shadowing driver. 11.15.8.
Using BACKUP 11.16 Restoring User Disks 2. Load and mount the volume. If the backup is contained in a Files–11 save set, make sure you mount the volume in the Files–11 format. If the backup is contained in a sequential disk save set, make sure you load the volume and mount it using the MOUNT/FOREIGN command. If the backup copy is on a tape save set, load the first tape. 3.
Using BACKUP 11.16 Restoring User Disks • DRA2: is the device name of the disk to which the files will be restored. $ MOUNT/FOREIGN DRA2:! %MOUNT-I-MOUNTED, DISK1 mounted on _DRA2: $ BACKUP/IMAGE MIA1:FULL_BACKUP.SAV/REWIND DRA2:" $ DISMOUNT/NOUNLOAD DRA2:# In this example, the individual command lines perform the following actions: ! Mount the disk DRA2. The files will be restored to this disk. The disk must be loaded before it can be mounted.
Using BACKUP 11.16 Restoring User Disks • If the save set is on magnetic tape, load the tape and enter the following command, substituting the name of the tape drive you use for MIA0: $ BACKUP/LIST/REWIND MIA0: Listing of save set(s) Save set: Written by: UIC: Date: . . . 19APRIL2000.SAV SYSTEM [000001,000004] 19-APR-2000 22:03:03.63 The save set is named 19APRIL2000.SAV. 4.
Using BACKUP 11.16 Restoring User Disks Example The next example shows the process of restoring an entire disk after a series of incremental backups, using the following elements and assumptions: • The save set for the image backup is named WORK_BACKUP.SAV. This save set was created using the BACKUP/IMAGE/RECORD command. • The save sets for the incremental backups are named as follows: WORK_16_JAN.SAV WORK_17_JAN.SAV WORK_18_JAN.
Using BACKUP 11.16 Restoring User Disks Note Renaming directories is not recommended. Also, changing security information for a directory changes its modification date. Thus, a directory might appear to be ‘‘renamed’’ and its contents included in incremental save sets if the file protection or security information is changed. The addition of renamed directory contents might increase the size of some incremental save sets.
Using BACKUP 11.17 Backing Up and Restoring the System Disk 11.17 Backing Up and Restoring the System Disk Backing up your system disk is critical for the following reasons: • A system disk could become inoperable if a problem occurs during a software upgrade, update, or installation. Before you attempt any of these operations, back up the system disk. If a problem occurs, you can restore the backup copy of the system disk. • System files could inadvertently be deleted.
Using BACKUP 11.17 Backing Up and Restoring the System Disk Answer the questions. When the procedure asks if an automatic system boot should be performed, press Return for NO. When the procedure is finished, it displays the following message: SYSTEM SHUTDOWN COMPLETE On VAX systems, the following message is also displayed: USE CONSOLE TO HALT SYSTEM Halt the system if you see this message. 2. Boot the system: • On OpenVMS Alpha systems, boot the distribution compact disc.
Using BACKUP 11.17 Backing Up and Restoring the System Disk %SYSINIT-E, error %SYSINIT-E, error %SYSINIT, primary %SYSINIT, no dump %SYSINIT-E, error $! Copyright (c) $set noverify opening page file, status = 0000025C opening swap file, status = 0000025C PAGEFILE.SYS not found; system initialization continuing file - error log buffers not saved mounting system device, status = 00000F64 2000 Compaq Computer Corporation. All rights reserved. Copyright © (c) 2000 Compaq Computer Corporation.
Using BACKUP 11.17 Backing Up and Restoring the System Disk Table 11–8 (Cont.
Using BACKUP 11.17 Backing Up and Restoring the System Disk To build standalone BACKUP, execute SYS$UPDATE:STABACKIT.COM. The procedure copies the files for booting standalone BACKUP to a new directory on the target device that you specify, creating the directory if necessary. When you build a kit on the system disk, the procedure copies the files to the [SYSE] directory. When you build the kit on a user disk, the procedure copies the files to the [SYS0] directory.
Using BACKUP 11.17 Backing Up and Restoring the System Disk 11.17.2.2 Booting Standalone BACKUP from a Disk (VAX Only) To boot standalone BACKUP from a disk, perform the following steps: 1. If the operating system is not running, go to step 2. If the operating system is running, log in to the SYSTEM account. Enter the following command and press Return: $ @SYS$SYSTEM:SHUTDOWN Answer the questions. When the procedure asks if an automatic system boot should be performed, press Return for NO.
Using BACKUP 11.17 Backing Up and Restoring the System Disk 7. When standalone BACKUP finishes booting, it displays an identification message followed by the dollar sign prompt ( $ ): %BACKUP-I-IDENT, Standalone BACKUP Vn.n; the date is 19-APR-2000 15:00 $ To make a backup copy of the system disk, see Section 11.17.3. To restore the system disk, see Section 11.17.4. 11.17.2.
Using BACKUP 11.17 Backing Up and Restoring the System Disk 11.17.2.4 Booting Standalone BACKUP from a Tape Cartridge (VAX Only) If the disk containing standalone BACKUP becomes unusable (for example, if the drive fails), you can boot standalone BACKUP from a tape cartridge. Booting standalone BACKUP from a tape cartridge takes approximately 20 minutes. How to Perform This Task To boot standalone BACKUP from a tape cartridge, use the following procedure: 1.
Using BACKUP 11.17 Backing Up and Restoring the System Disk 11.17.3 Backing Up the System Disk to Tape When backing up your system disk, you must understand the functions of the /IMAGE and /PHYSICAL qualifiers to the BACKUP command before using standalone BACKUP: Qualifier Function /IMAGE Lets you create a functionally equivalent copy of the entire system disk. When restored, files from an image backup are placed contiguously on the system disk, eliminating disk fragmentation.
Using BACKUP 11.17 Backing Up and Restoring the System Disk • label is the volume label of the tape in the drive. If the tape has been initialized already, use the same volume label that was assigned by the INITIALIZE command. For example: $ BACKUP/IMAGE/VERIFY DUA1: MUA0:DEC_31_BACKUP.BCK/REWIND/LABEL=WKY101 7. The following message indicates that BACKUP has transferred the files and is verifying the accuracy of the backup copy: %BACKUP-I-STARTVERIFY, starting verification pass 8.
Using BACKUP 11.17 Backing Up and Restoring the System Disk 15. Store the backup tapes in a safe place. 11.17.4 Restoring the System Disk from Tape If a problem occurs that renders your system disk unbootable, you can restore the system disk from your backup copy. How to Perform This Task To restore the system disk from tape, use the following procedure.
Using BACKUP 11.17 Backing Up and Restoring the System Disk 6. If your system disk contained more data than one tape could store, you receive the following messages and prompt: %BACKUP-I-RESUME, Resuming operation on volume 2 %BACKUP-I-READYREAD, Mount volume 2 on MUA0: for reading Enter "YES" when ready. If you do not receive these messages, see step 7. If you do receive these messages, perform the following steps: a. Remove the backup tape from the drive. b. Insert the next backup tape into the drive. c.
Using BACKUP 11.17 Backing Up and Restoring the System Disk How to Perform This Task To perform a disk-to-disk image backup, use the following procedure: 1. Obtain a disk with enough storage capacity to use for the backup. Make sure the disk does not contain files you need, because standalone BACKUP initializes the output disk. 2. Determine the device name of the system disk you are backing up. (See Section 8.2 for information about determining the names of your devices.
Using BACKUP 11.17 Backing Up and Restoring the System Disk 11. Reboot the system using the newly created system disk. 11.17.6 Using InfoServer Tapes to Back Up and Restore System Disks On VAX systems, you can back up the system disk to an InfoServer tape and restore the system disk from an InfoServer tape. How to Perform This Task 1. Boot the system from the SYS1 directory using the current version of the OpenVMS CD–ROM, which can be in a reader on the InfoServer or on a local drive.
Using BACKUP 11.17 Backing Up and Restoring the System Disk Example 11–1 (Cont.) System Disk Backup to an InfoServer Tape Copyright © (c) 2000 Compaq Computer Corporation. All rights reserved. Installing required known files... Configuring devices... **************************************************************** The menu can be used to execute DCL commands and procedures for various "standalone" tasks, such as backing up the system disk.
Using BACKUP 11.18 Ensuring Data Integrity 11.18.1 /CRC Qualifier The /CRC qualifier enables the software cyclic redundancy check (CRC). The default is /CRC; you must specify /NOCRC to disable checking. Disabling checking reduces processing time, but increases the risk of data error. As an output save-set qualifier, /CRC writes the CRC checking code into the blocks of the output save set. As an input save-set qualifier, /CRC checks the CRC information in the input save set.
Using BACKUP 11.18 Ensuring Data Integrity 11.18.4 /LOG Qualifier Use the /LOG qualifier to the BACKUP command to display the file specification of the files that BACKUP processes during a backup operation. For example, if you are copying files in a directory, you can use the /LOG qualifier to display the file specification of each file copied: $ BACKUP/LOG _From: WORK3:[OCONNELL]*.* _To: WORK1:[OCONNELL.SCRATCH]*.* %BACKUP-S-CREDIR, created WORK1:[OCONNELL.SCRATCH.
Using BACKUP 11.19 Troubleshooting 11.19 Troubleshooting This section describes some common BACKUP errors and how to recover from them. 11.19.
Using BACKUP 11.19 Troubleshooting 4. Place a new tape into the drive and enter YES in response to the prompt for a new tape. 5. BACKUP restarts the save operation from the beginning of VOL3; no data is lost. 11.19.
12 Security Considerations This chapter outlines the security features available with the OpenVMS operating system and suggests procedures to reduce the threat of a break-in on your system or cluster. It also tells how to use the access control list editor (ACL editor) to create and modify access control list entries (ACEs) on protected objects. For a more detailed description of security management, refer to the OpenVMS Guide to System Security.
Security Considerations 12.1 Understanding Security Management software plans, and computer time. These measures can also protect equipment, software, and files from damage caused by tampering. Types of Security Problems Security problems on most systems are generally caused by irresponsibility, probing, or penetration. The tolerance that your site might have to a breach of security depends on the type of work that takes place at your site.
Security Considerations 12.2 Managing Passwords Using the System Dictionary and the Password History List The OpenVMS operating system automatically compares new passwords with a system dictionary to ensure that a password is not a native language word. It also maintains a password history list of a user’s last 60 passwords. The operating system compares each new password with entries in the password history list to ensure that an old password is not reused. The system dictionary is located in SYS$LIBRARY.
Security Considerations 12.2 Managing Passwords Implementing system passwords is a two-stage operation involving the DCL commands SET TERMINAL and SET PASSWORD. First, you must decide which terminals require system passwords. Then, for each terminal, you enter the DCL command SET TERMINAL/SYSPASSWORD/PERMANENT. To enable system passwords for all terminals, set the appropriate bit in the system parameter TTY$DEFCHAR2. 12.2.
Security Considerations 12.2 Managing Passwords 12.2.5 Guidelines for Protecting Passwords Observe the following guidelines to protect passwords: • Make certain the password for the SYSTEM account, which is a standard account on all OpenVMS systems, is secure and is changed regularly. • Disable any accounts that are not used regularly with the AUTHORIZE qualifier /FLAGS=DISUSER (for example, SYSTEST and FIELD).
Security Considerations 12.2 Managing Passwords 12.2.6 Password History The password history database maintains a history of previous passwords associated with each user account. By default, the system retains these records for one year. Password history records that are older than the system password history lifetime are allowed as valid password choices. When a user account is deleted, the system removes the associated password history records from the history database. 12.
Security Considerations 12.3 Using Intrusion Detection Mechanisms Displaying the Intrusion Database The Security Server process, which is created as part of normal operating system startup, performs the following tasks: • Creates and manages the system’s intrusion database • Maintains the network proxy database file (NET$PROXY.DAT) The intrusion database keeps track of failed login attempts.
Security Considerations 12.4 Understanding Ways to Protect Objects user category User categories include system (S), owner (O), group (G), and world (W). Each category can be abbreviated to its first character. Categories have the following definitions: • System: Members of this category can include any of the following users: – Users with low group numbers, usually from 1 to 10 (octal). These group numbers are generally for system managers, security administrators, and system programmers.
Security Considerations 12.5 Creating Intra-Cluster Communications Security Objects 12.5 Creating Intra-Cluster Communications Security Objects OpenVMS provides SYS$MANAGER:ICC$SYSTARTUP.COM. This command procedure allows you to customize the ICC characteristics by creating ICC security objects and adding additional registry tables. The ICC$CREATE_SECURITY_OBJECT procedure creates permanent ICC security objects and optionally issues an initial SET SECURITY command for the object.
Security Considerations 12.6 Creating Access Control Lists ACE Description Identifier ACE Controls the types of access allowed to specific users based on the user’s identification. Each Identifier ACE includes one or more rights identifiers and a list of the types of access the user holding the identifier has permission to exercise. See Section 12.6.2 for a summary of identifiers.
Security Considerations 12.6 Creating Access Control Lists ACE Description Subsystem ACE Grants additional identifiers to a process while it is running the image to which the Subsystem ACE applies. Users with execute access to the image can access objects that are in the protected subsystem, such as data files and printers, but only when they run the subsystem image. The Subsystem ACE applies to executable images only.
Security Considerations 12.7 Assigning ACLs Security class System global section Volume Typically, ACLs are used when you want to provide access to an object for some, but not all, users, or if you want to deny access to specific, unprivileged users. When the operating system receives a request for access to an object having an ACL, it searches each access control list entry in the ACL, stopping at the first match. If another match occurs in the ACL, it has no effect.
Security Considerations 12.8 Using the ACL Editor As a result of this ACE, any file created in the [MALCOLM] directory has the following ACE: (IDENTIFIER=PERSONNEL,ACCESS=READ+WRITE) Refer to the OpenVMS Guide to System Security for further discussion of the Default attribute and its effect on the processing of an ACL. 12.8.
Security Considerations 12.9 Auditing Security-Relevant Events Table 12–1 Kinds of Security Events OpenVMS Can Report Event Class Description Access Specifies access events for all objects in a class. You can audit selected types of access, both privileged and nonprivileged, to all protected objects of a particular class. ACL Events requested by a security Audit or Alarm ACE in the access control list (ACL) of an object. Authorization Modification of any portion of SYSUAF.DAT, NETPROXY.
13 Managing the Queue Manager and Queue Database Before you can create and start queues, you must set up the queue manager and the queue database. This chapter tells how to set up and manage the queue manager and queue database for the OpenVMS batch and print queuing system. Information Provided in This Chapter This chapter describes the following tasks: Task Section Specifying the location of the queue database Section 13.3 Displaying information about queue managers Section 13.
Managing the Queue Manager and Queue Database 13.1 Understanding the Queue Manager Figure 13–1 illustrates how the queue manager works to manage queue activity in an OpenVMS Cluster environment.
Managing the Queue Manager and Queue Database 13.1 Understanding the Queue Manager One or more queue manager processes control queuing for all processes on a node or in an OpenVMS Cluster environment. Jobs can be submitted from one node and executed on a queue running on another cluster node. User processes, symbionts, and job controllers on each node communicate directly with queue managers.
Managing the Queue Manager and Queue Database 13.2 Understanding the Queue Database File Description Queue file, SYS$QUEUE_MANAGER.QMAN$QUEUES Contains the queue definitions formed when you create, start, or modify queues. Journal file, SYS$QUEUE_MANAGER.
Managing the Queue Manager and Queue Database 13.3 Specifying the Location of the Queue Database 13.3 Specifying the Location of the Queue Database You might need to specify a location for queue database files other than the default location of SYS$COMMON:[SYSEXE] for one of the following reasons: • In an OpenVMS Cluster environment with multiple system disks, the default location does not work because it has a different physical location on each system disk.
Managing the Queue Manager and Queue Database 13.3 Specifying the Location of the Queue Database In an OpenVMS Cluster environment, enter this command on every node in the cluster. Note In an OpenVMS Cluster environment, the directory you specify for the master file must be available to all nodes in the cluster.
Managing the Queue Manager and Queue Database 13.4 Displaying Information About Queue Managers Examples 1. The following example displays default (/BRIEF) information about two queue managers, PRINT_MANAGER and SYS$QUEUE_MANAGER. $ SHOW QUEUE/MANAGERS Queue manager PRINT_MANAGER, running, on NODEA:: Queue manager SYS$QUEUE_MANAGER, running, on NODED:: 2. Use the /FULL qualifier to display complete information about queue managers on the system or cluster.
Managing the Queue Manager and Queue Database 13.5 Starting the Queue Manager and Creating a Queue Database where: /NEW_VERSION Specifies that new queue database files are to be created: Master file Queue file Journal file Specify the /NEW_VERSION qualifier only if you want to create new database files. If your queuing system is already functioning, creating new database files is not necessary. /ON=(node,...) Allows you to customize failover of the queue manager. For more information, see Section 13.6.
Managing the Queue Manager and Queue Database 13.5 Starting the Queue Manager and Creating a Queue Database To create queue database files in a location other than the default, follow the instructions in Section 13.3.1 or Section 13.3.2, or both. 3. To start the queue manager and create queue database files, enter a START/QUEUE/MANAGER command. This command starts the queue manager process and, optionally, creates queue and journal files. If the queue manager does not start, see Section 13.11.
Managing the Queue Manager and Queue Database 13.7 Stopping and Restarting the Queue Manager Once you enter STOP/QUEUE/MANAGER/CLUSTER, the queue manager process remains stopped; requests to that queue manager are denied until you restart the queue manager by entering START/QUEUE/MANAGER. (Note that the queue system remains running as long as one or more queue managers are running.) OpenVMS Cluster transitions do not change the state of the queue manager.
Managing the Queue Manager and Queue Database 13.8 Using Multiple Queue Managers 13.8.1 Understanding Multiple Queue Managers Explanations of items related to the operation of multiple queue managers follow. Restrictions on Using Multiple Queue Managers Multiple queue managers have the following restrictions: • Queues running on one queue manager cannot reference queues running on a different queue manager.
Managing the Queue Manager and Queue Database 13.8 Using Multiple Queue Managers where: /ADD Creates an additional queue manager in the existing master file and creates new queue and journal files /NAME_OF_ MANAGER=name Creates a non-default queue manager with a name up to 31 characters long. You can create a maximum of five queue managers. /ON=(node,...) Allows you to customize failover of the queue manager. For more information, see Section 13.6.
Managing the Queue Manager and Queue Database 13.8 Using Multiple Queue Managers • The SHOW QUEUE/MANAGERS command displays information about the queue managers running on your system, as explained in Section 13.4. $ START/QUEUE/MANAGER/NEW_VERSION/NAME_OF_MANAGER=PRINT_MANAGER _$ /ON=(JADE,RUBY,*) $ START/QUEUE/MANAGER/ADD/NAME_OF_MANAGER=BATCH_MANAGER _$ /ON=(OPAL,PEARL,*) $ SHOW QUEUE/MANAGERS/FULL Master file: SYS$COMMON:[SYSEXE]QMAN$MASTER.
Managing the Queue Manager and Queue Database 13.9 Saving and Restoring the Queue Database Example The following example is a simple procedure showing how to save the queue database. $ SET DEFAULT SYS$COMMON:[SYSEXE] $ CONVERT/SHARE QMAN$MASTER.DAT MASTERFILE_9SEP.KEEP; $ CONVERT/SHARE SYS$QUEUE_MANAGER.QMAN$QUEUES QFILE_9SEP.KEEP; $ INITIALIZE MUA0: QDB $ MOUNT/FOREIGN MUA0: %MOUNT-I-MOUNTED, QDB mounted on _LILITH$MUA0: $ BACKUP/LOG MASTERFILE_9SEP.KEEP,QFILE_9SEP.KEEP MUA0:QDB_9SEP.
Managing the Queue Manager and Queue Database 13.9 Saving and Restoring the Queue Database Note When you restore your queue database, you must always restore both the master and queue files, even if you lost only one of those files. 5. Start the queue manager with the START/QUEUE/MANAGER command. Do not enter the /NEW_VERSION qualifier: a new, empty journal file will be created automatically. Example The following example is a simple procedure showing how to restore the queue database from tape.
Managing the Queue Manager and Queue Database 13.11 Solving Queue Manager Problems 13.11 Solving Queue Manager Problems Use the following sections to help solve queue manager problems: Topic For More Information Avoiding common problems: a troubleshooting checklist Section 13.11.1 If the queue manager does not start Section 13.11.2 If the queuing system stops or the queue manager does not run on specific nodes Section 13.11.3 If the queue manager becomes unavailable Section 13.11.
Managing the Queue Manager and Queue Database 13.11 Solving Queue Manager Problems 13.11.2.2 Cause The cause of the problem is the system’s inability to find the queue master file. Often the logical is not defined correctly, or the disk is not available. For example, the following message indicates that the master queue file does not exist in the expected location: %%%%%%%%%%% OPCOM 13-MAR-2000 15:53:52.
Managing the Queue Manager and Queue Database 13.11 Solving Queue Manager Problems 13.11.3 If the Queuing System Stops or the Queue Manager Does Not Run on Specific Nodes Use this section if the queue manager does not run on a specific node in the cluster, or if the queuing system stops, especially after one of the following actions: • The node on which the queue manager was running leaves the cluster. • A new node boots into the cluster.
Managing the Queue Manager and Queue Database 13.11 Solving Queue Manager Problems • If the queue database disk is not mounted for the node on which the queue manager attempts to run. In general, the queuing system will be shut off completely if the queue manager encounters a serious error and forces a crash or failover twice in two minutes consecutively on the same node.
Managing the Queue Manager and Queue Database 13.11 Solving Queue Manager Problems 13.11.5.1 Investigating the Problem Perform the following steps: 1. Search the operator log that was current when the problem existed for the following messages. These messages are broadcast every 30 seconds after the affected node boots. %%%%%%%%%%% OPCOM 4-FEB-2000 15:36:49.
Managing the Queue Manager and Queue Database 13.11 Solving Queue Manager Problems 13.11.6 If You See Inconsistent Queuing Behavior on Different OpenVMS Cluster Nodes Use this section if you see the following symptoms: • After submitting a print job, you can display the job with a SHOW ENTRY command on the same node, but not on other nodes in the OpenVMS Cluster environment. • After defining or modifying a queue, the changes appear in a SHOW QUEUE display on some nodes, but not on others.
Managing the Queue Manager and Queue Database 13.11 Solving Queue Manager Problems 2. Reassign the logical name QMAN$MASTER on the affected systems and correct the definition in the startup procedure where the logical name is defined (usually SYLOGICALS.COM). 3. Enter STOP/QUEUE/MANAGER/CLUSTER on an unaffected node to stop the valid queue manager. 4. Enter START/QUEUE/MANAGER on any node and verify that the queuing system is working properly. 13.
Managing the Queue Manager and Queue Database 13.12 Reporting a Queuing System Problem to Compaq Information Description Translation of QMAN$MASTER logical name Verify that the translation is the same on all nodes.
14 Setting Up and Maintaining Queues If you have a printer connected to your system, or if you want to use batch processing, you must use queues. A queue allows users to submit requests for printing or batch processing at any time; the system then prints or processes jobs as resources allow. Before setting up queues, you need to understand how the queue manager and the queue database operate and how to create them for the OpenVMS queuing system. These are explained in Chapter 13.
Setting Up and Maintaining Queues Concept Section Forms and stock Section 14.6.7 Page and line overflow Section 14.6.7.8 Initial form feed Section 14.6.7.9 Device control libraries Section 14.6.8 Note This chapter contains many references to DCL commands. You can find additional information about all DCL commands in the OpenVMS DCL Dictionary. 14.
Setting Up and Maintaining Queues 14.1 Understanding Queuing 14.1.2 Understanding Classes and Types of Queues In general, queues can be divided into two classes: Class Description Execution queues Queues that accept batch or print jobs for processing. Generic queues Queues that hold jobs until an appropriate execution queue becomes available. The queue manager then requeues the job to the available execution queue. The following sections provide more details about execution and generic queues. 14.1.2.
Setting Up and Maintaining Queues 14.1 Understanding Queuing 14.1.2.2 Generic Queues Descriptions of types of generic queues follow: • Generic batch queues direct jobs only to batch execution queues. Generic batch queues are typically used in OpenVMS Cluster environments to distribute the batch work load across several nodes (see Section 14.2.1.3). Generic batch queues are not automatically stopped when a node shuts down. Therefore, they do not need to be started when a node reboots.
Setting Up and Maintaining Queues 14.2 Designing Queue Environments 14.2 Designing Queue Environments The following sections describe how to design batch queue and output queue environments. 14.2.1 Designing a Batch Queue Environment You can design batch queues for a single queue, multiple queues, or OpenVMS Cluster environments. Each section referred to in the following table contains figures showing sample configurations to assist you in designing your batch processing environment.
Setting Up and Maintaining Queues 14.2 Designing Queue Environments Figure 14–2 shows a configuration of several queues, each customized to process certain types of batch jobs.
Setting Up and Maintaining Queues 14.2 Designing Queue Environments Figure 14–3 Batch Queue Configuration with Clusterwide Generic Queue SYS$BATCH G E MOE_BATCH E MOE E LARRY_BATCH CURLY_BATCH LARRY CURLY Legend: G = Generic Queue E = Execution Queue ZK−3815A−GE In Figure 14–3, a generic clusterwide batch queue named SYS$BATCH feeds jobs to execution queues on each node in the OpenVMS Cluster environment.
Setting Up and Maintaining Queues 14.2 Designing Queue Environments 14.2.2 Designing an Output Queue Environment Use the following sample configurations to design your output environment. Your configuration will probably combine elements from several of these examples. Configuration For More Information A single print queue for limited printing Section 14.2.2.1 Printers of different types Section 14.2.2.2 PostScript printing Section 14.2.2.3 Access to printers from multiple systems Section 14.2.2.
Setting Up and Maintaining Queues 14.2 Designing Queue Environments Figure 14–5 shows such a configuration. Figure 14–5 Queue Configuration with Mixed Printers SYS$PRINT LN03_PRINT LA210_PRINT G E E LPA0 LPB0 LN03 E E LA210 TTA1: TTA3: Legend: LPA0 : LPB0 : Line Printers G = Generic Queue E = Execution Queue ZK−3821A−GE 14.2.2.3 Printing PostScript Files The operating system does not include software to support PostScript printing.
Setting Up and Maintaining Queues 14.2 Designing Queue Environments Figure 14–6 Configuration for Remote Printers on a Terminal Server Ethernet VAX Node Alpha Node E E LN03_PRINT LN03_PRINT Terminal Server Node LN03 LTA333: Legend: E= Execution Queue ZK−3822A−GE 14.2.2.5 Using Generic Output Queues If you have more than one printer of the same type (for example, if you have three line printers), use generic queues to balance the print load among the printers. Figure 14–7 shows such a configuration.
Setting Up and Maintaining Queues 14.2 Designing Queue Environments Figure 14–7 Queue Configuration with Three Like Printers and a Generic Queue SYS$PRINT G LPA0 LPB0 LPC0 E E E LPA0 : LPB0 : LPC0 : Line Printers Legend: G = Generic Queue E = Execution Queue ZK−3818A−GE For information about how to create a generic queue, see Section 14.4.3. 14.2.2.6 Using OpenVMS Cluster Queues Figure 14–8 shows a typical OpenVMS Cluster output queue configuration.
Setting Up and Maintaining Queues 14.2 Designing Queue Environments Figure 14–8 Output Queue Configuration in an OpenVMS Cluster SYS$PRINT Legend: G = Generic Queue E = Execution Queue G E E JUPITR_LPA0 JUPITR_LPB0 JUPITR JUPITER LPA0: E E SATURN_LPA0 LPB0: E SATURN_LPB0 SATURN LPA0: LPB0: URANUS_LPA0 URANUS LPA0: ZK−8749A−GE 14.2.2.
Setting Up and Maintaining Queues 14.2 Designing Queue Environments Figure 14–9 Queue Configuration with Spooled Devices Application A Line Printer LPA0: Application B Spooled LN03 Printer TTA3: Spooled Line Printer LPB0: E E LPA0 LPB0 SYS$DISK E LN03_PRINT G SYS$PRINT SYS$DISK Legend: G = Generic Queue E = Execution Queue ZK−3817A−GE For more information about spooling printers, see Section 8.8.2.1. 14.2.2.
Setting Up and Maintaining Queues 14.3 Planning Your Queue Setup For More Information Step Task 3 If you plan to use any queue options, such as forms, characteristics, and banner pages, determine the qualifiers needed to specify those options. In addition, define any forms and characteristics you will use before you create queues. (Because of the length of the instructions for this step, the corresponding section in the manual follows the section for step 5.) Section 14.6 4 Create and start queues.
Setting Up and Maintaining Queues 14.
Setting Up and Maintaining Queues 14.4 Creating and Starting Queues The commands in this example perform the following tasks: ! Creates an autostart queue named LPA0 and activates it for autostart. Because this is an autostart queue with a failover list, this queue can run on either LILITH::LPA0 or SMITTN::LPA0. " Creates an autostart queue named LN03_1 for LAT printers and activates it for autostart.
Setting Up and Maintaining Queues 14.4 Creating and Starting Queues 14.4.1.2 Activating an Autostart Queue You must activate an autostart queue in one of the following ways: • Use the /START qualifier in the INITIALIZE/QUEUE command used to create the queue, as follows: INITIALIZE/QUEUE/START/AUTOSTART_ON[/qualifiers,...] queue-name • Enter START/QUEUE after you create the queue, as follows: START/QUEUE[/qualifiers,...
Setting Up and Maintaining Queues 14.4 Creating and Starting Queues How to Start Stopped Autostart Queues You can start all stopped active autostart queues on a node by enabling autostart for queues with ENABLE AUTOSTART/QUEUES. Including a separate START/QUEUE command to start an active autostart queue is not necessary. When a node reboots, autostart is disabled until you enter ENABLE AUTOSTART/QUEUES. 14.4.1.
Setting Up and Maintaining Queues 14.4 Creating and Starting Queues • Enter START/QUEUE after you create the queue, using the following format: START/QUEUE[/qualifiers,...] queue-name For each nonautostart queue, you must include a START/QUEUE command naming the queue in your startup command procedure. 14.4.3 Creating and Starting Generic Queues This section describes how to create and start a generic queue. 14.4.3.
Setting Up and Maintaining Queues 14.5 Restarting Execution Queues on Reboot 14.5 Restarting Execution Queues on Reboot Information about forms, characteristics, and queues is stored in the queue database. For this reason, creating forms, queues, and characteristics each time the node or OpenVMS Cluster system reboots is unnecessary. However, you must start nonautostart execution queues and enable autostart each time a node reboots. To do so, create a command procedure.
Setting Up and Maintaining Queues 14.6 Using Queue Options Table 14–1 (Cont.) Qualifiers for Specifying Queue Options Qualifier Type of Queue For More Information Description /BASE_PRIORITY Batch and output Specifies a base process priority (not the same as the job scheduling priority). For a batch queue, specifies the base priority for processes executing jobs in the queue. For output queues, specifies the base priority of the symbiont process. Section 14.6.4.
Setting Up and Maintaining Queues 14.6 Using Queue Options Table 14–1 (Cont.) Qualifiers for Specifying Queue Options Qualifier Type of Queue For More Information Description /NAME_OF_ MANAGER Batch and output Specifies the name of the queue manager with which the queue will be associated. Section 13.8 /NO_INITIAL_FF Output Specifies the qualifier for an output execution queue; suppresses the initial form feed sent to an output execution queue. Section 14.6.7.
Setting Up and Maintaining Queues 14.6 Using Queue Options Table 14–1 (Cont.) Qualifiers for Specifying Queue Options Qualifier /WSQUOTA Type of Queue Description For More Information Batch and output For batch queues, specifies the working set quota for batch jobs executed in the queue. For output queues, specifies a working set quota for the symbiont process. Section 14.6.4 The value set by this qualifier overrides the value defined in the UAF of any user submitting a job to the queue. 14.6.
Setting Up and Maintaining Queues 14.6 Using Queue Options Access Type Gives you the right to... Delete Delete a job in the queue or modify the elements of a job. Manage Affect any job in the queue. You can start, stop, or delete a queue and change its status and any elements that are unrelated to security. Control Modify the protection elements and owner of a queue. Note that when a process receives read or delete access through a protection code, it can operate on only its job in the queue.
Setting Up and Maintaining Queues 14.6 Using Queue Options Command Description SET SECURITY/CLASS=QUEUE/OWNER=uic Modifies the owner element of a queue. Specify the UIC in the standard format. SET SECURITY/CLASS=QUEUE/ PROTECTION=ownership[:access] Modifies the protection code of a queue. The protection code defines the type of access allowed to users, based on their relationship to the object’s owner. SHOW SECURITY/CLASS=QUEUE Shows protection currently set for objects of the queue class.
Setting Up and Maintaining Queues 14.6 Using Queue Options Examples 1. The SET QUEUE/PROTECTION command in the following example modifies the default protection of queue SYS_QUE1 to prevent access by nonprivileged users. The SET SECURITY/ACL command then restricts access to only those members of a project group who hold the ULTRA_LITE or MINUTES identifiers. Members with the MINUTES identifier have only read and submit access to the queue.
Setting Up and Maintaining Queues 14.6 Using Queue Options 14.6.2 Using Job Retention Options Job retention options allow users to retain a job in a queue after the job completes. System managers can use job retention options to keep information about all jobs in the queue after the jobs complete; this is helpful when tracking jobs submitted by other users. 14.6.2.1 Setting Job Retention Users can set job retention, as can system managers. The following sections explain how each can perform this task.
Setting Up and Maintaining Queues 14.6 Using Queue Options Figure 14–10 Determining Job Retention User submits job with retention option to generic queue.1 Job sent to execution queue. Does the job completion status match the execution queue’s job retention setting? Yes Job retained on execution queue. Yes Job retained on generic queue. Yes Job retained on queue to which it was submitted.
Setting Up and Maintaining Queues 14.6 Using Queue Options 14.6.2.2 Specifying Timed Job Retention Users can specify timed job retention. For example: $ SUBMIT/RETAIN=UNTIL=19-MAY-2000:07:31:0.0 MYFILE.DAT This eliminates the need to delete retained jobs from queues. Encourage users who include the /RETAIN qualifier to also use timed retention. 14.6.2.
Setting Up and Maintaining Queues 14.6 Using Queue Options Example You manage three LN03 printers in each of the four corners of a building. A generic queue LN03$PRINT feeds execution queues for each printer. You can define the characteristics EAST, WEST, NORTH, and SOUTH. When a user submits a print job to LN03$PRINT with the EAST characteristic, the job prints on the first idle LN03 printer in the eastern corner of the building.
Setting Up and Maintaining Queues 14.6 Using Queue Options Example In the following example, the characteristic name SECOND_FLOOR is assigned to characteristic number 2. The logical names SALES_FLOOR and SALES_ DEPT are defined as equivalent to the characteristic name SECOND_FLOOR. As a result, the logical names SALES_FLOOR and SALES_DEPT are equivalent to the characteristic name SECOND_FLOOR and characteristic number 2.
Setting Up and Maintaining Queues 14.6 Using Queue Options 14.6.3.6 Deleting Characteristics To delete a characteristic definition, enter DELETE/CHARACTERISTIC. You must specify the characteristic-name with DELETE/CHARACTERISTIC. If you know the number assigned to the characteristic but do not know the name, enter SHOW QUEUE/CHARACTERISTICS to display the names and numbers assigned to characteristics on the system.
Setting Up and Maintaining Queues 14.6 Using Queue Options • The OpenVMS Performance Management By default, a process running a batch job uses values taken from the UAF record of the user submitting the job or from system parameter settings. If you specify values for any of these options, processes for jobs executed in the queue will use the values you set unless the user specifies values when the job is submitted.
Setting Up and Maintaining Queues 14.6 Using Queue Options Process Limit Description Working set quota The value that approximates the amount of physical memory used by each batch job in the queue in a memory-constrained system. Working set extent The value that approximates the amount of physical memory in a memory-rich system. You should set this to a high value.
Setting Up and Maintaining Queues 14.6 Using Queue Options 14.6.4.6 Options for Memory-Constrained Systems On memory-constrained systems, total the pages required for the batch working sets on all batch queues. Also make sure that enough fluid memory remains for interactive jobs. Fluid memory can be reassigned from one process to another through swapping and paging.
Setting Up and Maintaining Queues 14.6 Using Queue Options If the jobs’ scheduling priorities are identical, the job that was submitted first is processed first. How to Perform This Task To specify job scheduling options, follow these steps: 1. Decide if you want the order of print jobs to be based on size. 2. Decide if you want to set a block limit on jobs to be printed.
Setting Up and Maintaining Queues 14.6 Using Queue Options is lighter. Users can specify the /AFTER qualifier with the PRINT command to specify that a job is to be printed after a specific time. 14.6.5.2 Changing the Scheduling Priority of a Job If a batch or print job cannot be processed, it is placed in a pending state and is not processed until the cause of the pending state is resolved. For more information, see Section 14.8.2.
Setting Up and Maintaining Queues 14.6 Using Queue Options Note If you do not need to burst pages of a printer’s output—for example, if your printer uses cut sheet paper—avoid the burst page option. Flag pages, or flag and trailer pages, are usually sufficient for identifying the end of a job. Table 14–2 describes the information found on job flag pages, file flag pages, job trailer pages, and file trailer pages.
Setting Up and Maintaining Queues 14.6 Using Queue Options Table 14–2 (Cont.) Contents of Job and File Pages Item Description Qualifier phrase (file trailer page only) Indicates the print, queue, and form qualifiers active when the job was submitted; nonactive qualifiers (except /NORECORD_BLOCKING and /NOFEED) are not included.
Setting Up and Maintaining Queues 14.6 Using Queue Options Table 14–2 (Cont.) Contents of Job and File Pages Item Description Ruler (file trailer and job trailer pages only) A sequence of numbers counting to the end of the form. Figure 14–11 shows job flag and burst pages. Figure 14–12 shows file flag and burst pages. Figure 14–13 shows file trailer and job trailer pages.
Setting Up and Maintaining Queues 14.
Setting Up and Maintaining Queues 14.6 Using Queue Options Figure 14–12 File Flag and Burst Pages BBBBBBBBBB BBBBBBBBBB BBBBBBBBBB 11111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111 11111111111111111111 Digital Equipment Corporation − OpenVMS VAX Version X7.
Setting Up and Maintaining Queues 14.
Setting Up and Maintaining Queues 14.6 Using Queue Options form length until the 40-character threshold is exceeded. Margins are not taken into account when formatting banner pages. Note All banner pages format information to the width and length of the default form size of 80 characters by 51 lines. Therefore, information might be truncated, depending on the form sizes you specify. See Section 14.6.7.8 for information about controlling line and page overflow.
Setting Up and Maintaining Queues 14.6 Using Queue Options In OpenVMS, you have the option of using either of the following forms: • A systemwide default form If your printing needs are limited, use the systemwide default form (named DEFAULT) for all queues. Note that you can make changes to the systemwide default form. • Forms that you create and assign to specific queues To format output or indicate special paper, you can create customized forms.
Setting Up and Maintaining Queues 14.6 Using Queue Options The following sections provide guidelines for performing these tasks with all forms, systemwide default forms, or customized forms: Task Type of Form Reference Display forms defined on a system All Section 14.6.7.1 Display the form assigned to a queue All Section 14.6.7.2 Change the systemwide default form Default Section 14.6.7.3 Create a form Customized Section 14.6.7.4 Assign a default form for a queue Customized Section 14.6.7.
Setting Up and Maintaining Queues 14.6 Using Queue Options Table 14–3 explains these options in detail. To change the systemwide default form, enter the DEFINE/FORM command in the following format: DEFINE/FORM DEFAULT 0 /qualifier[s] Example To change the default bottom margin from 6 to 4, and the page length from 66 to 55, enter this command: $ DEFINE/FORM DEFAULT 0/MARGIN=(BOTTOM=4)/LENGTH=55 Note Once a queue or job references a form, you cannot change the stock for that form.
Setting Up and Maintaining Queues 14.6 Using Queue Options Table 14–3 (Cont.) DEFINE/FORM Qualifiers Qualifier Purpose /[NO]PAGE_ SETUP=(module[,...]) Specifies one or more device control modules that set up a device at the start of each page. /SETUP=(module[,...]) Specifies one or more device control modules that set up the device at the start of each file. /[NO]SHEET_FEED Specifies that print jobs pause at the end of every physical page so that a new sheet of paper can be inserted.
Setting Up and Maintaining Queues 14.6 Using Queue Options Example In the following example, the SET QUEUE command changes the default form to LN03_PORTRAIT for the LN03_PRINT queue. $ SET QUEUE/DEFAULT=FORM=LN03_PROTRAIT LN03_PRINT 14.6.7.6 Mounting a Form on a Queue To mount a form on a queue, use the /FORM_MOUNTED qualifier with INITIALIZE/QUEUE, START/QUEUE, or SET QUEUE in the following format: INITIALIZE/QUEUE/FORM_MOUNTED=type where type is the form name or number defined by the DEFINE/FORM command.
Setting Up and Maintaining Queues 14.6 Using Queue Options the same stock as the currently mounted form. Operator assistance is needed only to mount a form that has a stock that differs from the stock of the currently mounted form. For more information, see Section 14.8.2.1. To control line overflow, create forms using DEFINE/FORM with the /[NO]TRUNCATE and /[NO]WRAP qualifiers described in Table 14–3.
Setting Up and Maintaining Queues 14.6 Using Queue Options 2. Assign the device control library to a queue. (This step is not necessary if you use the default library name SYSDEVCTL.TLB.) 3. Create one or more forms with setup or page setup modules. 4. Assign reset modules to a queue.
Setting Up and Maintaining Queues 14.6 Using Queue Options 18. Reset modules assigned to the queue. The following sections describe how to manage device control libraries. 14.6.8.2 Creating a Device Control Library and Inserting Modules To create a device control library and insert modules, perform the following steps: 1. Create a device control library by entering a command in the following format: LIBRARY/CREATE/TEXT SYS$COMMON:[SYSLIB] filename.TLB 2.
Setting Up and Maintaining Queues 14.6 Using Queue Options Operations that request a particular device control library module use the module from the library specified for the queue. Guidelines for using libraries follow: • If you have a small configuration of printers and normally use only a few modules, you usually store all modules in a single library and assign that same library to each printer queue.
Setting Up and Maintaining Queues 14.6 Using Queue Options Examples In the following example, the reset sequence contained in the module resets the printer at the end of each job. It also resets the printer when the queue is started to ensure that the first job prints correctly. $ INITIALIZE/QUEUE/LIBRARY=MYDEVCTL/SEPARATE=RESET=MODULE2 PDQ_QUE The following example uses device control library modules to process a print job. Two device control modules are created and inserted into the library file MYDEVCTL.
Setting Up and Maintaining Queues 14.7 Maintaining Queues 14.7.1 Using Queue Management Commands Table 14–4 lists commands for creating and controlling queues and tells whether they have the same effect on all queues or if they have different effects on autostart and nonautostart queues. Table 14–4 Effects of Queue Commands Command Effect on Autostart Queues Nonautostart Queues ASSIGN/MERGE Moves jobs from one queue to another. Moves jobs from one queue to another.
Setting Up and Maintaining Queues 14.7 Maintaining Queues Task For More Information Closing a queue Section 14.7.1.4 Stopping a queue Section 14.7.1.5 Preventing autostart queues from starting Section 14.7.1.6 Disabling autostart on a node Section 14.7.1.7 Stopping all queues on a node Section 14.7.1.8 Stopping queues before shutting down a system Section 14.7.1.9 Assigning a logical queue Section 14.7.1.10 Moving all jobs from one queue to another Section 14.7.1.
Setting Up and Maintaining Queues 14.7 Maintaining Queues Qualifier Description /ALL_JOBS Displays information about all jobs for the selected queues. /BRIEF Displays a brief listing of information about job entries in the queue. The brief listing is the default for the SHOW QUEUE command. /FILES Adds a list of files associated with each job to the display. /FULL Displays complete queue and job information (also displays any ACLs set for the queues).
Setting Up and Maintaining Queues 14.7 Maintaining Queues You can use the F$GETQUI lexical function to obtain information about the following types of objects: Characteristics Forms Queues Jobs contained in queues Files of jobs contained in queues For example, you could write a command procedure to display the total number of blocks of jobs in a pending state in all printer queues. You must have read access to the job or SYSPRV or OPER privilege to obtain job and file information.
Setting Up and Maintaining Queues 14.7 Maintaining Queues Entry Jobname Username Status ----- ------------------874 PIPE FITZGERALD Executing Submitted 26-FEB-2000 11:25 /KEEP /NOTIFY /NOPRINT /PRIORITY=100 /RESTART=CLUSTER_BATCH /RETAIN=UNTIL="0 01:00" File: _$333$DISK1:[FITZGERALD]PIPE.
Setting Up and Maintaining Queues 14.7 Maintaining Queues 14.7.1.4 Closing a Queue When a queue is not available for an extended period of time (for example, when a printer needs servicing), you can prevent new jobs from entering the queue by specifying the /CLOSE qualifier with SET QUEUE, INITIALIZE/QUEUE, or START/QUEUE. The /CLOSE qualifier prevents users from entering jobs in the queue with PRINT or SUBMIT commands.
Setting Up and Maintaining Queues 14.7 Maintaining Queues • Upon completion of any jobs currently executing on one of the node’s autostart queues, force the queue to fail over to the next available node in the queue’s failover list on which autostart is enabled. (An autostart queue can only fail over if you have set it up to run on more than one node.) By default, DISABLE AUTOSTART/QUEUES affects the node from which it is entered. Specify the /ON_NODE qualifier to disable autostart on a different node.
Setting Up and Maintaining Queues 14.7 Maintaining Queues Use one of the following methods: Timing Method Before executing SHUTDOWN.COM Define the logical name SHUTDOWN$DISABLE_AUTOSTART to be the number of minutes in the following format: While executing SHUTDOWN.
Setting Up and Maintaining Queues 14.7 Maintaining Queues The ASSIGN/MERGE command moves all jobs currently in the source queue. If new jobs are entered into the source queue before it is deleted, those new jobs remain in the source queue, and are not transferred to the target queue. You might want to close the queue to prevent new jobs from being entered in the queue, as explained in Section 14.7.1.4, before entering ASSIGN/MERGE.
Setting Up and Maintaining Queues 14.7 Maintaining Queues Table 14–6 describes the job statuses returned by the SHOW ENTRY command. Table 14–6 Job Statuses Returned by SHOW ENTRY Status Description Aborting Executing job is halting prior to normal completion and will not continue processing. Executing Job is executing from a batch queue. Holding Job is being held in the queue indefinitely. For more information, see Section 14.7.2.3. Pending Job is waiting its turn to execute.
Setting Up and Maintaining Queues 14.7 Maintaining Queues 14.7.2.2 Modifying Job Processing Options You can modify many job processing options by specifying qualifiers with a command in the following format: SET ENTRY/qualifier[,...] entry-number Table 14–7 lists some qualifiers that are frequently used to change jobs. For a list of all the job processing options you can change with the SET ENTRY command, refer to the OpenVMS DCL Dictionary.
Setting Up and Maintaining Queues 14.7 Maintaining Queues You can use the following commands to hold and release jobs: Command Purpose SET ENTRY/HOLD Holds a job in a queue indefinitely before processing. SET ENTRY/AFTER=time Holds a job in a queue for processing after a specified time. To specify /AFTER for a job on hold, you must also specify /NOHOLD to cause the job to be held only until the specified time.
Setting Up and Maintaining Queues 14.7 Maintaining Queues Examples 1. A job is executing in output execution queue BETA_LPB0 when the printer on which the queue is running jams. If no other jobs are pending in the queue, you might want to stop and requeue the job to a queue running on another printer. Because the printer in this example is jammed, you might also want to stop the queue.
Setting Up and Maintaining Queues 14.7 Maintaining Queues Example A user has noticed that a job is processing in an endless loop. The user is not the owner of the job and lacks sufficient privilege to stop it. The user enlists your aid as the system manager.
Setting Up and Maintaining Queues 14.7 Maintaining Queues Qualifier Description /BACKWARD[=n] Restarts a print queue n pages before the current page; n defaults to 1. If you omit the value, printing resumes at the top of the current page. /FORWARD[=n] Advances the specified number of pages before resuming printing the current file in the current job; the default is 1. If you omit the page value, printing resumes at the top of the next page.
Setting Up and Maintaining Queues 14.7 Maintaining Queues Option Description MASK Specifies that input data is masked by replacing alphabetic characters with the character X and numbers with the number 9. Mask characters let you prevent the printing of sensitive information. If you omit the MASK option, data is printed unaltered. n A decimal number in the range 1 to 20 that specifies the number of alignment pages to print. By default, one page of alignment data is printed.
Setting Up and Maintaining Queues 14.8 Solving Queue Problems 2. Enter the SHOW LOGICAL/FULL SMBSRVSHR command to determine whether the logical name SMBSRVSHR is assigned, and, if it is assigned, its access mode (SUPERVISOR_MODE or EXECUTIVE_MODE). In most cases, this logical name should not be defined. However, if SMBSRVSHR is assigned, deassign it by entering the DEASSIGN SMBSRVSHR command with the /USER_MODE, /SUPERVISOR_MODE, or /EXECUTIVE_MODE qualifier. 3.
Setting Up and Maintaining Queues 14.8 Solving Queue Problems For example: $ SHOW QUEUE/FULL/ALL_JOBS/BY_JOB_STATUS=PENDING Generic printer queue REG$GENERIC /GENERIC=(REG$Q1,REG$Q2,REG$Q3)/OWNER=[SYSTEM]/PROTECTION=(S:M,O:D,G:R,W:R) Entry Jobname Username Blocks Status ----- ------------------- -----684 PROBLEMS CHURCHILL 3118 Pending (check execution queues) Submitted 7-MAR-2000 17:49 /FORM=DEFAULT /NOTIFY /PRIORITY=100 File: _$5$DUA174:[CHURCHILL]PROBLEMS.
Setting Up and Maintaining Queues 14.8 Solving Queue Problems Table 14–8 (Cont.) Common Causes and Solutions for Pending Job Status Problem Solution An output job requires an output device that is enabled for lowercase printing. If the printer supports lowercase printing, use the /LOWERCASE qualifier with SET PRINTER or SET TERMINAL. Otherwise, use SET ENTRY/REQUEUE to move the job to an execution queue that sends its output to a printer with lowercase printing enabled. 14.8.2.
Setting Up and Maintaining Queues 14.8 Solving Queue Problems 14.8.3 Fixing a Stalled Output Queue If an output queue is in the stalled state, the device on which the queue is running is malfunctioning. Check the device and fix the problem. Once the problem is fixed, the queue will leave the stalled state. If you cannot fix the problem immediately, stop the queue by entering STOP/QUEUE/RESET.
Setting Up and Maintaining Queues 14.8 Solving Queue Problems If you see a message similar to the following one, a reference to the queue, form, or characteristic still exists: %DELETE-E-NOTDELETED, error deleting object-name -JBC-E-REFERENCED, existing references prevent deletion For example, the queue you are attempting to delete might be named as a target for a generic queue, or the form you are attempting to delete might be specified for a print job.
Setting Up and Maintaining Queues 14.8 Solving Queue Problems Example The following example includes several commands used to fix problems preventing the deletion of a queue: $ DELETE/QUEUE JADE_BATCH! %DELETE-E-NOTDELETED, error deleting JADE_BATCH -JBC-E-QUENOTSTOP, queue must be stopped to perform operation" $ STOP/QUEUE/NEXT JADE_BATCH# $ DELETE/QUEUE JADE_BATCH$ %DELETE-E-NOTDELETED, error deleting JADE_BATCH% -JBC-E-REFERENCED, existing references prevent deletion $ SHOW QUEUE/FULL . . .
Setting Up and Maintaining Queues 14.8 Solving Queue Problems However, if your operating environment does not allow you to mount a disk clusterwide, you can resolve this problem by running the queue manager process on a node that has access to the disk. You can specify the node on which the queue manager process runs by specifying the /ON=node qualifier with the START/QUEUE/MANAGER command. For more information about this qualifier, refer to the OpenVMS DCL Dictionary. 14.8.
Setting Up and Maintaining Queues 14.8 Solving Queue Problems If your site has a large number of different printers, you can help prevent this problem by using more libraries, so that each library is assigned to fewer queues. For example, you should create and assign a different library for each type of printer, as explained in Section 14.6.8.3. 14.8.8 Fixing a Disabled Queue The queue manager attempts to correct any kind of corruption detected.
Index A Aborting job status, Vol 1, 14–64 Access control entries See ACEs Access Control Entry (ACE), Vol 1, 10–9, 10–10 Access control lists See ACLs Accessibility field tape file system checks, Vol 1, 10–26 Access modes recommended for logical names of system components, Vol 1, 5–9 Access types abbreviations of, Vol 1, 12–8 checking when writing files to tape volumes, Vol 1, 10–27 protecting directory files, Vol 1, 10–20 disk files, Vol 1, 10–15 protection codes and, Vol 1, 12–8 read, Vol 1, 10–22 continu
ADD_PAGEFILEn_SIZE symbol, Vol 2, 16–31 ADD_PAGEFILE symbol, Vol 2, 16–31 ADD_ prefix for AUTOGEN, Vol 2, 15–19 ADD_SWAPFILEn_SIZE symbol, Vol 2, 16–31 ADD_SWAPFILE symbol, Vol 2, 16–31 AGEN$FEEDBACK.DAT file description, Vol 2, 15–11 AGEN$FEEDBACK_REQ_TIME logical name, Vol 2, 15–22 AGEN$PARAMS.REPORT logs sizes of page, swap, and dump files, Vol 2, 15–18 AGEN$PARAMS.
ASTLM process limit, Vol 1, 7–43 value for efficient backups, Vol 1, 11–11 Asymmetric vector processing configuration, Vol 2, 28–4 Asynchronous DECnet using virtual terminals, Vol 1, 8–22, 8–23 Attached processors, Vol 2, 28–2 Audit Analysis utility (ANALYZE/AUDIT), Vol 1, 12–14 See also ANALYZE/AUDIT command generating security reports, Vol 2, 20–31 Auditing security, Vol 1, 12–13 See also Security audit log files; Security auditing displaying using SHOW AUDIT command, Vol 2, 20–28 Audit log files, Vol 2,
AUTOGEN.
BACKUP command (cont’d) /SINCE qualifier, Vol 1, 11–36, 11–37 /VERIFY qualifier, Vol 1, 11–67 backing up a save set twice, Vol 1, 11–67 with multiple output devices, Vol 1, 11–26, 11–34, 11–35 Backup log file BACKUP.
Batch jobs (cont’d) changing scheduling priority, Vol 1, 14–35 completing before using VMSINSTAL.
Booting problems (cont’d) hardware, Vol 1, 4–18 invalid boot block, Vol 1, 4–19 solving, Vol 1, 4–18 use of boot block, Vol 1, 4–19 with an alternate system parameter file, Vol 1, 4–7 with controlled system startup, Vol 1, 4–13 Boot messages indicating execution of STARTUP.COM procedure, Vol 1, 4–5 indicating execution of STARTUP_VMS.
CLUSTER_CONFIG.COM command procedure (cont’d) creating SATELLITE_PAGE.
Connecting devices manually (cont’d) in system startup, Vol 1, 5–7 on VAX, Vol 1, 8–8 network communications device, Vol 1, 8–10 on VAX systems, Vol 1, 8–9 virtual terminals, Vol 1, 8–22 Connecting to a Windows NT system, Vol 2, D–9 CONSCOPY.
Crash dumps (cont’d) freeing page file of, Vol 2, 16–24 in system startup, Vol 2, 16–22 physical, Vol 2, 16–4 releasing, Vol 2, 16–24, 16–25 requirements for saving, Vol 2, 16–4 saving contents of page file on reboot, Vol 2, 16–3 saving contents of system dump file on reboot, Vol 1, 5–13 selective, Vol 2, 16–4 Crash Log Utility Extractor (CLUE) description, Vol 2, 16–21 CREATE/DIRECTORY command to specify UIC-based directory protection, Vol 1, 10–21 CREATE command creating directories, Vol 1, 10–29 limiting
Data blocks partially recorded ISO 9660 standard, Vol 1, 9–8 Data card deck, Vol 1, 8–40 Data Communications Equipment, Vol 1, 8–27, 8–28 Data interleaving ISO 9660, Vol 1, 9–8 Data loss avoiding by dismounting volume, Vol 1, 9–58 Date formats, Vol 1, 6–17 predefined, Vol 1, 6–21 specifying, Vol 1, 6–19, 6–20 Daylight saving time, Vol 1, 6–2 changing to, Vol 1, 6–13 automatically, Vol 1, 6–13 DBBFs (detected bad block files), Vol 1, 9–80 DCL commands accessing disk and tape files, Vol 1, 10–22 executing on
DECW$TAILOR See Tailoring utilities Deductible resource, Vol 1, 7–3 DEFAULT account in UAF, Vol 1, 7–6 Default boot procedure, Vol 1, 4–2 Default directories, Vol 1, 7–15 Default form, Vol 1, 14–48 DEFAULT form, Vol 1, 14–46 Default protection UIC, Vol 1, 10–16 Default Protection ACEs, Vol 1, 12–10 Default system parameters booting with, Vol 1, 4–9 Deferred memory testing on AlphaServer 4100 computers, Vol 1, 4–3 DEFINE/CHARACTERISTIC command, Vol 1, 14–30 DEFINE/FORM command, Vol 1, 14–47 for controlling l
Devices autoconfiguration of (cont’d) supported buses, Vol 1, 8–17 availability OPCOM message, Vol 1, 9–73 configuring automatically, Vol 1, 8–11 in system startup, Vol 1, 5–7, 8–7 manually, Vol 1, 5–7, 8–8 special devices, Vol 1, 8–8, 8–9 connecting, Vol 1, 8–8 determining available, Vol 1, 8–2 Ethernet adapter specifying number for AUTOGEN, Vol 2, 15–21 getting information about, Vol 1, 8–2, 8–38 ISO-9660 getting information about, Vol 1, 8–5 LTAn, Vol 1, 8–23 magnetic tape See Tapes managing, Vol 1, 8–1
Disk files copying (cont’d) from disk volumes, Vol 1, 10–29 to tapes, Vol 1, 10–31 using COPY command, Vol 1, 10–28 modifying characteristics, Vol 1, 10–18, 10–19 Disk I/O resource offloading virtual I/O cache, Vol 2, 18–10 DISKQUOTA/DISABLE command, Vol 1, 9–67 DISKQUOTA/ENABLE command, Vol 1, 9–67 DISKQUOTA commands See also Disk Quota utility in SYSMAN, Vol 1, 2–12 Disk quotas, Vol 1, 7–15 See also Disk Quota utility creating, Vol 1, 9–65 definition, Vol 1, 9–63 disabling, Vol 1, 9–67 displaying, Vol 1,
Disk volumes (cont’d) binding into volume sets, Vol 1, 9–43 characteristics modifying, Vol 1, 9–41 console, Vol 1, 10–33 copying files from, Vol 1, 10–29 copying files to and from foreign volumes, Vol 1, 10–33 copying files to tape volumes, Vol 1, 10–31 creating Files-11 structure, Vol 1, 9–16 creating shadowed volume sets, Vol 1, 9–46 creating volume sets from, Vol 1, 9–45 definition, Vol 2, A–1 definitions, Vol 1, 9–3 disk quota operations, Vol 1, 9–64 dismounting, Vol 1, 9–57 displaying type, Vol 1, 10–3
Drivers See Device drivers DSA device naming, Vol 1, 8–1 DSI (DIGITAL System Identifier) ISO 9660 media protection, Vol 1, 9–25 mount option, Vol 1, 9–24 DSI keyword with MOUNT/PROTECTION command, Vol 1, 9–30 DTE (data terminal equipment), Vol 1, 8–27, 8–28 Dual-architecture OpenVMS Cluster systems installing images, Vol 2, 22–18 example, Vol 2, 22–18 Dual format ISO 9660 CD and ODS, Vol 1, 9–4 DUMPBUG system parameter, Vol 2, 16–4 Dump file information saving automatically, Vol 2, 16–19 Dump files See also
Error log files (cont’d) SYSPRV privilege to access, Vol 2, 20–7 Error logging See also ERRFMT process; Error log files; Error Log utility description, Vol 2, 20–2 facility, Vol 2, 20–2 reports produced, Vol 2, 20–3 Error Log Report Formatter (ERF), Vol 2, 20–2 Error log reports See Error Log utility, reports Error Log utility (ERROR LOG) See also ERRFMT process; Error logging; Error log files ANALYZE/ERROR_LOG command, Vol 2, 20–7 definition, Vol 2, 20–5 error logging, Vol 2, 20–2 relationship to UETP, Vol
Extended File Cache, Vol 2, 18–1 Extended File Specifications backing up ODS-5 volumes, Vol 1, 10–9 BACKUP limitations, Vol 1, 9–10 BACKUP support of, Vol 1, 11–6 case blindness, Vol 1, 10–4 case preservation, Vol 1, 10–4 CONDENSED file names, Vol 1, 10–5 converting existing volumes, Vol 1, 9–36 converting from ODS-1 to ODS-2, Vol 1, 9–39 converting from ODS-5 to ODS-2, Vol 1, 9–39 deep directory levels, Vol 1, 10–2 DID (Directory ID) displaying, Vol 1, 10–5 displaying volume structure, Vol 1, 10–3 enabling
File formats use with BACKUP, Vol 1, 11–10 File fragmentation of page and swap files, Vol 2, 16–34 File headers index file, Vol 2, A–7 contents, Vol 2, A–7 extension, Vol 2, A–8 primary, Vol 2, A–8 File identification file number, Vol 2, A–4 Files–11, Vol 2, A–4 file sequence number (SEQ), Vol 2, A–4 relative volume number (RVN), Vol 2, A–4 File Log VMSINSTAL.
Files–11 On-Disk Structure structure (cont’d) Level 5, Vol 2, A–4 terminology, Vol 2, A–2 UIC, Vol 2, A–4 using with Exchange utility (EXCHANGE) to transfer data, Vol 1, 10–33 File specifications ANSI, Vol 1, 10–25 for installing images, Vol 2, 17–15 OpenVMS extended, Vol 1, 10–25 standard, Vol 1, 10–25 File structures disk and CD–ROM, Vol 1, 9–4 options on OpenVMS systems, Vol 1, 9–4 File system controlling data caching, Vol 2, 18–1 File versions relative input BACKUP supports, Vol 1, 11–6 File windows map
Header labels on tape files, Vol 1, 9–12, 10–24 reading attributes of, Vol 1, 10–26 Header resident images, Vol 2, 17–10, 17–11 Help POLYCENTER Software Installation utility, Vol 1, 3–26 HELP command affected during layered product installation, Vol 1, 3–28 Help Message utility (MSGHLP), Vol 1, 5–25 accessing $STATUS values for uninstalled messages, Vol 1, 5–26 adding .
Images (cont’d) system version dependent registering, Vol 1, 5–23 user-level calling of protected code, Vol 2, 17–10, 17–14 version checking, Vol 1, 5–23 writable, Vol 2, 17–10 Incremental backup command format for disks, Vol 1, 11–37 command format for tapes, Vol 1, 11–36 definition, Vol 1, 11–3 restoring files from, Vol 1, 11–47 to disk, Vol 1, 11–36 to tape, Vol 1, 11–35 INDEXF.
INITIALIZE command (cont’d) creating volume identifiers for continuation volumes, Vol 1, 9–54 disk volumes, Vol 1, 9–17 for formatting page and swap file disks during system startup, Vol 1, 5–6 mounting volume sets, Vol 1, 9–54 qualifiers, Vol 1, 9–18 setting device protection, Vol 1, 9–23 for tape volumes, Vol 1, 10–22, 10–31 specifying logical names, Vol 1, 10–31 to format and write label to volume, Vol 1, 9–18 Initializing queues, Vol 1, 14–15 See also INITIALIZE/QUEUE command volumes See also INITIALIZE
Internet specifying transport, Vol 1, 5–34 Intra-Cluster communications, Vol 1, 12–9 Intrusion databases, Vol 1, 12–7 Intrusions detection, Vol 1, 12–6 evasion, Vol 1, 12–6 Intrusion services managed by security server, Vol 1, 5–5 IO AUTOCONFIGURE command in SYSMAN, Vol 1, 8–7, 8–9 in system startup, Vol 1, 5–4, 5–7, 8–7 IO CONNECT command in SYSMAN, Vol 1, 8–9 in system startup, Vol 1, 5–7 IO LOAD command in SYSMAN, Vol 1, 8–9 IPC (Interrupt Priority C) adjusting quorum, Vol 1, 9–78 canceling mount verific
K Kernel mode calling images running in, Vol 2, 17–10, 17–14 logical names, Vol 2, 17–14 Keypad definitions, Vol 2, 22–6, 22–7 Key processes definition, Vol 2, 16–14 KFMSB adapter system tuning, Vol 2, 15–37 Kits See Software products Known file lists definition, Vol 2, 17–9 in system startup, Vol 1, 5–13 Known images definition, Vol 2, 17–9 deleting, Vol 2, 17–17 dismounting volume, Vol 2, 17–17 displaying, Vol 2, 17–16 evaluating merits of installing, Vol 2, 17–11, 17–16 file specification for, Vol 2, 17–
LANs (local area networks) (cont’d) displaying OPCOM messages, Vol 2, 24–29 displaying status and counters, Vol 2, 24–27 enabling MOP downline load service, Vol 2, 24–27 LANACP related OPCOM messages, Vol 2, 24–26 LAN Auxiliary Control Program (LANACP) utility, Vol 2, 24–6 LAN Control Program (LANCP) utility, Vol 2, 24–7 LANCP command files, Vol 2, 24–10 LANCP SPAWN function, Vol 2, 24–10 LAN MOP and DECnet MOP, Vol 2, 24–24 Load Trace facility, Vol 2, 24–29 migrating DECnet MOP to LAN MOP, Vol 2, 24–24 MOP
LAT software (cont’d) queuing incoming requests, Vol 2, 26–21 service announcements, Vol 2, 26–4, 26–14 database, Vol 2, 26–14 dedicated applications, Vol 2, 26–2 definition, Vol 2, 26–2 node, Vol 2, 26–3, 26–4, 26–14 remote printing, Vol 2, 26–2 setting up limited services, Vol 2, 26–21 setting up ports, Vol 2, 26–20 starting network in command procedure, Vol 1, 5–15; Vol 2, 26–17 starting with LAT$STARTUP.
Log files (cont’d) operator creating new, Vol 2, 20–23 enabling and disabling classes, Vol 2, 20–24 maintaining, Vol 2, 20–25 printing, Vol 2, 20–25 restarting, Vol 2, 20–25 security alarm messages, Vol 2, 20–22 setting up, Vol 2, 20–23 specifying location, Vol 2, 20–23 troubleshooting the queue manager, Vol 1, 13–16 security audit, Vol 2, 20–2 creating new version, Vol 2, 20–31 reviewing, Vol 2, 20–27 Logging in, Vol 1, 2–10 See also Logins when errors in login procedures prevent, Vol 1, 4–10 when errors i
Login command procedures (cont’d) user-specified, Vol 1, 7–20 when errors prevent you from logging in, Vol 1, 4–10 Logins See also Logging in controlling number of dialup attempts, Vol 1, 12–6 restricting by function, Vol 1, 7–30 restricting by time, Vol 1, 7–28 sequence of events, Vol 1, 7–5 LOGOUT command, Vol 2, 28–9 Logout command procedures LOGOUT command, Vol 1, 7–23 SYLOGOUT.
MAX_PAGEFILE symbol, Vol 2, 16–31 MAX_ prefix for AUTOGEN, Vol 2, 15–20 MAX_SWAPFILEn_SIZE symbol, Vol 2, 16–31 MAX_SWAPFILE symbol, Vol 2, 16–31 Media definition, Vol 1, 9–2 Media errors analyzing, Vol 1, 9–80 Memory allotted to vector consumer processes, Vol 2, 28–7 cache, Vol 2, 18–1 conserving with shareable images, Vol 2, 17–12 deferred testing, Vol 1, 4–3 images in, Vol 2, 17–10 information captured in crash dump, Vol 2, 16–2 physical dump, Vol 2, 16–4, 16–12 selective dump, Vol 2, 16–4, 16–12 making
MODPARAMS.DAT file (cont’d) MIN_ prefix, Vol 2, 15–20 sample, Vol 2, 15–17 specifying an alternate default startup command, Vol 1, 4–14 specifying parameter values absolute, Vol 2, 15–20 maximum, Vol 2, 15–20 minimum, Vol 2, 15–20 storing your system parameter changes in, Vol 2, 15–5 Modules device control See Device control modules MONITOR.
MOUNT command (cont’d) enabling mount verification feature for disks, Vol 1, 9–30 enabling mount verification feature for tapes, Vol 1, 9–32 enabling the processing of Subsystem Aces, Vol 1, 9–31 enabling the write cache for a tape device, Vol 1, 9–32 ensuring that tape volume set has been initialized, Vol 1, 9–54 establishing default file attributes for records on ISO 9660 media, Vol 1, 9–31 foreign volumes, Vol 1, 9–30, 9–32, 10–22 including a quoted text string as part of mount request, Vol 1, 9–30 inhib
MSGHLP See Help Message utility .MSGHLP$DATA files adding to the Help Message database, Vol 1, 5–28 MSGHLP$LIBRARY.
ODS (On-Disk Structure) (cont’d) definition, Vol 1, 9–2, 9–3 disk and CD–ROM file structures, Vol 1, 9–4 Levels 1, 2, and 5, Vol 1, 9–4 on dual format CDs, Vol 1, 9–4 reserved files, Vol 1, 9–5 ODS-1 comparing with ODS-2 and ODS-5, Vol 1, 9–6 migrating to ODS-2, Vol 1, 9–39 ODS-2 comparing with ODS-1, Vol 1, 9–6 converting from ODS-1, Vol 1, 9–39 converting from ODS-5, Vol 1, 9–39 converting to ODS-5, Vol 1, 9–36 displaying type of volume, Vol 1, 10–3 ODS-5 backing up, Vol 1, 10–9 case of file name, Vol 1,
OpenVMS Cluster environments (cont’d) test failure during UETP, Vol 2, 19–26 OpenVMS Cluster systems adjusting quorum after shutting down a node, Vol 1, 4–23 autostart queues in, Vol 1, 14–4 benefits, Vol 2, 22–2 common parameter files in, Vol 2, 15–22 cross-architecture booting, Vol 2, 24–26 DECnet node configuration, Vol 2, 23–10 defining in SYSMAN, Vol 1, 2–16 defining location of queue database files, Vol 1, 13–5 device names, Vol 1, 8–1 disks in, Vol 1, 9–3 dismounting a volume, Vol 1, 9–60 dual-archit
Operator log file (cont’d) recording changes to system parameters, Vol 2, 20–21 request identification number, Vol 2, 20–20 response recorded in, Vol 2, 20–20 restarting, Vol 2, 20–25 security alarm messages in, Vol 2, 20–22 setting up, Vol 2, 20–17, 20–23 size, Vol 2, 20–23 specifying default state, Vol 2, 20–24 terminal enable and disable message, Vol 2, 20–23 troubleshooting the queue manager, Vol 1, 13–16 user request and operator reply messages, Vol 2, 20–23 volume mount and dismount messages, Vol 2, 2
Output queuing environment (cont’d) for multiple printers of the same kind, Vol 1, 14–10 in OpenVMS Cluster environments, Vol 1, 14–11 sample configurations, Vol 1, 14–8 to 14–13 single printer, Vol 1, 14–8 spooled printers, Vol 1, 14–12 standalone workstation, Vol 1, 14–8 steps for setting up, Vol 1, 14–13 Overdraft limit user exceeding quota, Vol 1, 9–64 Overflow See Lines, overflow; Page overflow Overriding DECnet parameters, Vol 2, 15–21 Owner category of user access, Vol 1, 12–8 Ownership file displayi
PAKs (Product Authorization Keys) installing before using VMSINSTAL.COM command procedure, Vol 1, 3–4 loading in system startup, Vol 1, 5–5 preventing nodes from sharing, Vol 1, 3–5 PAN command, Vol 2, 22–6 PAN keypad function, Vol 2, 22–7 Paper See Printer paper; Stock Paper jam pausing printer to fix, Vol 1, 14–68 Parameter files See also System parameters ALPHAVMSSYS.
Performance disk, Vol 1, 9–35 effect of file extension on, Vol 2, 17–7 file system data caches, Vol 2, 18–1 importance of correct page file size, Vol 2, 16–9 importance of correct swap file size, Vol 2, 16–11 importance of sufficient hardware capacity, Vol 2, 17–5 improving decompressing system libraries, Vol 2, 17–6 designing efficient applications, Vol 2, 17–4 disabling high-water marking, Vol 2, 17–6 encouraging batch processing, Vol 2, 17–3 for vector processing with batch queues, Vol 2, 28–7 installing
PRINT/DELETE command, Vol 1, 14–76 PRINT command bypassing symbiont formatting, Vol 1, 14–50 overriding default form-feed options with, Vol 1, 14–50 preventing users from executing, Vol 1, 14–60 processing of, Vol 1, 14–2 specifying a form, Vol 1, 14–45 specifying banner pages, Vol 1, 14–44 specifying job retention, Vol 1, 14–29 specifying scheduling priority, Vol 1, 14–35 specifying setup and page setup modules, Vol 1, 14–53 Printer paper controlling with forms, Vol 1, 14–45, 14–49 pausing to align, Vol 1,
Processing environments multiprocessing See Multiprocessing vector processing See Vector processing Processing job status, Vol 1, 14–64 Process limits, Vol 1, 7–2 account jobs, Vol 1, 7–45 adjusting for vector processing, Vol 2, 28–7 AST queue, Vol 1, 7–43 CPU default specifying a value for batch queues, Vol 1, 14–20, 14–32, 14–34 CPU maximum specifying a value for batch queues, Vol 1, 14–21, 14–32, 14–34 CPU time, Vol 1, 7–44 detached process, Vol 1, 7–46 direct I/O count, Vol 1, 7–44 enqueue quota, Vol 1,
Protection checks MOUNT command overriding, Vol 1, 9–30 Protection codes access types, Vol 1, 12–8 changing, Vol 1, 10–17 format, Vol 1, 12–7 null access specification, Vol 1, 12–8 specifying, Vol 1, 10–15 Protocols LASTport, Vol 2, 25–5 Proxy accounts adding, Vol 1, 7–38 Proxy authorization files NET$PROXY.DAT, Vol 1, 7–4, 7–38 NETPROXY.
Queue databases See also Journal file of queue database; Master file of queue database; Queue file of queue database closing, Vol 1, 13–9 creating files, Vol 1, 13–7 default location, Vol 1, 13–4 definition, Vol 1, 13–3 detection of queue corruption, Vol 1, 14–78 determining location, Vol 1, 13–9 of master file, Vol 1, 13–5 of queue and journal file, Vol 1, 13–6 files comprising, Vol 1, 13–3 for multiple queue managers, Vol 1, 13–4, 13–11 naming convention, Vol 1, 13–4 function, Vol 1, 13–3 logical name def
Queues (cont’d) changing DEFAULT form, Vol 1, 14–46 changing options on, Vol 1, 14–59 closing, Vol 1, 14–60 commands See Queue commands creating, Vol 1, 14–15, 14–18 autostart execution, Vol 1, 14–15, 14–17 generic, Vol 1, 14–19 nonautostart execution, Vol 1, 14–18 creating a form, Vol 1, 14–47 defining a characteristic, Vol 1, 14–30 deleting, Vol 1, 14–63 deleting a job in, Vol 1, 14–67 disabled, Vol 1, 14–78 displaying information about, Vol 1, 14–56 failover of, Vol 1, 14–16 forms, Vol 1, 14–44 gathering
Read access (cont’d) for disk files, Vol 1, 10–15 granting through protection codes, Vol 1, 12–8 Read-ahead caching, Vol 2, 18–8 Read error if returned when booting, Vol 1, 4–18 Read operation See Access types, read Real-time priority, Vol 1, 7–33 Rebooting after creation of system files, Vol 2, 16–35 Rebuilding volumes, Vol 1, 8–5 Reconfiguration of software installation options, Vol 1, 3–29 Records blocking on tapes, Vol 1, 9–11 size, Vol 1, 9–33 Recovering lost files, Vol 1, 9–72 Reducing I/O on system d
Reserved files (cont’d) volume security profile (SECURITY.SYS), Vol 2, A–9 volume set list file (VOLSET.
SCBs (storage control blocks) in storage bitmap file, Vol 2, A–8 Scheduling, Vol 1, 7–2, 7–33 See also Priority, job scheduling batch jobs, Vol 1, 14–35 print jobs, Vol 1, 14–35 Scheduling priority for a batch or print job changing, Vol 1, 14–35 SCROLL command, Vol 2, 22–13 SCROLL keypad function, Vol 2, 22–7 SCSI (Small Computer Systems Interface), Vol 1, 11–43 SCSNODE system parameter, Vol 2, 25–11 in DECnet-Plus networks, Vol 2, 27–4 SDA (System Dump Analyzer utility) See System Dump Analyzer utility SDA
Services bindings, Vol 2, 25–15 nodes, Vol 2, 26–4 password protection, Vol 2, 25–15 write protection, Vol 2, 25–15 Sessions maintaining on more than one terminal, Vol 1, 8–22 maintaining when disconnecting a terminal, Vol 1, 8–22 SET (Field) command SHOW CLUSTER, Vol 2, 22–11 SET/STARTUP command in conversational boot, Vol 1, 4–14 SET ACCOUNTING command controlling which resources are tracked, Vol 2, 21–3 starting up a new accounting file, Vol 2, 21–3 SET ACL command modifying file characteristics, Vol 1,
SET VOLUME command (cont’d) modifying disk volume characteristics, Vol 1, 9–41 modifying file characteristics, Vol 1, 10–18 performing data checks, Vol 1, 9–41 specifying file retention periods, Vol 1, 9–69 Shadow sets backing up, Vol 1, 11–43 mounting disks, Vol 1, 11–45 restoring, Vol 1, 11–50 Shareable images, Vol 2, 17–10, 17–12 assigning logical names for, Vol 2, 17–17 Shared address data address data section, Vol 2, 17–12 assigns P1 space, Vol 2, 17–12 executable images can use, Vol 2, 17–12 image sec
SHUTDOWN$MINIMUM_MINUTES logical name, Vol 1, 4–27 SHUTDOWN$QUEUE_MINUTES logical name, Vol 1, 4–28 SHUTDOWN$TIME logical name, Vol 1, 4–28 SHUTDOWN$VERBOSE logical name, Vol 1, 4–28 SHUTDOWN.
Standalone BACKUP booting, Vol 1, 11–56, 11–58 building, Vol 1, 11–54, 11–57 definition, Vol 1, 11–54 qualifiers, Vol 1, 11–53 relation to Backup utility, Vol 1, 11–54 using to back up the system disk, Vol 1, 11–54, 11–59, 11–62 using to restore the system disk, Vol 1, 11–61 Standard time, Vol 1, 6–2 changing to, Vol 1, 6–13 automatically, Vol 1, 6–13 Star couplers definition of, Vol 1, 14–7 START/CPU command, Vol 2, 28–3, 28–6 START/QUEUE/MANAGER command, Vol 1, 13–7, 13–10 caution, Vol 1, 13–8 creating an
Startup command procedure site-independent (cont’d) See also STARTUP.COM command procedure specifying an alternate, Vol 1, 4–13 as the default, Vol 1, 4–14 site-specific See Site-specific startup command procedure specifying execution mode, Vol 1, 5–21 specifying node restrictions, Vol 1, 5–21 specifying startup phase, Vol 1, 5–21 starting queues, Vol 1, 14–18 SYCONFIG.COM See SYCONFIG.COM command procedure SYLOGICALS.COM See SYLOGICALS.COM command procedure SYPAGSWPFILES.COM See SYPAGSWPFILES.
SUBMON.COM command procedure sample, Vol 2, 20–43 used with Monitor utility, Vol 2, 20–41 Subprocesses creating with the LANCP SPAWN command, Vol 2, 24–10 subprocess creation limit, Vol 1, 7–2, 7–46 Substituting volumes, Vol 1, 9–35 Subsystem ACEs example, Vol 1, 12–11 Subsystems protected, Vol 1, 9–36 Supervisor mode logical names, Vol 2, 17–14 Suspended job status, Vol 1, 14–64 Suspending a job, Vol 1, 14–68 SVD (Supplementary Volume Descriptor) using to mount ISO 9660 volumes, Vol 1, 9–49 SWAPFILE.
Symbols (cont’d) PAGEFILEn_NAME, Vol 2, 16–29 STARTUP$AUTOCONFIGURE_ALL, Vol 1, 8–10 STARTUP$INTERACTIVE_LOGINS, Vol 1, 5–16 SWAPFILEn_NAME, Vol 2, 16–29 Symmetric multiprocessing See Multiprocessing Symmetric vector processing configuration, Vol 2, 28–4 SYPAGSWPFILES.
SYSTARTUP_VMS.
System dump files (cont’d) storing selective portions of memory, Vol 2, 16–12 System failures, Vol 2, 16–2 See also Crash dumps; System dump files determining cause, Vol 2, 16–2, 16–19 reporting to Compaq support representative, Vol 2, 16–19 saving contents of system dump file after, Vol 1, 5–13; Vol 2, 16–22 writing of system dump file, Vol 2, 16–2 System files duplicating using VMSKITBLD, Vol 1, 2–27 moving off system disk to improve performance, Vol 2, 17–7 on public volumes, Vol 1, 9–14 optional adding
System Management utility (SYSMAN) (cont’d) managing system parameters, Vol 2, 15–4, 15–26 modifying the system parameter file, Vol 2, 15–28 PARAMETERS command, Vol 2, 15–26 privileges required, Vol 1, 2–11 profile, Vol 1, 2–16 adjusting, Vol 1, 2–17 rights limitation, Vol 1, 2–11 showing system parameters, Vol 2, 15–27 showing the contents of a startup database, Vol 1, 5–21 showing the name of the target startup database, Vol 1, 5–20 shutdown, Vol 1, 4–29 SMISERVER process, Vol 1, 2–12 specifying the curre
System parameters (cont’d) STARTUP_P1, Vol 1, 4–15 STARTUP_P2, Vol 1, 4–16 storing your changes for use with AUTOGEN, Vol 2, 15–5 symmetric multiprocessing, Vol 2, 28–3 TAPE_MVTIMEOUT, Vol 1, 9–75, 9–77 TTY_DEFCHAR, Vol 1, 8–21 TTY_DEFCHAR2, Vol 1, 8–21, 8–23 types of, Vol 2, 15–2 dynamic, Vol 2, 15–2 general, Vol 2, 15–2 major, Vol 2, 15–2 UAFALTERNATE, Vol 1, 4–12 user definable, Vol 2, 15–3 VAXVMSSYS.
System startup in an emergency (cont’d) without the UAF, Vol 1, 4–11 installing images, Vol 1, 5–4; Vol 2, 17–9 installing page and swap files, Vol 1, 5–5, 5–6; Vol 2, 16–6, 16–26, 16–27 limiting the number of interactive users, Vol 1, 5–16 LMF database, Vol 1, 5–5 loading of device drivers, Vol 1, 5–4 loading of licenses, Vol 1, 5–5 loading of Product Authorization Keys (PAKs), Vol 1, 5–5 location of files used in, Vol 1, 4–5 logging with SYSMAN, Vol 1, 4–17 making remote InfoServer devices available, Vol
Tape files (cont’d) accessing for read and write operations, Vol 1, 10–23 append operation, Vol 1, 10–27 closing after opening for read access, Vol 1, 10–26 closing after opening for write access, Vol 1, 10–27 copying, Vol 1, 10–31 definition, Vol 1, 9–12 locating for read and write access, Vol 1, 10–24 modifying characteristics, Vol 1, 10–18 reading, Vol 1, 10–26 update operation, Vol 1, 10–27 writing to, Vol 1, 10–27 Tape file system checking continuation volume, Vol 1, 9–56 expiration date field, Vol 1,
Tape volumes (cont’d) write-enabling, Vol 1, 9–35 write-locking, Vol 1, 9–51 write rings, Vol 1, 9–51 writing files to, Vol 1, 10–31 writing to files on, Vol 1, 10–27 TAPE_MVTIMEOUT system parameter, Vol 1, 9–75, 9–77 TCP/IP (Transmission Control Protocol/Internet Protocol), Vol 2, 23–5 See Compaq TCP/IP Services for OpenVMS TCPIP$CONFIG configuring Compaq TCP/IP Services for OpenVMS, Vol 2, 23–6, 23–7 TDF (time differential factor), Vol 1, 6–2 map for determining, Vol 1, 6–3 tables of, Vol 2, B–1 Template
Troubleshooting (cont’d) holding jobs, Vol 1, 14–71 if a device is not recognized by the system, Vol 1, 8–8 jobs that will not execute, Vol 1, 14–71 jobs with characteristic mismatch, Vol 1, 14–73 OPCOM failure, Vol 1, 2–23 pending jobs, Vol 1, 14–71 print jobs with stock mismatch, Vol 1, 14–73 problems deleting a queue, form, or characteristic, Vol 1, 14–74 queue manager, Vol 1, 13–16 queue problems, Vol 1, 14–70 stalled output queue, Vol 1, 14–74 startup problems, Vol 1, 4–16 system dump file for, Vol 2,
UETPHAS00.EXE program, Vol 2, 19–31, 19–32 UETUNAS00.
VCC_MAXSIZE system parameter, Vol 2, 18–11, 18–14 VCC_MAX_CACHE system parameter, Vol 2, 18–5 VCC_MAX_IO_SIZE system parameter, Vol 2, 18–6 VCC_PTES system parameter, Vol 2, 18–12 VCC_READAHEAD system parameter, Vol 2, 18–8 VCRs (vector count registers), Vol 2, 28–4 Vector capability determining availability within a system, Vol 2, 28–9 placing an ACL on, Vol 2, 28–8 Vector-capable, Vol 2, 28–4 Vector consumer determining the identity of, Vol 2, 28–9 managing, Vol 2, 28–6 marginal, Vol 2, 28–8 obtaining inf
VMSINSTAL.
Volume set list file definition, Vol 2, A–9 reserved file, Vol 2, A–9 used by Analyze/Disk_Structure utility, Vol 2, A–9 VOLSET.
Writeboot utility (WRITEBOOT), Vol 1, 4–19 error messages, Vol 1, 4–20 Write cache enabling for tape device, Vol 1, 9–32 Write-enabling a tape, Vol 1, 9–35 Write-lock errors recovering from, Vol 1, 9–76 Write-locking disk volumes, Vol 1, 9–74 tape volumes, Vol 1, 9–51 Write operation See Access types, write Write rings on tape volumes, Vol 1, 9–51 Write-through caching, Vol 2, 18–2 WSDEFAULT process limit choosing a value for batch queues, Vol 1, 14–33 specifying a value for batch queues, Vol 1, 14–22, 14–3
