|
NIA #11 - VMS System Managers Manual 1
NOTICE: TO ALL CONCERNED Certain text files and messages contained on this site deal with activities and devices which would be in violation of various Federal, State, and local laws if actually carried out or constructed. The webmasters of this site do not advocate the breaking of any law. Our text files and message bases are for informational purposes only. We recommend that you contact your local law enforcement officials before undertaking any project based upon any information obtained from this or any other web site. We do not guarantee that any of the information contained on this system is correct, workable, or factual. We are not responsible for, nor do we assume any liability for, damages resulting from the use of any information on this site.
ZDDDDDDDDDDDDDDDDDD? IMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM; ZDDDDDDDDDDDDDDDDDD?
3 Founded By: 3 : Network Information Access : 3 Founded By: 3
3 Guardian Of Time 3D: 02APR90 :D3 Guardian Of Time 3
3 Judge Dredd 3 : Guardian Of Time : 3 Judge Dredd 3
@DDDDDDDDBDDDDDDDDDY : File 11 : @DDDDDDDDDBDDDDDDDDY
3 HMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM< 3
3 IMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM; 3
@DDDDDDDDDDD6 VMS System Manager's Manual :DDDDDDDDDDDDY
: Chapter 1 :
HMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM<
PREFACE AND CHAPTER 1
APRIL 1988
This Manual provides the basic concepts and procedures for VMS system
management; it is especially intended for managers of small clusters and
systems.
PREFACE
The VMS SYSTEM MANAGER'S MANUAL provides system managers with the concepts and
procedures needed to manage daily operations on a VMS system. This manual
contains a subset of information included in the Extended VMS System
managements documentation subkit.
INTENDED AUDIENCE
This manual can be used by anyone who performs the functions of a system
manager or operator on a VMS system. It is especially intended for managers of
small clusters and systems.
Document Structure
The VMS SYSTEM MANAGER'S MANUAL is divided into two main sections: System
Management Tasks and Reference.
Part I ( Chapters 1 through 11 ) are task-oriented descriptions of the
functions that are generally assigned to system managers. Part II, the
Reference section, documents the utilities that serve as system management
tools on a VMS system.
Chapter 1 describes each chapter in some detail. REad Chapter 1 to determine
which of the remaining chapters in the book are appropriate for your needs.
The Reference section contains quick reference information on the VMS system
management utilities. Each utility chapter includes a usage summary and a
subset of frequently use commands and qualifiers.
The Reference section includes the following utilities:
: Accounting Utility
: Analyze/Disk_Structure Utility
: Authorize Utility
: Backup Utility
: Bad Block Locator Utility
: Error Log Utility
: Exchange Utility
: Install Utility
: LAT Control Program Utility
: Mount Utility
: Network Control Program ( NCP ) Utility
: SYSGEN Utility
: SYSMAN Utility
: Terminal Fallback Utility
ASSOCIATED DOCUMENTS
In the VMS Base documentation set:
( The extended VMS documentation set is the complete set of software manuals
for the VMS operating system. For information about ordering any of the
manuals in the extended VMS documentation set, see the OVERVIEW OF VMS
DOCUMENTATION or contact your DIGITAL representative. )
: For general background information about the system, see the INTRODUCTION
TO VMS.
: For more information on setting up the system for operation, see the GUIDE
TO SETTING UP A VMS SYSTEM.
: For more information on maintaining the system, see the GUIDE TO MAINTAINING
A VMS SYSTEM.
: For information on security management, see the GUIDE TO VMS SYSTEM SECURITY.
: For more information on networking, see the GUIDE TO DECNET-VAX NETWORKING.
: For more information on VMS clusters, see the VMS VAXCLUSTER MANUAL.
: For more information on performance tuning, see the GUIDE TO VMS PERFORMANCE
MANAGEMENT.
: For more information on utilities, see the individual VMS utility manuals.
: For complete descriptions of DCL commands, see the VMS DCL DICTIONARY
: For descriptions of system messages and suggested user action, see the VMS
SYSTEM MESSAGES AND RECOVERY PROCEDURES REFERENCE VOLUME.
Other related documentation:
: For information on system installation and other processor-specific
procedures, se your VAX processor installation and operations guide.
: If you have purchased the volume shadowing option, see the VAX VOLUME
SHADOWING MANUAL for information on creating and maintaining volumes using
volume shadowing.
: If you have purchases the RMS journaling option, see the VAX RMS JOURNALING
MANUAL for information on RMS journaling.
: For hardware operating instructions, see the appropriate hardware owner's
manual.
The VMS operating system and the other software products that run on your
computer provide you and the other users on your system with a wide range of
computing capabilities. In order to create and maintain a proper and
efficient computing environment, certain administrative tasks must be
undertaken. These tasks are called SYSTEM MANAGEMENT, and they include the
following:
: Setting up the system
: Giving individual users access to the system
: Installing software (and software updates)
: Managing acceptable performance levels
: Preventing the loss of important information that you keep on line
: Making sure that the system is secure
: Handling media (such as disks/magnetic tapes)
: setting up the software to allow for printers and for batch jobs
: Setting up a cluster
: Setting up a network
As system manager, you may need to do some of these tasks only once (for
example, setting up software to allow for printers or batch jobs, or setting
up a network); others are done on a continuing basis (for example, maintaining
system security and preventing the loss of data). At some sites, one or more
people are designated as SYSTEM MANAGERS, and other individuals are designated
as OPERATORS. In these cases, operators are responsible for tasks such as
physically mounting magnetic tapes and disks, monitoring printers, responding
to emergencies or security alarms, and maintaining system log files.
Not all of the tasks described in this manual may be necessary for your site.
This chapter provides an overview of the information that this manual
contains. You should read this introductory chapter to determine which parts
of the manual may be applicable to your site.
<NOTE: I overlooked section 1.1 because all it does is say that system >
< Managers should use this chapter / Operators should use this Chapter >
< there was NO useful information on that part...Guardian of Time >
1.2 SYSTEM MANAGEMENT CONCEPTS AND TERMS
Some concepts and terms are used frequently in system management, and you
should become familiar with them. The following terms and concepts are used
both in the context of everyday general use in a VMS system and in the context
of system management; they are described in the VMS GENERAL USER'S MANUAL:
: Accounts and directories
: Command Procedures
: Digital Command Language (DCL)
The following concepts and terms apply primarily to system management:
: SYSTEM account and [SYSMGR] directory
The SYSTEM account is reserved for use by the system manager. When you
are logged into the SYSTEM ACCOUNT, your default directory (Which is also
reserved for the system manager) is SYS$SYSROOT:[SYSMGR].
Always be careful when you are logged into the SYSTEM account. When you
are logged into the SYSTEM account, all privileges are enabled, by default.
You need these privileges to perform many system management tasks; however,
they can also produce unwanted or even destructive results if you use them
carelessly.
: CONSOLE (OPERATOR'S) TERMINAL
You can perform most system management tasks from any terminal that is
connected to the processor (or the cluster). However, certain tasks such
as bootstrapping the system and communicating with the VAX processor's
console subsystem must be performed at a special terminal called the
CONSOLE TERMINAL.
The console terminal, which always has the designation OPA0, is also
usually designated as the OPERATOR'S TERMINAL. You use the operator's
terminal to send messages to system users and respond to user requests,
using the operator communication process (OPCOM).
[OTHER WORLD BBS]
|
|
