OpenVMS System Manager's Manual
[Digital logo]
[HR]

OpenVMS System Manager's Manual

November 1996

This manual is a task-oriented guide to managing an OpenVMS system.

Revision/Update Information: This manual supersedes the OpenVMS System Manager's Manual, OpenVMS Alpha Version 6.2 and OpenVMS VAX Version 6.2

Software Version: OpenVMS Alpha Version 7.1 OpenVMS VAX Version 7.1




Digital Equipment Corporation Maynard, Massachusetts

November 1996

Digital Equipment Corporation makes no representations that the use of its products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description.

Possession, use, or copying of the software described in this publication is authorized only pursuant to a valid written license from Digital or an authorized sublicensor.

Digital conducts its business in a manner that conserves the environment and protects the safety and health of its employees, customers, and the community.

© Digital Equipment Corporation 1996. All rights reserved.

The following are trademarks of Digital Equipment Corporation: ALL-IN-1, ATMWORKS, AXP, Bookreader, CI, DBMS, DDCMP DEC, DEC C, DECchip, DECdtm, DECevent, DECintact, DECnet, DECNIS, DECserver, DECwindows, Digital, DNA, GIGAswitch, HSC, HSJ, IAS, InfoServer, LA, LASTport, LAT, LN03, LP27, MicroVAX, MicroVAX II, MSCP, OpenVMS, OpenVMS Cluster, PATHWORKS, POLYCENTER, RSTS, RSX, RZ, StorageWorks, ThinWire, TK, TMSCP, TURBOchannel, VAX, VAX C, VAXcluster, VAXstation, VMS, VT, and the DIGITAL logo.

The following are third-party trademarks:

IEEE and POSIX are registered trademarks of the Institute of Electrical and Electronics Engineers.

Microsoft is a registered trademark, and Windows is a trademark of Microsoft Corporation.

Motif and Open Software Foundation are registered trademarks of the Open Software Foundation, Inc.

Oracle is a registered trademark, and Oracle Rdb is a trademark of Oracle Corporation.

OSI is a registered trademark of CA Management, Inc.

POSTSCRIPT is a registered trademark of Adobe Systems Incorporated.

UNIX is a registered trademark in the United States and other countries, licenses exclusively through X/Open Company Ltd.

Xerox is a registered trademark of Xerox Corporation.

All other trademarks and registered trademarks are the property of their respective holders.

ZK6017

The OpenVMS documentation set is available on CD-ROM.

Contents

Preface

Intended Audience

The intended audience for this manual is OpenVMS system managers.

Document Structure

The OpenVMS System Manager's Manual consists of the following chapters:

For more information about the structure of the OpenVMS System Manager's Manual, see Section 1.1.

Related Documents

For additional information on the Open Systems Software Group (OSSG) products and services, access the Digital OpenVMS World Wide Web site. Use the following URL: 

http://www.openvms.digital.com

The following books are helpful when you use them in conjunction with the OpenVMS System Manager's Manual:

Reader's Comments

Digital welcomes your comments on this manual.

Print or edit the online form SYS$HELP:OPENVMSDOC_COMMENTS.TXT and send us your comments by:
Internet openvmsdoc@zko.mts.dec.com
Fax 603 881-0120, Attention: OSSG Documentation, ZK03-4/U08
Mail OSSG Documentation Group, ZKO3-4/U08
110 Spit Brook Rd.
Nashua, NH 03062-2698

How To Order Additional Documentation

Use the following table to order additional documentation or information. If you need help deciding which documentation best meets your needs, call 800-DIGITAL (800-344-4825).

Conventions

The name of the OpenVMS AXP operating system has been changed to OpenVMS Alpha. Any references to OpenVMS AXP or AXP are synonymous with OpenVMS Alpha or Alpha.

In this manual, every use of DECwindows and DECwindows Motif refers to DECwindows Motif for OpenVMS software.

The following conventions are also 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 or
GOLD 		A sequence such as PF1 x or GOLD x indicates that you must first press and release the key labeled PF1 or GOLD and then press and release another key or a pointing device button.

GOLD key sequences can also have a slash (/), dash (--), or underscore (_) as a delimiter in EVE commands.

[Return] In examples, a key name enclosed in a box indicates that you press a key on the keyboard. (In text, a key name is not enclosed in a box.)
... Horizontal ellipsis points in examples indicate one of the following possibilities:
  • Additional optional arguments in a statement have been omitted.
  • The preceding item or items can be repeated one or more times.
  • Additional parameters, values, or other information can be entered.
.
.
. 		Vertical ellipsis points indicate the omission of items from a code example or command format; the items are omitted because they are not important to the topic being discussed.
( ) In command format descriptions, parentheses indicate that, if you choose more than one option, you must enclose the choices in parentheses.
[ ] In command format descriptions, brackets indicate optional elements. You can choose one, none, or all of the options. (Brackets are not optional, however, in the syntax of a directory name in an OpenVMS file specification or in the syntax of a substring specification in an assignment statement.)
{ } In command format descriptions, braces indicate a required choice of options; you must choose one of the options listed.
text style This text style represents the introduction of a new term or the name of an argument, an attribute, or a reason.

This style is also used to show user input in Bookreader versions of the manual.

italic text Italic text indicates important information, complete titles of manuals, or variables. Variables include information that varies in system output (Internal error number), in command lines (/PRODUCER= name), and in command parameters in text (where device-name contains up to five alphanumeric characters).
UPPERCASE TEXT Uppercase text indicates a command, the name of a routine, the name of a file, or the abbreviation for a system privilege.
Monospace type Monospace type indicates code examples and interactive screen displays.

In the C programming language, monospace type 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.

- 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.
numbers All numbers in text are assumed to be decimal unless otherwise noted. Nondecimal radixes---binary, octal, or hexadecimal---are explicitly indicated.

Chapter 1
Overview of This Manual

Together, the two parts of this manual explain tasks and concepts related to managing a 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:

Information Provided in This Chapter

This chapter describes 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.4

This chapter explains the following concept:
Concept Section
How this manual relates to other system management documentation Section 1.2

1.1 Using the OpenVMS System Manager's Manual

The OpenVMS System Manager's Manual is made up of two parts:

Use these two books to get step-by-step instructions for general system management tasks.

The first page of each chapter in these books provides two tables to help you find information within the chapter.

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.4

The Concept Table

The second table lists the major concepts explained in the chapter. If you want to learn more about an underlying concept, go to the appropriate concept section. For example, the concept table in this chapter lists the following concept:
Concept Section
How this manual relates to other system management documentation Section 1.2

1.2 How This Manual Relates to Other System Management Documentation

This manual is intended to be used as a companion to other OpenVMS system management manuals. The Preface of this manual lists the books you should be prepared to use along with the OpenVMS System Manager's Manual.

1.3 Finding Information About Managing Complex Environments

If you are managing large or complex configurations, you will need additional specialized information. Table 1-1 lists some typical environments and OpenVMS manuals containing specialized information for managing those environments.

Table 1-1 Documentation for Managing Complex Environments
Task Manual
Networked environments DECnet-Plus for OpenVMS Network Management
OpenVMS Cluster environments OpenVMS Cluster Systems and
Guidelines for OpenVMS Cluster Configurations
Migrating from VAX to Alpha environment Migrating an Environment from OpenVMS VAX to OpenVMS Alpha
Performance management OpenVMS Performance Management
System security OpenVMS Guide to System Security

1.4 Finding Information About Managing Small Systems

If you are managing a small standalone system---for example, a desktop workstation---you probably need to perform only basic system management tasks.

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
Task Chapter, Section, or Other Manual
Installing and upgrading the operating system The Upgrade and Installation Manual
Installing layered products Section 3.3
Loading software licenses Section 3.4.2
Booting the system Section 4.1.2.1
Shutting down the system Section 4.8.1
+Using VMSTAILOR to remove files from the system disk Section 5.1
Modifying site-specific startup command procedures Section 5.2
Modifying login command procedures Section 5.3
Setting up user accounts Chapter 6
Backing up workstation disks Section 10.15.7
Backing up and restoring the system disk Section 10.17
Starting the queue manager and creating the queue database Section 12.5
Setting up and starting simple queues Section 13.1.1
Setting system parameters with AUTOGEN Section 14.5
Tuning the system Chapter 16

+VAX specific

Chapter 2
Using OpenVMS System Management Utilities and Tools

This chapter provides general information about system management utilities and tools that are provided with the 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 8.11.2 describes how to use SYSMAN to manage disk quotas. Section 14.7 describes how to use SYSMAN to manage system parameters.

To use system management tools, you can also refer to the following:

Information Provided in This Chapter

This chapter describes the following tasks:
Task Section
Logging in to the SYSTEM account Section 2.2
Using SYSMAN to centralize system management Section 2.3
Using OPCOM to communicate with system users Section 2.4
Using VMSKITBLD.COM to modify a system disk Section 2.5

This chapter explains the following concepts:
Concept Section
OpenVMS system management tools Section 2.1
DCL commands for system management Section 2.1.2
System messages Section 2.1.3
DCL command procedures for system management Section 2.1.4
System management utilities Section 2.1.5
MGRMENU.COM command procedure Section 2.1.6
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

Digital supplies the following software tools to monitor and control system operations and resources:
Tool For More Information
OpenVMS Management Station Section 2.1.1
DIGITAL Command Language (DCL) commands; for example, COPY and MOUNT Section 2.1.2
System messages Section 2.1.3
Command procedures; for example, AUTOGEN.COM and STARTUP.COM Section 2.1.4
System management utilities; for example, the Authorize utility (AUTHORIZE) and the Backup utility (BACKUP) Section 2.1.5
MGRMENU.COM command procedure Section 2.1.6
OPCOM Section 2.4

2.1.1 OpenVMS Management Station

The OpenVMS Management Station is a powerful, Microsoft Windows based management tool for system managers and others who perform account management tasks on OpenVMS systems. OpenVMS Management Station software provides a comprehensive user interface to OpenVMS account management across multiple systems. You can manage multiple systems from a single source.

OpenVMS Management Station software coexists with all of the existing OpenVMS system management utilities. Figure 2-1 shows a sample OpenVMS Management Station screen.

Figure 2-1 Sample OpenVMS Management Station Screen

OpenVMS Management Station addresses the problem of having to use multiple utilities to manage accounts. For example, creating an account usually involves the following steps:

  1. Add a UAF entry
  2. Grant rights identifiers
  3. Create a directory
  4. Create disk quotas
  5. Grant network proxies

These steps require that you use DCL, the Authorize utility, and the DISKQUOTA component of the SYSMAN utility. OpenVMS Management Station provides an easy-to-use interface to this process.

The OpenVMS Management Station consists of two components:

Documentation for the OpenVMS Management Station

The Microsoft Windows help files completely describe features, functions, instructions, and examples of using the OpenVMS Management Station. The OpenVMS Management Station Overview and Release Notes document provides an overview of OpenVMS Management Station and describes how to get started using the software.

Information about installing the OpenVMS Management Station on your Alpha or VAX computer and your PC is located in the following manuals:

2.1.1.1 Managing Resources

OpenVMS Management Station allows you to organize the systems you need to manage in ways that are meaningful to you and your environment, and allows you to manage user accounts on those systems.

You can easily manage user accounts across multiple OpenVMS systems, depending on your needs. The systems might be some of the clusters in a network, all of the systems on one floor of a building, a mix of clusters and nonclustered nodes, and so forth.

You can use OpenVMS Management Station to manage OpenVMS user accounts in a convenient, easy manner. For example, when creating an account on multiple systems, OpenVMS Management Station can add a user authorization file (UAF) entry, grant rights identifiers, create an OpenVMS directory, set a disk quota, set up OpenVMS Mail characteristics, and so forth, for each instance of the account.

OpenVMS Management Station manages the following OpenVMS resources:

2.1.1.2 Managing Operations

The OpenVMS Management Station supports the following account management operations:

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).

The general format of a DCL command is as follows: 

command-name[/qualifier[,...]] [parameter[,...]] [/qualifier[,...]]

Because a command can be continued on more than one line, the term command string is used to define the entire command. A command string is the complete specification of a command, including the command name, command qualifiers, parameters, and parameter qualifiers.

For complete descriptions of each DCL command, see the online DCL help or the OpenVMS DCL Dictionary. If you are not familiar with DCL command syntax, see the OpenVMS User's Manual.

2.1.3 System Messages

When you enter commands in DCL or in utilities, the system returns messages to help you understand the result of each command. System messages can indicate the following:

At times, you might need to interpret a system message, for example, to find out how to recover from a warning or failure. The Help Message utility allows you and system users to quickly access online descriptions of system messages from the DCL prompt.

For more information about the Help Message utility, see the OpenVMS System Messages: Companion Guide for Help Message Users. In addition, the OpenVMS System Messages and Recovery Procedures Reference Manual provides detailed descriptions of system messages.

2.1.4 DCL Command Procedures

You can use command procedures to efficiently perform routine tasks. A command procedure is a file containing DCL commands and, optionally, data used by those DCL commands. When you execute a command procedure, the system reads the file and executes the commands it contains. This eliminates the need for you to enter each command interactively. You can create command procedures to automate some of the routine system management tasks specific to your site.

A simple command procedure can contain a sequence of commands that you use frequently. For example, you could include the following commands in a command procedure called GO_WORK.COM: 

$ SET DEFAULT [PERRY.WORK] 
$ DIRECTORY 
$ EXIT

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 high-level programming language. For more information on creating command procedures, see the OpenVMS User's Manual.

2.1.4.1 Executing Command Procedures in Batch Mode

You can execute command procedures in batch mode by submitting the procedure to a batch queue. When resources are available, the system creates a batch process to execute the commands in the procedure. Usually, processes running in batch mode execute at a lower process priority to avoid competing with interactive users for system resources.

You might execute a command procedure in batch mode for the following reasons:

A batch-oriented command procedure can include a command to resubmit itself to a batch queue, thereby repetitively performing the task with no user intervention. For example, you might create a batch-oriented command procedure to run the Analyze/Disk_Structure utility (ANALYZE/DISK_STRUCTURE) to report disk errors. If you include a command to resubmit the procedure to a batch queue, the procedure will automatically execute when scheduled, unless errors cause the procedure to fail. The following is a simple example of this kind of command procedure, named SYSTEM-DAILY.COM: 

$ SET NOON 
$! Resubmit this procedure to run again tomorrow. 
$! 
$ SUBMIT/KEEP/NOPRINT/QUEUE=SYS$BATCH/AFTER="TOMORROW+1:00"/USER=SYSTEM - 
  SYS$MANAGER:SYSTEM-DAILY.COM; 
$! 
$! Purge the log files 
$ PURGE/KEEP=7 SYS$MANAGER:SYSTEM-DAILY.LOG 
$! 
$! Analyze public disks 
$! 
$ ANALYZE/DISK/LIST=SYS$MANAGER:WORK1.LIS; WORK1: 
$ ANALYZE/DISK/LIST=SYS$MANAGER:WORK2.LIS; WORK2: 
$! 
$! Print listings 
$! 
$ PRINT/QUEUE=SYS$PRINT SYS$MANAGER:WORK1.LIS;,SYS$MANAGER:WORK2.LIS; 
$ EXIT

2.1.4.2 Using Digital-Supplied Command Procedures for System Management

Digital 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.COM The system uses this command procedure to automatically perform certain tasks that are required to start up an OpenVMS system. This procedure is executed when the system boots. Do not modify this command procedure.
SYS$STARTUP:SYSTARTUP_VMS.COM STARTUP.COM executes this procedure when the system boots. Add commands to this procedure to perform site-specific tasks each time the system boots.
SYS$SYSTEM:SHUTDOWN.COM Use to shut down the system in an orderly fashion.
SYS$UPDATE:AUTOGEN.COM Use to automatically set system parameters and page, swap, and dump file sizes to values appropriate for the system configuration and work load.
SYS$UPDATE:VMSINSTAL.COM Use to install software on a running system.

2.1.5 System Management Utilities

With the operating system, Digital supplies a number of system management utilities to help perform system management tasks. A system management utility is a program that performs a set of related operations. For example, the Mount utility (MOUNT) makes disks and tapes available to the system, and the Backup utility (BACKUP) saves and restores files.

Next | Contents | [Home] | [Comments] | [Ordering info] | [Help]

[HR] 

  6017P.HTM
  OSSG Documentation
  22-NOV-1996 14:21:15.82

Copyright © Digital Equipment Corporation 1996. All Rights Reserved.

Legal