MULTICS TECHNICAL BULLETIN MTB-656, Revision 1
To: MTB Distribution
From: Karen MacKenzie
Date: 08/08/84
Subject: Reorganizing/Rewriting Administration and Maintenance
Documentation
This MTB proposes a plan for reorganizing and rewriting our
administration and maintenance documentation. It explains which
manuals should be considered as part of such a
reorganizing/rewriting effort and what our goals should be for
improving those manuals. It proposes a reorganization which
attempts to meet those goals and talks about how we can make the
reorganization happen. It also offers detailed outlines of the
proposed new manuals.
Revision 1 of this MTB contains all of the changes which |
were agreed to during its "design review." This design review |
took the form of a discussion held in the SysAdmin_doc forum |
(>udd>Pubs>km>mtgs>sad on System M). The changes include general |
ones to the proposed reorganization of the manuals, and detailed |
ones to the proposed outlines for the new manuals. A summary of |
the forum discussion is available in MTB 669. |
Comments on this MTB should be sent to the author:
via Multics mail:
KMacKenzie.Pubs on System M
or via telephone:
(HVN) 492-9308 or (617) 492-9308
_________________________________________________________________
Multics Project internal working documentation.
Not to be reproduced or distributed outside the Multics Project.
MTB-656, Revision 1
INTRODUCTION
Most of us agree that our administration and maintenance
documentation desperately needs to be improved. This has been
true for years, but right now we have an especially pressing
reason to do something about it. With the advent of the new
Multics business plan, especially the Flower Project, we expect
to start selling a lot more Multics systems. In the past, we've
been able to send a Multics expert to each new site, to help our
customers learn to perform the necessary administration and
maintenance tasks. In the future, when we're selling more than
100 systems a year, we won't be able to do this. Our customers
will have to figure things out for themselves. To make this
possible, we'll have to provide them with documentation they can
understand and use. Thus, it's become crucial for us to get our
administration and maintenance manuals reorganized and rewritten
in the best possible way.
This MTB is in some respects an extension of two earlier
MTBs published by members of the documentation unit, MTBs 544 and
577. So I'll begin by summarizing them. I'll go on to discuss
which manuals I'm considering as part of this proposed
reorganization. I'll lay out our goals for administration and
maintenance documentation and propose a reorganization which
attempts to meet these goals. I'll then discuss the proposal in
more detail. Finally, I'll talk about how we can make this
reorganization happen.
BACKGROUND
MTB 544 was entitled "Rewriting the Multics Operators'
Handbook." It began by discussing the shortcomings of the MOH --
the audience not being clearly identified, the material not being
sensibly organized, the language not being friendly, active, or
direct. It went on to propose a solution which involved
converting the MOH to a straight reference/commands manual and
creating two new manuals -- an Operator's Guide and a System
Maintainer's Guide. The MTB presented an outline for the
Operator's Guide and stated that an outline for the System
Maintainer's Guide would be presented in a future MTB.
MTB 577 was entitled "Rewriting/Organizing the Multics
Administrators' Manuals." It discussed the shortcomings of the
SAM, which were seen to be much the same as those plaguing the
MTB-656, Revision 1
MOH -- audience problems, organization problems, language
problems. The solution it proposed involved the development of
three manuals -- a System Manager's Guide, a System
Administrator's Guide, and a reference/commands manual. The MTB
presented an outline for the System Manager's Guide.
All of the proposed Guides were intended to be cookbooks,
real "how to" manuals. So far, the Operator's Guide is the only
one of the proposed manuals to actually have been written. It's
available as part of MR10.2, with the order number GB61.
TERRITORY
In this MTB, I'm expanding the "territory" under
consideration to include all of our administration and
maintenance manuals, not just the MOH and the SAM. Specifically,
the manuals I'm considering are:
AM81 Multics Operators' Handbook (MOH)
AK50 MAM -- System (SAM)
AK51 MAM -- Project (PAM)
AS68 MAM -- Registration & Accounting (RAM)
CC74 MAM -- Resource Control
CC75 MAM -- Communications
CC34 Multics Bulk Input/Output
AN52 Multics System Metering
There are also a number of other manuals which may be seen
as fitting into the realm of administration and maintenance, but
which I'm not considering in this MTB. Among them are:
CG18 Remote Batch Facility
CY73 IMFT Reference Manual
GB60 HASP Service and Utility Manual
CJ97 Page Processing System Utility Manual
The main reason I've chosen not to consider these manuals at
this time is because they either document obscure parts of the
system or they document PSPs. At some point, we need to
formulate a policy for handling PSPs. (Communications PSPs, for |
example HASP, are especially problematic.) The question is |
whether a PSP should have all its documentation in a separate
manual or divided among manuals aimed at different audiences (the |
user's interface in the Programmer's Reference Manual, the |
administrator's interface in the SAM, the operator's interface in
the Operator's Guide) or both. This question is more complicated |
MTB-656, Revision 1
| than it might seem because we've found that it is often more
| important to be reasonable than consistent when documenting PSPs.
| In any case, a discussion of this question is beyond the scope of
this MTB. Depending on how the question gets answered,
information about PSPs can easily be added to administration and
maintenance manuals at a later time.
GOALS
Our goals for administration and maintenance documentation
are as follows:
1. To reduce the total number of these manuals as much as
possible. The thing people complain about most is having to
look in several manuals to get all the information they need
about one topic.
2. To have material in a separate manual when a distinct
audience for that material clearly exists.
3. To organize the material within each manual in a sensible,
useful way.
4. To turn as much murky prose as possible into recipe-style
procedures, using active, direct, friendly language.
5. To put all of the command descriptions in a single manual,
as we did when we reorganized the MPM.
DEFINITIONS
Before I talk about my proposal, I want to explain the
distinction I'm making between system administrators and system
maintainers.
| There are no absolute, correct definitions of the terms
| "system administrator" and "system maintainer." We can't depend
| on the distinctions our users make, because these titles are
| defined differently at different sites -- not everyone with the
| same title performs the same functions. Thus, we must pick our
| own definitions, explain them to our users carefully, and build
| our manuals on them.
MTB-656, Revision 1
This is an important point. I will discuss it again under |
"Notes on Outlines," but I think it deserves some elaboration |
here as well. The definitions I'm using may not always |
correspond to the definitions sites are used to. However, trying |
to define these terms the way sites currently define them is not |
a good idea in this case. Sites have never had adequate |
administration and maintenance documentation to learn from, so |
their way of defining these terms often isn't the best. My plan |
is to present sites with a new "model of the universe," a model |
which teaches them a different way of thinking about these terms, |
instead of mirroring their current, often mistaken, definitions. |
The definitions I'm using are as follows: |
System administrators provide their sites with a particular |
Multics operating environment. They are responsible for such
tasks as controlling and allocating resources (I'm using a broad |
notion of resources here, which includes those managed by RCP), |
registering projects and users, creating load control groups,
setting prices on resources, setting limits on and billing for |
resource usage, scheduling system activities such as hours of |
operation, shift change times, and unattended service, describing |
site parameters and setting site options, and assuring system |
security. |
System maintainers configure and tune the operating system
to make it comply with the special requirements of their sites.
They are responsible for such tasks as backing up and recovering
the system, salvaging and scavenging, analyzing crashes,
balancing disks, setting up things like I/O daemons and the |
message coordinator, metering and tuning, and maintaining system |
data bases.
It will be clear throughout this MTB that the reorganization |
I'm proposing rests on these definitions. |
PROPOSAL
The following chart summarizes my proposal:
MTB-656, Revision 1
New Book Audience Replaces
Operator's Guide Operators AM81, CC34
to Multics
System Administration System Administrators AK50, AS68,
Procedures CC74, CC34
System Maintenance System Maintainers AM81, AN52
Procedures
| Administration, Mainte- System Administrators AK50, AM81,
| nance and Operations System Maintainers AS68, CC74,
| Commands Communications Experts CC75, CC34,
| AN52
Project Administration Project Administrators AK51
Procedures
Communications Reference Communications Experts CC75
Manual
Owner's Manual System Managers ---
Pocket Guides Everyone ---
I'm going to discuss this proposal by considering each of
the existing manuals in turn, explaining what will happen to it
and how the changes will help to correct its shortcomings and
meet the goals expressed earlier.
The Multics Operator's Handbook
The MOH's prose will become part of the System Maintenance
Procedures manual and its command descriptions will become part
| of the Administration, Maintenance and Operations Commands
| manual.
Until recently, the MOH has served two audiences -- system
maintainers and operators. This has obviously been a problem,
because these two groups have vastly different needs and levels
of knowledge. Operators have been forced to wade through
complicated reference materials and command descriptions to
figure out how to do their jobs, and have often gotten in over
their heads as a result. The creation of the Operator's Guide
MTB-656, Revision 1
has solved this problem. There is no longer any reason for
operators to use the MOH.
However, system maintainers still have to use the MOH. This
proposal offers them a book of step-by-step procedures for all
the tasks they perform which isn't bogged down with explanations
of basic knowledge aimed at operators. It also offers them one
central location for all of the privileged commands they use.
The System Administrator's Manual
Most of the SAM's prose will become part of the System
Administration Procedures manual. A small amount of it will
become part of the Project Administration Procedures manual. Its
command descriptions will become part of the Administration, |
Maintenance and Operations Commands manual. |
The problem with the SAM isn't that it tries to serve too
many different audiences. Rather, it has one audience which it
doesn't serve completely. System administrators who are trying
to do accounting or control resources or manage I/O daemons must
look in other books for the necessary information. This proposal
offers system administrators a book of step-by-step procedures
for ALL of the tasks they perform and one central location for
all of the privileged commands they use.
The Project Administrator's Manual
The PAM's prose will become part of the Project
Administration Procedures manual. Its command descriptions will |
be REPEATED in the Administration, Maintenance and Operations |
Commands manual. |
The first section of almost every MAM book talks about the
way administration is divided into "roles:" system, security,
accounting, resource, volume, project. These roles are basically
treated as being equal. But there is a crucial difference
between the role of the project administrator and that of the
other administrators. The other administrators are all part of
the system-level team which provides services to customers. The
project administrator IS a customer. Thus, there is an important
reason to continue offering project administrators their own
manual, which includes descriptions of the commands they use. |
They are a distinct and separate audience. *
MTB-656, Revision 1
Registration and Accounting & Resource Control Administrator's
Manuals
Most of the RAM's and all of Resource Control's prose will
become part of the System Administration Procedures manual. A
small amount of the RAM's prose will become part of the Project
Administration Procedures manual. The RAM's and Resource
| Control's commands will become part of the Administration,
| Maintenance and Operations Commands manual. Its subroutines will
| be moved to the existing Subroutines and I/O Modules manual.
Unlike project administrators, accounting and resource
administrators are not distinct and separate audiences. The
tasks associated with their roles may get assigned to a single
person (in the case of resource control, a tape librarian, for
example), but the tasks are still part of the large set of tasks
performed to provide services to customers. There is no need to
have separate books on these topics.
Communications Administrator's Manual
Most of Communications' prose will become part of the
Communications Reference Manual. Some of its prose is intended
for users and will be moved to the Programmer's Reference Manual.
| Its commands will become part of the Administration, Maintenance
| and Operations Commands manual.
Performing communications tasks is a specialty, usually
handled by a "communications expert." This person's expertise is
not just Multics-specific. S/he must know about the networks,
protocols, etc. to which Multics is connected. This person
clearly represents a well-defined, distinct audience dealing with
a well-defined, distinct body of information, and thus deserves a
separate book.
Multics Bulk Input/Output
Bulk I/O's prose will be moved to a number of different
places: some to the Operator's Guide, some to the System
Administration Procedures manual, some to the System Maintenance
Procedures manual, and some to the Programmer's Reference Manual.
The information in Appendix G, "The HASP Workstation Simulator,"
will be moved to the new HASP manual (GB60). Bulk I/O's commands
| will be moved to the Administration, Maintenance and Operations
| Commands manual.
MTB-656, Revision 1
Bulk I/O is like the MOH -- it attempts to speak to
operators and system-level people (in this case system
maintainers and system administrators) at the same time. Some of
the information in Bulk I/O was duplicated in the Operator's
Guide. This process needs to be taken the rest of the way. All
of the information for operators needs to be moved to the Op
Guide.
Multics System Metering
Metering's prose will become part of the System Maintenance
Procedures manual and its commands and subroutines will become
part of the Administration, Maintenance and Operations Commands |
manual. Its subroutines will be moved to the existing Multics |
Subroutines and I/O Modules manual. |
Metering tasks are usually done by a system maintainer, so
they should be described in the same book which describes all of
the other system maintainer tasks. There's no reason to have
them in a separate book. Most of Metering is command and
subroutine descriptions anyway, and once these are moved out, the
remaining prose isn't of sufficient size to warrant a separate
book.
PLAN
First I'll talk about what has to be done to create each of
the proposed manuals. Then I'll present a step-by-step plan for
doing the work, including some problems which may come up during
each phase.
Operator's Guide to Multics
The information for operators in Bulk I/O needs to be
rewritten/converted to recipes and moved in.
Multics System Administration Procedures
The SAM will serve as the base for this manual. The prose
already in the SAM needs to be rewritten/converted to recipes.
Most of the prose in the RAM and all of the prose in Resource
Control needs to be rewritten/converted to recipes and moved in.
The information for administators in Bulk I/O needs to be
MTB-656, Revision 1
rewritten/converted to recipes and moved in. The commands in the
SAM need to be moved out.
For an outline of this manual, see Appendix A.
Multics System Maintenance Procedures
The MOH will serve as the base for this manual. The prose
already in the MOH needs to be rewritten/converted to recipes.
The prose in Metering needs to be rewritten/converted to recipes
and moved in. The prose in Bulk I/O also needs to be
rewritten/converted to recipes and moved in. A large number of
recipes which don't exist in any form yet need to be written up
and added. The commands in the MOH need to be moved out.
For an outline of this manual, see Appendix B.
| Multics Administration, Maintenance and Operations (AMO) Commands
| All of the commands in the MOH, the SAM, the RAM, Resource
| Control, Communications, Bulk I/O, and Metering need to be moved
| in. All of the commands in the PAM need to be copied in. In
| addition, privileged commands currently residing in the Multics
| Commands and Active Functions manual need to be moved or copied
| in.
| There will be two criteria for including a command in the
| AMO Commands manual: it requires the user to have some kind of
| privilege or special access in order to use it; it is used only
| in special situations in which normal users rarely find
| themselves. Where there is a question about the second
| criterion, the command will be documented in both the AMO
| Commands manual and the existing Commands and Active Functions
| manual.
MTB-656, Revision 1
The AMO Commands manual will have the following structure: |
Introduction: Command Environments |
Section 1: Privileged Multics Commands |
Section 2: Accounting Commands |
Section 3: Initializer Commands |
Section 4: Exec Commands |
Section 5: I/O Daemon Commands |
Section 6: BCE Commands |
Section 7: BOS Commands |
The introduction will describe the various command |
environments, and how to use them from the Multics environment |
with admin mode, send_admin_command (sac), ec admin, and |
sc_command. |
The exec commands will be in a separate section from the |
rest of the initializer commands to make it easier for sites to |
replace them with their own versions. The accounting commands |
will be in a separate section from the rest of the privileged |
Multics commands because they are used in a special environment. |
The exec_coms admin.ec and master.ec will be described with the |
privileged Multics commands, with pointers to the exec and |
accounting commands, respectively. |
Commands will be arranged alphabetically within each |
section. A user who doesn't know which section a command is in |
can easily find out by looking in the index. |
Each command description should include:
Examples (or a terminal session if the command is especially
confusing)
Notes (why would you want to use this command?)
Output messages
Error messages (and what to do about them)
Adherance to some standard for control argument descriptions
(caps or literals or parentheses or something)
Limitations on the use of control arguments (e.g., which
ones can't be used in combination)
MTB-656, Revision 1
Damage which results from incorrect usage
Restrictions on usage (e.g., is access is required to a
gate?)
Cross references to related commands
Data bases or segments used or modified by the command
| ABOUT PRIVILEGED SUBROUTINES
| Descriptions of privileged subroutines, especially gates and
| utilities, which don't exist in any form yet need to be written
| up and made available. There are two reasons for this. The
| first is that many customers have asked us to write them up. The
| second is that the B2 security rating we are trying to get
| requires that we document all gates to ring 0 and ring 1.
| However, privileged subroutines will NOT be documented in
| the same manual as privileged commands. Instead, some of them
| will be documented in the existing Subroutines and I/O Modules
| manual, and some of them will be documented in a separate, new
| manual. The decision as to which subroutines belong in the
| existing Subroutines manual and which subroutines belong in this
| new manual, as well as the decision as to whether or not the new
| manual should be a PLM, will be driven by B2 security
| requirements. A discussion of these requirements is beyond the
| scope of this MTB. For the time being, a separate section will
| be created in the existing Subroutines manual for privileged
| subroutines, and a discussion of privilege/access will be added
| to avoid user confusion as to which subroutines s/he may use.
Multics Project Administration Procedures
The PAM will serve as the base for this manual. The prose
already in the PAM needs to be rewritten/converted to recipes.
Some prose in the SAM and the RAM needs to be rewritten/converted
to recipes and moved in. The commands in the PAM need to be
| COPIED into the new Commands manual.
For an outline of this manual, see Appendix C.
Multics Communications Reference Manual
Communications will serve as the base for this manual. The
prose intended for users needs to be moved to the Programmer's
Reference Manual. The remaining prose needs to be
MTB-656, Revision 1
rewritten/converted to recipes. The commands in Communications
need to be moved out.
For an outline of this manual, see Appendix D.
Multics Owner's Manual
A good subtitle for this manual would be "How to Run a
Multics Site." Its audience is system managers. Its function is
to talk about what facilities Multics offers and what control the
manager has over them. It should focus on the options available
to the manager for setting policies, NOT on how to accomplish
technical tasks. (For example, it should talk about the fact |
that it is possible to divide up machine time and disk space |
among the users, and that it is possible to charge for |
EVERYTHING, but it should not talk about how to do these things.) |
There should be a one-to-one mapping between policy setting |
as described in the Owner's Manual and policy implementation as |
described in the System Administration and System Maintenance |
Procedures manuals. |
A revision of the outline for an Owner's Manual which was
presented in MTB 577 is available in MTR 183. This manual will
have to be written pretty much from scratch.
Pocket Guides
Possibilities include:
Privileged Multics Commands |
Accounting Commands |
Initializer Commands |
Exec Commands |
I/O Daemon Commands |
BCE Commands |
BOS Commands |
System Administration Commands |
System Maintenance Commands |
Project Administration Commands |
Communications Commands |
Backup Commands |
Answering Service Commands |
Configuration Cards |
Privileged Subroutines |
MTB-656, Revision 1
| Switch Settings
Hardware Configuration Rules
Brief Recipes for Commonly Performed Tasks
STEPS
1. Make the RAM, Resource Control, Bulk I/O and Metering
manuals obsolete. Move the information they contain into
the SAM, the PAM, the MOH, the Operator's Guide, the
Programmer's Reference Manual and the HASP manual as I've
already specified, rewriting it or converting it to recipes
along the way. This could be done for the next release. A
possible problem here is what to do with the commands in the
manuals which become obsolete. If we create the
| Administration, Maintenance and Operations Commands manual
for the next release, they can obviously go in there. But
if we don't, they'll have to be moved temporarily into the
books to which their prose is moved.
| 2. Create the Administration, Maintenance and Operations
| Commands manual, moving or copying the commands out of
* existing manuals. This could be done for the next release.
A possible problem here is what to do if we can't also
rewrite the prose in the administration and maintenance
manuals for the next release. If we just reorganize the
books (i.e., move the commands out and move the prose
around), but don't rewrite them, users will have to buy all
new books because of the reorganization, then turn around
and buy all new books again because of the rewriting. One
| alternative is to create the Administration, Maintenance and
| Operations Commands manual, but continue to document the
| commands in the other manuals. Users could just buy the AMO
Commands book alone, and not have to buy the other books
until they were rewritten. There would just be the
repetition of command descriptions for a release or two.
| Another alternative is to not create the AMO Commands manual
at all until the other books have been rewritten.
3. Rewrite the material in the SAM and/or convert it to
recipes. Move out the stuff which belongs in the PAM. This
could be done over the course of the next few releases. A
possible problem here is the proposed plan to rewrite a
large number of the administrative commands, tools and
exec_coms. Improving the documentation for administrative
interfaces which are about to become obsolete is obviously a
waste of time.
MTB-656, Revision 1
4. Rewrite the material in the MOH and/or convert it to
recipes. Write up descriptions of all the material which is
missing from the manual. This could be done over the course
of the next few releases. A possible problem here is the
gradual replacement of BOS with BCE. It doesn't make much
sense to put a lot of effort into improving this manual
until the replacement is complete.
5. Rewrite the material in the PAM and/or convert it to
recipes. This could be done over the course of the next few
releases. A possible problem here is the same one that
comes up in relation to rewriting the SAM.
6. Rewrite the material in Communications and/or convert it to
recipes. This could be done over the course of the next
several releases. A possible problem here is the impact of
the DSA project.
7. Create an Owner's Manual. This is a fairly low priority at
this point.
8. Create some Pocket Guides. This is a fairly low priority at
this point.
Note that throughout this reorganization/rewriting process,
we'll be converting the administration and maintenance manuals so
they can be printed on the 9700. We'll also be creating info
segs for the many administration and maintenace commands which
don't have them. The TOs have already begun working on these
projects.
NOTES ON OUTLINES |
1. The way administration and maintenance information has been |
split up between the outlines for the System Administration |
and System Maintenance Procedures manuals may not always |
correspond to the way sites are used to splitting up |
administrative and maintenance responsibilities. However, |
trying to organize our books according to the way sites |
currently do things is not a good idea in this case. Sites |
have never had adequate documentation to learn from, so |
their ways of accomplishing administration and maintenance |
tasks often aren't the best. By splitting up administrative |
and maintenance documentation the way the MTB suggests, |
we're presenting sites with a new model of how to do things. |
This model corresponds to a design goal for the code which |
MTB-656, Revision 1
| is driven in part by B2 security requirements. Hopefully,
| it will present sites with information in a way which is
| instructive, rather than a way which mirrors their current
| mistakes. Sites which choose not to do things the way we
| suggest shouldn't have any trouble finding the information
| they need, because there is a lot of overlap between the two
| books. This overlap is necessary because there is both an
| administrative and a maintenance aspect to taking care of
| many parts of the system. Of course, we will give a
| different emphasis to discussions of the same topic which
| occur in different books, provide plenty of cross
| references, and point out that neither discussion is
| complete.
| 2. The outlines do not include any software which is planned,
| but has not been installed yet. The most obvious example of
| this is BCE.
| 3. All of the software overviews will be arranged by function,
| not alphabetically, in order to give users a sense of how
| the different pieces of software interact with each other.
| This may mean describing some things in more than one place,
| although presenting things in a well-thought-out order
| usually results in a minimum of repeat descriptions. Just
| describing everything in alphabetical order requires a lot
| of awkward cross references and doesn't help the user really
| understand the environment s/he is trying to work in. If a
| user wants to find a definition quickly and in isolation,
| s/he can look in the glossary. For an example of the kind
| of software overview I have in mind, look at Section 3 of
| the Operator's Guide.
MTB-656, Revision 1
APPENDIX A
This appendix offers an outline of the Multics System
Administration Procedures manual. Specific suggestions on the
outline are welcome, especially those related to recipes that may
be missing.
MULTICS SYSTEM ADMINISTRATION PROCEDURES
PART I. INTRODUCTION
Section 1 Introduction
How To Use This Manual
Manual Conventions
Other Manuals of Interest
Section 2 Overview of System Administration Responsibilities
System Administration vs System Maintenance
What System Administrators Do
PART II. SYSTEM DESCRIPTION
Section 3 Hardware Overview
Same as Op Guide
What Boxes Exist
How They're Connected
Important Differences Between Various Models of CPU,
SCU, FNP, IOM, etc.
Section 4 Overview of System Tables/Data Bases
(Including Their Functions and Contents)
System Administrator Table (SAT)
Master Group Table (MGT)
Project Master File (PMF)
Project Definition Table (PDT)
Person Name Table (PNT)
MTB-656, Revision 1
User Registration File (URF)
Resource Type Master File (RTMF)
Resource Type Description Table (RTDT)
Channel Master File (CMF)
Channel Definition Table (CDT)
Terminal Type File (TTF)
Terminal Type Table (TTT)
I/O Daemon Tables
Billing Segments (>udd>sa>a)
billing_footnote
disk_stat
miscfile
PDTs (safe_pdts)
projfile
reqfile
today.use_totals
Using Tools to Maintain System Tables (and ecs) (MAD_018)
>udd>sa>a>smf.cur.sat --- >sc1>sat
>udd>sa>a>MGT.mgt --- >sc1>mgt
>udd>Proj_dir>Proj_id.pmf --- >udd>Proj_dir>Proj_id.pdt ---
>sc1>pdt>Proj_id.pdt
>sc1>PNT
>udd>sa>a>URF
>udd>sa>a>RTMF --- >udd>sa>a>RTMF.rtdt --- >sc1>rtdt
>udd>sa>a>CMF --- >udd>sa>a>CMF.cdt --- >sc1>cdt
>udd>sa>a>TTF --- >udd>sa>a>TTF.ttt --- >sc1>ttt
>ddd>idd>iod_tables.iodt --- >ddd>iod>iod_tables
>ddd>idd>rqt_info_segs>RQTI ---
>ddd>idd>rqt_info_segs>RQTI.rqti ---
>ddd>idd>rqt_info_segs>rqti
Removing Old Versions of System Tables and Old "io" Segments
with date_deleter
Setting Access to System Tables and Data Bases
Suggested Access
Reasoning Behind It
Implications of Deviations
Section 5 Software Overview (doesn't include system tables
or accounting reports)
(NOTE: in the book, these terms will be organized logically,
not alphabetically)
absentee process
absentee user table (>sc1>absentee_user_table)
MTB-656, Revision 1
access control segment (ACS)
access isolation mechanism (AIM)
accounting start up (acct_start_up.ec)
accounting update
administrative directory (>udd>sa>admin)
administrative exec_com (>sc1>admin.ec)
administrative library (>udd>sa>lib)
administrative lock segment (>udd>sa>lib>sys_admin_data)
administrative value segment (>udd>sa>lib>value_seg)
alias
anonymous user
answer table (>sc1>answer_table)
answering service
answering service person name table (>udd>sa>a>as_pnt)
background process
billing
billing exec_com (>udd>sa>lib>biller.ec)
canonicalization routine
communications channel
communications link
communications system
coordinator data segment (>ddd>idd>iodc_data)
crank (>udd>sa>lib>crank.absin)
daemon
daemon lock segment (>ddd>idd>coord_lock)
daemon user table (>sc1>daemon_user_table)
daily logs (>udd>sa>a>daily_log_N)
daily report control segment (>udd>sa>a>daily_report.control)
device class
device table (>sc1>device_table)
disk run (>udd>sa>lib>dodrp.absin)
disk quota
disk statistics segment (>udd>sa>a>disk_stat)
disk subsystem
disk usage name list (>udd>sa>lib>starname_list)
driver
errors exec_com (>udd>sa>lib>err.ec)
foreground process
initializer process
installation parameters (sc1>installation_parms)
interactive process
I/O interfacer (IOI)
I/O deamon exec_com (>ddd>idd>iod_admin.ec)
I/O daemon working tables (>ddd>idd>iod_working_tables)
limited service subsystem (LSS)
line type
load control group
MTB-656, Revision 1
local device
log select control segment (>udd>sa>a>log_select_file)
logical disk
logical volume
logical volume registration record
logs (>sc1>log)
major device
make system segment exec_com (make_sys_seg.ec)
master directory
master exec_com (>udd>sa>lib>master.ec)
message coordinator
message of the day (>sc1>message_of_the_day)
message routing table (>sc1>MRT)
message segment
minor device
paging volume
password
permanent syserr log (>sc1>perm_syserr_log)
Person_id
physical volume
printer notice (>ddd>idd>printer_notice)
private logical volume
process
process overseer
processed log files (>udd>sa>a>history)
programmer number
project
project directory
project registration segment (>udd>sa>a>projfile)
Project_id
public logical volume
quota
rate structure (sc1>rate_structure_N)
RCP resource management (RCPRM)
registry
remote device
remote driver
request type
requisition
resource
resource control package (RCP)
resource price
ring
root logical volume (RLV)
root physical volume (RPV)
safe project definition tables
(>udd>sa>a>safe_pdts>Project_id.pdt)
MTB-656, Revision 1
safe project registration file (>udd>sa>a>HF>safe_projfile)
safe requisition file (>udd>sa>a>HF>safe_reqfile)
safe system administrator table (>udd>sa>a>safe_sat)
SAT copy (>udd>sa>a>smf.cur.sat)
shift
shift configuration change exec_com
(>sc1>shift_config_change.ec)
statistics segment (>sc1>stat_seg)
syserr log control file (>udd>sa>a>syserr_select_file)
system error log (>sc1>perm_syserr_log)
system message table (as_error_table)
system start up exec_com (>sc1>system_start_up.ec)
time-record product (TRP)
today usage totals (>udd>sa>a>today.use_totals)
usage and revenue control file
(>udd>sa>a>usage_and_revenue.control)
user
User_id
utility exec_com (>udd>sa>lib>util.ec)
virtual console
virtual console table (>sc1>vcons_tab)
who table (>sc1>whotab)
work class
yesterday usage totals (>udd>sa>a>yesterday.use_totals)
PART III. CONTROLLING RESOURCES
Section 6 Understanding Resources
Interactive CPU Time (Machine Time)
Interactive Real Time (Connect Time)
Interactive Memory Units
Interactive Terminal I/O
Absentee CPU Time
Absentee Memory Units
I/O Daemon Usage
Disk Storage
Devices
Volumes
Channels
Section 7 Managing I/O Resources -- RCP |
Understanding I/O Resources
Devices
MTB-656, Revision 1
Volumes
Resource Types
System Resources
* Understanding RCP Resource Management Functions
Maintaining Resource Information
Controlling Access to Devices
Reserving and Cancelling Reservations of Resources
Assigning and Unassigning Devices
Attaching and Detaching Devices
Performing Special Device Control Functions
* Setting Up RCP
* Setting RCP Modes for Tapes (in installation_parms)
(e.g., to require/disable exact label validation, to
unload volumes on detachment)
| Determining the Status of RCP Devices
| Managing an RCP ACS
| Understanding the Relationship Between RCP & RCPRM
*
| Section 8 Managing I/O Resources -- RCPRM
| Understanding RCPRM Resource Management Functions
| Registering and Deregistering Resources
| Aquiring and Releasing Resources
| Controlling Access to Devices and Volumes
| Setting Up RCPRM & RCPRM Modes (in installation_parms)
| (e.g., to register volumes automatically)
| Setting the AIM Access Class Range of a Resource
| Clearing Resources
| Releasing Locks on Resources
| Managing a RCPRM Free Pool
| Deciding How Many Tapes Should Be in the Pool
| Adding Tapes to the Pool
| Listing Free Tapes in the Pool
| Removing Tapes from the Pool
| Registering/Deregistering Foreign Tapes for Users
| Setting/Resetting Usage Lock and Location Fields
| Getting Information About a Particular Tape
| Getting Information About a Group of Tapes
| Using RCPRM for Tape Library Maintenance (MAD_013)
| Section 9 Managing the Resource Type Master File
Understanding the Resource Type Master File (RTMF)
Function
Format/Syntax
Sample
Modifying the RTMF
MTB-656, Revision 1
Fixed Resource Parameters
Default Resource Parameters
Canonicalization Routines
Special Registration Parameters
Resource Type Synonyms
Attributes
Understanding Defaults
Understanding Reserved Resource Names
Understanding Reserved Attribute Names
Adding a Resource Type
Changing a Resource Type
Deleting a Resource Type
Understanding the Resource Type Definition Table (RTDT)
Converting the RTMF into a RTDT
Installing the RTDT
Printing the Contents of the RTDT
Writing a Canonicalization Routine for Resource Names
Section 10 Managing Resource Registries |
Understanding Registries
Registering a Resource
Devices (Drives)
Attributes
Speed
Model
Densities
Type
Name
Unique Id
Potential Attributes
Potential Access Class
Access Class
ACS Pathname
Volumes
Type (automatic)
Name (automatic)
Unique Id (automatic)
Potential Attributes (str -priv, rgr)
Potential Access Class (str -priv, rgr)
Release Lock (str -priv, rgr)
Owner (str -priv, aqr)
Access Class (str -priv, aqr)
Attributes (str, rgr, aqr)
Allocation Flag (str, rgr, aqr)
ACS Pathname (str, rgr, aqr)
Registering a System Resource
MTB-656, Revision 1
Dealing with Automatic Registration
Changing a Resource's Registration/Setting its Attributes
Deregistering a Resource
Making Checkpoint Copies of Registries
Deleting a Registry
Setting Access to a Registry
*
Section 11 Setting Prices for Resources
Figuring Out What Things Should Cost
Setting Rates in installation_parms
Interactive CPU Time (Machine Time)
Interactive Real Time (Connect Time)
Interactive Memory Units
Interactive Terminal I/O
Absentee CPU Time
Absentee Memory Units
I/O Daemon Usage (resource price per queue)
Disk Storage (quota)
Registration Fee
Device Prices
Resource Prices
Channels
Tapes
Setting Rates in iod_tables
Line Charge
Page Charge
Setting Rates for Miscellaneous Charges
| Understanding Rate Structures
| Assigning Projects to Rate Structures
Charging for Volume Dumper Services
Charging for Volume Retrievals
| PART IV MANAGING THE STORAGE SYSTEM HIERARCHY
Section 12 Understanding System Directories
(Including Important Segments in Each Directory)
>daemon_dir_dir (>ddd)
>cards
>gcos
>io_daemon_dir (>idd)
>coord_dir
>io_msg_dir
MTB-656, Revision 1
><major device>
>meter_dir
>rqt_info_segs
>volume_backup
>documentation (>doc)
>dumps
>library_dir_dir (>ldd)
>lv
>process_dir_dir (>pdd)
>reload_dir
>site
>system_control_1 (>sc1)
>pdt
>proxy
>rcp
>update
>system_library_auth_maint (>am)
>system_library_standard (>sss)
>system_library_tools (>t)
>system_library_unbundled (>unb)
>udd
>SysAdmin>admin
>SysAdmin>lib
Section 13 Managing Quota
Understanding Segment Quota |
Understanding Directory Quota |
Giving a Project More Quota
Moving Storage System Quota
Raising the Total System Quota
Creating Quota
Setting Directory Quotas (including implementation |
restrictions) |
Cleaning Up Segments
Wiring Pages of a Segment
Unwiring Pages of a Segment
Monitoring Disk Space (MAD_005)
Understanding Salvaging
MTB-656, Revision 1
| PART V. MANAGING STORAGE SYSTEM VOLUMES
Section 14 Managing Storage System Disk Volumes
Understanding Physical and Logical Volumes
Organizing Disk Storage into Logical Volumes
Demountable Volumes
Shared Spindle Devices
Defining Public and Private Volumes
Understanding Conventions for Disk Volume Names
Registering a Physical or Logical Volume (avr)
Modifying a Volume Registration (cvr)
Deleting a Volume Registration (dvr)
Getting Information About Volume Registrations (lvr)
Section 15 Managing Logical Volume Access
Understanding Quota Accounts
Understanding Master Directories
Understanding Access Needed to Administer a Volume
Finding Logical Volume ACS Segments
Setting Access to Logical Volume ACSs
Section 16 Using a Logical Volume
What You Can Do With a Logical Volume
Allocating Logical Volume Quota
Creating a Quota Account (svq)
Changing the Quota Available in a Quota Account (svq)
Deleting a Quota Account (dlvq)
Setting the Owner of a Master Directory (smdo)
Setting the Quota Account of a Master Directory (smda)
Getting Information
get_dir_quota
list_mdir
Section 17 Using a Quota Account
What You Can Do With a Quota Account
Creating a Master Directory (cd -lv)
Deleting a Master Directory (dd)
Setting the Quota on a Master Directory (smdq)
MTB-656, Revision 1
PART VI. ASSURING SYSTEM SECURITY
(NOTE: this part will be expanded in whatever ways are |
necessary to meet B2 security requirements) |
Section 18 Assuring the Security of the File System
Setting ACLs
On Library Directories
On SysAdmin Directoires
On Gates (e.g., giving system programmers access to
phcs_ gate)
On Project Directories
On System Data Bases
On Interactive Queues
On Absentee Queues
Giving Access to Special Projects
TOLTS/CSD
SysMaint
SysAdmin
Understanding AIM
Turning AIM On
Setting AIM
On Library Directories
On SysAdmin Directoires
On Gates
On Project Directories
On System Data Bases
On Interactive Queues
On Absentee Queues
Managing Ring Brackets |
Understanding How Multics Uses Rings (esp. 0, 1, 2, 4, 5) |
Assigning Login Rings to Projects and Users |
Maintaining Proper Ring Brackets in System Libraries |
Correcting "Out of Service" Problems
Specifying Authorizations
For Users
For Projects
Section 19 Assuring the Security of RCPRM
Setting Access to ACSs
For Devices Managed by RCP
For Disk Packs
Setting AIM for RCPRM
MTB-656, Revision 1
Section 20 Assuring the Security of Communications Channels
Setting Access to ACSs
For Registered Dial Identifiers
For Dial-Out Channels
For Slave Channels
For Login Channels
Setting AIM for Communications Channels
Managing Terminal Identification Codes and Security
Attributes
Section 21 Assuring the Security of I/O Daemons
Giving a User Access to a Request Type (setting access to
msg seg)
Giving a Driver Access to a Request Type (editing iod_table)
Giving a Daemon Access to a Driver (editing iod_table)
Setting Access to ACSs
For Card Input Stations
For Anonymous Bulk Data Input
For Card Data Input
Marking the Access of a Device (editing iod_table)
Setting the Access Class of a Request Type (editing
iod_table)
Section 22 Assuring the Security of the Absentee Facility
Giving a User Access to an Absentee Queue (setting access to
msg seg)
Giving a Daemon Access to Proxy (setting access to ACS)
Giving an Administrator Access to Proxy (setting access to
ACS)
Section 23 Assuring the Security of Privileged Operations
Understanding Privilege
Granting Access to Use System Privileges (via
system_privilege_ gate)
Using System Privileges (set_system_priv)
Setting Access to ACS for System Table Installation
Setting Access to ACS for Large I/O Buffers
Setting Access to Privileged Gates
audit_gate_
hphcs_
installation_tools_
mdc_priv_
metering_gate_
MTB-656, Revision 1
phcs_
rcp_admin_
rcp_priv_
rcp_sys_
Section 24 Logging and Auditing
Setting Logging Parameters
In Person Name Table (PNT)
In System Administrator Table (SAT)
In Channel Definition Table (CDT)
Checking Daily Log Reports
Structuring Log Control Files to be Most Useful
Deciding What to Audit
Setting Auditing Flags
Looking at Auditing Logs Online
Checking Audit Reports on SysAdmin Directories
Checking Audit Reports on System Libraries
Auditing the Message Coordinator Log
Auditing the Answering Service Log
Auditing the System Message Log
Auditing the Syserr Log
Auditing Critical Directories
Section 25 Miscellaneous Security Tasks
Maintaining Physical Security
Assigning Project_ids
Assigning Person_ids
Managing Passwords
Locating the Possessor of a Password Being Used Improperly
Locating Users Having Trouble Using the System
Changing the Admin Mode Password
Managing Gates (MAD_020) *
Setting Access to GCOS Simulator Segments
Examining Answering Service Dumps
Reviewing Software Changes in New System Releases
PART VII. MANAGING I/O DAEMONS
Section 26 Understanding I/O Daemons
Coordinator
Drivers
Major Devices
MTB-656, Revision 1
Minor Devices
Local Devices
Remote Devices
Device Classes
Request Types
Lines
Queues
Section 27 Setting Up I/O Daemons
Specifying I/O Daemon Information in the PMF
Process Overseer
Authorization
Attributes
daemon
dialok
Setting Up the Message Coordinator
Setting Up the Printer Daemon
Setting Up the Punch Daemon
Setting Up the Card Input Daemon
Changing I/O Daemon Search Rules
Managing io_daemon_dir
(e.g., assigning quota to it)
Section 28 Managing I/O Daemon Output
Understanding the Printer & Punch Daemons
Setting Rates for Printing & Punching
Deciding Which Process Runs the Printer Daemon
Deciding Which Process Runs the Punch Daemon
Setting Access to I/O Daemon Queues
Understanding Remote Daemon Stations
Maintaining AIM Features for I/O Daemons
Listing Extended Access on I/O Daemon Queues
Changing Extended Access on I/O Daemon Queues
Section 29 Managing I/O Daemon Input
Understanding Card Input
Understanding Card Input Stations
Managing a Card Input Station
Registering Card Input Users
Registering Passwords for Card Input Users
Registering Stations and Their Passwords in the
Person Name Table (PNT)
Creating an ACS for a Station
Giving Users Access to the ACS of a Station
MTB-656, Revision 1
Understanding Proxy/RJE
Setting Access to a Card Input Station for RJE Submission
Setting Access to a Proxy ACS
Reading Cards
Understanding the Card Pool
Understanding the Structure of the Card Pool Directory
Hierarchy
Managing the Card Pool
Managing the Card Pool's Quota
Setting Access to a User Directory in the Card Pool
Doing Periodic Cleanups of the Card Pool
Section 30 Running I/O Daemons
Understanding admin exec_coms
Sample General I/O Daemon admin exec_com
Sample Driver I/O Daemon admin exec_com
Modifying iod_admin.ec
Writing an admin exec_com for a Specific Driver
PART VIII. MANAGING PROJECTS AND USERS
Section 31 Managing Projects
Organizing Projects on the System
Deciding Which Logical Volume a Project Directory Should
Be On
Understanding the Project Master File (PMF)
Function
Format/Syntax
Sample
Modifying the PMF
Specifying Login and Load Control Attributes
Specifying Spending Limit Attributes
Specifying Special Environment Attributes
Understanding the Project Definition Table (PDT)
Converting the PMF to a PDT
Installing the PDT
Deciding What Rate Structure to Use for a Project |
Understanding the System Default start_up.ec |
(>sc1>start_up.ec) |
Registering a New Project
Using new_proj
Editing the PMF
Default Project Attributes
MTB-656, Revision 1
Specific User Attributes
Converting the PMF to a PDT
Installing the PDT
Running a Forced Accounting Update
Changing a Project's Registration
Setting AIM Attributes for a Project
Setting Access to a Project Directory
Setting Special Attributes for a Project
Understanding the System Administrator Table (SAT)
Function
Format/Syntax
Sample
Modifying the SAT
Modifying the Header
Modifying a Project Entry
Installing a New SAT
Deleting a Project
Delegating a Project
Undelegating a Project
Renaming a Project
Changing a Project's Administrator
Section 32 Managing Users
Determining if a User is Already Registered
Creating a Person_id
Understanding the Person Name Table (PNT)
Function
Format/Syntax
Sample
Modifying the PNT
Name
Login Alias
Login Attributes
Default Project
Password
Card Password
AIM Authorizations
Audit Flags
Understanding the User Registration File (URF)
Modifying the URF (Changing a User's Registration)
Address
Programmer Number
Adding an Anonymous User to an Undelegated Project
Setting AIM Attributes for a User
Managing Special User Identities
MTB-656, Revision 1
SA1.SysAdmin
Repair.SysAdmin
anonymous.HFED
Operator.Operator
Backup.SysDaemon
Dumper.SysDaemon
Repair.SysDaemon
Retriever.SysDaemon
Ring_1_Repair.SysDaemon
Salvager.SysDaemon
Scavenger.SysDaemon
Utility.SysDaemon (MAD_011)
Card_Input.Daemon
Metering.Daemon
Volume_Dumper.Daemon
Volume_Reloader.Daemon
Volume_Retriever.Daemon
Creating a Fictitious Person
PART IX. CONTROLLING SYSTEM USAGE
Section 33 Managing Shifts
Determining Hours of Operation
Understanding Shifts
Determining Shift Change Times
Overriding Values in the Shift Table
Using the Shift Change Exec_Com
Section 34 Managing System Load/Allocating Processor Resources
Understanding Load Control Groups
What to Consider When Setting Up Load Control Groups
Defining Load Control Groups
Managing Load Units
Time Leveling
Understanding Work Classes
Tuning Work Classes
Defining Percentages
Understanding the Master Group Table (MGT)
Function
Format/Syntax
Sample
Modifying the MGT
Defining Primary and Secondary Users
MTB-656, Revision 1
Defining Preemption and Grace
Installing a New MGT
Section 35 Managing Absentee Usage
Understanding How Absentee Usage Differs From Interactive
Usage
Understanding How Foreground Usage Differs From Background
Usage
Defining Absentee Usage Quotas
Defining Absentee Queues
Managing Absentee Load Control
Section 36 Automatic Mode & Unattended Service
Determining When to Run in Automatic Mode
Determining When to Run with Unattended Service
PART X. MANAGING THE ACCOUNTING SUBSYSTEM
Section 37 Managing Accounting Operations
Customizing Accounting Parameters
Understanding Automatic Operations
What They Do/How They Work
Scheduling the Accounting Update
Scheduling the Disk Report (>udd>sa>lib>dodrp.absin)
Scheduling the Crank (>udd>sa>lib>crank.absin)
Understanding Manual Operations
Scheduling Billing
Scheduling Miscellaneous Charges
Running the Disk Report Manually
Checking the Crank Output
Checking the Crank Run for Errors
Restarting the Crank
Recovering Accounting Files Lost in a System Crash
Modifying crank.absin
Modifying dodrp.absin
Section 38 Managing Accounting Reports/Billing
Doing Billing
Storage Requirements for Billing
Scheduling Billing
Preparing the Billing Footnote Segment
MTB-656, Revision 1
Preparing the Bill
Making Sure Disk Report Has Been Run Recently
Making Sure Billing Footnote is Up-to-date
Making Sure Miscfile is Up-to-date
Running the Bill
bill
diskreport
long_bill
mailing_copy
miscs.print
msum
short_bill
system_month.report
Checking the Bill
Accepting the Bill
Cleaning Up the Bill
Managing the Miscfile
Entering Charges
Deleting Charges
Entering Credits
Deleting Credits
Printing the Contents
Creating a Status Report for a Project
Understanding Accounting Reports (>udd>sa>a)
(Including Their Functions and Formats)
Daily Account Status Summary Report (sumry)
Daily Cutoff Account Report (cutrpt)
Daily Disk Statistics/Usage Report (diskreport)
Daily Usage and Revenue Report
(usage_and_revenue.report)
Daily System Statistical Report (system.report)
Weekly Black and White Chart
Weekly Report (weekly.report)
Monthly Long Usage Report/Bill
Monthly Short Usage Report/Bill
Monthly Account Bill
Monthly Charge Summary
Monthly Billing Cards
Monthly Miscellaneous Charges Summary
Monthly Disk Report
Monthly Usage and Revenue Report
(monthly_usage_and_revenue.report)
Monthly Black and White Chart (bwchart.print)
Billing Footnote (billing_footnote)
MTB-656, Revision 1
PART XI. SETTING OTHER SYSTEM OPTIONS
Section 39 Managing Settable Parameters
Understanding installation_parms
Modifying installation_parms
Default Absentee CPU Time Limit/Queue
Maximum Absentee CPU Time Limit/Queue & /Shift
Default Absentee Queue
Absentee Timax/Queue
Access Ceiling
Default Security Level for Volume Authentication
Automatic Volume Registration
Authorization Names (AIM info)
Config Table
Count Parameter of Terminal Channel Wakeup Loop Detector
Time Parameter of Channel Wakeup Error Loop Detector
Device Names
Device Prices
Default CPU Time Limit for Foreground Absentee Queue
Count Parameter of Fatal Process Error Loop Detector
Time Parameter of Fatal Process Error Loop Detector
Idle Time
Inactive Time
Installation Identification
Log Parameters
Login Time
Per-Shift Upper Limit
Per-Shift & Per-Queue Upper Limit
Per-Shift Lower Limit
Per-Shift & Per-Queue Lower Limit
Percent of Idle Units Available to Background Absentee
Jobs
Percent of Absentee Slots Reserved for Each Queue
Prices
disk storage
per-month registration
per-shift CPU time
per-shift connect time
per-shift terminal I/O operations
per-shift memory usage
Queue Prices
absentee virtual CPU time
absentee memory usage
I/O daemon usage
Resource Names
MTB-656, Revision 1
Resource Prices
Resource Wait Time
RCPRM Activation
Shift Table
CPU Time Limit (for suspended process)
Real Time Limit (for suspended process)
Titles
Tries
CPU Time Limit (for terminating process)
Real Time Limit (for terminating process)
Automatic Volume Detachment
Accounting Update Interval
Warning Time
Rebooting to Have Changes Take Effect
Understanding value_seg
Modifying value_seg
Crank Time
Disk Accounting Time
Crank Abort
Last Crank
Last Disk Report
Weekly Report Time
Dprint Destintation
Dprint Header
Crank Message Recipient
Understanding sys_admin_data
Modifying sys_admin_data
Admin Lock
Log File Controls
User Accounts Office Info
Mailing Banner
Minimum Ring
Maximum Ring
Maximum Grace
Load Control Group
Project Attributes
Section 40 Delegating Responsibilities
Project Administration
Accounting Administration
Volume Administration
Resource Administration
Security Administration
MTB-656, Revision 1
Section 41 Miscellaneous Tailoring Tasks
Tailoring the Time Tables
Setting Your Search Rules
Using Accounting Commands
GLOSSARY
INDEX
MTB-656, Revision 1
APPENDIX B
This appendix offers an outline of the Multics System
Maintenance Procedures manual. Specific suggestions on the
outline are welcome, especially those related to recipes that may
be missing.
MULTICS SYSTEM MAINTENANCE PROCEDURES
PART I. INTRODUCTION
Section 1 Introduction
How To Use This Manual
Manual Conventions
Other Manuals of Interest
Section 2 Overview of System Maintenance Responsibilities
System Maintenance vs System Administration
What System Maintainers Do
PART II. SYSTEM DESCRIPTION
Section 3 Hardware Overview
Same as Op Guide
What Boxes Exist
How They're Connected
Important Differences Between Various Models of CPU,
SCU, FNP, IOM, etc.
Section 4 Software Overview
(NOTE: in the book, these terms will be organized logically,
not alphabetically)
access control segments (ACSs)
activate
active process table (APT)
active process table entry (APTE)
MTB-656, Revision 1
active segment
active segment table (AST)
active segment table entry (ASTE)
admin mode
appending unit (APU)
AST hash table
AST pool
AST trickle
average time between (ATB)
base address register (BAR)
blocked process
bound fault
branch
cache
computed address (CA)
connect
connected segment
control unit (CU)
core map
core map entry (CME)
deadline
deadlock
decimal unit (DU)
delay until interrupt signal (DIS)
derail (DRL)
descriptor segment (DSEG)
descriptor segment base register (DSBR)
device interface module (DIM)
device interface adapter (DIA)
direct channel
disk table
dispatching
execute double (XED)
execute interrupt mask assignment (EIMA)
extended intruction set (EIS)
eligible process
entry
entry hold switch (EHS)
error detection and correction (EDAC)
fault/interrupt vector
flagbox
get_processor
hardcore checker map
hardcore process (hproc)
history registers
high-speed line adapter (HSLA)
idle process
MTB-656, Revision 1
idle time
indirect to segment (ITS)
instruction buffer
instruction counter (IC)
interactive queue
interprocess transmission table (ITT)
interprocess transmission table entry (ITTE)
I/O interfacer (IOI)
I/O assignment table (IOAT)
isolated online test subsystem (ISOLTS)
known segment table (KST)
known segment table entry (KSTE)
link adapter (LA)
loaded process
lock
locking hierarchy
logical channel
low-speed line adapter (LSLA)
machine conditions
max_eligible
max_max_eligible
memory frame
message coordinator tables
message routing table (MRT)
metering cell
migrate
min_eligible
multiprocessing
multiprogramming
notify time-out
operations unit (OU)
page
page fault
page frame
page table
page table lock
page table word (PTW)
page table word associative memory (PTWAM)
page thrashing
peripheral subsystem
physical channel
post purge
preempt
procedure pointer register (PPR)
procedure ring register (PRR)
procedure segment register (PSR)
process data segment (PDS)
MTB-656, Revision 1
process directory (PDIR)
process loading
processor data segment (PRDS)
processor time
PSI adapter (PSIA)
pxss
quantum
read switches (RSW)
ready process
realtime process
real time
record
response time
return to BOS (RTB)
ring alarm register (RALR)
running process
salvager
scavenger
scheduler
scheduling
seek distance
segment descriptor word (SDW)
segment descriptor word associative memory (SDWAM)
segment fault
segment thrashing
setfault
shift table
spooling
stack frame
stack header
store pointers and length (SPL)
store pointers as ITS pairs (SPRI)
store registers (SREG)
subsystem
system communications segment (SCS)
system segment table (SST)
system segment table name table (SSTNT)
system trailer segment (STR)
traffic control data base (tc_data)
temporary pointer register (TPR)
temporary ring register (TRR)
temporary segment register (TSR)
time eligible (te)
time eligible first (tefirst)
time eligible last (telast)
threaded
threaded list
MTB-656, Revision 1
throughput
timax
time since interaction (ti)
time since scheduling (ts)
time since state change (tssc)
time slice
timer runout (TRO)
total online test system (TOLTS)
total CPU time
traffic controller (tc)
transfer (TRA)
unpaged memory
virtual console table
virtual CPU time
volume table of contents entry (VTOCE)
wakeup
wait
wait event
wired page
wired segment
work class
working set
working set addend (WSA)
working set factor (WSF)
PART III. CONFIGURING THE SYSTEM
Section 5 Configuring the Hardware
Making IOM Channel Assignments
Making Communications Channel Assignments
Making Port Assignments
(Including Memory Order and Switch Settings)
Deciding Whether to Use a DPU or a DMP/VIP
Understanding the Rules for Setting Up a Configuration
Building a Configuration
Translating Hardware into a Config Deck
Adding New Hardware to the Configuration
Section 6 Tailoring the Config Deck
Defining a Disk Subsystem
Shared Spindle Devices
Defining a Tape Subsystem
Setting Options for Bootloading
MTB-656, Revision 1
Setting Options for Salvaging Operations
Setting Scheduling Factors and Parms
Making it Possible to Split the System
Listing the Config Deck
Changing the Config Deck
Saving the Config Deck
Section 7 Setting the Switches
Understanding Why Switches Must Be Set A Certain Way
Understanding What Will Happen If Switches are Set
Incorrectly
Deciding How Switches Should Be Set At Your Site
(Including Differences Between Various Models)
PART IV. COMMUNICATING WITH THE SYSTEM
Section 8 Managing the System Console
Resetting a System Console
Adding an Alternate System Console
Changing the Bootload Console
Deciding When to Delete a System Console
Deleting a System Console
Sending an Interrupt from an IOM to a System Console
(MAD_010)
Recovering from a System Console Failure
Section 9 Using Admin Mode
Understanding When to Use Admin Mode
Using the sac Command
What You Can Do in Admin Mode
What You Shouldn't Do in Admin Mode
Managing the Admin Mode Password
Section 10 Managing the Message Coordinator
Setting Up the Message Coordinator
Defining a Virtual Console
Removing a Virtual Console
Routing Daemon Output
Communicating With Daemons
MTB-656, Revision 1
PART V. BRINGING THE SYSTEM UP AND SHUTTING THE SYSTEM DOWN
(NOTE: this part will change quite a bit when BCE replaces |
BOS) |
Section 11 Bootloading BOS
Deciding on the Correct Values for Loading Firmware into
MPCs
Loading MPCs Not Connected to IOM A
What to Do When an MPC Can't Be Loaded
Reloading Firmware Into an MPC
Deciding When to Do a WARM Boot
What to Do When BOS Won't Boot
Using the BOS Toehold
What to Check for When the CLOK Card Needs to Be Changed
Section 12 Setting Up the Bootload Environment
Using Utility.SysDaemon (MAD_011)
Setting Up the Message Coordinator
Modifying system_start_up.ec (MAD_017)
Setting Access to Gates for Special Individuals
Logging in Particular Daemons
Copying a MST in Your Own Process
Section 13 Bootloading Multics
Deciding When to Do a Cold Boot
What to Do When an FNP Won't Load
What to Do When the Clock Setting is Before the RPV Label
Time
What to Do When the RPV Label Time is Wrong
What to Do if Multics Crashes Repeatedly
Deciding Which Dump to Keep
What to Do if the Answering Service Fails Repeatedly
Resetting the CACHE ENABLE Switches
Enabling/Disabling Associative Memory Switches
Starting the System Up for a Special Session
Starting the System Up Manually
Modifying the AUTO REBOOT Runcom (MAD_016)
MTB-656, Revision 1
Section 14 Shutting the System Down
Understanding Automatic Shutdown (down command)
Deciding When to Do a Nonscheduled Shutdown
What to Do When You Try to Shutdown and Users Are Still On
| PART VI. MAINTAINING STORAGE SYSTEM VOLUMES (S. S. DISKS)
Section 15 Managing Physical and Logical Volumes
Setting Up a Physical Volume
(label, VTOC, volume map)
Allocating Space on Disk Packs
Deciding Who May Have Permission to Use Which Disk Packs
Understanding Logical Volumes
Organizing Disk Storage into Logical Volumes
Demountable Volumes
Shared Spindle Devices
Configuring Logical Volumes
Defining Public and Private Volumes
Registering a Physical or Logical Volume (avr)
| Evacuating a Physical Volume
Modifying a Volume Registration (cvr)
Deleting a Volume Registration (dvr)
Getting Information About Volume Registrations (lvr)
Adding a Logical Volume to the Set Available for Process
Directory Segments
Removing a Logical Volume from the Set Available for Process
Directory Segments
Managing Process Directory Volumes
What to Do When the Operator Has to Delete a Logical Volume
(How to Access the Impact on Users and Process Directory
Volumes)
Section 16 Recovery: Reloading
Understanding Reloading
Understanding the Difference Between a Complete Volume Dump
and a BOS SAVE
Understanding the Difference Between a Volume Reload and a
BOS RESTOR/Hierarchy Reload
| Deciding Which Volumes Need to Be Reloaded (and figuring out
| whether they include root volumes)
Doing a BOS SAVE
Restarting a BOS SAVE
MTB-656, Revision 1
Doing a Volume Reload
Doing a BOS RESTOR/Hierarchy Reload
Restarting a BOS RESTOR/Hierarchy Reload
Recovering from a Pack Failure
(head crash, bad spot, MPC failure, etc.)
Recovering a NonRoot Pack with a Volume Reload
Recovering a NonRoot Pack with a BOS RESTOR/Hierarchy Reload
Recovering a Root Pack with a Volume Reload
Recovering a Root Pack with a BOS RESTOR/Hierarchy Reload
Recovering the RPV with a Volume Reload
Recovering the RPV with a BOS RESTOR/Hierarchy Reload
Using Backup Tapes to Reload the Entire System
Section 17 Recovery: Volume Salvaging
Understanding Volume Salvaging
When Most Sites Salvage and Why
Requesting the Volume Salvager
Salvaging the RPV
Salvaging Other Volumes of the RLV
Salvaging Non-RLV Volumes During Initialization
Salvaging Non-RLV Volumes While the System is Running
Section 18 Recovery: Scavenging
Understanding Volume Scavenging
When Most Sites Scavenge and Why
Requesting the Volume Scavenger
Scavenging Any In-Use Volume
Scavenging All Volumes of a Mounted Logical Volume
Scavenging All Volumes With Inconsistencies
Scheduling a Forced Volume Scavenge
Section 19 Sweeping
Understanding Sweeping
Compressing a Logical Volume
Performing VTOC Garbage Collection on a Pack
Balancing Packs
Running Sweeping in an Absentee Process
Interpreting Sweeping Output
Deciding How Often to Run Sweeping
Section 20 Moving Packs
Moving a Pack When Multics is Running
Moving a Pack When Multics is Not Running
MTB-656, Revision 1
Moving 451 Packs When CPUs Are Put in Step By Turning off
Their PORT ENABLE Switches
Section 21 Formatting Packs
| Setting Up Alternate Tracks (MTR under TOLTS)
Operating Multics with Alternate Tracks
Operating BOS with Alternate Tracks
Handling Defective Disk Tracks
| Formatting a Disk Pack (MTR under TOLTS)
Increasing the Number of VTOCs on a Pack
Exercising Disks
(pointer to Hardware Diagnostic Aids)
Adopting Segments
Evacuating a Physical Volume
| PART VII. MAINTAINING THE STORAGE SYSTEM HIERARCHY
Section 22 Setting Up the Hierarchy
Organizing Site Directories
>site
>ldd
>ddd
>Project_id
Setting Access to Parts of the Hierarchy
Section 23 Directory Salvaging
Directory Salvaging
Understanding How and When the Online Salvager Works
Salvaging the RPV Directory
When to Do a Directory Salvage
Section 24 Maintaining Master Directories
Creating a Master Directory
Changing the Owner of a Master Directory
Changing the Quota Account of a Master Directory
Adding Quota to a Master Directory
Removing Quota from a Master Directory
Getting Information About Master Directories
Salvaging Master Directory Control Segments
Reregistering a Master Directory
MTB-656, Revision 1
Section 25 Recovering the Hierarchy
Finding Damaged Segments
Handling Connection Failures
Finding Quota Problems
Salvaging After a Crash
Volume Retrieving After a Crash
Hierarchy Retrieving After a Crash
Section 26 Retrieving for Users
Understanding User Retrievals
Deciding When to Do Which Kind of Retrieval
Deciding What Time of Day to Do Retrievals
PART VIII. MANAGING THE BACKUP SYSTEMS
Section 27 Choosing a Dumper
Understanding the Volume Dumper
Understanding the Hierarchy Dumper
Advantages and Disadvantages of Each Dumper
(Costs, Benefits, Mechanisms, Tailoring Options Available)
Choosing the Right Dumper(s) for Your Site
What Most Other Sites Do and Why
Deciding When Each Dumper Should Run
(Deciding What to Dump, When, and By Which Dumper)
Writing Exec Commands to Run Dumpers Automatically
Section 28 Volume Dumping
Setting Up the Volume Dumper
Registering Volume Dumper Daemons
Deciding How Many Tapes are Needed for the Volume Dumper
Deciding How Long Volume Dump Tapes Should Be Kept
Data Bases Used by the Volume Dumper
Setting Up a Volume Dump Control File
Understanding How the Volume Dumper Finds Things
Partitioning Volume Dumping
Managing a Volume Tape Pool (manage_volume_pool) |
Registering Tapes for the Volume Backup System |
Deregistering Tapes for the Volume Backup System |
Managing Volume Dumper Segments
Managing Volume Reload Groups
Handling Errors While Volume Dumping
MTB-656, Revision 1
Section 29 Hierarchy Dumping
Setting Up the Hierarchy Dumper
Registering Hierarchy Dumper Daemons
Deciding How Many Tapes are Needed for the Hierarchy Dumper
Deciding How Long Hierarchy Dump Tapes Should Be Kept
Data Bases Used by the Hierarchy Dumper
Seting Up a Hierarchy Dump Control File
Handling Errors While Hierarchy Dumping
PART IX. MANAGING RCPRM (I/O DISKS & TAPES)
Section 30 Managing RCP/RCPRM Operations
Understanding RCP
Understanding RCPRM
Managing Tapes
Authenticating Tapes
Registering Tapes Automatically
Preloading Tapes
Dealing With Foreign Tapes
Managing Disks
Understanding Disk Labels
Understanding Disk Authetication
Section 31 Maintaining Registries and Resources
Understanding Registries
Registering a Resource
Devices (Drives)
Attributes
Speed
Model
Densities
Type
Name
Unique Id
Potential Attributes
Potential Access Class
Access Class
ACS Pathname
Volumes
Type (automatic)
Name (automatic)
Unique Id (automatic)
MTB-656, Revision 1
Potential Attributes (str -priv, rgr)
Potential Access Class (str -priv, rgr)
Release Lock (str -priv, rgr)
Owner (str -priv, aqr)
Access Class (str -priv, aqr)
Attributes (str, rgr, aqr)
Allocation Flag (str, rgr, aqr)
ACS Pathname (str, rgr, aqr)
Registering a System Resource
Dealing With Automatic Registration
Changing a Resource's Registration/Setting its Attributes
Deregistering a Resource
Making Checkpoint Copies of Registries
Recovering/Reconstructing Registries
Deleting a Registry
Setting Access to a Resource
Replacing Missing Resource ACSs
PART X. MANAGING I/O DAEMONS
Section 32 Managing I/O Daemon Processes
Understanding the Coordinator Process
Understanding Driver Processes
What to Do When the Coordinator Process Cannot Be Initialized
Dealing With Fatal Errors During Driver Initialization
Section 33 Managing I/O Daemon Tables
Understanding the I/O Daemon Tables
iod_tables.iodt vs iod_tables vs iod_working_tables
Function
Format/Syntax
Sample
Modifying iod_tables.iodt
Defining Major Devices
Defining Minor Devices
Defining Device Classes (AIM)
Defining Local Devices
Defining Remote Devices
Defining Request Types
Defining Lines
Defining Driver Modules
Defining Attributes for tty Printer I/O Module
Converting iod_tables.iodt to iod_tables
MTB-656, Revision 1
Installing iod_tables
Displaying Contents of iod_tables
Displaying Contents of iod_working_tables
Creating I/O Daemon Queues
Section 34 Managing Devices and Request Types
Dealing With Local Devices
Dealing With Remote Devices
Dealing With Major and Minor Devices
Adding a New Device
Adding a New Request Type
Creating a New Queue for a New Request Type
Deleting a Request Type
Deleting an Obsolete Queue
Specifying a Control Terminal for a Local Device
Specifying a Control Terminal for a Remote Device
Using Preprinted Accountability Forms on a Control Terminal
Getting a List of Devices for Each Request Type
Getting a List of Logical line_ids and Associated
Communications Channels
Understanding Request Type Info Source Segments
Function
Format/Syntax
Sample
Creating a Request Type Info Source Segment
Converting a Request Type Info Source Segment to a Request
Type Info Segment
Displaying the Contents of a Request Type Info Segment
Section 35 Miscellaneous I/O Daemon Tasks
Printing the Contents of a Spooling Tape
Writing an I/O Daemon Operator Command
Modifying admin.ec to Add a New Command
Setting Up a Driver to Driver Message Facility
Setting Up Driver Mailboxes
Defining Commands for Driver Communication
Allowing the Driver to Accept Messages
Allowing the Driver to Send Messages
Allowing the Driver to Print Pending Messages
Section 36 Generating a Driver Process in Test Mode
Creating the Necessary Directories and Segments
Test Directory
rqt_info_segs Directory
MTB-656, Revision 1
card_pool Directory
iod_tables Segment
Message Segment Queues for Request Types
Special TTT
admin exec_coms
Setting Access to ACSs
Making Commands Aware of the Test Environment
Creating the Test Process
Testing a Remote Station
Terminating the Test
Setting Breakpoints
Sample exec_com for Setting Up and Running a Test
Environment
PART XI. DEALING WITH FAILURES
Section 37 Recognizing System Failures
Understanding Symptoms of System Failure
Interpreting User Phone Calls
Understanding the Ways in Which Multics Can Crash
Reading Processor Lights (MAD_002, updated for DPS 8)
Section 38 Responding to System Failires
Deciding When to Execute Fault
Deciding When to Execute Switches
Resetting the Answering Service
Knocking the Initializer Out of a Loop (MAD_009)
Section 39 Recovering from System Failures
Deciding When to Perform ESD
Recovering From ESD Failure (MAD_008)
Setting Up a Procedure for Cleaning Up Incremental Backup
Tapes
Dumping the System (MAD_012)
Dumping the Initializer Process (MAD_012)
Processing an FDUMP (MAD_012)
Copying an FDUMP
Printing an FDUMP
What to Do if the Clock Jumps
Recovering from a Bad Clock Setting
MTB-656, Revision 1
Section 40 Performing Unusual Recovery Procedures
Dumping Main Memory
Patching Main Memory
Saving Main Memory
Saving the DUMP Partition
Clearing Memory Parity Errors
Section 41 Dealing with NonSystem Failures
Recognizing an FNP Failure
Dumping an FNP
Reloading an FNP
Recognizing an MPC Failure
Reloading MPC Firmware
PART XII. SPECIAL OPERATIONS
Section 42 Managing User Logins, Logouts, and Channels
Setting the Message of the Day
Setting the Maximum Number of Users Who Can Log In
Deciding When a User Should Be Logged Out
Accepting a Terminal Device Channel
Controlling Communications Channels
What to Do When an FNP Masks a Channel
Using the Message Coordinator to Accept a Terminal
Using the Message Coordinator to Handle a Hung-up Terminal
Section 43 Managing the Absentee Facility
Starting the Absentee Facility
Stopping the Absentee Facility
Setting the Number of Absentee Slots
Stopping an Absentee Queue
Restarting an Absentee Queue
Moving an Absentee Job From One Queue to Another
Setting the Highest Numbered Queue Which Will Be Serviced
Bumping an Absentee Job
Deferring an Absentee Job
Suspending an Absentee Job
Releasing an Absentee Job
Forcing an Absentee Job to Log In Next
Getting Information About Absentee Jobs
MTB-656, Revision 1
Section 44 Reconfiguration/Splitting the System
Understanding Reconfiguration
Adding a Processor
Deleting a Processor
Adding Memory
Deleting Memory
Splitting the System
Recovering from Reconfiguration Failures
PART XIII. MONITORING THE SYSTEM
Section 45 Reading System Logs
Reading the Syserr Log
Reading the Answering Service Log
Monitoring the Answering Service Log
Section 46 Checking System Status
Getting Information About
RCP
Load Control
File System
Message Coordinator
Hardcore
Section 47 Using System Diagnostic Aids |
(brief description -- mostly a pointer to AR97) |
*
PART XIV. TUNING (MAD_003) (Metering Manual)
Section 48 Reading the Meters
Writing Metering Commands and Subroutines
Extracting Metering Information
Reporting Metering Information
Understanding Metering Data Bases
SST
tc_data
Understanding Different Types of Metering Time
What to Look for in Metering Output (Threshhold Values to
MTB-656, Revision 1
Watch For)
Understanding How Users Are Using the System
Analyzing Your Load
Using Metering Exec_Coms
Device Meters
Disk Meters
Disk Queue
File System Meters
Interrupt Meters
List Vols
Post Purge Meters
Total Time Meters
Traffic Control Meters
Traffic Control Queue
VTOC Buffer Meters
| Communications Metering (pointer to Section 8 of
| Communications Reference Manual)
Section 49 Tuning
Tuning Guidelines
Configuration Guidelines
| Estimating What Resources are Needed to Meet Your Load
| Level
| Configuring Resources to Achieve Optimum Performance
| and Availability (including software resources, e.g.,
| sty channels)
| Locating Bottlenecks
Changing Hardware
Changing Configuration
Changing Static Table Sizes
Changing Dynamic Tuning Parameters
Changing Workload
Changing Process Directory Volumes
How To Know When You Need More Hardware
Figuring Out Where Performance Gains Can Be Made
Section 50 Managing the Master Group Table
Understanding the Master Group Table (MGT)
Function
Format/Syntax
Sample
Modifying the MGT
Installing a New MGT
MTB-656, Revision 1
PART XV. HELPING OPERATORS AND USERS
Section 51 Helping Operators
Replacing Our Exec Commands With Yours
Writing New Exec Commands
Adding Exec Commands to admin.ec
Managing the Message Coordinator for Operators
Creating Help Files for Operators
Setting Up an Operator Message Facility
Section 52 Helping Users
(e.g., Figuring Out Why a User Can't Log In)
PART XVI. ANALYZING MULTICS DUMPS AND TERMINATED PROCESSES
TBD (separate research project required) (MAD_012)
PART XVII. MAINTAINING THE ADMINISTRATIVE SUBSYSTEM
Section 53 Maintaining Administrative Exec_coms
(Including Up-to-date, Annotated Samples of Each One)
make_sys_seg.ec
shift_config_change.ec
master.ec
biller.ec
err.ec
util.ec
fnp_crash_notify.ec
Section 54 Recovering Administrative Data Bases
System Administrator Table (SAT)
Master Group Table (MGT)
Project Master File (PMF)
Project Definition Table (PDT)
Person Name Table (PNT)
User Registration File (URF)
Resource Type Master File (RTMF)
MTB-656, Revision 1
Resource Type Description Table (RTDT)
Channel Master File (CMF)
Channel Definition Table (CDT)
Terminal Type File (TTF)
Terminal Type Table (TTT)
I/O Daemon Tables
Billing Segments (>udd>sa>a)
billing_footnote
disk_stat
miscfile
PDTs (safe_pdts)
projfile
reqfile
today.use_totals
Salvaging the Mail Table
PART XVIII. MAINTAINING SYSTEM LIBRARIES
Section 55 Understanding System Libraries
Understanding the Standard Library
>ldd
Executable Directories
>t
>sss
>unb
>sl1
>am
>obs
Understanding Site-Specific Library Organization
>site
>site_ldd
Section 56 Managing Installations
Installing Code in Site Libraries
Source
Object
Installing Executable Code in System Libraries
Section 57 Managing the Firmware Library
Understanding IFAD Tapes
Loading IFAD Tapes
Listing IFAD Tapes
MTB-656, Revision 1
Understanding the tandd_deckfile
Making New IFAD Information Available to CSD
Section 58 Managing the Hardcore Library
Understanding the Hardcore Library (>ldd>hardcore)
How the Hardcore Library is Organized
MSTs
Understanding the Hardcore Header
Creating a Site Hardcore Library
Making a MST
Section 59 Making System Changes
Modifying System Software
Modifying the System Message Table
Installing Critical Fixes
GLOSSARY
INDEX
MTB-656, Revision 1
APPENDIX C
This appendix offers an outline of the Multics Project
Administration Procedures manual. Specific suggestions on the
outline are welcome, especially those related to recipes that may
be missing.
MULTICS PROJECT ADMINISTRATION PROCEDURES
Section 1 Introduction
How To Use This Manual
Manual Conventions
Other Manuals of Interest
Section 2 The Project Administration Environment
Understanding the Environment
Understanding the Division of Control Between SAs and PAs
Software Overview & Definition of Terms
Section 3 Registering a Project
Filling Out a Requisition (if required)
Filling Out a Project Registration Form (if required)
Filling Out an Initial List of Users Form (if required)
Deciding How Much Disk Space Your Project Needs (Initial
Quota)
* Deciding on Spending Limits
| Understanding the System Default start_up.ec
| (>sc1>start_up.ec)
| Writing a Project Default start_up.ec
| (>udd>[user project]>start_up.ec)
Section 4 Managing the Project Master File
Understanding the Project Master File (PMF)
Function
Format/Syntax
Sample
Modifying the PMF
Specifying Login and Load Control Attributes
Specifying Spending Limit Attributes
Specifying Special Environment Attributes
MTB-656, Revision 1
Understanding SAT Limits
Recovering the PMF if You Delete it By Mistake
Understanding the Project Definition Table (PDT)
Converting the PMF to a PDT
Installing the PDT
Printing the Contents of the PDT
Section 5 Registering a User
Organizing Users on a Project
Registering a New User
Modifying the PMF
Converting the PMF to a PDT
Installing the PDT
Filling Out a Person Registration Form (if required)
Registering an Anonymous User
Deleting a User *
Section 6 Tailoring the User Environment
General
Restricting User to Limited Service Subsystem (LSS)
Restricting User CPU Consumption
Replacing Standard Command System Interface
Isolating User Within Closed Subsystem
Creating Separate Accounting for Anonymous Users
Creating Additional User Identification Procedures
Creating Specialized Accounting Procedures
Using Special Terminal Devices
Extending the User Environment
Specific
Writing a Process Overseer Procedure
Writing a project_start_up.ec |
Writing a LSS Control Segment
Section 7 Managing Load Control Groups and Work Classes
Getting Information About Load Control Groups
Getting Information About Work Classes
Specifying Primary and Secondary Users
Specifying Preemption and Grace
Specifying Load Control Groups for Individual Users
Section 8 Managing Resources
Deciding How to Allocate Resources Among Project Users
Moving Storage System Quota
MTB-656, Revision 1
Monitoring Project Resource Usage
Getting Information About User Disk Usage
Getting Information About Directory Quota Usage
Reporting Resource Usage
Section 9 Using a Logical Volume
Understanding Logical Volumes
Understanding Quota Accounts
Understanding Master Directories
What You Can Do With a Logical Volume
Allocating Logical Volume Quota
Creating a Quota Account (svq)
Changing the Quota Available in a Quota Account (svq)
Deleting a Quota Account (dlvq)
Setting the Owner of a Master Directory (smdo)
Setting the Quota Account of a Master Directory (smda)
Getting Information
get_dir_quota
list_mdir
Section 10 Using a Quota Account
What You Can Do With a Quota Account
Creating a Master Directory (cd -lv)
Deleting a Master Directory (dd)
Setting the Quota on a Master Directory (smdq)
| Section 11 Project Administration Commands
GLOSSARY
INDEX
MTB-656, Revision 1
APPENDIX D
This appendix offers an outline of the Multics
Communications Reference Manual. Specific suggestions on the
outline are welcome, especially those related to recipes that may
be missing.
MULTICS COMMUNICATIONS REFERENCE MANUAL
Section 1 Introduction
How to Use This Manual
Manual Conventions
Other Manuals of Interest
Pointers to the Programmer's Reference Manual and the System
Maintenance Procedures Manual
Section 2 The Communications System
Understanding the Communications System
Terminals
Communications Channels
FNPs
Controllers/Adapters
Subchannels
Multiplexed Channels
Channel Names
Initialization
Consistent Configuration
Terminal Types
Line Types
Communications Links
Modems
Communications Protocols
Automatic Baud Rate Detection
Channel Management (FNP)
Terminal Management (User_ring and Supervisor)
Section 3 The Channel Master File
Understanding the Channel Master File (CMF) (MAD_004)
Function
Format/Syntax
Defaults
MTB-656, Revision 1
Sample
Modifying the CMF
Changing FNP Entries
Changing Channel Entries
Assigning Line Types to Channels
Understanding the Channel Definition Table (CDT)
Converting the CMF to a CDT
Installing the CDT
Displaying the Contents of the CDT
Displaying Information About Communications Channels Defined
in CDT
Section 4 Communications Channels
Modifying the Channel Configuration
Changing the CDT
Reloading the Multiplexer
Adding a Channel
Deleting a Channel
Changing the Status of a Channel
Changing the Attributes of a Channel
Changing the Service Type of a Channel
Attaching a Channel
Detaching a Channel
Removing a Channel
Section 5 Multiplexers
Adding a Multiplexer
Deleting a Multiplexer
Changing the State of a Multiplexer
Stopping a Multiplexer
Starting a Multiplexer
Reloading a Multiplexer
Writing an fnp_crash_notify.ec
Section 6 The FNP Core Image
Understanding the FNP Core Image
Required Modules
Optional Modules
Modifying the FNP Core Image
Changing the Contents of an FNP Module
Editing the Source Segment
Producing the Object Segment
Extracting Unchanged Object Segments from the
Object Archive
MTB-656, Revision 1
Understanding the Bindfile
Modifying the Bindfile
Binding
Using the New Core Image
Section 7 The Terminal Type File
Understanding the Terminal Type File (TTF)
Function
Format/Syntax
Sample
Modifying the TTF
Assigning Terminal Types to Channels
Adding a New Terminal Type
Changing a Terminal Type
Understanding the Terminal Type Table (TTT)
Converting the TTF to a TTT
Installing the TTT
Changing AIM Attributes for Terminals
Section 8 Metering
Getting Metering Information
About Communications Channels
About System Terminal Usage
About FNP Idle Time
About FNP Character Throughput
About Ring Zero Multics Communications Management
Section 9 Miscellaneous
Setting the Minimum Size of X.25 "Long" Packets
Displaying the Contents of Ring Zero Data Bases
Using the Comunications System Memory Configurator
Figuring Out Space Requirements in tty_buf
For Static Storage
For Dynamic Storage
Section 10 Setting Up System-Supplied Multiplexers
HASP Workstations and Hosts
Understanding the HASP Communications Protocol
Modifying the FNP Core Image
Defining HASP Channels
Defining HASP Terminal Types for Channels
Defining HASP Terminal Types for Subchannels
MTB-656, Revision 1
IBM3270 Terminals
Understanding an IBM3270 Terminal System
Typing Conventions (*)
raw3270 Mode (*)
Modifying the FNP Core Image
Defining IBM3270 Channels
Defining IBM3270 Terminal Types for Channels
Defining IBM3270 Terminal Types for Subchannels
Polled VIP Terminals
Understanding a VIP Terminal Subsystem
Input Size Considerations (*)
Function Codes (*)
Quits (*)
Formfeeds (*)
End of Page (*)
Blank Lines (*)
Tabs (*)
Circumflex and Tilde (*)
Dialups and Hangups (*)
Modifying the FNP Core Image
Defining Polled VIP Channels
Defining Polled VIP Terminal Types for Channels
Defining Polled VIP Terminal Types for Subchannels
Software Simulated Terminals
Understanding Software Simulated Terminals
Defining Software Simulated Channels
Defining Software Simulated Terminal Types for Channels
X.25 Network Connections
Understanding Networks
Hardware Requirements
Software Requirements/Link Level
Software Requirements/Packet Level
Software Requirements/Terminal Control Level
Modifying the FNP Core Image
Defining X.25 Network Channels
Defining a Special TTF
Connecting to a Foreign System Through a Protocol Converter
Mapping the Terminal Type to the Foreign System (*)
Defining Channels with a Protocol Converter
(*) = information aimed at users which should be moved to
Programmer's Reference Manual.
Section 11 Security
TBD
MTB-656, Revision 1
GLOSSARY
INDEX