OpenVMS User's Manual

Updated: 11 December 1998

Order Number: AA--PV5JD--TK

January 1999

This manual describes how to use the OpenVMS operating system. The information contained in this manual is intended for all OpenVMS users and is applicable to all computers running the OpenVMS operating system.

Revision/Update Information: This manual supersedes the OpenVMS User's Manual, Version 7.1.

Software Version: OpenVMS Alpha Version 7.2
OpenVMS VAX Version 7.2

Compaq Computer Corporation
Houston, Texas

January 1999

Compaq Computer 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 Compaq or an authorized sublicensor.

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

The following are trademarks of Compaq Computer Corporation: Alpha, Bookreader, Compaq, DECdirect, DECnet, DECprint, DECspell, DECwriter, DIGITAL, EDT, OpenVMS, OpenVMS RMS, PrintServer, VAX, VAXcluster, VAX DOCUMENT, VMS, and the Compaq logo.

The following are third-party trademarks:

Adobe, Adobe Illustrator, Display POSTSCRIPT, and POSTSCRIPT are registered trademarks of Adobe Systems Incorporated.

BITSTREAM is a registered trademark of Bitstream, Inc.

COMPAQ is a registered trademark of COMPAQ Computer Corporation.

Microsoft, MS, and MS--DOS are registered trademarks of Microsoft Corporation.

Motif, OSF, OSF/1, and OSF/Motif are registered trademarks, and Open Software Foundation is a trademark of the Open Software Foundation, Inc.

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

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

ZK6489

The OpenVMS documentation set is available on CD-ROM.

Contents Index

Preface

Intended Audience

This manual is intended for all users of the OpenVMS operating system.

A system manager performs the administrative tasks that create and maintain an efficient computing environment. If you are a system manager or want to understand system management concepts and procedures, refer to the OpenVMS System Manager's Manual.

Document Structure

This manual contains 19 chapters, 4 appendixes, and a glossary. Each chapter describes concepts and procedures for performing computing tasks. Basic information is presented first within each chapter; more complex concepts and procedures are presented last.

Getting Started

Refer to the following chapters to help you get started using the OpenVMS operating system:

Chapter 1
Introduction: OpenVMS Concepts and Definitions describes basic concepts about the OpenVMS operating system and its components. The chapter serves as an introduction to the rest of the manual.
Chapter 2
Getting Started: Interacting with the OpenVMS Operating System describes how to log in and log out of the system, how to change your password, and how to get help.
Chapter 3
The DIGITAL Command Language: Interacting with the System describes how to use the DIGITAL Command Language (DCL). It includes a summary of keypad key combinations that let you enter and edit DCL commands.
Chapter 4
Files: Storing Information describes files and how you can use them to store information. It includes examples for creating, copying, renaming, displaying, deleting, protecting, and printing files.
Chapter 5
Directories: Organizing and Managing Files describes how to use directories to organize and manage files.

Communicating with Other Users

Refer to the following chapters to learn about communicating with other users:

Chapter 6
Mail: Communicating with Other Users describes how to use the Mail utility (MAIL) to communicate with other users on your system or on any other computer that is connected to your system with the DECnet for OpenVMS network. The chapter includes a sample mail message; step-by-step instructions for reading, sending, replying to, forwarding, and organizing mail messages; a summary of Mail commands; and instructions on how to use the MIME utility.
Chapter 7
Phone: Communicating with Other Users describes how to use the Phone utility (PHONE) to communicate with other users on your system or on any other computer that is connected to your system with the DECnet for OpenVMS network.

Manipulating Text and Records

Refer to the following chapters to learn about text processing and record sorting:

Chapter 8
Editing Text Files: Using EVE describes EVE, an interactive text editor that is included with the OpenVMS operating system. The chapter describes how to use EVE to create and edit new files or to edit existing files. It includes summaries of EVE commands.
Chapter 9
Editing Text Files: Using EDT describes EDT, an interactive text editor that preceded EVE and is still included with the OpenVMS operating system. The chapter describes how to begin and end an EDT session, how to enter EDT commands, and how to get help in EDT. It includes a summary of EDT commands.
Chapter 10
DIGITAL Standard Runoff (DSR): Formatting Text Files describes the DIGITAL Standard Runoff (DSR) text-formatting facility. The chapter includes a summary of DSR commands.
Chapter 11
Sort/Merge Utility: Sorting and Merging Files describes how to use the Sort/Merge utility (SORT/MERGE) to sort records from one or more input files or to merge files that have been sorted. The chapter includes a summary of Sort/Merge command qualifiers.

Using Devices

Refer to the following chapter to learn about devices:

Chapter 12
Devices: Using Private Tapes and Disks describes how to reserve tapes or disks for private use. Unlike devices that are shared by a group of users, private devices might not be set up and maintained by a system manager.

Logical Names and Symbols

Refer to the following chapters to learn about logical names and symbols:

Chapter 13
Logical Names: Defining Names for Devices and Files describes how to create and use logical names to represent files, directories, and devices. The chapter also summarizes the logical names created by the system.
Chapter 14
Programming with DCL: Defining Symbols, Commands, and Expressions describes how to use symbols to represent commands, character strings, and numeric data. The chapter also describes how to combine symbols into expressions to manipulate the values that the symbols represent.

Programming

Refer to the following chapters to learn about writing programs and using programming functions:

Chapter 15
Programming with DCL: Introduction to Command Procedures describes basic techinques used in writing command procedures, which are files that contain DCL commands and data lines used by DCL commands.
Chapter 16
Advanced Programming with DCL describes advanced techniques used in writing command procedures. This chapter also describes how to use the PIPE command interactively and within command procedures.
Chapter 17
Lexical Functions: Obtaining and Manipulating Information describes how to use lexical functions within a command procedure to get information about your process or the system environment.

Managing Processes

Refer to the following chapter to learn about managing processes:

Chapter 18
Processes and Batch Jobs: Using the OpenVMS Environment describes processes, which are environments created by the OpenVMS operating system that let you interact with the system. The chapter describes how and when to use subprocesses, programs, and batch jobs.

Ensuring Security

Refer to the following chapter to learn about security:

Chapter 19
Security: Controlling Access to Resources describes general security issues such as controlling access to protected objects and accessing data on remote systems.

Reference Sections

The following information is provided for reference:

Appendix A
Customizing EVE contains information on customizing your EVE editing environment.
Appendix B
Character Sets describes the DEC Multinational character set and the DCL character set.
Appendix C
Annotated Command Procedures contains complete command procedures that demonstrate the concepts and techniques discussed in Chapters 15, 16, and 17.
Appendix D
Terminal Keys describes how the OpenVMS operating system responds when various keys and control characters are pressed on an LK201 keyboard (VT200 series and later terminals, and workstations) or on a VT100 series terminal.
Glossary
The Glossary provides a list of terms used in this manual. Glossary terms are highlighted when first used in text.

Reader's Comments

Compaq 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 884-0120, Attention: OSSG Documentation, ZKO3-4/U08

Mail Compaq Computer Corporation
OSSG Documentation Group, ZKO3-4/U08
110 Spit Brook Rd.
Nashua, NH 03062-2698

How To Order Additional Documentation

Use the following World Wide Web address to order additional documentation:

http://www.openvms.digital.com:81/

If you need help deciding which documentation best meets your needs, call 800-DIGITAL (800-344-4825).

Conventions

In this manual, any reference to OpenVMS is synonymous with DIGITAL OpenVMS.

VMScluster systems are now referred to as OpenVMS Cluster systems. Unless otherwise specified, references to OpenVMS Clusters or clusters in this document are synonymous with VMSclusters.

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 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. (In text, a key name is not enclosed in a box.)
In the HTML version of this document, this convention appears as brackets, rather than a box.

... A horizontal ellipsis 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.

.
.
. A vertical ellipsis 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 you must enclose the options in parentheses if you choose more than one.

[ ] 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, vertical bars separating items inside brackets indicate that you choose one, none, or more than one of the options.

{ } In command format descriptions, braces indicate required elements; you must choose one of the options listed.

bold text This text style represents the introduction of a new term or the name of an argument, an attribute, or a reason.

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 dd represents the predefined code for the device type).

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 text
Monospace text indicates code examples and interactive screen displays.
In the C programming language, monospace 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.

- 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
Introduction: OpenVMS Concepts and Definitions

OpenVMS is an interactive virtual memory operating system. While you are logged in to the computer, you and the system conduct a dialogue using the DIGITAL Command Language (DCL). You use DCL by entering commands, which the system reads and translates. You enter a command by typing it from your keyboard and pressing the Return key; the system responds by executing the command or by displaying an error message on the screen if it cannot interpret what you entered.

This chapter describes basic concepts about the OpenVMS operating system and its components. It includes introductory information about the following topics:

Logging in to the system
Networks
DIGITAL Command Language (DCL)
Files and directories
OpenVMS utilities
Devices
Logical names
Symbols
Command procedures
Lexical functions
Processes and programs
System security

Differences in Your Local Environment

Note that this manual covers standard DCL commands only. System managers at your site may tailor your system to support the local environment. They might decide to:

Use a different command language interpreter
Change the default action of some standard DCL commands so that they do not reflect what is described in the OpenVMS documentation
Disable some DCL commands
Alter some system defaults, such as the DCL prompt
Configure an environment with Extended File Specifications

For additional information about the commands discussed in this chapter, refer to:

The OpenVMS DCL Dictionary or online help, for complete information on DCL commands, lexical functions, qualifiers, and syntax. See Section 2.10 in this manual or enter the HELP command at the DCL prompt for information about obtaining online help.

For additional information about Extended File Specifications, refer to:

The OpenVMS Guide to Extended File Specifications, which contains complete information about Extended File Specifications, features and benefits, on-disk structures, character sets available in such an environment, extended file names, and directory structures.

1.1 Logging In to the System

Logging in consists of gaining access to the system and identifying yourself as an authorized user. When you log in, the system creates an environment from which you can enter commands. This environment is called your process.

Chapter 2 describes how to log in to and out of the system.

To interact with the operating system, you must log in to a user account. An account is a name or number that identifies you to the system when you log in. That name or number tells the system where your files are stored and the type of access you have to other files.

Your system manager (or whoever authorizes system use at your installation) usually sets up accounts and grants privileges according to your needs. The type of access rights and privileges enabled for your account determine whether you have access to files, images, or utilities that might affect system performance or other users.

1.1.1 Access Requirements

To access your account, you need to enter your user name and password. Your system manager usually provides you with your user name and initial password. Your user name identifies you to the system and distinguishes you from other users. In many cases, a user name is your first or last name. Your password is for your protection. If you maintain its secrecy, other users cannot use system resources under your user name.

1.2 Networks

When computer systems are linked together, they form a network. Operating systems in a DECnet for OpenVMS network are able to communicate with each other and share information and resources. Each system in a network is called a network node and is identified by a unique node name.

1.2.1 Network Nodes

When you are logged in to a network node, you can communicate with other nodes in the network. The node at which you are logged in is called the local node; other nodes on the network are called remote nodes. If you have access to an account on a remote node, you can log in to that account from your local node and perform tasks on that node while remaining connected to your local node.

Chapter 2 describes how to log in to a remote node. Additional tasks you can perform on remote nodes are described in the appropriate chapters of this manual.

1.2.2 Executing Programs over Networks

Because of support provided by DECnet software, programs can execute across the network as if they were executing locally. Because DECnet software is integrated within the operating system, it is easy to write programs that access remote files. To access a remote file in an application program, you need only include the name of the remote node and any required access control information in the file specification.

Task-to-task communications, a feature common to all DECnet implementations, allows two application programs running on the same or different operating systems to communicate with each other regardless of the programming languages used. Examples of network applications are distributed processing applications, transaction processing applications, and applications providing connection to servers.

Note

In the examples of remote operations in this manual, proxy accounts enable users to perform operations on remote systems. Proxy accounts are one way users can access remote systems. For additional ways to access remote systems, see the OpenVMS System Manager's Manual.

Contents

Index

Legal

 
6489PRO.HTML

Internet	openvmsdoc@zko.mts.dec.com
Fax	603 884-0120, Attention: OSSG Documentation, ZKO3-4/U08
Mail	Compaq Computer Corporation OSSG Documentation Group, ZKO3-4/U08 110 Spit Brook Rd. Nashua, NH 03062-2698

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. (In text, a key name is not enclosed in a box.) In the HTML version of this document, this convention appears as brackets, rather than a box.
...	A horizontal ellipsis 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.
. . .	A vertical ellipsis 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 you must enclose the options in parentheses if you choose more than one.
[ ]	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, vertical bars separating items inside brackets indicate that you choose one, none, or more than one of the options.
{ }	In command format descriptions, braces indicate required elements; you must choose one of the options listed.
bold text	This text style represents the introduction of a new term or the name of an argument, an attribute, or a reason.
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 dd represents the predefined code for the device type).
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 text	Monospace text indicates code examples and interactive screen displays. In the C programming language, monospace 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.
-	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.