[next] [previous] [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:


  .
        
Chapter 1, Overview of This Manual
  .
        Chapter 2, Using OpenVMS System Management
        Utilities and Tools
  .
        Chapter 3, Installing, Upgrading, and Updating Software
  .
        Chapter 4, Starting Up and Shutting Down the System
  .
        Chapter 5, Customizing the Operating System
  .
        Chapter 6, Managing User Accounts
  .
        Chapter 7, Managing Peripheral Devices
  .
        Chapter 8, Managing Storage Media
  .
        Chapter 9, Using Files and Directories
  .
        Chapter 10, Using BACKUP
  .
        Chapter 11, Security Considerations
  .
        Chapter 12, Managing the Queue Manager and Queue
        Database
  .
        Chapter 13, Managing Batch and Print Queues
  .
        Chapter 14, Managing System Parameters
  .
        Chapter 15, Managing System Page, Swap, and Dump
        Files
  .
        Chapter 16, Performance Considerations
  .
        Chapter 17, Testing the System with UETP
  .
        Chapter 18, Getting Information About the System
  .
        Chapter 19, Tracking Resource Use
  .
        Chapter 20, VMScluster Considerations
  .
        Chapter 21, Network Considerations
  .
        Chapter 22, Managing the Local Area Network (LAN)
        Software
  .
        Chapter 23, Managing InfoServer Systems
  .
        Chapter 24, Managing the LAT Software
  .
        Chapter 25, Managing DECdtm Services
  .
        Chapter 26, Managing Special Processing Environments
  .
        Appendix A, Files-11 Disk Structure
  .
        Appendix B, Tables of Time Differential Factors (TDFs)
  .
        Glossary

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

  The following books are helpful when you use them 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

  .
        Guide to OpenVMS Performance Management

  .
        VMScluster Systems for OpenVMS

  .
        The manuals in the networking kit of the OpenVMS
        Standard Documentation Set:

        - DECnet for OpenVMS Guide to Networking
        - DECnet for OpenVMS Networking Manual
        - DECnet for OpenVMS Network Management Utilities
  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.

  The following conventions are used to identify information
  specific to OpenVMS Alpha or to OpenVMS VAX:
                            The Alpha icon denotes the beginning of
                            information specific to OpenVMS Alpha.
                            The VAX icon denotes the beginning of
                            information specific to OpenVMS VAX.
                            The diamond symbol denotes the end of a
                            section of information specific to OpenVMS
                            Alpha or to OpenVMS VAX.

  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 indi-
                                cates 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, parenthe-
                                ses indicate that, if you choose more than
                                one option, you must enclose the choices in
                                parentheses.
  [ ] In command format descriptions, brackets
                                indicate optional elem 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 in-
                                dicate a required choice of options; you must
                                choose one of the options listed.
  boldface text
Boldface text represents the introduction of a
                                new term or the name of an argument, an at-
                                tribute, or a reason (user action that triggers
                                a callback).
                                Boldface text 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 messages (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.
  struct Monospace type in text identifies the fol-
                                lowing C programming language elements:
                                keywords, the names of independently com-
                                piled external functions and files, syntax
                                summaries, and references to variables or
                                identifiers introduced in an example.
  - A hyphen in code examples indicates that ad-
                                ditional arguments to the request are provided
                                on the line that follows.
  numbers All numbers in text are assumed to be dec-
                                imal unless otherwise noted. Nondecimal
                                radixes-binary, octal, or hexadecimal-are
                                explicitly indicated.