2.1 Understanding OpenVMS System Management Tools
  Digital supplies the following software tools to monitor and
  control system operations and resources:

                                                                                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
  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 pro-
  vides a comprehensive user interface to OpenVMS account
  management across multiple systems. You can manage mul-
  tiple systems from a single source. OpenVMS Management
  Station coexists with all of the existing OpenVMS system
  management utilities.

  OpenVMS Management Station addresses the problem of
  having to use multiple utilities to manage accounts. For ex-
  ample, 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 util-
  ity, and the DISKQUOTA component of the Sysman utility.
  OpenVMS Management Station provides an easy-to-use
  interface to this process.

  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.

  Documentation for OpenVMS Management Station
  The Microsoft Windows help files completely describe fea-
  tures, 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 OpenVMS Management Station
  on your Alpha or VAX computer and your PC is located in
  the following manuals:

  .
        OpenVMS Alpha Version 6.2 Upgrade and Installation
        Manual
  .
        OpenVMS VAX Version 6.2 Upgrade and Installation
        Manual

  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 sys-
  tems on a given 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 autho-
  rization 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:

  .
        The SYSUAF.DAT user authorization file
  .
        The RIGHTSLIST.DAT user rights file
  .
        The network proxy database
  .
        Account login-directory trees
  .
        User account disk quotas
  .
        The OpenVMS Mail VMSMAIL_PROFILE.DATA file

  2.1.1.2 Managing Operations
  OpenVMS Management Station supports the following ac-
  count management operations:

  .
        Creating user accounts
  .
        Modify user accounts (any aspect)
  .
        Deleting user accounts
  .
        Renaming user accounts
  .
        Displaying user account attributes

  2.1.2 DCL Commands
  You perform many system management tasks by entering
  DCL (DIGITAL Command Language) commands. For ex-
  ample, you enter the DCL command MOUNT to make disks
  and tapes available to the system. Most of the DCL com-
  mands used by system managers require special privileges
  (such as OPER privilege). See the OpenVMS DCL Dictionary
  or DCL Help for the required privileges and syntax for each
  command.

  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 on-
  line 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:

  .
        Successful completion of a command
  .
        Information about the effect of the command
  .
        Warning about the effect of the command
  .
        Failure to successfully complete the command

  At times, you might need to interpret a system message, for
  example, to find out how to recover from a warning or fail-
  ure. 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 contain-
  ing 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 in-
  teractively. 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 in-
  stead of a high-level programming language. For more
  information on creating command procedures, see the
  OpenVMS User's Manual .

  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:

  .
        To automate a task
  .
        To process work at a lower scheduling priority, so as not
        to compete with interactive users for system resources
  .
        To perform a task during off hours, such as at night or
        on weekends
  .
        To allow an operation to continue without having a ter-
        minal logged in, thereby increasing the security of the
        system

  A batch-oriented command procedure can include a com-
  mand to resubmit itself to a batch queue, thereby repetitively
  performing the task with no user intervention. For exam-
  ple, you might create a batch-oriented command procedure
  to run the Analyze/Disk_Structure utility to report disk er-
  rors. 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

  Digital-Supplied Command Procedures for System Management
  Digital provides several command procedures that you can
  use when managing a system. Table 2-1 lists some com-
  monly used command procedures.

  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 pro-
  gram that performs a set of related operations. For example,
  you use the Mount utility (MOUNT) to make disks and
  tapes available to the system, and you use the Backup utility
  (BACKUP) to save and restore files.

  Most system management utilities require special privileges.
  Generally, you run these utilities from the SYSTEM account,
  which has all privileges by default. Section 2.2 describes
  logging in to the SYSTEM account.

  You invoke some utilities using the following command
  format:
  RUN SYS$SYSTEM:utility_name

  To invoke other utilities, such as MOUNT and ANALYZE
  /DISK_STRUCTURE, you enter a DCL command. For
  example:
  $ ANALYZE/DISK_STRUCTURE

  For information on invoking utilities and the commands
  you can use in these utilities, see the OpenVMS System
  Management Utilities Reference Manual .

  Table 2-2 lists the system management utilities and their
  purposes. This manual describes how to use most of these
  utilities. For detailed information on utility commands and
  qualifiers, see the OpenVMS System Management Utilities
  Reference Manual .

  This manual does not describe the following utilities in detail:

  2.1.6 MGRMENU.COM Command Procedure
  To help you perform basic system management tasks, Digital
  provides a command procedure named SYS$EXAMPLES:MGRMENU.COM.
  This procedure displays a menu that you can use to perform
  the following tasks:

  .
        Add a user account
  .
        Build a standalone BACKUP kit
  .
        Shut down your system

  You can use this command procedure as is, or modify it to
  serve your own site-specific needs. If you modify this pro-
  cedure, Digital recommends you first copy the procedure to
  another directory (for example, SYS$MANAGER), so that an
  original version of MGRMENU.COM is always available in
  the SYS$EXAMPLES directory.

  To see and use the menu, enter the following command:
  $ @SYS$EXAMPLES:MGRMENU