1
page 1
1 Preface
SECTION 1 - INTRODUCTION
1
page 2
1.1 Introduction
This manual describes how to install the "PLATO Lesson
Delivery and Authoring System" application on your operating
system.
If the PLATO application media you ordered requires an
upgrade of your operating system, we assume that that
upgrade has already been installed. This guide will only
discuss the PLATO application installation.
This manual has been written for system analysts and
Engineering Services personnel who have a working knowledge
of the hardware and software involved, including information
in the operating system reference manual, the operating
system operator's guide and the operating system analysis
handbook.
Other documentation for the PLATO application may be found
in the following publications.
PLATO Operations Guide SMD 133345
PLATO Installation Guide SMD 133346
PLATO Configuration Handbook SMD 133347
PLATO Software Release Bulletin SMD 133348
The Operations Guide for the PLATO application contains
operations information. The installing analyst should read
the "PLATO Overview" section of the Operations Guide before
starting the installation.
The Configuration Handbook for the PLATO application contains
information on setting up the configuration parameters which
are referenced in this manual.
The PLATO Software Release Bulletin for a particular release
contains last-minute information about installations. This
document should be read before beginning the installation.
Any conflicts between information contained in the SRB and
the Installation Guide should be resolved in favor of the
SRB.
1
page 3
1.2 Operating System Compatibility
Since the PLATO application is delivered as binaries which
have been assembled for a specific level of the operating
system, you must make sure that the PLATO Release you are
installing is compatible with your operating system.
Releasing the PLATO software as binaries on multiple levels
of the operating system requires that there be different
versions of the release materials. These different versions
are assembled for a specific NOS level and are not interchangable.
For example, the PLATO Release 43 for NOS 2.7.1 level 739
will not run on NOS 2.7.1 level 750 and vice versa. If you
are running PLATO Release 43 under NOS 2.7.1 level 739 and
wish to upgrade your operating system, but continue to use
the same PLATO Release, you must reorder the installation
materials and reinstall the PLATO application.
Each new PLATO Release will run under the most current level
and the two most recent past levels of the operating system.
Refer to the following charts for a presentation of the
operating system and hardware dependencies of PLATO releases.
PLATO Release Level History
Release 41 of the PLATO application software was released
under NOS 2.5.2 level 678, NOS 2.5.3 level 688 and NOS 2.6.1
level 700.
Release 42 of the PLATO application software was released
under NOS 2.5.3 level 688, NOS 2.6.1 level 700 and NOS 2.7.1
level 716.
Release 43 of the PLATO application software was released
under NOS 2.6.1 level 700, NOS 2.7.1 level 716 and NOS 2.7.1
level 739.
Release 44 of the PLATO application software was released
under NOS 2.7.1 level 716, NOS 2.7.1 level 739 and NOS 2.7.1
level 750.
1
page 4
1.2.1 Operating System Dependency Chart
----------------------------------------------------------
: :
: PLATO - OPERATING SYSTEM DEPENDENCY :
: :
----------------------------------------------------------
: PLATO Release : R41 : R42 : R43 : R44 :
----------------------------------------------------------
: : : : : :
: OPERATING SYSTEM LEVEL : : : : :
: : : : : :
: NOS 2.5.2 - 678 : X : : : :
: NOS 2.5.3 - 688 : X : X : : :
: NOS 2.6.1 - 700 : X : X : X : :
: NOS 2.7.1 - 716 : : X : X : X :
: NOS 2.7.1 - 739 : : : X : X :
: NOS 2.7.1 - 750 : : : : X :
: : : : : :
----------------------------------------------------------
1
page 5
1.2.2 Hardware Dependency Chart
----------------------------------------------------------
: :
: PLATO - HARDWARE DEPENDENCY :
: :
----------------------------------------------------------
: PLATO Release : R41 : R42 : R43 : R44 :
----------------------------------------------------------
: : : : : :
: MAINFRAMES : : : : :
: : : : : :
: CYBER 17x : X : X : X : X :
: CYBER 170-700 : X : X : X : X :
: CYBER 180-810 : X : X : X : X :
: CYBER 180-815 : X : X : X : X :
: CYBER 180-825 : X : X : X : X :
: CYBER 180-830 : X : X : X : X :
: CYBER 180-835 : X : X : X : X :
: CYBER 180-840 : X : X : X : X :
: CYBER 180-845 : X : X : X : X :
: CYBER 180-850 : X : X : X : X :
: CYBER 180-855 : X : X : X : X :
: CYBER 180-860 : X : X : X : X :
: CYBER 180-865 : : : : :
: CYBER 180-875 : : : : :
: CYBER 180-960 : : X : X : X :
: CYBER 180-990 : X : X : X : X :
: : : : : :
----------------------------------------------------------
: : : : : :
: DISK SUBSYSTEMS : : : : :
: : : : : :
: 7155-401/885-42 (DB) : : : : :
: 7165/895 (DC) : : X : X : X :
: 7255/834 (DD) : X : X : X : X :
: 887 (DF / DH) : : : : :
: 7255/836 (DG) : X : X : X : X :
: 7x5x/844-21 (DI) : X : X : X : X :
: 7x5x/844-41/-44 (DJ) : X : X : X : X :
: 7152/7154/844-21 (DK) : X : X : X : X :
: 715x/844-41/-44 (DL) : X : X : X : X :
: 7155/885 (DM / DQ) : X : X : X : X :
: 819 (DV / DW) : : : : :
----------------------------------------------------------
1
page 6
1.2.3 Operating system changes
The following section describes changes in the past several
NOS releases which have required changes to the operation
or installation of the PLATO application. This is included
to inform analysts performing an upgrade installation or
reinstallation of the PLATO application of important changes
in operational procedures.
The following information highlights those NOS changes
which may have the greatest impact on the PLATO application.
Rather than duplicate other documentation on NOS, it
describes areas of significance and cites references for
further information.
The most informative documents addressing NOS changes
are the following:
NOS Software Release Bulletin (SRB)
NOS Feature Notes
NOS V2 Installation Handbook (IHB)
NOS V2 Operations Handbook (OHB)
NOS V2 Analysis Handbook (AHB)
CHANGES FOR NOS 2.5.2 LEVEL 678
There were no operating system changes which required changes
in the operation of the PLATO application for this level.
CHANGES FOR NOS 2.5.3 LEVEL 688
There were no operating system changes which required changes
in the operation of the PLATO application for this level.
CHANGES FOR NOS 2.6.1 LEVEL 700
There were no operating system changes which required changes
in the operation of the PLATO application for this level.
CHANGES FOR NOS 2.7.1 LEVEL 716
There were no operating system changes which required changes
in the operation of the PLATO application for this level.
CHANGES FOR NOS 2.7.1 LEVEL 739
There were no operating system changes which required changes
in the operation of the PLATO application for this level.
CHANGES FOR NOS 2.7.1 LEVEL 750
1
page 7
There were no operating system changes which required changes
in the operation of the PLATO application for this level.
1
page 8
1.3 Organization
This Installation Guide is organized as follows:
1. Introduction
2. New system installation procedures.
Procedures to be used when initially installing
the PLATO Lesson Delivery and Authoring System.
3. Optional installation procedures.
Procedures to be used to install optional features
of the PLATO application.
4. Update installation procedures.
Procedures to be used to upgrade the PLATO Lesson
Delivery and Authoring System from one full release
to another (e.g., from Release 38 to Release 39).
5. "Mini-release" installation procedures.
Procedures to be used to upgrade the PLATO Lesson
Delivery and Authoring System to correct critical
problems (e.g., from Release 39.1 to Release 39.2).
6. Reinstallation procedures.
Procedures to be used to reinstall the same PLATO
Release on a new operating system level.
7. PLATO Bill of Materials.
A description of the components of the PLATO Lesson
Delivery and Authoring System.
The following convention is used in describing computer
console commands.
- upper-case letters indicate terms to be entered
exactly as given
- lower case letters indicate terms which vary from
system to system, and which should be replaced with
values applicable to your system.
1
page 9
1.4 Installation Materials
As part of your installation package, you will receive two
copies of the Operations Guide and the Configuration Hand-
book. You will also receive the following:
TAPE FILE
VSN No. CONTENTS
PLAT1A 1 Installation procedures
INSTALL
UPGRADE
LOADMF
BKSPRU
2 Release binaries for the PLATO application
3 Release submit file (PLATOD)
4 Release configuration file
5 Release procedure MFNX
6 Release procedure MFDX
7 Release procedure SETPUN
8 Release procedure Z1DAILY
9 Release procedure Z1ENDBC
10 Modifications to NOS to support the PLATO
application
11 Modifications to NAM to support the PLATO
application
12 Modifications to CCP to support the PLATO
application
13 Modifications to RHP to support the PLATO
Inter-system Link
14 LIBDECK entries for PLATO application
15 Terminal resident load files
16 PLATO load procedures
17 PLATO PSR reports
18 Empty file
PLAT2A 1 System lesson master file (part 1)
2 Empty file
PLAT2B 1 System lesson master file (part 2)
2 Empty file
PLAT2C 1 New installation master file "newins"
2 Empty file
(Sent to new installations only, not to
sites updating existing software)
1
page 10
1.5 Where to Start
Check to make sure that you have all the materials you will
need for the installation. Read the entire PLATO Software
Release Bulletin, including any addenda. Then,:
a) if you are performing a new system installation, begin
with the "New System Installation Procedures" section.
b) if you are performing an upgrade installation from one
PLATO Release to another (for example, from R43 to R44),
begin with the "Update Installation Procedures" section.
c) if you are performing a "mini-release" installation (for
example, from R44.1 to R44.2), begin with the "Mini-Release
Installation Procedures" section.
d) if you are reinstalling the same PLATO Release on a new
operating system level, begin with the "Reinstallation
Procedures" section.
1
page 11
2 New System Installation Procedures
SECTION 2 - NEW SYSTEM INSTALLATION PROCEDURES
1
page 12
2.1 Introduction
This section describes how to install the PLATO application
for the first time.
The following information will be asked of you during
the installation procedures:
- Your system routing identifier (RID).
This is a unique identifier which has been assigned to
your system by Control Data Software Manufacturing and
Distribution. You will find your RID on the CDC tape
label affixed to each of your tapes. The RID will be
the last three characters of the "Customer Name"
section of the tape. For example:
CUSTOMER NAME CFN NUMBER
SMITH COMPMNA 9315-00042222
In this example, the system RID is "MNA".
- Your computer hardware configuration.
This information will be used to determine installation
procedures.
For future reference, keep this information with your PLATO
Operations guide. It will also be required should you have
to call or write for help with the PLATO application and
when you order updates for the PLATO application.
1
page 13
The following is a list of the steps to be taken to install
the PLATO application. Each of these steps is discussed in
detail in the following sections.
1. Determine disk system configuration.
2. Create PLATO system user name(s).
3. Obtain files from installation tape.
4. Modify the ASCII network.
a. Modify network configuration file.
b. Reinstall NAM and CCP.
5. Reinstall selected NOS programs.
6. Modify system deadstart file text records.
7. Modify release procedure files.
a. PLATO configuration file
b. Submit file PLATOD
c. MFNX
d. MFDX
e. SETPUN
f. Z1DAILY
g. Z1ENDBC
8. Build new deadstart file.
9. Initialize ESM.
10. Deadstart on new deadstart file.
11. Load PLATO master files.
12. Create binary master file.
13. Load PLATO via PLAINS DSD-command.
14. Initialize system files.
a. Installation parameters
b. EM allocation tables
c. System groups
d. Notes files
e. Bulletin board
f. Central print options
g. AIDS package
h. AUTHORS package
15. Install optional features.
16. Execute post-installation cleanups.
a. Delete "install" from group "p".
b. Run account cleanup programs.
c. Purge installation-only files.
d. Convert master files.
1
page 14
17. Install published courseware.
18. Dump all master files.
19. Reload PLATO via PLATO DSD-command.
1
page 15
2.2 Determine disk system configuration.
Before beginning the installation of the PLATO Lesson Authoring
and Delivery application, you must decide how the disk packs
to be used for the PLATO application will be defined.
The NOS V2 Installation Handbook, the NOS V2 Reference Manual
Volume 3 and the NOS V2 Analysis Handbook have information on
how the disk system can be configured.
The default disk system configuration uses the default family
devices. All release procedures are already configured for
this disk system configuration.
If you wish to use an alternate family for all PLATO files,
you will have to modify the release procedures. Each affected
section will describe the changes which need to be made if you
are using an alternate family for all PLATO files.
You may also use either the default family or an alternate
family for the PLATO application, but place the PLATO master
files on auxilary devices. Each affected section will describe
the changes which need to be made if you are using auxiliary
devices for the PLATO master files.
1
page 16
2.3 Create PLATO system user name(s).
Before you can create the PLATO system user name(s), the NOS
validation files must be created.
If you are using the default family for PLATO files, these
validation files were created during the installation of the
operating system.
If you are using an alternate family for PLATO files, the
NOS validation files for the family must be created. This
may be done by entering the following commands on the computer
console:
X.DIS.
FAMILY(family name)
GENVAL.
DROP.
To add required user names when using the default family,
enter the following command on the computer console.
X.MODVAL.
Or, if you are using an alternate family device for PLATO
files, enter the following command on the computer console.
X.MODVAL(FM=fnam,OP=K)
The MODVAL job will then request the K-display. You must
assign this display to the job by the following procedure.
1. Find the job which is requesting the K-display on
the console B-display.
2. Note the job sequence number (JSN) of the job. This
is a four character identifier for the job.
3. Enter the following command on the computer console.
K,jsn.
Using the MODVAL options documented in the NOS Administration
Handbook, create the following user names. Suggested names
are given, but any legal NOS user name may be used.
1. A user name for PLATO system tasks (usually "sys").
2. A user name for PLATO print jobs (usually "prints").
Give both user names all possible privileges (AW=ALL) and
maximum resource limits (RL=ALL). The validation mask
parameter for these user names must be set to allow them to
submit system service class jobs (VM=ALL). The user index
for these user names must be less than "auimx" (377700b).
1
page 17
The PLATO application also requires the user names PLATOMF
and SYSTEMX. These user names were automatically created
when the operating system was installed.
The passwords for user names PLATOMF and SYSTEMX are needed
later in this procedure. They were set to "platomf" and
"systemx", respectively, when the user names were created.
User name PLATOMF is used when loading the PLATO master files.
You must set the maximum resource limits (RL=ALL) for this
user name.
Once these steps have been completed, you will next obtain
the PLATO application files from the installation tape.
1
page 18
2.4 Obtain files from installation tape.
This step will load the files which make up the PLATO
application from the first installation tape.
Mount the first installation tape (the one labeled PLAT1A)
on an available tape drive. Make sure the tape drive is
available by checking the console E,T-display.
Enter the following commands on the computer console:
X.DIS.
FAMILY(family name) if using alternate family
USER(sys,password) sys is the system user name
created in the previous step
LABEL(TAPE,VSN=PLAT1A)
GTR(TAPE,INSTALL)PROC/INSTALL
BEGIN(INSTALL,INSTALL,PPW=ps1,SPW=ps2)
where ps1 = password for user name PLATOMF
(default = "platomf")
ps2 = password for user name SYSTEMX
(default = "systemx")
This procedure creates the following files.
User sys: PLABINS PLATO release binaries
PLATOD PLATO submit file
CONFIG PLATO configuration file
MFNX procedure to attach master files
MFDX procedure to dump master files
SETPUN procedure to set PLATO user name
Z1DAILY procedure to copy PLATO account
summaries to disk
Z1ENDBC procedure to copy PLATO account
summaries to tape
PLANOS modifications to NOS
PLANAM modifications to NAM
PLACCP modifications to CCP
PLARHP modifications to RHP
LIBDIR LIBDECK entries for PLATO programs
PSRREP PLATO PSR reports
LOADMF procedure to load installation
master files
BKSPRU program used to load installation
master files
User PLATOMF: ISTLF00 terminal resident load file
ISTLF01 terminal resident load file
ISTLF03 terminal resident load file
ISTLF08 terminal resident load file
User SYSTEMX: PLATO PLATO load procedure
PLAINS PLATO load procedure
PLAUPD PLATO load procedure
1
page 19
The following empty files are also created.
User PLATOMF: AUDIT
AUDITX
BACKDIR
COMBUF
DUMPDIR
S0BACKC
User SYSTEMX: RAFMON
See the PLATO Bill of Materials section for more information
about these files.
You will next modify the ASCII network to support the PLATO
application.
1
page 20
2.5 Modify the ASCII network.
It is assumed that NAM and CCP or CDCNET have already been
installed on any system which will be using the PLATO ASCII
Network. It is also assumed that the NAM configuration files
(Network Definition Language (NDL) files) have been initialized
so that terminals may be logged into NAM.
This section describes changes which may be needed to the
NAM configuration to allow the use of the PLATO application.
2.5.1 Modify network configuration file.
Make changes to the NAM network definition configuration
file as described below:
IST terminals are defined as type TTY (tc=m33).
CDC-721 (Viking) terminals are defined as type 721
(tc=721).
Micro-computers used as PLATO terminals are defined as
type TTY (tc=m33).
In order to allow IST and Viking terminals to automatically
load their resident, "pappl" must be set to "plato"
("pappl=plato"). You must also set "mfam" and "muser"
for IST terminals. If you fail to do this, the resident
load sequence will be hung up at the NAM/NVF prompts for
family/user name. In addition, for IST terminals, you
cannot enable auto-recognition. Refer to the sample NDL
file below for an example.
Ensure that the NOS user names specified for the
"muser" and "duser" parameters in the NDL source file,
are validated for the "plato" application via MODVAL.
If you are running on NOS 2.5.1 level 664 or higher,
these user names must also have the concurrent access
(CACA) and disable personal ID (COPI) bits set in the
access word (AW) parameter of the validation file via
MODVAL.
1
page 21
2.5.1.1 Sample NDL file.
For more information on the NDL and NDL Processor, refer to
the NAM Network Definition Language Reference Manual.
A sample program using NDL is shown below. In this example,
it is assumed that a NOS user name of "namnet" exists and
is validated for access only to application "plato".
In order for automatic loading of the terminal resident to
occur, that line must have "pappl" set to "plato".
Only the Viking Terminal is supported at 9600 baud.
ncffile: nfile.
comment plato network definition.
comment these defines describe the various ways to define
comment a port and terminal to the plato/nam interface..
platl12: define tiptype=async,lspeed=1200.
platl24: define tiptype=async,lspeed=2400.
platl48: define tiptype=async,lspeed=4800.
platl96: define tiptype=async,lspeed=9600.
pnitty: define tc=m33,pri.
comment. beginning of first npu...npu0..
comment. node number for npu is any unique number.
npu0: npu node=5,variant=np1,dmp=yes.
suplink llname=link0.
comment. node number for coupler is any unique number, but
comment. must match the node number specified for the 2550
comment. equipment definition in the eqpdeck.
cplr0: coupler node=2,hname=host1.
link0: loglink ncname=npu0.
comment. port number for cla must match the physical
comment. address on the cla.
cla0: group port=01,ltype=a2,platl12,ni=1.
pni0a: termdev pnitty.
cla0: group port=02,ltype=a2,platl48,ni=1.
pni0a: termdev pnitty.
cla0: group port=03,ltype=a2,platl12,ni=9.
pni0a: termdev pnitty.
cla0: group port=0c,ltype=a2,platl96,ni=1.
pni0a: termdev pnitty.
cla0: group port=0d,ltype=a2,platl12,ni=2.
pni0a: termdev pnitty.
lcffile: lfile.
1
page 22
plauser: define mfam=0,muser=namnet,pappl=plato.
plato: appl.
comment. user defined for npu0.
pni0a01: user plauser.
pni0a02: user plauser.
pni0a03: user plauser.
pni0a04: user plauser.
pni0a05: user plauser.
pni0a06: user plauser.
pni0a07: user plauser.
pni0a08: user plauser.
comment etc.
1
page 23
2.5.1.2 Sample CDCNET Configuration file
For more information on CDCNET Configuration, refer to the
CDCNET Network Configuration and Site Administration Guide.
A sample system configuration file is shown below. In this
example, it is assumed that the system is running on only
one MTI (Mainframe/Terminal device Interface) unit.
"plato mti configuration file"
defs " define_system " ..
sn=mti_plato cs=true
defos " define operator support "
..
deffs " define_file_support " ..
ft = all ..
defrlg " define_recorder_log_group "
defslg " define_source_log_group " ..
chaslg " change_source_log_group " ..
chaslg " change_source_log_group " ..
defsam " define_source_alarm_message " ..
defntg " define network products interactive gateway" ..
t = (plato) ..
deft " define_tip " ..
tn = async ..
defl l=0,p=0,tn=async,ar=s,cct=20,cdt=20,tup=plato,ln=cdcn00
defl l=0,p=1,tn=async,ar=s,cct=20,cdt=20,tup=plato,ln=cdcn01
defl l=0,p=2,tn=async,ar=s,cct=20,cdt=20,tup=plato,ln=cdcn02
defl l=0,p=3,tn=async,ar=s,cct=20,cdt=20,tup=plato,ln=cdcn03
defl l=1,p=0,tn=async,ar=s,cct=20,cdt=20,tup=plato,ln=cdcn10
defl l=1,p=1,tn=async,ar=s,cct=20,cdt=20,tup=plato,ln=cdcn11
defl l=1,p=2,tn=async,ar=s,cct=20,cdt=20,tup=plato,ln=cdcn12
defl l=1,p=3,tn=async,ar=s,cct=20,cdt=20,tup=plato,ln=cdcn13
defl l=2,p=0,tn=async,ar=s,cct=20,cdt=20,tup=plato,ln=cdcn20
defl l=2,p=1,tn=async,ar=s,cct=20,cdt=20,tup=plato,ln=cdcn21
defl l=2,p=2,tn=async,ar=s,cct=20,cdt=20,tup=plato,ln=cdcn22
defl l=2,p=3,tn=async,ar=s,cct=20,cdt=20,tup=plato,ln=cdcn23
defl l=3,p=0,tn=async,ar=s,cct=20,cdt=20,tup=plato,ln=cdcn30
defl l=3,p=1,tn=async,ar=s,cct=20,cdt=20,tup=plato,ln=cdcn31
defl l=3,p=2,tn=async,ar=s,cct=20,cdt=20,tup=plato,ln=cdcn32
defl l=3,p=3,tn=async,ar=s,cct=20,cdt=20,tup=plato,ln=cdcn33
defl l=4,p=0,tn=async,ar=s,cct=20,cdt=20,tup=plato,ln=cdcn40
defl l=4,p=1,tn=async,ar=s,cct=20,cdt=20,tup=plato,ln=cdcn41
defl l=4,p=2,tn=async,ar=s,cct=20,cdt=20,tup=plato,ln=cdcn42
defl l=4,p=3,tn=async,ar=s,cct=20,cdt=20,tup=plato,ln=cdcn43
defl l=5,p=0,tn=async,ar=s,cct=20,cdt=20,tup=plato,ln=cdcn50
defl l=5,p=1,tn=async,ar=s,cct=20,cdt=20,tup=plato,ln=cdcn51
defl l=5,p=2,tn=async,ar=s,cct=20,cdt=20,tup=plato,ln=cdcn52
defl l=5,p=3,tn=async,ar=s,cct=20,cdt=20,tup=plato,ln=cdcn53
defl l=6,p=0,tn=async,ar=s,cct=20,cdt=20,tup=plato,ln=cdcn60
defl l=6,p=1,tn=async,ar=s,cct=20,cdt=20,tup=plato,ln=cdcn61
defl l=6,p=2,tn=async,ar=s,cct=20,cdt=20,tup=plato,ln=cdcn62
defl l=6,p=3,tn=async,ar=s,cct=20,cdt=20,tup=plato,ln=cdcn63
defl l=7,p=0,tn=async,ar=s,cct=20,cdt=20,tup=plato,ln=cdcn70
1
page 24
defl l=7,p=1,tn=async,ar=s,cct=20,cdt=20,tup=plato,ln=cdcn71
defl l=7,p=2,tn=async,ar=s,cct=20,cdt=20,tup=plato,ln=cdcn72
defl l=7,p=3,tn=async,ar=s,cct=20,cdt=20,tup=plato,ln=cdcn73
2.5.1.3 Sample CDCNET NDL local config
In order for automatic loading of the terminal resident to
occur, the line names defined with the "ln" parameter on the
CDCNET system configuration "define_line" statement, should
match lines defined in your NDL local definition configur-
ation file.
A sample program using NDL is shown below. In this example,
it is assumed that a NOS username of "namnet" exists and
is validated for access only to application "plato".
lcffile: lfile.
title plato system local definitions.
plauser: define mfam=0,muser=namnet,mappl=plato.
netou: appl,kdsp,rs,priv.
netfs: appl,kdsp,rs,priv.
netls: appl,rs,priv.
nlterm: appl,kdsp.
initmdi: appl,kdsp.
plato: appl.
comment. incalls for cdcnet jobs
incall fam=0,uname=netops,aname=netou,dbl=2,abl=2,
dbz=2000,ubz=20,ubl=7.
incall fam=0,uname=netops,aname=netls,dbl=2,abl=2,
dbz=2000,ubz=20,ubl=7.
incall fam=0,uname=netops,aname=netfs,dbl=7,abl=7,
dbz=2000,ubz=20,ubl=7.
incall fam=0,uname=netops,aname=nlterm,dbl=7,abl=7,
dbz=2000,ubz=20,ubl=7.
cdcn000: user plauser.
cdcn010: user plauser.
cdcn020: user plauser.
cdcn030: user plauser.
cdcn100: user plauser.
cdcn110: user plauser.
cdcn120: user plauser.
cdcn130: user plauser.
cdcn200: user plauser.
cdcn210: user plauser.
cdcn220: user plauser.
cdcn230: user plauser.
cdcn300: user plauser.
cdcn310: user plauser.
cdcn320: user plauser.
cdcn330: user plauser.
cdcn400: user plauser.
1
page 25
cdcn410: user plauser.
cdcn420: user plauser.
cdcn430: user plauser.
cdcn500: user plauser.
cdcn510: user plauser.
cdcn520: user plauser.
cdcn530: user plauser.
cdcn600: user plauser.
cdcn610: user plauser.
cdcn620: user plauser.
cdcn630: user plauser.
cdcn700: user plauser.
cdcn710: user plauser.
cdcn720: user plauser.
cdcn730: user plauser.
end.
An example of a Terminal User Procedure (modified to work
with PLATO) is shown below. Notice that the procedure name
is the same as the terminal user procedure parameter (tup)
on the "define_line" statement in the system configuration
file.
2.5.1.4 Sample CDCNET User Procedure
"TUP CONFIGURATION FILE"
PROC PLATO
"TC3 CONFIGURATION TEMPLATE"
" This Terminal Class 3 (TC3) Terminal User Procedure (TUP) template "
" should be used to configure the following types of terminals- "
" CDC721 "
chata " change_terminal_attributes " ..
bc = BS ..
" backspace_character " ..
" " ..
" Specify the character to be treated " ..
" as a backspace. " ..
cfc = TRUE ..
" character_flow_control " ..
" " ..
" Indicate if the tip should regulate the " ..
" flow of input and output through the use " ..
" of the XOFF and XON characters. " ..
clc = CAN ..
" cancel_line_character " ..
" " ..
" Specify the character to be treated " ..
" as a cancel input line if followed " ..
" by an EBC or ELC. " ..
1
page 26
crd = 0 ..
" carriage_return_delay " ..
" <0 to 999> " ..
" Units of milliseconds to send NUL " ..
" characters to a terminal device " ..
" after a carriage return. " ..
crs = CR ..
" carriage_return_sequence " ..
" " ..
" Sequence of characters to be sent " ..
" to the terminal whenever a carriage " ..
" return is required. " ..
e = FALSE ..
" echoplex " ..
" " ..
" Specify if the received characters must be" ..
" echoed to the terminal device. " ..
elc = CR ..
" end_line_character " ..
" " ..
" Specify the end of line character. " ..
elp = LFS ..
" end_line_positioning " ..
" <NONE,CRS,LFS,CRSLFS> " ..
" Specify the cursor positioning " ..
" action to be performed after an " ..
" end_line_character has been " ..
" received. " ..
epc = LF ..
" end_partial_character " ..
" " ..
" Specify the end of partial character. " ..
epp = CRS ..
" end_partial_positioning " ..
" <NONE,CRS,LFS,CRSLFS> " ..
" Specify the cursor positioning " ..
" action to be performed after an " ..
" end_partial_character has been received. " ..
2.5.1.5 Sample CDCNET User Procedure
ffs = FF ..
" form_feed_sequence " ..
" " ..
" Sequence of characters to be sent to the " ..
" terminal whenever a form feed action is " ..
" required. " ..
fl = FALSE ..
" fold_line " ..
" " ..
" Indicate if output lines that are " ..
" longer than the page_width must be " ..
" folded by the TIP (versus the " ..
" terminal). " ..
hp = FALSE ..
1
page 27
" hold_page " ..
" " ..
" Indicate if page wait is to be " ..
" performed after transmission of a " ..
" full page of text. " ..
lfd = 0 ..
" line_feed_delay " ..
" <0 to 999> " ..
" Units of milliseconds to send NUL " ..
" characters to a terminal device " ..
" after a line feed action. " ..
lfs = LF ..
" line_feed_sequence " ..
" " ..
" Sequence of characters to be sent " ..
" to the terminal whenever a line " ..
" feed action is required. " ..
ncc = ('%') ..
" network_command_character " ..
" " ..
" Specify the character which causes " ..
" the user to enter into network " ..
" control or command sequences. " ..
p = EVEN ..
" parity " ..
" <ZERO,MARK,EVEN,ODD,NONE,IGNORE> " ..
" Specify the type of parity to be " ..
" checked on input or generated on " ..
" output. " ..
pl = 30 ..
" page_length " ..
" <0,2 to 255> " ..
" Specify the page length of the " ..
" device. " ..
pw = 80 ..
" page_width " ..
" <0,10 to 255> " ..
" Specify the page width of the " ..
" device. " ..
sa = DISCARD ..
" status_action " ..
" <SEND,S,HOLD,H,DISCARD,D> " ..
" Specify whether unsolicited status should " ..
" be held, sent or discarded. "
puts s=' '
puts s='One moment...Connecting to PLATO'
puts s=' '
crec sn=plato cn=plato
PROCEND PLATO
1
page 28
2.5.2 Reinstall NAM and CCP.
If you are using only CDCNET, you do not need to do anything
with CCP as discussed in this section. You still may need
to reinstall NAM.
Inspect the contents of files PLANAM and PLACCP under the
PLATO system user name. If either of these files contains
modsets, it will be necessary to reinstall NAM and CCP
with these modsets. Refer to the NOS Installation Handbook
for instructions.
The PLATO application requires only the standard asynchronous
TIP in the CCP build procedure.
Save any modsets in PLANAM and PLACCP so they may be used
again if NAM and CCP must be reinstalled in the future.
You will next reinstall selected NOS programs.
1
page 29
2.6 Reinstall selected NOS programs.
Inspect the contents of file PLANOS under the PLATO system
user name. If this file contains modsets, it will be
necessary to reinstall the affected programs with these
modsets. Refer to the NOS Installation Handbook for more
information.
By looking at the contents of this file, determine what NOS
programs will need to be reassembled. Only the programs
which have modifications will need to be reassembled.
Be sure that, any time in the future, when these programs
are reassembled, that these modifications are included.
Save the binaries produced for replacement on your deadstart
file after all the PLATO materials are ready to be installed.
Save any modsets in PLANOS so they may be used again if the
affected NOS programs must be reinstalled in the future.
You will next modify the system deadstart file text records.
1
page 30
2.7 Modify deadstart file text records.
The system deadstart file text records are used to define
the configuration of your computer and its equipment and
the operating system.
You must make changes to the following deadstart text records
to allow the PLATO application to function correctly.
CMRDECK
EQPDECK
LIBDECK
IPRDECK
This can be done using O26 or some other text editor available
on your system. Instructions for using O26 may be found in
the NOS V2 System Programmer's Instant manual.
Save the modified text records for replacement on your dead-
start file after all the PLATO materials are ready to be
installed.
Refer to the section titled "Deadstart File" in the PLATO
Configuration Handbook for descriptions of the specific
changes which must be made.
The following examples assume you are using O26 as the text
editor and that you are using the following copies of the
text records: CMRD02, EQPD02, LIBD02, IPRD00. The NOS
Installation Handbook should be used to determine which text
records should actually be used for your system.
Example: Modifying a text record.
X.DIS.
FAMILY(family name) if using alternate family
USER(sys,password)
COMMON(SYSTEM)
GTR(SYSTEM,EQPDECK)TEXT/EQPD02
O26.
READ.EQPDECK.
* make required changes.
DIS.
SAVE(EQPDECK)
Example: Inserting PLATO entries into LIBDECK.
X.DIS.
FAMILY(family name) if using alternate family
USER(sys,password)
GET(LIBDIR)
COMMON(SYSTEM)
GTR(SYSTEM,LIBDECK)TEXT/LIBD02
REWIND(*)
SKIPEI(LIBDECK)
COPYBR(LIBDIR,LIBDECK)
1
page 31
PACK(LIBDECK)
SAVE(LIBDECK)
You will next modify the release procedure files.
1
page 32
2.8 Modify release procedure files.
The following files have been created under the PLATO system
user name.
CONFIG
MFDX
MFNX
PLATOD
SETPUN
Z1DAILY
Z1ENDBC
These files may require changes depending on the configuration
of your system. You may use O26 or any other text editor
available on your system to make these changes.
The following procedure may be used to modify these files.
X.DIS.
FAMILY(family name) if using alternate family
USER(sys,password)
GET(file name)
O26.
READ.file name.
* make required changes.
DIS.
REPLACE(file name)
The following sections describe the changes which may be
required for each of these files.
1
page 33
2.8.1 PLATO configuration file
The following changes to your PLATO configuration file are
required. Refer to the PLATO Configuration Handbook for
more information on the configuration file entries.
1. Change the "rid" entry to the routing identifier
assigned to your system by Control Data. See the
section titled "Required Information" for instructions
on how to determine your routing identifier.
2. You should change the "sid" entry to a name you
wish your system to be known by. This name may be
a string of any alphanumeric characters of up to
seven characters.
3. If you did not use "sys" as the PLATO system user
name, you must change the "subun" entry to the user
name actually used.
4. If you did not use "prints" as the PLATO print job
user name, you must change the "prtun" entry to the
user name actually used.
5. If you are using an alternate family for PLATO files,
you must change the "famly" entry to the family name
used.
The following changes to your PLATO configuration file are
recommended, but are not critical to the installation
procedure. These changes may be made now or at a later time.
1. If your mainframe is not a CYBER 180-810, you should
change the "cpspd" entry to the recommended value
for your mainframe.
1
page 34
2.8.2 Procedure MFDX
This procedure is used by the "backups" file dump procedure
to copy master files to tape or disk. See the PLATO Operations
Guide for more information on this procedure.
Initially, this procedure is set up to dump master files
SYS1I and NEWINS.
This file initially contains the following:
.PROC,MFDX,VSN=.
.*
IFE($VSN$ .EQ. $$, DUMPB)
.*
COPYMF(NA,V,MF=SYS1I)
COPYMF(NA,V,MF=NEWINS)
.*
ELSE(DUMPB)
.*
COPYMF(NA,V=VSN,MF=SYS1I)
COPYMF(NA,V=VSN,MF=NEWINS)
.*
ENDIF(DUMPB)
.*
REVERT. MFDX COMPLETE
.*
SKIP(NEXT1)
EXIT.
** ERRORS IN MFDX
WAIT. MFDX ABORTED
REVERT,ABORT. MFDX ABORTED
ENDIF(NEXT1)
The release procedure uses the system default tape density.
If you wish to use a different density for master file dumps,
you must add the "D" parameter to each of the COPYMF commands.
Refer to the PLATO Operations Guide for information on using
this parameter.
1
page 35
2.8.3 Procedure MFNX
This procedure file is called by the MASTOR job to attach
all required PLATO master files.
Initially, this file is set up to attach master files SYS1I,
NEWINS, and BINARY. These files will be loaded from the
installation tapes or created in later steps of this
installation procedure.
This file initially contains the following:
.PROC,MFNX,M=R.
.*
.* ATTACH PLATO MASTER FILES
.*
SETPUN. SET PLATO USER NAME
.*
ATTACH(BINARY/:M=M)
+ -
ATTACH(SYS1I/:M=M)
+ -
ATTACH(NEWINS/:M=M)
+ -
.*
REVERT.
The character ":" is the PLATO division sign or the
+ -
NOS equivalence symbol. It is produced under O26 by
using an upper case 0 (zero).
If you are using an alternate family for PLATO master files,
you must add a FAMILY command to this procedure.
If you are using auxiliary devices for PLATO files, you must
add the appropriate RESOURC and PACKNAM commands to this
procedure.
1
page 36
2.8.4 Submit file PLATOD
This file contains calls to the CCL procedures on the system
deadstart file which initiate the PLATO application jobs. The
release file contains the following.
NORERUN.
PLATX(CP=$+1$) PLATO
FRAMX(CP=$+2$) FORMATTER
PNIX(CP=$+3$) PNI
CONDX(CP=$+4$) CONDENSOR
EXIT.
The "CP" argument of each procedure call indicates which
control point is occupied by that PLATO job relative to the
control point specified on the ENABLE,PLA entry you have
added to the IPRDECK.
The release submit file assumes that you have used a low-
numbered control point for the ENABLE,PLA IPRDECK entry. If
you wish to use a high-numbered control point, you should
modify the submit file to read as follows:
NORERUN.
PLATX(CP=$-1$) PLATO
FRAMX(CP=$-2$) FORMATTER
PNIX(CP=$-3$) PNI
CONDX(CP=$-4$) CONDENSOR
EXIT.
Since the field length of the condensor is dynamic, it is
best to keep it as the last control point to prevent storage
moves for the other control points.
The release submit file assumes there are four contiguous
control points available following the control point specified
by the ENABLE,PLA IPRDECK entry. If this is not the case,
you should modify the PLATO submit file to skip control
points which are occupied by subsystems or change the control
point assignments of other subsystems so there are four
contiguous control points available.
1
page 37
2.8.5 Procedure SETPUN
This procedure file is called by several PLATO load jobs
to set the PLATO user name, PLATOMF.
Initially, this procedure uses the default password which
was placed on user name PLATOMF when it was created and
the default family.
This file initially contains the following:
.PROC,SETPUN,PW=PLATOMF,FM=.
.*
.* SET PLATO USER NAME.
.*
IFE(OT.NE.SYO,ORIGIN)
REVERT,ABORT.
ENDIF(ORIGIN)
.*
USER(PLATOMF,PW,FM)
.*
REVERT.
If you are using a different password for user name PLATOMF
or are using a different family, you must change the default
values in the procedure header line to the actual values you
are using. This is necessary because the PLATO load jobs
call this procedure without parameters. Whenever you change
the password for user name PLATOMF, you must also change this
procedure so the PLATO load jobs will continue to work.
1
page 38
2.8.6 Procedure Z1DAILY
This procedure file is used by the PLATO Account Summaries
option under "system options" in lesson "accounts". Refer
to the "Usage Tracking" section of the PLATO Operations Guide
for more information.
Initially, this procedure is set up to do the bare minimum
of copying the reformatted data from dataset "z1data" to a
NOS file under the default family, user name SYSTEMX, and
the default system pack. If you wish customize this procedure
for your site's needs, you should do so now.
This file initially contains the following:
.PROC,Z1DAILY*I.
WAIT(3)
SETTL(*)
SETASL(*)
RFL(100000)
.IF,OT.EQ.SYO,Z1DAY1.
* JOB IS SYSTEM ORIGIN
SUI(377777)
PACKNAM.
ATTACH(Z1ACNT/M=A,WB)
SKIP,Z1DAY2.
EXIT.
WAIT.Z1DAILY FAILED, DO *DAYFILE,JSN.*
REVERT,ABORT. FILE *Z1ACNT* MISSING
ENDIF,Z1DAY2.
* READ THE PLATO DATASET *Z1DATA*
PF(DAT,Z1DATA,Z1DATA,1,*,320D)
PACK(Z1DATA)
* APPEND NEW INFO TO END OF NOS FILE
SKIPEI(Z1ACNT)
COPYEI(Z1DATA,Z1ACNT)
UNLOAD(*)
REVERT. *Z1DAILY* COMPLETE
.ELSE,Z1DAY1.
WAIT.Z1DAILY WAS NOT RUN, DO *DAYFILE,JSN.*
REVERT,ABORT. PROCEDURE *Z1DAILY* FAILED
.ENDIF,Z1DAY1.
1
page 39
2.8.7 Procedure Z1ENDBC
This procedure file is used by the PLATO Account Summaries
option under "system options" in lesson "accounts". Refer
to the "Usage Tracking" section of the PLATO Operations Guide
for more information.
Initially, this procedure is set up to do the bare minimum
of copying the month's worth of PLATO account summaries to
tape, making a copy of Z1ACNT into OZ1ACNT, then reinitializing
the current file (Z1ACNT) to prepare it for the next month.
If you wish customize this procedure for your site's needs,
you should do so now.
This file initially contains the following:
.PROC,Z1ENDBC*I.
WAIT(3)
SETTL(*)
SETASL(*)
RFL(100000)
.IF,OT.EQ.SYO,Z1END1.
* JOB IS SYSTEM ORIGIN
SUI(377777)
PACKNAM.
ATTACH(ZZZZZZ1=Z1ACNT/M=R,WB)
SKIP,Z1END2.
EXIT.
WAIT.Z1ENDBC FAILED, DO *DAYFILE,JSN.*
REVERT,ABORT. FILE *Z1ACNT* MISSING
ENDIF,Z1END2.
NOEXIT.
RESOURC(PE=1)
SET(R1=1)
WHILE,R1.NE.0,CPYTP1.
SET(EF=0)
WAIT.MOUNT A PLATO ACCOUNT SUMMARIES TAPE.
BLANK(VSN=Z1ACNT,D=PE)
LABEL(TAPE,VSN=Z1ACNT,D=PE,F=I,L=$PLATO/Z1ACNT$,PO=FW,W)
REWIND(ZZZZZZ1)
COPYEI,ZZZZZZ1,TAPE,V,R.
UNLOAD(TAPE)
.IF,EF.EQ.0,CHKEF.
SET(R1=0)
.ELSE,CHKEF.
***************************************
* ERROR--TAPE MAY BE BAD. *
***************************************
WAIT.TAPE MAY BE BAD, DO *DAYFILE,JSN.*
.ENDIF,CHKEF.
ENDW,CPYTP1.
ONEXIT.
UNLOAD(*)
* SAVE OLD COPY ON DISK
PURGE(OZ1ACNT/NA)
CHANGE(OZ1ACNT=Z1ACNT)
1
page 40
* CREATE NEW Z1ACNT FOR NEXT MONTH
DEFINE(Z1ACNT)
REVERT. *Z1ENDBC* COMPLETE
.ELSE,Z1END1.
WAIT.Z1ENDBC WAS NOT RUN, DO *DAYFILE,JSN.*
REVERT,ABORT. PROCEDURE *Z1ENDBC* FAILED
.ENDIF,Z1END1.
You will next build a new deadstart file.
1
page 41
2.9 Build new deadstart file.
Build a new deadstart file which includes the following:
1. The NAM which was reinstalled with the modsets in
file PLANAM, if any were present.
2. The NOS programs which were reinstalled with the
modsets in file PLANOS, if any were present.
3. The CMRDECK, EQPDECK, LIBDECK and IPRDECK which
were modified earlier in this procedure.
4. The files CONFIG, MFNX, MFDX, SETPUN, Z1DAILY, and
Z1ENDBC which were loaded from the installation tape
and modified earlier in this procedure.
5. The PLATO release binaries which were loaded from
the installation tape earlier in this procedure.
The following is a sample procedure which could be used to
build the deadstart file.
X.DIS.
FAMILY(family name) if using alternate family
USER(sys,password)
COMMON(SYSTEM)
ATTACH(nam binary file)
ATTACH(nos binary file)
GET(CMRDECK)
GET(EQPDECK)
GET(LIBDECK)
GET(IPRDECK)
GET(CONFIG)
GET(MFNX)
GET(MFDX)
GET(SETPUN)
GET(Z1DAILY)
GET(Z1ENDBC)
ATTACH(PLABINS)
UNLOAD(DIR)
NOTE(DIR,NR).*FILE nam binary file
NOTE(DIR,NR).*FILE nos binary file
NOTE(DIR,NR).*FILE CMRDECK
NOTE(DIR,NR).*FILE EQPDECK
NOTE(DIR,NR).*FILE LIBDECK
NOTE(DIR,NR).*FILE IPRDECK
NOTE(DIR,NR).*FILE CONFIG
NOTE(DIR,NR).*FILE MFNX
NOTE(DIR,NR).*FILE MFDX
NOTE(DIR,NR).*FILE SETPUN
NOTE(DIR,NR).*FILE Z1DAILY
NOTE(DIR,NR).*FILE Z1ENDBC
NOTE(DIR,NR).*FILE PLABINS
PACK(DIR)
1
page 42
REWIND(*)
LIBEDIT(P=SYSTEM,I=DIR)
REWIND(*)
* tape or disk
ASSIGN,xx,T,F=I. or INSTALL(NEW=EQxx)
COPY(NEW,T,V)
You will next initialize Extended Semiconductor Memory, if
your system is using it.
1
page 43
2.10 Initialize ESM.
The PLATO application on 17x or 170-700 series mainframes
uses either Extended Core Storage (ECS) or Extended Semi-
conductor Memory (ESM) to store lesson material. The 800
series mainframes use Unified Extended Memory (UEM). This
section is only applicable to systems which use ESM. Users
of other types of memory should go on to the next step.
ESM may be run in either ECS mode or ESM mode. You should
skip this section if you are using your ESM in ECS mode.
Sites which will be using ESM should read the section titled
"ESM Management" in the PLATO Configuration Handbook before
proceeding with the installation of the PLATO application.
ESM must be properly initialized using the following procedure
before the PLATO application can be run.
1. Deadstart the system WITHOUT an ESM equipment (DE or
DP) entry in the EQPDECK.
2. Create an indirect access file named ESMRM under
NOS user name SYSTEMX. This file is used to hold
the relocation memory map.
3. Enter "X.ESM." at the computer console.
4. Assign the K-display to the job.
5. Enter "K.CONFIG." at the console. This will initialize
the relocation memory to your current ESM configuration.
6. Enter "K.GO." at the console.
7. Re-deadstart the system WITH the ESM equipment in
the EQPDECK.
You will next deadstart with the new deadstart file created
earlier in this procedure.
1
page 44
2.11 Deadstart on new deadstart file.
You should now deadstart your system on the newly-created
deadstart file.
You will next load the release PLATO master files.
1
page 45
2.12 Load PLATO master files.
Use the PLATO procedure LOADMF to copy the PLATO master
files from the installation tapes to disk.
The formats of this procedure call are:
LOADMF(MF=mf) default family
LOADMF(MF=mf,FAMILY=fn) alternate family
LOADMF(MF=mf,PN=pn,R=dt) auxiliary device
where:
mf = master file name
fn = family name
pn = auxiliary pack name
dt = device type if PN argument is used
Mount each installation tape as it is requested via the
E,P-display.
Example: Default family.
If you are using the default family device for PLATO
master files, enter the following on the computer console.
X.DIS.
USER(sys,password)
GET(LOADMF)
LOADMF(MF=SYS1I)
* press "." to execute.
* wait for this to finish.
LOADMF(MF=NEWINS)
* press "." to execute.
* wait for this to finish.
DROP.
Example: Alternate family.
If you are using an alternate family device for PLATO
master files, enter the following on the computer console.
X.DIS.
FAMILY(family name)
USER(sys,password)
GET(LOADMF)
LOADMF(MF=SYS1I,FAMILY=family name)
* press "." to execute.
* wait for this to finish.
LOADMF(MF=NEWINS,FAMILY=family name)
* press "." to execute.
* wait for this to finish.
DROP.
1
page 46
Example: Auxiliary devices.
To load the PLATO master files onto an auxiliary device,
enter the following on the computer console.
X.DIS.
FAMILY(family name) if using alternate family
USER(sys,password)
GET(LOADMF)
LOADMF(MF=SYS1I,PN=pack name,R=device type)
* press "." to execute.
* wait for this to finish.
LOADMF(MF=NEWINS,PN=pack name,R=device type)
* press "." to execute.
* wait for this to finish.
DROP.
You will next create the binary master file.
1
page 47
2.13 Create binary master file.
Use the PLATO utility MFCREAT to create a binary master
file. See the PLATO Operations Guide for more information
about the MFCREAT utility.
The customary name for this master file is BINARY. If you
wish to use a different name, you must change the name of
the binary master file attached in procedure MFNX.
You should use the default size for this file for the
device type on which it is being created. If this causes
a track limit error, run the procedure again, using the SP
parameter of the MFCREAT command to create a smaller master
file.
Example: Default family.
X.DIS.
USER(PLATOMF,password)
PURGE(BINARY/NA)
MFCREAT(MF=BINARY,PT=BINARY)
DROP.
Example: Alternate family.
X.DIS.
USER(PLATOMF,password)
FAMILY(family name)
PURGE(BINARY/NA)
MFCREAT(MF=BINARY,PT=BINARY)
DROP.
Example: Auxiliary device.
X.DIS.
USER(PLATOMF,password)
PACKNAM(pack name)
PURGE(BINARY/NA,R=device type)
MFCREAT(MF=BINARY,PT=BINARY,DT=device type)
DROP.
You will next load the PLATO application.
1
page 48
2.14 Load PLATO via PLAINS.
You will now load the PLATO application via the PLAINS
DSD-command.
1. If your system is to use the PLATO ASCII network, NAM
must be brought up at this point.
2. Load the PLATO application by entering the following on
the computer console.
PLAINS.
When PLATO (job "PLA1") first comes up, the following
system dayfile message will be seen:
ERROR - SYSTEM ID .NE. ROUTING ID
SYSTEM ID =
ROUTING ID = *rid*
where "rid" is the routing identifier for your system as
set by the value of the "rid" configuration file keyword.
This message appears because the system routing identifer
has not yet been set. This will be done as the first step
of the system file initialization later in this procedure.
The following system dayfile message will also be seen:
SYSTEM *sid* NOT IN NETWORK TABLE
where "sid" is the name of your system you chose for
the value of the "sid" configuration file keyword.
This message appears because there is no entry in the
network system table for your system. This will be done
as the second step of the system file initialization
later in this procedure.
Following this message, another error message will be
seen:
(S0INIT) ERROR IN CWARE ACCESS COMMON
This message indicates that there is no published
courseware on the system. The file containing the
courseware access limit common will be delivered
with the first published courseware shipment. If no
published courseware is to be available on a system,
this message will be seen every time the application
is brought up. This message should be ignored.
You will next initialize PLATO system files.
1
page 49
2.15 Initialize system files.
During the following system file initialization, you will
be working with PLATO lessons which have been designed to
prompt you through their use. This prompting is accomplished
through the use of "arrows" where input is requested and
through function key prompts (such as NEXT, BACK, LAB, etc).
Some important ideas to keep in mind about function keys:
1. Function keys also have upper-case (shifted) versions
such as SHIFT-NEXT. These are produced by holding down
the SHIFT key and pressing the desired function key.
2. When entering data at an arrow, you usually must press
NEXT following the input, unless the data is only one
character in length (such as choosing an option on an
index or menu).
3. When entering data at an arrow which requires an extra
measure of caution (such as destroying a file), you may
be required to press SHIFT-HELP instead of NEXT.
4. NEXT usually takes you "forward" in a PLATO lesson while
BACK usually takes you "backward". SHIFT-NEXT and SHIFT-
BACK may take you forward or backward in larger jumps.
5. On many displays, the HELP key may be used to see a more
detailed description of available options.
6. The SHIFT-STOP key is used to exit from any lesson back
to the AUTHOR MODE display.
At this time, using a PLATO terminal, sign into the PLATO
application with the following sign-on information.
PLATO name: "install"
PLATO group: "p"
password: "install"
1
page 50
2.15.1 Installation parameters
Set system installation parameters.
1. Set the system identifier as follows:
a. Enter the lesson name "ipedit" on the AUTHOR MODE
display as shown in Figure 1a. Press DATA after
the name to begin execution of the lesson. This
procedure will be referred to as "executing lesson
"ipedit"" later in this document.
b. From the first display of options (shown in Figure
1b), choose the "Network management" option.
c. On the next display (shown in Figure 1c), choose the
"System Identifier" option.
d. Take note of the WARNING (as shown in Figure 1d) that
you are given regarding the assignment of the system
identifier. After reading the warning, press NEXT.
e. Set the System Identifier (RID discussed earlier).
It must match the "rid" PLATO configuration file
entry and must NEVER be changed after it has been
entered for the first time.
f. Once you have set the system identifier, press BACK
once to return to the "Network management" display
(Figure 1c).
2. Add your system to the network system table.
a. Choose the "System Table" option. This takes you to
the "Network System Table Management" display (Figure
1f).
b. Choose the "Add a new system to the table" option.
c. On the next display, enter your system name. This
must match the "sid" PLATO configuration file entry.
d. On the next display, choose the "Directly connected
by PCN" option. This is done so the AUTHORS database
may be used on your system.
e. On the next display (Figure 1e), choose the "routing
identifier" option and enter your system RID. This
must match the "rid" configuration file entry and
the system identifier entered in step 1 of this section.
f. Also on this display, choose the "Authors database
availability" option to toggle this flag to "on".
3. Return to the "Network System Table Management" index
(Figure 1f) and choose the "Update the EM copy of the
1
page 51
system table" option. Press SHIFT-HELP when instructed
to do so.
4. Now press BACK to return to the main index of
"Installation Parameters" ("ipedit") shown in Figure 1b
and set the remaining desired values. Most, if not all,
of the parameters should be adequate for the time being.
5. After setting all desired installation parameters, press
SHIFT-STOP to return to the Author Mode display.
You are now ready to initialize the EM allocation tables.
1
page 52
2.15.2 EM allocation tables
When your system is first brought up, two logical sites,
named "network" and "system", have already been created
with a minimum amount of extended memory allocated to them
to allow you to sign on and initialize the system files.
In this step, you will allocate additional extended memory
to logical site "network" for use by other users.
1. Execute lesson "allocate".
2. Choose the "Special Functions" option.
3. On the next display, choose the "Initialize EM Tables"
option.
4. Press SHIFT-HELP when requested.
5. When the initialization has completed, you will be
returned to the main index. Press SHIFT-STOP to leave
lesson "allocate".
You are now ready to initialize the system groups.
1
page 53
2.15.3 System groups
The following functional groups are to be considered for the
following steps.
p = Controllers
o = Operations
pso = Consultants
m = Communications
Add sign-ons as needed to these groups using the following
procedure.
NOTE
Be sure to add yourself to group "p".
1. Enter the name of the group you wish to edit on the
Author Mode display and press NEXT.
2. On the first display you see (Figure 2a), select the
"Roster operations" option by pressing NEXT.
3. On the Roster Operations display (Figure 2b), choose the
"Add someone to the roster" option.
4. You will be asked to choose the type of record you wish
to create (Figure 2c). Choose to create an "author" sign-on.
5. On the next display (Figure 2d), you will be asked to type
the name of the new author.
6. You will then be prompted for a password (twice, to make
sure you have entered it correctly), and an expiration
date.
7. Press DATA to edit this user's sign-on. You should see
a display resembling Figure 2e.
8. Choose the "choose allowable author OPTIONS" option.
You will be shown a display which will allow you to
press DATA to give the person all the options you have
(Figure 2f). Press DATA.
9. If you are editing group "o" or "p", press NEXT to return
to editing the sign-on. Otherwise, press BACK to add
another sign-on (step 5).
11. Choose the "SPECIAL options" from Figure 2e. You will see
a display similar to the one in Figure 2g.
12. Press the letter to "change batch jobs allowed flag" to
permit this user to submit batch jobs.
13. Next, press the letter to "change NOS user name/family".
1
page 54
14. At the first arrow, enter the NOS user name to be
associated with this user's sign-on. Customarily, it
is set to be the same as the "subun" PLATO configuration
file entry.
15. At the second arrow, either press NEXT or LAB to use the
family under which PLATO will normally submit jobs (as
specified by the "famly" configuration file entry), or
enter some other valid NOS family name.
16. Press BACK to return to Figure 2e.
17. If you are not editing group "p", press BACK to add
another new sign-on (beginning again at step 5) or press
SHIFT-STOP to return to the AUTHOR MODE display.
18. Choose the "Choose allowable author OPTIONS" option
again.
19. Select the "General Record Editing Options" option on
the next display (Figure 2f).
20. Turn the "set NOS user name" option ON if it is not
already ON by choosing the letter next to that option.
(See Figure 2h).
21. Press SHIFT-BACK, then BACK to return to Figure 2e.
22. On this display, press BACK to add another sign-on
(beginning again at step 5) or press SHIFT-STOP if you
are done.
You are now ready to initialize system notes files.
1
page 55
2.15.4 Notes files
User access to any of the following notes files may now be
changed if you do not wish to use the default access. These
notes files and their default access are discussed in the
PLATO Bill of Materials section of this document.
"announce"
"lessnotes"
"opsnotes"
"pbnotes"
"psonotes"
"sysln"
"s0sysmsg"
To change the access for a notes file, do the following:
1. Enter the name of the notes file you wish on the Author
Mode display and press NEXT.
2. From the main display of the notes file, press SHIFT-DATA
for the notes file director options.
3. If someone has used the director options before you, you
will see a display giving the information about who has
used an option. Press NEXT to go to the Director Options
display.
4. Press NEXT to inspect or change the access list.
5. You will now see a display titled "Notes Access Options"
(Figure 3a). Press NEXT to see or edit access for people
on the same system as the notes file.
6. On the "Local" system display (Figure 3b), enter the
group or account for which you wish to inspect or change
the access, and press NEXT.
7. On the next display, you may see a list of user types.
Choose the user type for which you wish to inspect or
change the access, and press NEXT. You may also choose
user type "Other" to edit the access for all unlisted
user types.
8. You will now have several options to grant privileges to
users of the notes file (Figure 3c). You may select upper
case (SHIFTed) letters to set the associated flags, or
you may press individual lower case letters corresponding
to the privileges you wish to grant.
9. When you are done changing the access list, press BACK
until you are at the main notes index. Then, press
SHIFT-STOP to return to the Author Mode display.
Follow this procedure for all of the notes files mentioned
above, if desired.
1
page 56
The option "to see all listed sign-ons" from the notes access
options index (Figure 3a) may be used to see all the sign-
ons that you have added to the access list.
Once you have completed this procedure for each file, if
desired, you will be ready to initialize the "Bulletin Board".
1
page 57
2.15.5 Bulletin board
Customize the PLATO Bulletin Board for your system.
1. Edit file "bullfile". If someone has edited this file
before you, you will see a display giving information
about who was the last editor of the file. Press NEXT
to begin editing the file.
2. Edit block "bull" by pressing the letter associated with
it.
3. Customize the Bulletin Board to suit your system.
It is not necessary to add any code to this file.
Simply add the text as you wish it to be displayed.
4. Return to the Author Mode display by pressing BACK.
You are now ready to initialize the central print options.
1
page 58
2.15.6 Central print options
This section describes how to customize the jobs submitted
through the central system print request lesson, "prints".
The jobs submitted by lesson "prints" are initially set to
use an upper case only print train. You will need to use
this procedure only if you wish to use a different print
train, or do something special with user-requested prints.
If you do not wish to change the default print types, go on
to the next step, customizing the AIDS package.
1. Edit file "prtsub".
2. Customize the procedures in the following blocks only
if you wish to do something special with prints. Other-
wise, you may continue with step 4.
- "upperlower" = upper/lower case prints
- "upper case" = upper case only prints
3. Press BACK until you have returned to the Author Mode
display.
4. Execute lesson "prints".
5. On the next display, you may see a message which says
"There are no prints to do". If this is the case, press
NEXT to go to the "Print Requests" options (Figure 4a).
Otherwise, you will see a page which shows options to
press SHIFT-DATA and SHIFT-LAB (Figure 4b). These options
are used when you are actually going to request a print,
and wish to use a different format from the default format.
On this display, press SHIFT-BACK for the "Print Requests"
options, as shown in Figure 4a.
6. If you wish to change the print train, choose the "Print
Log MAINTENANCE" option.
7. On the next display (Figure 4c), choose the "Setup Print
Types" option.
8. On the next display (Figure 4d), choose the print type
which you wish to change.
9. Enter a description of the print type.
10. Enter the names of the file and block to be submitted
for this print type.
11. When you are done entering print types, press BACK.
12. Now return to the Log Maintenance index (Figure 4c) and
customize any other desired parameters on the index.
You are now ready to customize the AIDS package.
1
page 59
2.15.7 AIDS package
You should edit the contents of the blocks in the following
"aids" files to contain specific information about your
system:
a0psoless
a0ss1
You are now ready to customize the AUTHORS package.
1
page 60
2.15.8 AUTHORS package
Create an AUTHORS database for your system as follows:
1. Execute lesson "authors". You will see a display
informing you that "authors" is turned off. On this
display, press SHIFT-DATA for the director options.
2. On the next display, you will see a message informing
you of a "FATAL error in lesson authors" which gives
the name of a file which does not exist. The following
procedure will create and initialize this file. On this
display, press SHIFT-NEXT to initialize the authors
database.
3. When asked about expected values for the database, the
numbers you enter are not critical at this time. They
may be changed later.
4. When the database initialization is complete, you will
be taken to the AUTHORS director options display. On
this display, press DATA for the system information
display.
5. You will be presented with four options which you may
change if desired. You MUST choose the second option
to toggle it to read "AUTHORS is on".
6. When you are done, press BACK twice to go to the main
"Directory of PLATO Authors" display.
7. Press SHIFT-STOP to return to the AUTHOR MODE display.
You are now ready to install optional features.
1
page 61
2.16 Install optional features.
There are several optional features which may or may not be
initialized depending on the resources available and the
desire for the feature. Some of these features are NOT
available on all systems.
These optional features may be installed during the initial
system installation or at any time afterward.
See the "Optional Installation Procedures" section for more
information and procedures to initialize these optional features.
If you do not wish to install any of these optional features
at this time, or, after completing the installation of all
desired optional features, you should continue with the Post-
Installation Cleanup, as described in the following section.
1
page 62
2.17 Execute post-installation cleanups.
The following cleanup procedures should now be executed:
- remove the installation signon record
- make sure all files are in the proper PLATO account
- purge installation-only disk files
- convert release PLATO master files
1
page 63
2.17.1 Delete "install" of group "p".
You should now delete sign-on "install" of group "p".
Follow these steps:
1. Sign off the system and sign back on with your own
sign-on in group "p".
2. Edit group "p".
3. Select "Roster Operations".
4. Select the "delete someone from the roster" option.
5. Enter the name "install" when asked what name to delete
and press SHIFT-HELP.
6. Press BACK until you have returned to the AUTHOR MODE
display.
1
page 64
2.17.2 Run account cleanup programs.
Run an account cleanup on all accounts on the system. This
procedure involves the following:
1. Execute lesson "accountu".
2. Choose the "update an account file name table" option.
3. Choose "b" for more processing time.
4. Press NEXT to build a new list of files.
5. After the list of files has been sorted, you will be
prompted for an account name. Press SHIFT-NEXT to
process all accounts.
6. Press SHIFT-HELP to start the process.
NOTE
The process can be very lengthy
depending on how many master files
are on your system.
7. When the word "DONE" appears, press SHIFT-STOP to return
to the Author Mode display.
1
page 65
2.17.3 Purge disk files.
The following NOS permanent files may be purged to save
space since they are needed only during the installation
process.
PLABINS PLATO release binaries
CONFIG PLATO configuration file
MFNX procedure to attach master files
MFDX procedure to dump master files
SETPUN procedure to set PLATO user name
Z1DAILY procedure to copy PLATO account
summaries to disk
Z1ENDBC procedure to copy PLATO account
summaries to tape
LIBDIR LIBDECK entries for PLATO programs
LOADMF procedure to load installation
master files
BKSPRU program used to load installation
master files
Enter the following commands on the computer console:
X.DIS.
FAMILY(family name) if using alternate family
USER(sys,password)
PURGE(PLABINS)
.
.
.
1
page 66
2.17.4 Convert master files.
These procedures are not critical. The PLATO application
will work correctly if these procedures are not done until
some time in the future.
You may want to rename your master files to use a naming
convention which is popular at other sites.
To rename master files SYS1I and NEWINS to SYSTEM and AMAST,
do the following:
1. Take the PLATO application down.
2. Execute the following job at the computer console.
X.DIS.
FAMILY(family name) if using alternate family
USER(PLATOMF,password)
PACKNAM(pack name) if using auxiliary devices
CHANGE(SYSTEM=SYS1I)
CHANGE(AMAST=NEWINS)
ATTACH(SYSTEM,AMAST/M=W)
MFALTER(MF=SYSTEM,N=SYSTEM)
MFALTER(MF=AMAST,N=AMAST)
DROP.
4. Change procedure MFNX on the current deadstart file to
change the master file names.
5. Change procedure MFDX on the current deadstart file to
change the master file names.
6. Make a new deadstart file with the changed MFNX and MFDX
procedures and reload the system with it.
7. Bring up the PLATO application.
8. Rename the master files in the required master files
table in lesson "ipedit".
9. Use program BACKMOD to rename the master files in the
list of master files to be dumped.
If you wish to expand the disk space available for user
files on your system, you may do one of the following:
- Add another required master file to your system. Refer
to the "Adding/Changing a Required Master File" section
of the PLATO Configuration Handbook for information on
how to do this.
- Use procedure MFPACK to increase the size of the existing
type general master file. This would permit you to
take better advantage of the capacity of the master file
1
page 67
directories. In order to do this, you may have to add
another disk pack to your system.
The following example assumes you have renamed master
file NEWINS to AMAST. The SP parameter given in the
example is the maximum size for a master file on an
834 (DD) device. If your master file is on a different
device type, use the maximum for that device given in
the section describing the MFCREAT command in the PLATO
Operations Guide.
1. Take the PLATO application down.
2. Increase the size of the master file by executing
one of the following jobs at the computer console.
Default family or alternate family:
X.DIS.
FAMILY(family name) if using alternate family
USER(PLATOMF,password)
MFPACK(MF=AMAST,N=AMAST,PT=GENERAL,SP=3680)
DROP.
Auxiliary devices:
X.DIS.
USER(PLATOMF,password)
MFPACK(MF=AMAST,N=AMAST,PN=pack name,
R=device type,NPN=new pack name,NR=new
device type,PT=GENERAL,SP=3680)
DROP.
You will next install published courseware.
1
page 68
2.18 Install published courseware.
The initial shipment of new courseware to your site will be
composed of any or all of the following courseware Categories:
Category I - Academic (Libraries A/B)
Category II - Authors Library
Category III - Educational (Libraries C/E/G/H/M and LDEC)
Category IV - Training (Libraries D/F/I/J/K/L)
The tapes containing the courseware will be labeled as follows:
Category I - cat1a / cat1b / cat1c / ...
Category II - cat2a / ...
Category III - cat3a / ...
Category IV - cat4a / ...
In addition, the initial shipment will include a site-specific
tape, whose label will correspond to the site name. It contains
the published courseware catalog (accessed by pressing shifted
"F" from the Author Mode display) and the file that holds the
courseware access limit for your site. This limit is the
maximum number of users who may simultaneously be accessing
published courseware. This tape also contains other course-
ware management work files.
NOTE: The courseware access limit will not take effect
until (1) the site-specific tape has been in-
stalled, and (2) the PLATO application has been
taken down and brought back up, since the limit
is read in and set only at that time. Until
then, nobody will be able to access any of the
courseware.
If your site has ordered courseware by title, rather than by
entire Categories, the initial shipment tapes tapes will be
labeled like the site-specific tape: "site1", "site2", etc.
For every tape received, there will be an accompanying
MFPRINT, listing all the files within that master file tape.
Regardless of the tape labels and the contents, each tape
contains a single, 2000-part master file. The method for
installing the courseware involves adding each master file
as a required master file and performing account clean up
procedures.
The following steps should be followed for all tapes EXCEPT
the site-specific tape, which should be installed as described
in the "Courseware Installation" section of the PLATO Operations
Guide after all other tapes have been installed. These steps
are described in more detail in the following sections.
a. Ensure sufficient disk space under NOS.
1
page 69
b. Copy all tapes to disk via MFTLOAD.
c. Use the procedure described in the "Changing a Required
Master File" section of the PLATO Configuration Hand-
book to change the master file name and the master file
type for all the newly-copied courseware master files.
d. Execute the "Search for duplicate files" option of
lesson "installu".
e. Execute the "Update account file name table" option of
lesson "accountu".
f. Execute the "Account directory and file checks" option
of lesson "accountu".
g. Execute the "Search for files not in an account" option
of lesson "accountu".
h. Install the site-specific tape as described in the
"Courseware Installation" section of the PLATO Operations
Guide.
2.18.1 Courseware installation - details
The following is a detailed explanation of each of the steps
described above:
a. "Ensure sufficient disk space under NOS."
A single disk part is 35 sectors, so each 2000-part
master file will occupy 70,000 sectors. The number of
free tracks required for each master file on each
supported device type is shown below. The following
table gives the number of free tracks assuming you are
using single-spindle devices. If you are using multi-
spindle devices, divide the required free tracks by the
number of spindles in the device to be used.
DC 144b tracks
DD 667b tracks
DG 175b tracks
DI 1217b tracks
DJ 465b tracks
DK 1161b tracks
DL 465b tracks
DM 156b tracks
DQ 156b tracks
If you received more courseware than there is room for
on your system, please contact your sales representative.
Your representative should then, in turn, call PLATO
Courseware Delivery to discuss the resolution of this
problem.
1
page 70
b. "Copy all tapes to disk via MFTLOAD."
Refer to the PLATO Operations Guide for details on how
to use MFTLOAD to copy master file tapes to disk.
c. "Use the procedure described in the "Changing a Required
Master File" section of the PLATO Configuration Hand-
book to change the master file name and the master file
type for all the newly-copied courseware master files."
Using MFALTER (refer to the PLATO Operations Guide for
details), change the master file names from names like
"cat1a", etc., to a name similar to others in use on
your system. Traditionally, the names "amast", "bmast",
etc., have been used. In addition, to ensure the proper
operation of your system, the first four (4) letters of
all master file names must be unique.
At the same time as each master file name is being
changed, its type should be changed to "general".
d. "Execute the "Search for duplicate files" option of
lesson "installu"."
The way the various Categories are built is such that
each of them is self-sufficient, as opposed to requi-
ring that a different Category also be installed. For
this reason, it is necessary to delete any duplicate
files that may exist on your system. The steps to
follow are:
1. Execute lesson "installu".
2. Select the "Search for duplicate files" option.
3. At the arrow, just press SHIFT-NEXT, to indicate
that all master files are to be searched.
You will then see each master file name displayed, and
every 64th file shown. Should a duplicate be encoun-
tered, you will be shown the information for each file
(account, last edit info, master file, length, etc.).
Based on that information, with primary consideration
of the last edit date/time and the master file of resi-
dence (the copy of the file on the earlier-numbered
master file will be the copy accessed by users), press
either SHIFT-HELP or SHIFT-DATA to delete one file or
the other.
Follow this procedure until all duplicate files have
been deleted, before proceeding to the next step.
2.18.2 Courseware installation - details
e. "Execute the "Update account file name table" option of
lesson "accountu"."
1
page 71
This step is performed to update the directories of all
accounts on the system so that they accurately represent
the file and space count for the files in each account.
The procedure to be performed is as follows.
1. Reload the PLATO application using the PLAINS
command or turn off file management options through
lesson "account1".
2. Execute lesson "accountu".
3. Choose the "Update an account file name table"
option.
4. Press "b" to indicate that processing is to be
done in "background" mode (gives more processing
time).
5. Press NEXT to "build a new list of files".
6. After the list is built and sorted, you will be
given the option to press SHIFT-NEXT to process
all accounts. Do so.
7. Press SHIFT-HELP to start the process. When com-
pleted, the screen will erase and the message
"DONE" will appear.
f. "Execute the "Account directory and file checks" option
of lesson "accountu"."
This option checks each file on the system, and
sets the published flag, if the account is published,
and resets the account ordinal in the file directory.
Before actually performing the steps, it might be of
use to press HELP from within this option to see the
list of features, followed by a list of the possible
errors and what to do in case of each.
The steps to be followed are:
1. From the index of "accountu", choose the "Account
directory and file checks" option.
2. Press "b" to indicate that processing is to be
done in "background" mode (gives more processing
time).
3. On the following display, choose the options as
follows:
File space computation? y
NL space computation? n
Directory pointer check? y
Log errors in datafile? y (see below)
1
page 72
Display errors on screen? n (see below)
NOTE: Since this process will take a long time,
it is assumed that you will not want to stand
by and wait for an error to be encountered, but
rather that you will examine the error log (file
"accerrlog") after processing, to see if any errors
were encountered.
4. When prompted for an account name, press NEXT
with no input, to indicate that all accounts are
to be processed.
5. You will then be given the choice of pressing NEXT
to begin processing or SHIFT-HELP to clear the
datafile. Press SHIFT-HELP.
When all accounts have been processed, the message
"COMPLETED" will be displayed. At that point, check
the log ("accerrlog") to see what kinds of problems
may have come up. To find out how to correct them,
refer back to the HELP sequence. If there were no
errors, looking at "accerrlog" will show that 0 blocks
are in use; otherwise, you will be given the option to
look through the file contents.
2.18.3 Courseware installation - details
g. "Execute the "Search for files not in an account" option
of lesson "accountu"."
This option involves going through each master file on
the system, and logging every file that does not appear
in the "list of files" prepared earlier. Seeing as the
existing files/accounts are all in accordance with each
other, the only files that show up in this search will
be those which indicate they are in non-existent accounts.
The steps to follow are:
1. Choose the "Search for files not in any account"
option from the main index of "accountu".
(From this point, you may wish to press HELP to
get a more detailed explanation of what this op-
tion does.)
2. Press "b" to indicate that processing is to be
done in "background" mode (gives more processing
time).
3. If you feel certain of the integrity of the
earlier-built list of files, press SHIFT-NEXT
to proceed; otherwise, press NEXT to build and
sort a new list.
4. Assuming that all problems previously logged in
1
page 73
"accerrlog" have been resolved, press SHIFT-HELP
when prompted to initialize the datafile.
You will then see a display where each master file name
will be plotted, and then every "offending" file name
shown, along with the alleged account name. Since the
displayed entries are being logged, there is no need to
watch/record the file names as they appear.
When processing is complete, the message "DONE" will be
displayed at the bottom of the display.
As indicated in the HELP sequence, problem files should
be moved into legitimate accounts via "account1".
h. "Install the site-specific tape as described in the
"Courseware Installation" section of the PLATO Operations
Guide."
This concludes the initial installation of courseware on
your system.
1
page 74
2.19 Dump all master files.
All master files should be dumped for protection against
disk problems happening before the first regularly scheduled
dump.
1
page 75
2.20 Reload PLATO via PLATO.
Take down the PLATO application as described in the Operations
section of the PLATO Operations Guide.
Bring the PLATO application back up by entering "PLATO."
at the computer console. This is the normal entry to bring
up the PLATO application when not doing a system installation
or upgrade. This will allow any users to sign in.
The installation of the PLATO Lesson Authoring and Delivery
1 application is now complete.
1
page 76
3 Optional Installation Procedures
SECTION 3 - OPTIONAL INSTALLATION PROCEDURES
1
page 77
There are several optional features of the PLATO Lesson
Delivery and Authoring System which may be initialized
depending on the resources available and the desire for
the feature. Some of these features are NOT available
on all systems.
These optional features may be initialized during the initial
system installation or at any time afterward.
See the following sections for more information and procedures
to initialize these optional features.
1
page 78
3.1 Archiving
Please read the section in the PLATO Operations Guide which
describes the Archiving Utility and its operation.
The archiving utilities are included in the software sent
to every system. To use this feature on your system,
install as follows:
1. Set the warning and deletion cycles for archive files
as follows:
a. Execute lesson "ipedit".
b. Choose option "archive recycle period".
c. Enter settings as desired.
d. Press SHIFT-STOP to exit "ipedit".
2. Create file "s0archds" according to the specifications
given in the PLATO Bill of Materials section of this
document.
3. Execute lesson "archiver". It will prompt for
initialization when executed the first time. Press
SHIFT-NEXT to initialize.
4. Enable the archive feature as follows:
a. Execute lesson "account1".
b. Choose "file backup and archive options".
c. If archiving is currently disallowed, choose the
option to "allow archiving".
Before an account can use the archiving utility, it must
be assigned "archive rights". See the PLATO Operations
Guide for instructions on how to do this.
1
page 79
3.2 Backups
Please read the section in the PLATO Operations Guide which
describes the Backups Utility and its operation.
The Backup procedure BACKDMP requires that SORT5 be available
on the system.
The procedure to initialize the Backups utility for use is
described below.
1. Use the procedure "Setting Up Dump Directory Datasets"
in the PLATO Operations Guide to set up 6 datasets.
2. Create file "s0backa" according to the specifications
given in the PLATO Bill of Materials section of this
document.
3. Create file "s0backc" according to the specifications
given in the PLATO Bill of Materials section of this
document.
4. Run the following job at the console:
X.BACKMOD.
K,jsn.
K.INITIALIZE
K.WR
K.END
X.BACKCPY.
5. Use the procedure "Initializing the Slot Table" in the
PLATO Operations Guide to set up the desired dump cycle.
6. Use the "Changing the Master Files to be Dumped"
procedure in the PLATO Operations Guide to initialize
the list of master files you wish to dump. You should
add master files SYS1I and NEWINS to this list.
1
page 80
3.3 Central Micro PLATO executor
The Central Micro PLATO Executor (CMP) allows lessons written
in the Micro PLATO Language to be executed on the central
system. It aids in development of lessons written in the
Micro PLATO Language, but also increases the amount of EM
used as overhead by the PLATO system, reducing the amount
of EM available for user lessons.
To install the Micro PLATO Executor:
1. Add the following to the PLATO configuration file:
cmp=on.
2. Create file "s0cmp0" according to the specifications
given in the PLATO Bill of Materials section of this
document.
3. Edit file "s0cmp0".
4. Press DATA to edit the file information.
5. Choose the "associated files" option.
6. Set the -use- file to "s0cmpuse".
7. Press BACK to return to the file information index.
8. Choose the "Micro PLATO level" option.
9. Set the Micro PLATO level to "3" and the execution mode
to "Central System execution".
10. If you are using more than one condensor, repeat this
procedure for files "s0cmp1" and "s0cmp2".
1
page 81
3.4 Network database
A network database describing all aspects of your communi-
cations network may be built using lesson "pnet". This
database may be quickly scanned to aid in the isolation
of network problems.
A HELP-section in lesson "pnet" provides additional
information.
The network database is built via options in "pnet" as
follows:
1. Enter all locations in the location table.
2. Enter all equipment types in the equipment table.
3. Enter all terminal types in the terminal type table.
4. Define any desired utility fields.
5. Add all circuits and rotaries in your network. As
each entry is made, add all known information to the
corresponding information fields.
1
page 82
3.5 Computer Interface Unit network
The CIU (Central Interface Unit) and SIU (Site Interface
Unit) are unique to the PLATO application. This network
is not available on CYBER 170-800 series machines.
1. Add the CI and D2 EQPDECK entries. See the PLATO
Configuration Handbook for more information.
2. Add / Change the following entries in the PLATO
configuration file.
c0sit
c1sit
nc0si
nc1si
Lesson "ciudiag" is the CIU diagnostics utility. If you
wish to use this optional feature, do the following:
1. Create file "s0ciuna" according to the specifications
given in the PLATO Bill of Materials section of this
document.
2. Execute lesson "s0ciuin" and execute all initialization
options.
3. Add the following to the runner list according to the
specifications given in the PLATO Configuration Hand-
book.
s0ciuru
1
page 83
3.6 TRANSMIT Utility
The TRANSMIT Utility allows users to transfer data from
PLATO files into NOS files for batch jobs to process.
To install TRANSMIT, the following steps should be followed:
1. One or more datasets must be created for use in trans-
ferring data. These files should be created in account
"s0files", and have the following characteristics:
record size: 64 words
length: minimum of 10 parts. Performance
improves as the length approaches
63 parts. (The length determines
how many separate batch jobs must
be submitted to transfer the files
to NOS files.)
The number of datasets created determines how
many users can use TRANSMIT simultaneously. Any number
from one to 60 is acceptable, assuming sufficient sys-
tem resources are available.
2. Enter the names of all datasets created in leslist
"s0xmit" in file "s0common".
3. Enable the use of TRANSMIT on the system:
a. Execute lesson "ipedit".
b. Choose the "batch submission control" option.
c. Edit the appropriate mainframe entries to enable
both the "User jobs" and "Transmit" features on
the desired mainframe(s).
Accounts must be allowed to use this utility. See the
"TRANSMIT" section in the PLATO Operations Guide for more
information on how to do this.
1
page 84
3.7 PLATO Inter-System Link
Before beginning the installation of the PLATO Inter-System
Link optional product, please read the overview given in the
PLATO Operations Guide.
Before you install the PLATO Inter-System Link, you must
first install both the PLATO (level 34.2 or higher) and RHP
applications.
The RHP installation process is described in the NOS Ver-
sion 2 Installation Handbook. Be sure to specify "NAM" as
the supporting network when building the application. Also,
you must include the modifications delivered on the PLAT1A
PLATO release tape and placed into NOS file PLARHP by the
INSTALL or UPGRADE PLATO installation procedure.
The following is a list of the steps to be taken to install
the PLATO Inter-system Link. Each of the numbered steps is
discussed in detail in the following sections.
Install the PLATO application on your operating
system.
Install (or re-install) the RHP application
using any modsets in file PLARHP.
1. Determine accounting method to be used.
2. Create NOS user names.
3. Modify the network configuration file.
4. Modify the PLATO network system table.
5. Create required system-specific files.
6. Install the required runner programs.
3.7.1 Determine accounting method
Read the "Link accounting" section of the PLATO Configuration
Handbook and decide which method of accounting for link traffic
you wish to use for your system. This will affect the
information you must enter into the PLATO network system table
for each linked system.
3.7.2 Create NOS user names
You need to set up two NOS user names that are used to
transfer data between systems. Follow these steps:
1. You have the option of placing your link data files
on an alternate family device.
If you wish to use an alternate family, the NOS
1
page 85
validation files for the family must be created if they
do not already exist. This may be done by entering the
following commands on the computer console:
X.DIS.
FAMILY(family name)
GENVAL.
DROP.
2. If you are using the default family, enter the following
command:
X.MODVAL.
Or, if you are using an alternate family device for the
link files, enter the following command:
X.MODVAL(FM=fnam,OP=K)
3. The MODVAL job will then request the K-display. Assign
this display to the job by the following procedure:
a. Find the job which is requesting the K-display on
the console B-display.
b. Note the job sequence number (JSN) of the job. This
is a four character identifier for the job.
c. Enter the following command on the computer console:
K,jsn.
4. Using the MODVAL options documented in the NOS Version 2
Administration Handbook, create the following user
names:
a. User name "PLASEND". This name stores data that
is sent to other systems.
b. User name "PLARECV". This name stores data that
is received from other systems.
5. The user names must have certain validations for
security reasons. Unless otherwise noted, validations
not mentioned are assumed to be site-specific.
a. You must set the following validations:
- AW = CSPF, CCNR, CSRP, CSAP, CPLK, CUST, CSAF,
COPR, CNRD.
- CC = 77B.
- CP = 0.
- CS = 7.
- DB = 7.
- DF = 77B.
- DS = 0.
- DT = 0.
1
page 86
- EC = 0.
- FC = 7.
- FS = 7.
- LP = 0.
- MS = 77B.
- MT = 0.
- PT = 0.
- RP = 7.
- SL = 77B.
- TL = 77B.
- UC = BCCT, RBCT, IACT.
- VM = ALL.
b. Choose a password, and set both user names to use
this password. The user names MUST have identical
passwords. This password is the key to controlling
access from other systems. You must exchange
passwords with the administrators of the remote
site when you wish to permit inter-system data
transfers.
c. If you wish to set a default charge number for
accounting purposes, you should do so at this time
as described in the PLATO Configuration Handbook.
3.7.3 Modify network configuration file
Now you need to set up your NOS communication network. To
establish a connection to another system, you need to define
a path through NAM's network configuration file and RHP's
logical identifier (LID) table. This procedure and other
details about the installation and operation of these
applications can be found in the following references:
NOS Version 2 Feature Notes
NOS Version 2 Installation Handbook (60459320)
NOS Version 2 Analysis Handbook (60459300)
Network Definition Language Reference Manual (60480000)
Follow these steps:
1. Update your NOS level communication network.
a. Update the LID configuration file. Refer to the
the NOS Version 2 Analysis Handbook for examples.
You need to specify a LID for your system -- we
suggest you use your routing identifier as specified
by the "rid" PLATO configuration file keyword. You
will also need to add PIDs and LIDs for all the
other systems in your network. You will need to
share this information with the administrators of
other sites.
b. Update your NDL file with changes necessary to run
the RHP applications. Here are some examples of
NDL entries you will need to make:
1
page 87
* LINE definitions
line: LINE,PORT=port,LTYPE=ltype,TIPTYPE=tiptype,
PSN=psn,NSVC=svcric,DFL=dfl,FRAME=frame,
RTIME=timer,RCOUNT=count,DCE=yn2.
device: TERMDEV,STIP=stiptyp,NCIR=numcir,NEN=encir,
DT=devtyp.
* APPL statements
PTF: APPL,PRU,NETXFR,MXCOPYS=4.
PTFS: APPL,PRU,RS,NETXFR,MXCOPYS=4.
* INCALL and OUTCALL statements for X.25
INCALL ANAME=ptfs,FAM=famname,UNAME=usernam,
SNODE=srcnode,PORT=portnum,DNODE=dstnode,
DBZ=dwnlsiz,UBZ=upbsize,DPLS=dpls.
OUTCALL NAME1=ptfs,PID=pidname,SNODE=srcnode,
DNODE=dstnode,PORT=portnum,DBZ=dwnlsiz,
UBZ=ubpsize,DPLS=dpls,SHOST=srchost,
DHOST=dsthost,DTEA=dtea.
* INCALL and OUTCALL statements for shared 2550
INCALL ANAME=ptfs,FAM=famname,UNAME=usernam,
DBL=dwnblim,ABL=abl.
OUTCALL NAME1=ptfs,PID=pidname,SNODE=srcnode,
DNODE=dstnode,DBL=dwnblim,ABL=abl.
* INCALL and OUTCALL statements for direct line
* or TRUNK
INCALL ANAME=ptfs,FAM=famname,UNAME=usernam,
SNODE=srcnode,PORT=portnum,DNODE=dstnode,
DBZ=dwnlsiz,UBZ=upbsize,DPLS=dpls.
OUTCALL NAME1=ptfs,PID=pidname,SNODE=srcnode,
DNODE=dstnode,PORT=portnum,DBZ=dwnlsiz,
UBZ=ubpsize,DPLS=dpls,SHOST=srchost,
DHOST=dsthost.
Refer to the NOS Version 2 Feature Notes for more
examples.
c. Build your new network configuration file and
corresponding local configuration file using the
NDLP system command. Refer to the Network
Definition Language Reference Manual for examples.
d. Update your current NAM start-up file with the new
NAM start-up file that was created with the RHP
build process. Also, please make sure that the
following NOS files are moved to the same user
index as the NAM start-up file:
ZZPTFS
ZZQTFS
1
page 88
e. Bring down NAM, then reload NAM using the new
configuration files.
2. Your NOS communication network is now updated. Be sure
to test your network.
3.7.4 Modify PLATO network system table
You now need to update the PLATO network system table,
which includes descriptions of the links between your
system and other systems, and the options available to
each link.
First, you must modify the network system table entry for
your own system as follows:
a. Sign on to PLATO with your "p" signon.
b. Execute lesson "ipedit".
c. Choose the "Network Management" option.
d. Choose the "System Table" option. This takes you
to the "Network System Table Management" display.
e. Choose the "Inspect or change a table entry" option.
f. On the next display, enter your system name and
press NEXT. This name is the same as that specified
by the "sid" PLATO configuration file keyword.
g. Choose the "Network Type:" option.
h. Choose the "Directly connected by 2550" option.
The display will replot and show a number of
additional options.
i. Choose the "NAM mainframe number" option. Enter
the number of the mainframe that executes the NAM
application. On most systems this will be the
default value of 0.
j. Choose the "Family name:" option. Enter the NOS
family name that you set up to send and receive
data. If you wish to use the default family,
simply press NEXT.
k. Choose the "User name password:" option. Enter the
the password that you assigned to the user names
PLASEND and PLARECV. The password entered MUST
be the one entered for both user names earlier in
the installation process. There is no default.
l. Choose the "Charge number:" option. If you will
not be using NOS charge numbers, or, if you plan to
use the default charge number you specified for the
1
page 89
PLARECV/PLASEND user names, press NEXT. If you
want to account for each system's usage, enter a
charge number here. Refer to the "Link Accounting"
section of this document for details.
m. You may wish to store the sending and receiving
data files on an auxiliary pack because of space
constraints on your "system" pack. If so, choose
the "Pack name:" option and enter the desired NOS
pack name. If you are using the default pack,
press NEXT.
n. If you chose to store your files on an auxiliary
pack, choose the "Pack device type:" option and
enter the device type of the pack you entered. The
default is 'dl'.
o. Press BACK to return to the "Network System Table
Management" index.
You should now use the procedure described in the "Adding a
system" section of the PLATO Configuration Guide to add new
systems or use the same procedure, selecting the "Inspect or
change a table entry" option in place of the "Add a new system
to the table" option on the "Network System Table Management"
index, to modify existing systems to establish a link.
3.7.5 Create system-specific files
If the following required, system-specific files do not
exist on your system, you should now create them in account
"s0files" according to the specifications given in the
PLATO Bill of Materials section. Because "s0linkdata" has
a ten-character name, you must use lesson "operator" to
create it as "accounts" will not allow you to create files
with more than eight characters in the name.
s0linkdata
s0notesq
s0rhpds
s0rhplog
s0rhpns
3netinq
3netoutq
3.7.6 Install runner programs
Now you need to set up a runner which will execute the
PLATO lesson which looks for link traffic. Follow these
steps:
a. Sign on to the system with your group "p" signon.
b. Execute lesson "runnersys".
c. Choose the option to "Add lesson to list".
1
page 90
d. On the next display, enter the lesson name "s0rhp".
e. On the next display, choose the "cycle" option and
enter a cycle time of 5 minutes.
f. No other options need be set, unless you have some
specific site requirements.
g. On the same display, press SHIFT-LAB to make the
runner active.
h. Use the same procedure to add lessons "pnotes",
"s0notrun" and "account4" to the runner list. These
lessons distribute personal notes and group notes
received from remote systems to the appropriate files
and perform file requests made by users through
the network features of lesson "accounts". Use
the attributes listed in the "Runner Lesson Management"
section of the PLATO Operations Guide when adding
these lessons.
i. Press SHIFT-STOP to return to the Author Mode page.
The installation of the PLATO Inter-system Link optional
feature is now complete.
3.8 PLATO-BITNET Email Gateway
Before you install the non-PLATO mail system, you must
install both the PLATO and NJEF applications.
The following is a list of steps to be taken to install
non-PLATO mail. Each of the numbered steps is discussed in
detail in the following sections:
1. Decide upon a BITNET node name for your system.
2. Decide upon the name for your mailer.
3. Register with the BITNET operations organization.
4. Connect your system to the BITNET network.
5. Install the PLATO application on your operating system.
6. Install the NJEF application.
7. Define all (or a subset) of the BITNET nodes to the NJEF
application.
8. Create the mailer user name.
9. Create required system-specific files.
10. Define parameters in "s0bitsys".
11. Install the required runner programs.
1
page 91
12. Customize access lists.
13. Define networks in "s0bitsys".
14. Define nodes in "s0bitsys".
3.8.1 Choose BITNET node name
You must choose a name for your system to be known by in
the non-PLATO world. This name must be 8 characters or
less in length. One possibility is to use your PLATO
system name (such as "pca" or "pdev") as your system name.
This approach will allow you to use the same machine name
in both the PLATO and non-PLATO worlds.
3.8.2 Choose mailer name
The non-PLATO mail software operates as a mailer. A mailer
is a program and receives and distributes mail for a
machine. You must choose a user name for this mailer. By
convention, this user name should be MAILER.
3.8.3 Register with BITNET
You must register your system with the BITNET Network
Information Center before connecting to the network. Among
the pieces of information you'll need to supply are the
node name and mailer name you chose above.
3.8.4 Connect with BITNET
Physically connect your system to the BITNET network via
the appropriate hardware.
3.8.5 Install PLATO application
See other sections of this document as appropriate.
3.8.6 Install NJEF application
See the NJEF Installation Handbook (part number 15190118)
for details.
3.8.7 Define BITNET nodes
Instructions for this are in the NJEF Installation
Handbook.
3.8.8 Create mailer user name
Create an NOS user name for your mailer. This name should
be the same name you choose in step 2 above.
3.8.9 Create system-specific files
If the following required, system-specific files do not
1
page 92
exist on your system, you should now create them in account
"s0files" according to the specifications given in the
PLATO Bill of Materials section.
s0bitparam
s0emailds
s0emailns
3.8.10 Define parameters in s0bitsys
Execute lesson "s0bitsys" and choose the "Change Network
Parameters" option. Set the options as follows:
BITNET mailer NOS name: the NOS user name
of your MAILER
BITNET mailer NOS family: the NOS family the
MAILER name appears
under
Runner Delay: 10 minutes
BITNET mail is enabled: YES
Default network: bitnet
BITNET system name: the name chosen in
step 1
3.8.11 Install runner program
Now you need to set up a runner which will execute the
PLATO lesson that looks for non-PLATO mail. Follow these
steps:
a. Sign on to the system with your group "p" signon.
b. Execute lesson "runnersys".
c. Choose the option to "Add lesson to list".
d. On the next display, enter the lesson name
"s0emrec".
e. On the next display, set both the "cycle" and
"restart" times to 1 minute.
f. No other options need to be set, unless you have
some specific site requirements.
g. On the same display, press SHIFT-LAB to make the
runner active.
h. Press SHIFT-STOP to return to the Author Mode page.
3.8.12 Customize access lists
Edit access list "s0bitsys" in file "s0sysfile". This
access list controls:
Who can execute lessons "s0bitsys" and "s0emrec"
directly. Only people in group "p" should have these
1
page 93
abilities.
Who can use the non-PLATO mail facility. You'll need
to keep in mind restrictions on usage imposed by the BITNET
Operations Organization.
Who can send to nodes that aren't explicitly defined
in "s0bitsys".
Who can override the access list for a node.
Who can override the access list for a network.
3.8.13 Define networks in s0bitsys
Every network that you'll be exchanging mail with needs to
be explicitly defined in "s0bitsys". If a network isn't
listed there, you won't be able to access it. Follow these
steps to add a network:
a. Execute lesson "s0bitsys".
b. Choose the option to "Create a New Network Entry."
c. Set the "Network Name on PLATO" to the name you
want this network known by to PLATO users. Some examples
of possible network names are "arpa", "edu" and "uucp".
d. Set the "Node of BITNET gateway" to the BITNET node
name of the system that is functioning as the gateway
between the BITNET network and the network you are
defining.
e. Set the "BITNET mailer name" to the name of the
mailer program on the gateway system.
f. If the mailer on the gateway requires mail to have
a Basic Simple Mail Transfer Protocol header, set the
"BSMTP required" option to YES.
g. If you want to limit access to this network, create
an access list to do this. The access list should be
copied from "s0subfil".
h. Set the address of this network in relation to the
BITNET network.
3.8.14 Define nodes in s0bitsys
It is possible to define nodes as well as networks in
"s0bitsys". Defining nodes allows users to reach them
using the shorthand names you define, or permits
restriction of access by node. (See 3.8.12, though.)
It is suggested that nodes frequently accessed by users on
your PLATO system be defined. Follow these steps to add a
network:
1
page 94
a. Execute lesson "s0bitsys".
b. Choose the option to "Create a New Node Entry."
c. Set the "Node Name on PLATO" to the name you want
this node known by to PLATO users. This should be the same
as the node name in the non-PLATO world. You might want to
create multiple entries for a node: One entry using the
'official' name for the node, one using a local or
shorthand name.
d. Set the "BITNET node name" to the BITNET node name
of the node that you are defining.
e. Set the "BITNET mailer name" to the name of the
mailer program (if any) on the new node.
f. Set the "Default Network" to the name of the
network on which the node you are defining resides.
g. If you want to limit access to this node, create an
access list to do this. The access list should be copied
from "s0subfil".
h. Set the address of this node in relation to the
network on which it resides.
1
page 95
4 Update Installation Procedures
SECTION 4 - UPDATE INSTALLATION PROCEDURES
1
page 96
INTRODUCTION
The following sections describe the procedure to be followed
to update your PLATO system from one major release to another
(for example, from PLATO Release 43 to PLATO Release 44).
If you are only upgrading your operating system and wish to
reinstall the same PLATO Release level on it, you should use
the "Reinstallation Procedures" section instead of this one.
If the PLATO Release you are updating to requires a different
level of the operating system, it is assumed that it has already
been installed.
When updating to a new level of the operating system, the
following PLATO-related items must be carried over from the
old operating system deadstart file to the new one.
1. Changes to deadstart file text records (CMRDECKs,
EQPDECKs, LIBDECKs, IPRDECKs) as described in the
"Deadstart File" section of the PLATO Configuration
Handbook.
2. Procedure MFNX.
3. Procedure MFDX.
4. Procedure SETPUN.
5. Procedure Z1DAILY.
6. Procedure Z1ENDBC.
7. The PLATO configuration file.
If there are changes required to the above for the new PLATO
release, they will be described in the "Change deadstart
file text records" section of the following procedure. Do
not carry over any PLATO binaries or procedures other than
the ones listed above from one operating system to another.
This update installation procedure is designed to allow
analysts to upgrade their system from PLATO release 35
or higher to the current release.
Each section which is dependent on the PLATO Release which
is currently running has a separate list of changes required
for each release. To use these update installation procedures,
you must start with the list describing the changes for the
PLATO release immediately following the release level currently
running on your system and proceed through all lists of changes
up to and including the release level being installed.
For example, if you are currently running release level 43
and you wish to upgrade to level 44, you should use only the
list of changes for PLATO R44 in each section. If your
system is currently running at release level 42 and you wish
to upgrade to release level 44, you must use the list of
1
page 97
changes for PLATO R43 and PLATO R44 in all sections.
1
page 98
4.1 PLATO Operations Changes
The following describes major changes to the operation or
installation of the PLATO application. This is included to
inform analysts performing the upgrade installation of the
PLATO application of important changes in operational
procedures.
CHANGES FOR PLATO R41
- The procedure Z1ENDBC has been modified to use a
temporary file name instead of the actual permenant
file name (Z1ANCT), when preparing to copy the file to
tape.
CHANGES FOR PLATO R42
There were no major changes to PLATO operations procedures
for this release.
CHANGES FOR PLATO R43
There were no major changes to PLATO operations procedures
for this release.
CHANGES FOR PLATO R44
There were no major changes to PLATO operations procedures
for this release.
1
page 99
4.2 Update installation procedures
The following is a list of the steps to be taken to upgrade
the PLATO application software. Each of these steps is
discussed in detail in the following sections.
1. Execute pre-installation cleanups.
2. Obtain files from installation tape.
3. Reinstall NAM and CCP.
4. Reinstall selected NOS programs.
5. Change NOS validation files.
6. Change local deadstart file records.
7. Change PLATO configuration file.
8. Build new deadstart file.
9. Clear operator action queues.
10. Complete file dumps.
11. Deadstart on new deadstart file.
12. Load release master files.
13. Change MFNX procedure.
14. Load PLATO via PLAINS DSD-command.
15. Change existing access lists.
16. Change existing PLATO files.
17. Destroy obsolete files.
18. Install new system lessons.
19. Initialize binary master file(s).
20. Reload PLATO.
21. Run required conversion programs.
22. Run file installation check.
23. Change local AIDS files.
24. Install new optional features.
25. Post-installation cleanups.
1
page 100
26. Dump all master files.
1
page 101
4.2.1 Execute pre-installation cleanups.
There are several checkouts and cleanups that should be
done as part of normal operations. The procedures in the
following sections should be done before the installation
to resolve possible existing problems and to minimize the
cleanups necessary after installation.
1. Execute the following cleanup programs in lesson
"accountu" for all accounts. Errors are logged in
"accerrlog".
a. "Account directory and file checks"
b. "Search for files not in any account"
2. Execute the "Search for duplicate files" option in
lesson "installu" for all active master files.
3. Execute the "File Directory Verification Check" option
in lesson "utility". If the "utility" runner is turned
on, it should not be necessary to run this manually.
4. If any errors are found as a result of these checks,
they will be logged. Print the corresponding log file
and correct any errors before proceeding.
5. A new software release will usually require more disk
space. The amount required may vary from a few parts
to over a hundred. Make sure there is adequate space
on your required master files to handle the new soft-
ware. This may involve adding another master file to
your system if you are currently at or close to the
limit of available space.
6. During the installation process, a temporary master
file must be loaded onto your disk packs. You must
make sure there is enough disk space available on
your disk packs to create one 3680-part master file.
The number of free tracks required for this master
file is shown below for each supported device type.
In addition, there must also be half as many tracks
of temporary file space available. The following
table gives the number of free tracks assuming you
are using single-spindle devices. If you are using
multi-spindle devices, divide the required free tracks
by the number of spindles in the device to be used.
DC 270b tracks
DD 1445b tracks
DG 344b tracks
DI 2264b tracks
DJ 1067b tracks
DK 2176b tracks
DL 1067b tracks
1
page 102
DM 312b tracks
DQ 312b tracks
7. When installing PLATO Release 35 or above, you may
need to lengthen common "link" in file "sysfile"
before beginning the installation. Use the following
procedure to determine if you will need to lengthen
this common.
a. Edit file "sysfile".
b. Press "+" until you find the block named "link".
c. Press the letter which appears next to block "link"
to edit it.
d. Near the top of the next display, you will see the
current length of the common displayed.
e. If this length is greater than (1 + 10 * the value
of the "netms" configuration file entry), you will
not need to lengthen this common.
If the current length of the common is too short, you
should use the following procedure to lengthen it.
a. At a convenient time, back out all users. This is
necessary to prevent a user from writing a common
into file "sysfile" while the file is reorganized.
b. Edit file "sysfile".
c. Press "+" until you find the block named "link".
d. Press the letter which appears next to block "link"
to edit it.
e. Press SHIFT-LAB for "other options".
f. Choose the "change length of common" option.
g. Choose a new length which is the lowest multiple of
320 greater than (1 + 10 * the value of the "netms"
configuration file entry).
1
page 103
4.2.2 Obtain files from installation tape.
This step will load the files which make up the PLATO
application from the first installation tape.
Mount the first installation tape (the one labeled PLAT1A)
on an available tape drive. Make sure the tape drive is
available by checking the console E,T-display.
Enter the following commands on the computer console:
X.DIS.
FAMILY(family name) if using alternate family
USER(sys,password) sys is the PLATO system
user name (usually SYS)
LABEL(TAPE,VSN=PLAT1A)
GTR(TAPE,UPGRADE)PROC/UPGRADE
BEGIN(UPGRADE,UPGRADE,PPW=ps1,SPW=ps2)
where ps1 = password for user name PLATOMF
(default = "platomf")
ps2 = password for user name SYSTEMX
(default = "systemx")
This procedure creates or replaces the following files.
User sys: PLABINS PLATO release binaries
PLANOS modifications to NOS
PLANAM modifications to NAM
PLACCP modifications to CCP
PLARHP modifications to RHP
LIBDIR LIBDECK entries for PLATO programs
PSRREP PLATO PSR reports
LOADMF procedure to load installation
master file
BKSPRU program used to load installation
master file
User PLATOMF: ISTLF00 terminal resident load file
ISTLF01 terminal resident load file
ISTLF03 terminal resident load file
ISTLF08 terminal resident load file
User SYSTEMX: PLATO PLATO load procedure
PLAINS PLATO load procedure
PLAUPD PLATO load procedure
See the PLATO Bill of Materials section for more information
about these files.
1
page 104
4.2.3 Reinstall NAM and CCP.
If you are using only CDCNET, you do not need to do anything
with CCP as discussed in this section. You still may need
to reinstall NAM.
Inspect the contents of files PLANAM and PLACCP under the
PLATO system user name. If either of these files contains
modsets, it will be necessary to reinstall NAM and CCP
with these modsets. Refer to the NOS Installation Handbook
for instructions.
The PLATO application requires only the standard asynchronous
TIP in the CCP build procedure.
Save any modsets in PLANAM and PLACCP so they may be used
again if NAM and CCP must be reinstalled in the future.
1
page 105
4.2.4 Reinstall selected NOS programs.
Inspect the contents of file PLANOS under the PLATO system
user name. If this file contains modsets, it will be
necessary to reinstall the affected programs with these
modsets. Refer to the NOS Installation Handbook for more
information.
By looking at the contents of this file, determine what NOS
programs will need to be reassembled. Only the programs
which have modifications will need to be reassembled.
Be sure that, any time in the future, when these programs
are reassembled, that these modifications are included.
Save the binaries produced for replacement on your deadstart
file after all the PLATO materials are ready to be installed.
Save any modsets in PLANOS so they may be used again if the
affected NOS programs must be reinstalled in the future.
1
page 106
4.2.5 Change NOS validation files.
Changes to the format or content of the NOS validation files
may affect the user names used by the PLATO application or
by users of the PLATO application.
You should make all changes listed for all NOS levels
beginning with the one following the level you are updating
from through the NOS level you are updating to.
CHANGES FOR NOS 2.5.2 LEVEL 678
There are no NOS validation file changes necessary
for this NOS level.
CHANGES FOR NOS 2.5.3 LEVEL 688
There are no NOS validation file changes necessary
for this NOS level.
CHANGES FOR NOS 2.6.1 LEVEL 700
There are no NOS validation file changes necessary
for this NOS level.
CHANGES FOR NOS 2.7.1 LEVEL 716
There are no NOS validation file changes necessary
for this NOS level.
CHANGES FOR NOS 2.7.1 LEVEL 739
There are no NOS validation file changes necessary
for this NOS level.
CHANGES FOR NOS 2.7.1 LEVEL 750
There are no NOS validation file changes necessary
for this NOS level.
1
page 107
4.2.6 Change local deadstart file records.
Changes in the format or content of the NOS deadstart file
text records (CMRDECKs, EQPDECKs, LIBDECKs, IPRDECKs) or the
local PLATO procedures MFNX, MFDX, SETPUN, Z1DAILY, and
Z1ENDBC may be required because of changes in NOS or in the
PLATO application software.
This can be done using O26 or some other text editor available
on your system. Instructions for using O26 may be found in
the NOS V2 System Programmer's Instant manual.
Save the modified records for replacement on your deadstart
file after all the PLATO materials are ready to be installed.
The following example assumes you are using O26 as the text
editor and that you are using the first (0) copies of the
text records (CMRD00, EQPD00, LIBD00, IPRD00).
Example: Modifying a text record.
X.DIS.
FAMILY(family name) if using alternate family
USER(sys,password)
COMMON(SYSTEM)
GTR(SYSTEM,CMRDECK)TEXT/CMRD00
O26.
READ.CMRDECK.
* make required changes.
DIS.
PURGE(CMRDECK/NA)
SAVE(CMRDECK)
Example: Modifying a procedure.
X.DIS.
FAMILY(family name) if using alternate family
USER(sys,password)
COMMON(SYSTEM)
GTR(SYSTEM,MFNX)PROC/MFNX
O26.
READ.MFNX.
* make required changes.
DIS.
PURGE(MFNX/NA)
SAVE(MFNX)
4.2.6.1 Deadstart record changes
CHANGES TO CMRDECKS
The following change should be made to all CMRDECKs on
the deadstart file. If there are on-line copies of these
decks, be sure to change them as well. See the "Deadstart
File" section in the PLATO Configuration Handbook for a
list of all PLATO-related CMRDECK entries.
1
page 108
Change the version line if the release level of the
PLATO software is referenced. Also, change the NOS
version line, if updating the operating system.
CHANGES TO EQPDECKS
The following changes should be made to all EQPDECKs on
the deadstart file. If there are on-line copies of these
decks, be sure to change them as well. See the "Deadstart
File" section in the PLATO Configuration Handbook for a
list of all PLATO-related EQPDECK entries.
CHANGES FOR PLATO R41
There are no required EQPDECK changes for this
release.
CHANGES FOR PLATO R42
There are no required EQPDECK changes for this
release.
CHANGES FOR PLATO R43
There are no required EQPDECK changes for this
release.
CHANGES FOR PLATO R44
There are no required EQPDECK changes for this
release.
CHANGES TO LIBDECKS
The following changes should be made to all LIBDECKs on
the deadstart file. If there are on-line copies of these
decks, be sure to change them as well. See the "Deadstart
File" section in the PLATO Configuration Handbook for a
list of all PLATO-related LIBDECK entries.
CHANGES FOR PLATO R41
There are no required LIBDECK changes for this
release.
CHANGES FOR PLATO R42
There are no required LIBDECK changes for this
release.
CHANGES FOR PLATO R43
There are no required LIBDECK changes for this
1
page 109
release.
CHANGES FOR PLATO R44
There are no required LIBDECK changes for this
release.
CHANGES TO IPRDECKS
The following changes should be made to all IPRDECKs on
the deadstart file. If there are on-line copies of these
decks, be sure to change them as well. See the "Deadstart
File" section in the PLATO Configuration Handbook for a
list of all PLATO-related IPRDECK entries.
CHANGES FOR PLATO R41
There are no required IPRDECK changes for this
release.
CHANGES FOR PLATO R42
There are no required IPRDECK changes for this
release.
CHANGES FOR PLATO R43
There are no required IPRDECK changes for this
release.
CHANGES FOR PLATO R44
There are no required IPRDECK changes for this
release.
4.2.6.2 Deadstart record changes
CHANGES TO MFNX
The following changes should be made to procedure MFNX
on your deadstart file. If there are on-line copies of
this procedure, be sure to change them as well. See the
"MFNX" section in the PLATO Operations Guide for a
complete description of the MFNX procedure.
CHANGES FOR PLATO R41
There are no required changes to MFNX for this
release.
CHANGES FOR PLATO R42
There are no required changes to MFNX for this
release.
CHANGES FOR PLATO R43
1
page 110
There are no required changes to MFNX for this
release.
CHANGES FOR PLATO R44
There are no required changes to MFNX for this
release.
CHANGES TO MFDX
The following changes should be made to procedure MFDX
on your deadstart file. If there are on-line copies of
this procedure, be sure to change them as well. See the
"MFDX" section in the PLATO Operations Guide for a
complete description of the MFDX procedure.
CHANGES FOR PLATO R41
There are no required changes to MFDX for this
release.
CHANGES FOR PLATO R42
There are no required changes to MFDX for this
release.
CHANGES FOR PLATO R43
There are no required changes to MFDX for this
release.
CHANGES FOR PLATO R44
There are no required changes to MFDX for this
release.
CHANGES TO SETPUN
The following changes should be made to procedure SETPUN
on your deadstart file. If there are on-line copies of
this procedure, be sure to change them as well. See the
"SETPUN" section in the PLATO Operations Guide for a
complete description of the SETPUN procedure.
CHANGES FOR PLATO R41
There are no required changes to SETPUN for this
release.
CHANGES FOR PLATO R42
There are no required changes to SETPUN for this
release.
1
page 111
CHANGES FOR PLATO R43
There are no required changes to SETPUN for this
release.
CHANGES FOR PLATO R44
There are no required changes to SETPUN for this
release.
4.2.6.3 Deadstart record changes
CHANGES TO Z1DAILY
The following changes should be made to procedure Z1DAILY
on your deadstart file. If there are on-line copies of
this procedure, be sure to change them as well. See the
"Z1DAILY" section in the PLATO Operations Guide for a
complete description of the Z1DAILY procedure.
CHANGES FOR PLATO R41
There are no required changes to Z1DAILY for this
release.
CHANGES FOR PLATO R42
There are no required changes to Z1DAILY for this
release.
CHANGES FOR PLATO R43
There are no required changes to Z1DAILY for this
release.
CHANGES FOR PLATO R44
There are no required changes to Z1DAILY for this
release.
CHANGES TO Z1ENDBC
The following changes should be made to procedure Z1ENDBC
on your deadstart file. If there are on-line copies of
this procedure, be sure to change them as well. See the
"Z1ENDBC" section in the PLATO Operations Guide for a
complete description of the Z1ENDBC procedure.
CHANGES FOR PLATO R41
The procedure Z1ENDBC has been modified to use a
temporary file name instead of the actual permenant
file name (Z1ANCT), when preparing to copy the file
to tape.
1
page 112
CHANGES FOR PLATO R42
There are no required changes to Z1ENDBC for this
release.
CHANGES FOR PLATO R43
There are no required changes to Z1ENDBC for this
release.
CHANGES FOR PLATO R44
There are no required changes to Z1ENDBC for this
release.
1
page 113
4.2.7 Change PLATO configuration file.
The following changes should be made to the PLATO configuration
file on the deadstart file. If there are on-line copies of
this file, be sure to change them as well. Refer to the
PLATO Configuration Handbook for a complete list of all PLATO
configuration file entries.
You may use O26 or any other text editor available on your
system to make these changes.
Save the modified configuration file for replacement on your
deadstart file after all the PLATO materials are ready to be
installed.
The following procedure may be used to modify the PLATO
configuration file.
X.DIS.
FAMILY(family name) if using alternate family
USER(sys,password)
COMMON(SYSTEM)
GTR(SYSTEM,CONFIG)TEXT/CONFIG
O26.
READ.CONFIG.
* make required changes.
DIS.
PURGE(CONFIG/NA)
SAVE(CONFIG)
4.2.7.1 Configuration file changes
CHANGES FOR PLATO R41
There are no required configuration file changes
for this release.
CHANGES FOR PLATO R42
There are no required configuration file changes
for this release.
CHANGES FOR PLATO R43
There are no required configuration file changes
for this release.
CHANGES FOR PLATO R44
There are no required configuration file changes
for this release.
1
page 114
4.2.8 Build new deadstart file.
Build a new deadstart file which includes the following:
1. The NAM which was reinstalled with the modsets in
file PLANAM, if any were present.
2. The NOS programs which were reinstalled with the
modsets in file PLANOS, if any were present.
3. The CMRDECK, EQPDECK, LIBDECK, IPRDECK, MFNX, MFDX,
SETPUN, Z1DAILY, and Z1ENDBC which may have been
modified earlier in this procedure.
4. The PLATO configuration file which may have been
modified earlier in this procedure.
5. The PLATO release binaries which were loaded from
the installation tape earlier in this procedure.
The following is a sample procedure which could be used to
build the deadstart file.
X.DIS.
FAMILY(family name) if using alternate family
USER(sys,password)
COMMON(SYSTEM)
ATTACH(nam binary file)
ATTACH(nos binary file)
GET(CMRDECK)
GET(EQPDECK)
GET(LIBDECK)
GET(IPRDECK)
GET(MFNX)
GET(MFDX)
GET(SETPUN)
GET(Z1DAILY)
GET(Z1ENDBC)
GET(CONFIG)
ATTACH(PLABINS)
UNLOAD(DIR)
NOTE(DIR,NR).*FILE nam binary file
NOTE(DIR,NR).*FILE nos binary file
NOTE(DIR,NR).*FILE CMRDECK
NOTE(DIR,NR).*FILE EQPDECK
NOTE(DIR,NR).*FILE LIBDECK
NOTE(DIR,NR).*FILE IPRDECK
NOTE(DIR,NR).*FILE MFNX
NOTE(DIR,NR).*FILE MFDX
NOTE(DIR,NR).*FILE SETPUN
NOTE(DIR,NR).*FILE Z1DAILY
NOTE(DIR,NR).*FILE Z1ENDBC
NOTE(DIR,NR).*FILE CONFIG
NOTE(DIR,NR).*FILE PLABINS
PACK(DIR)
1
page 115
REWIND(*)
LIBEDIT(P=SYSTEM,I=DIR)
REWIND(*)
ASSIGN,50,T,F=I. or INSTALL(NEW=EQxx)
COPY(NEW,T,V)
1
page 116
4.2.9 Clear operator action queues.
The format of various operator action queues may change
with a new release. Therefore, all requested actions should
be performed just prior to the installation, thus clearing
the queues.
1. Print all requests in the print request queue.
2. Perform any file backup requests.
3. Complete any archive/retrieval requests.
1
page 117
4.2.10 Complete file dumps.
Before you begin the installation, do a complete dump of
all disk packs. If something goes wrong, good backups must
be available to allow retreating to the previous release,
if necessary.
1
page 118
4.2.11 Deadstart on new deadstart file.
Deadstart using the new deadstart file for this release.
DO NOT try to bring up PLATO yet; some changes must be
made first.
1
page 119
4.2.12 Load release master files.
Use the PLATO procedure LOADMF to copy the PLATO master
files from the installation tapes to disk.
The formats of this procedure call are:
LOADMF(MF=mf) default family
LOADMF(MF=mf,FAMILY=fn) alternate family
LOADMF(MF=mf,PN=pn,R=dt) auxiliary device
where:
mf = master file name
fn = family name
pn = auxiliary pack name
dt = device type if PN argument is used
Mount each installation tape as it is requested via the
E,P-display.
Example: Default family.
If you are using the default family device for PLATO
master files, enter the following on the computer console.
X.DIS.
USER(sys,password)
GET(LOADMF)
LOADMF(MF=SYS1)
* press "." to execute.
* wait for this to finish.
DROP.
Example: Alternate family.
If you are using an alternate family device for PLATO
master files, enter the following on the computer console.
X.DIS.
USER(sys,password)
FAMILY(family name)
GET(LOADMF)
LOADMF(MF=SYS1,FAMILY=family name)
* press "." to execute.
* wait for this to finish.
DROP.
Example: Auxiliary devices.
To load the PLATO master files onto an auxiliary device
named "PLATOA" of type "DL", enter the following on the
1
page 120
computer console.
X.DIS.
USER(sys,password)
FAMILY(family name) if using alternate family
GET(LOADMF)
LOADMF(MF=SYS1,PN=PLATOA,R=DL)
* press "." to execute.
* wait for this to finish.
DROP.
1
page 121
4.2.13 Change MFNX procedure.
Procedure MFNX must be changed to attach the new system
lesson master file, SYS1. This master file must be the
first master file attached so that files on this master
file which duplicate ones already on the system are used
when the PLATO application is loaded. You may also need to
change or add a RESOURC command if the new master file will
be on an auxiliary pack other than those already used by
required master files. DO NOT put this MFNX on your dead-
start file, it is only to be SYSEDITed.
In addition, check to be sure that the number of required
master files PLUS the one installation master file does not
exceed the value of the "ndsus" PLATO configuration file
entry. If necessary, obtain a copy of your configuration
file from the deadstart file and edit it to increase "ndsus"
as needed. DO NOT put this configuration file on your dead-
start file, it is only to be SYSEDITed.
Use SYSEDIT to make these changes to MFNX and the PLATO
configuration file part of the running system.
You may use a procedure similar to the following to make
these changes to MFNX and your PLATO configuration file.
X.DIS.
COMMON(SYSTEM)
GTR(SYSTEM,MFNX)PROC/MFNX
*
* At this point, procedure MFNX is in NOS
* local file MFNX. Use O26 to edit file MFNX
* to attach new master files.
*
GTR(SYSTEM,CONFIG)TEXT/CONFIG
*
* Use O26 to change the value of the "ndsus"
* entry in local file CONFIG, if necessary.
*
NOTE(DIR,NR).*FILE MFNX
NOTE(DIR,NR).*FILE CONFIG
PACK(DIR)
SYSEDIT(I=DIR,B=0)
1
page 122
4.2.14 Load PLATO via PLAINS.
You will now load the PLATO application via the PLAINS
DSD-command.
1. If your system is to use the PLATO ASCII network, NAM
must be brought up at this point.
2. Load the PLATO application by typing the following at
the computer console:
PLAINS.
This console command is used only during PLATO application
installations. It performs the following functions:
a. Alters the "cpspd" configuration entry so that the
PLATO application will allow more foreground processing
time for running installation programs.
b. Prevents groups other than "s", "p" and "convertc"
from signing onto the system.
When updating from PLATO release 34.1 or earlier, you
may see the dayfile message "network table obsolete".
This message may be ignored during installation since
the problem being reported will be corrected by a
conversion to the network system table later in this
process.
3. Now, sign on to the PLATO application with a PLATO
terminal, using your "p" sign-on.
1
page 123
4.2.15 Change existing access lists.
The PLATO application uses several access lists to control
user access to privileged system lessons and options. These
access lists are maintained by the local system. Sometimes
changes must be made to these access lists at the time of
the installation of a new PLATO release.
The following general procedure can be used to update these
access lists.
1. Edit file "s0sysfile".
2. Press "+" until the name of the access list to be
updated is seen on the block display of the editor.
3. Edit the access list which must be updated by
pressing the letter which appears next to the name
of the access list on the block display.
4. Select the "edit user option descriptions" option.
5. Now, select the "copy descriptions from another
access list" option.
6. Enter "s0subfil" as the name of the file from which
to copy.
7. Enter the name of the access list to be updated as
the block from which to copy.
8. Press "y" to adjust authorizations. (If this is not
done, all entries in the access list will be of type
"Special", instead of "Director" or "Operator", etc.).
9. Press SHIFT-HELP to copy the descriptions.
10. Any sign-on listed in the access list which was
previously of type "Special" still retains that
classification. You may want to check the individual
options assigned to that sign-on, and possibly change
some of them.
CHANGES FOR PLATO R41
There are no changes needed for this PLATO release.
CHANGES FOR PLATO R42
There are no changes needed for this PLATO release.
CHANGES FOR PLATO R43
There are no changes needed for this PLATO release.
1
page 124
CHANGES FOR PLATO R44
There are no changes needed for this PLATO release.
1
page 125
4.2.16 Change existing PLATO files.
For each new PLATO release, there may be changes needed for
existing system database files.
4.2.16.1 Change existing PLATO files.
CHANGES FOR PLATO R41
With this release of the PLATO application, a new
feature requires an addition of an access list to
"s0sysfile". Follow the steps below to complete
this process.
1. Edit file "s0sysfile".
2. Choose to add a new block to this file by pressing
the SHIFTed letter of the block you want the new
block to follow. You may have to lengthen "s0sysfile"
through accounts options if there is not enough room
to add new blocks.
3. Choose the option to copy blocks from another file.
4. Enter "s0subfil" as the file to copy from.
5. Choose the block named "s0bitsys" which has the
characters "ac" next to it as the block to copy.
You may get a message at this point which indicates
there is not enough space in the file to copy all
of the blocks. If this happens, lengthen the file
through account options and start this procedure
over at step 1.
6. After the blocks are copied, press BACK until you
are out of the file.
CHANGES FOR PLATO R42
There are no required changes for this release.
CHANGES FOR PLATO R43
There are no required changes for this release.
CHANGES FOR PLATO R44
There are no required changes for this release.
1
page 126
4.2.17 Destroy obsolete files.
With each release, there are certain files which become
obsolete and are no longer needed. These files should be
destroyed to save space. This is done through lesson
"transfer" as follows:
1. Execute lesson "transfer".
2. Choose the "Destroy Obsolete System Courseware"
option.
3. Choose "obsolete system files".
4. Press SHIFT-HELP to begin the operation.
5. Enter the name of a student datafile to use as an
error log or press NEXT to use the default log file
when requested.
5. If a particular file did not exist on the system, it
will be automatically skipped and entered into the
error log along with any other error that may have
occurred. If log entries were made, the log should
be scanned to see if anything unusual happened.
In addition to the lessons above, which are destroyed
automatically, you may also destroy file "s0leslst", if it
exists on your system, using account file management options.
1
page 127
4.2.18 Install new system lessons.
Install new versions of system lessons as follows:
1. Execute lesson "transfer".
2. Choose the "install new courseware" option.
3. Enter "sys1" and press NEXT.
4. You will be asked for the name of the first file to
process. Press NEXT to begin with the first file on
the master file.
5. Press "n" to specify that customer files are NOT to
be replaced.
6. Press "n" to specify that errors are NOT to be
automatically skipped.
7. Old system files will be automatically destroyed if
they are to be replaced. If a new file duplicates
a file found in a non-system account, "transfer"
will stop. The file in the non-system account must
be renamed.
8. If an error occurs, a message will be displayed.
Correct the problem reported and continue. There
should be no errors if the account cleanup programs
were run prior to the installation.
9. It may be necessary to increase the number of disk
parts allocated to account "system" during this
installation. If so, set the parts allocated to
unlimited.
1
page 128
4.2.19 Initialize binary master file(s).
All binary master files should be reinitialized. While the
system will still function properly without doing this, the
"utility" runner program will generate errors for any old
binary file it finds.
1. Execute lesson "ldr".
2. Choose the "Master File Initializations" option.
3. Enter the binary master file name.
4. Press NEXT to leave the master file name the same.
5. Press NEXT to leave the master file type the same.
6. Press "y" to initialize all files on the master file.
7. Press SHIFT-HELP to initialize the master file.
8. Repeat this procedure for all binary master files.
1
page 129
4.2.20 Reload PLATO.
All new system files have now been transferred to the
required master files. Therefore, master file SYS1
is no longer needed. Reload without it as follows:
1. Take the PLATO application down.
2. Enter the following at the computer console to
restore procedure MFNX and the PLATO configuration
file to their original state.
X.SYSEDIT(R)
3. Reload the PLATO application again using the PLAINS
DSD command.
1
page 130
4.2.21 Run required conversion programs.
For some releases, conversion programs must be run to update
user files so that they will work on the new release of the
application. The conversions which must be run for this
release are described below. Unless told otherwise below,
run the conversions according to the procedures described
in the "File Conversions" section of the PLATO Operations
Guide.
If there are no conversion programs to be run or after all
conversion programs are run, you must make sure that the
update levels of new files are being set correctly. This
is done as follows:
1. Execute lesson "ipedit".
2. Press NEXT on the first display for other options.
3. Select the "Update levels for new files" option.
4. Check the list of file types and update levels with
the list below. The update levels of file types not
listed below should be zero.
File type Update level
a 5
f 6
g 1
h 2
i 2
k 1
l 2
o 2
q 1
4. If there are any differences, enter the file type and
the new update level. Update levels will always
increase, do not change an update level to a lower
value.
CONVERSIONS FOR PLATO R41
There are no required conversion programs for this release.
CONVERSIONS FOR PLATO R42
There are no required conversion programs for this release.
CONVERSIONS FOR PLATO R43
There are no required conversion programs for this release.
CONVERSIONS FOR PLATO R44
1
page 131
There are no required conversion programs for this release.
1
page 132
4.2.22 Run file installation check.
All system lessons have now been replaced with the new
versions for this release. Test for proper installation
as follows:
1. Execute lesson "installu".
2. Choose "Special lesson list check" option.
3. Press NEXT to scan all active master files.
4. If any file is reported as missing, report it via
PSR. See the "Problem Reporting" section of the
PLATO Operations Guide for information on how to do
this.
1
page 133
4.2.23 Change local AIDS files.
Each PLATO release may require changes to the two AIDS files
which are maintained by each system, "a0ss1" and "a0psoless".
CHANGES FOR PLATO R41
There are no changes necessary for this release.
CHANGES FOR PLATO R42
There are no changes necessary for this release.
CHANGES FOR PLATO R43
There are no changes necessary for this release.
CHANGES FOR PLATO R44
There are no changes necessary for this release.
1
page 134
4.2.24 Install new optional features.
Each PLATO release may introduce new optional features for
which further installation procedures are needed. See the
"Optional Installation Procedures" section for more information
and installation procedures for the features listed below.
These new optional features may be installed at this time
or at any future time. If you do not wish to install any
of these features at this time, or, when you have completed
installing them, you should continue with the next section.
CHANGES FOR PLATO R41
There is a new type of electronic mail available with
this release, please refer to the section titled
"PLATO-BITNET Email Gateway".
CHANGES FOR PLATO R42
There are no new optional features for this release.
CHANGES FOR PLATO R43
There are no new optional features for this release.
CHANGES FOR PLATO R44
There are no new optional features for this release.
1
page 135
4.2.25 Post-installation cleanups.
The items listed below are things which must be done fol-
lowing a new PLATO release update, but are not critical.
They may be done as part of the actual installation or
during the following week. If you do not wish to do these
cleanups now, continue on to the next section.
PURGE RELEASE MASTER FILES
The release master file, SYS1, should be purged to
recover the disk space it occupies.
PURGE INSTALLATION-ONLY DISK FILES
The following NOS permanent files may be purged to save
space since they are needed only during the installation
process.
PLABINS PLATO release binaries
CONFIG PLATO configuration file
MFNX procedure to attach master files
MFDX procedure to dump master files
SETPUN procedure to set PLATO user name
Z1DAILY procedure to copy PLATO account
summaries to disk
Z1ENDBC procedure to copy PLATO account
summaries to tape
LIBDIR LIBDECK entries for PLATO programs
LOADMF procedure to load installation
master files
BKSPRU program used to load installation
master files
CHANGE ON-LINE CONFIGURATION FILE / PROCEDURES
If on-line copies of the PLATO configuration file,
deadstart file text records or PLATO procedures MFNX,
MFDX, SETPUN, Z1DAILY or Z1ENDBC are used, make the same
changes to those copies that were made when the new
deadstart file was built, if this has not already been
done.
REASSEMBLE PROGRAMS IF THERE HAS BEEN A NOS CHANGE
If the operating system has changed with this release,
be sure to reassemble any private programs in use on the
system.
1
page 136
4.2.26 Dump all master files.
The installation is now complete.
All master files should be dumped for protection against
disk problems happening before the next regularly scheduled
dump.
Once the dumps are complete, open the system to users by
taking the PLATO application down and reloading it via the
PLATO DSD command.
1
page 137
5 Mini-Release Installation Procedures
SECTION 5 - MINI-RELEASE INSTALLATION PROCEDURES
1
page 138
INTRODUCTION
The following sections describe the procedure to be followed
to update your PLATO system when you receive a "mini-release"
shipment. Mini-release shipments are used to distribute
fixes for critical problems which cannot wait until the next
major release.
This procedure may be used to update from any mini-release
version of the PLATO system to any other. Make sure you
follow any special instructions included with the mini-
release shipment as well as the procedure described here.
The following is a list of the steps to be taken to install
a mini-release of the PLATO application software. Each of
these steps is discussed in detail in the following sections.
1. Obtain files from mini-release binaries tape.
2. Perform special instructions.
3. Build new deadstart file.
4. Load mini-release master file.
5. Deadstart on new deadstart file.
6. Load PLATO via PLAINS DSD-command.
7. Change existing PLATO files.
8. Initialize binary master file(s).
9. Post-installation cleanups.
10. Reload PLATO.
1
page 139
5.1 Obtain files from installation tape.
This step will load the files which make up the PLATO
application from the mini-release binaries tape.
Mount the first installation tape (the one labeled PLAT1A)
on an available tape drive. Make sure the tape drive is
available by checking the console E,T-display.
Enter the following commands on the computer console:
X.DIS.
FAMILY(family name) if using alternate family
USER(sys,password) sys is the PLATO system
user name (usually SYS)
LABEL(TAPE,VSN=PLAT1A)
GTR(TAPE,UPGRADE)PROC/UPGRADE
BEGIN(UPGRADE,UPGRADE,PPW=ps1,SPW=ps2)
where ps1 = password for user name PLATOMF
(default = "platomf")
ps2 = password for user name SYSTEMX
(default = "systemx")
This procedure creates or replaces the following files.
User sys: PLABINS PLATO release binaries
PLANOS modifications to NOS
PLANAM modifications to NAM
PLACCP modifications to CCP
PLARHP modifications to RHP
LIBDIR LIBDECK entries for PLATO programs
PSRREP PLATO PSR reports
LOADMF procedure to load installation
master file
BKSPRU program used to load installation
master file
User PLATOMF: ISTLF00 terminal resident load file
ISTLF01 terminal resident load file
ISTLF03 terminal resident load file
ISTLF08 terminal resident load file
User SYSTEMX: PLATO PLATO load procedure
PLAINS PLATO load procedure
PLAUPD PLATO load procedure
See the PLATO Bill of Materials section for more information
about these files.
1
page 140
5.2 Perform special instructions.
The following may be changed by a specific mini-release,
but are not generally needed for all mini-releases. Make
these changes only if told to do so in the mini-release memo
included with the mini-release tapes or in the PLATO Software
Release Bulletin.
a. Reinstall NAM and CCP.
b. Reinstall selected NOS programs.
c. Change PLATO configuration file.
1
page 141
5.3 Build new deadstart file.
Build a new deadstart file which includes the PLATO binaries
which were loaded from the installation tape earlier in this
procedure and any items changed under the section on special
instructions.
The following is a sample procedure which could be used to
build the deadstart file.
X.DIS.
FAMILY(family name) if using alternate family
USER(sys,password)
COMMON(SYSTEM)
ATTACH(PLABINS)
UNLOAD(DIR)
NOTE(DIR,NR).*FILE PLABINS
PACK(DIR)
REWIND(*)
LIBEDIT(P=SYSTEM,I=DIR)
REWIND(*)
ASSIGN,50,T,F=I. or INSTALL(NEW=EQxx)
COPY(NEW,T,V)
1
page 142
5.4 Load mini-release master files.
Load the mini-release master file tapes as described in the
"Courseware Installation" section of the PLATO Operations
Guide.
You must be sure that no users are signed in while this
installation is being done. Since system files are being
replaced, users may begin using the new files before the
installation is complete and results are unpredictable.
When the installation is complete, take the PLATO system
down.
1
page 143
5.5 Deadstart on new deadstart file.
Deadstart using the new deadstart file.
1
page 144
5.6 Load PLATO via PLAINS.
You will now load the PLATO application via the PLAINS
DSD-command.
1. If your system is to use the PLATO ASCII network, NAM
must be brought up at this point.
2. Load the PLATO application by typing the following at
the computer console:
PLAINS.
This console command is only during PLATO application
installations. It performs the following functions:
a. Alters the "cpspd" configuration entry so that the
PLATO application will allow more foreground processing
time for running installation programs.
b. Prevents groups other than "s", "p" and "convertc"
from signing onto the system.
When updating from PLATO release 34.1 or earlier, you
may see the dayfile message "network table obsolete".
This message may be ignored during installation since
the problem being reported will be corrected by a
conversion to the network system table later in this
process.
3. Now, sign on to the PLATO application with a PLATO
terminal, using your "p" sign-on.
1
page 145
5.7 Change existing PLATO files.
The following may be changed by a specific mini-release,
but are not generally needed for all mini-releases. Make
these changes only if told to do so in the mini-release memo
included with the mini-release tapes or in the PLATO Software
Release Bulletin.
a. Change existing access lists.
b. Change existing PLATO database files.
1
page 146
5.8 Initialize binary master file(s).
All binary master files should be reinitialized. While the
system will still function properly without doing this, the
"utility" runner program will generate errors for any old
binary file it finds.
1. Execute lesson "ldr".
2. Choose the "Master File Initializations" option.
3. Enter the binary master file name.
4. Press NEXT to leave the master file name the same.
5. Press NEXT to leave the master file type the same.
6. Press "y" to initialize all files on the master file.
7. Press SHIFT-HELP to initialize the master file.
8. Repeat this procedure for all binary master files.
1
page 147
5.9 Post-installation cleanups.
The items listed below are things which may be done fol-
lowing a PLATO reinstallation, but are not critical. If
you do not wish to do these cleanups now, continue on to
the next section.
PURGE INSTALLATION-ONLY DISK FILES
The following NOS permanent files may be purged to save
space since they are needed only during the installation
process.
PLABINS PLATO release binaries
CONFIG PLATO configuration file
MFNX procedure to attach master files
MFDX procedure to dump master files
LIBDIR LIBDECK entries for PLATO programs
LOADMF procedure to load installation
master files
BKSPRU program used to load installation
master files
1
page 148
5.10 Reload PLATO.
The mini-release installation is now complete.
Open the system to users by taking the PLATO application
down and reloading it via the PLATO DSD command.
1
page 149
6 Reinstallation Procedures
SECTION 6 - REINSTALLATION PROCEDURES
1
page 150
INTRODUCTION
The following sections describe the procedure to be followed
to reinstall your PLATO system on a new level of the operating
system. If you are also upgrading your PLATO system to a new
release level as well as upgrading your operating system, you
should use the "Upgrade Installation Procedures" section instead
of this one.
When updating to a new level of the operating system, the
following PLATO-related items must be carried over from the
old operating system deadstart file to the new one.
1. Changes to deadstart file text records (CMRDECKs,
EQPDECKs, LIBDECKs, IPRDECKs) as described in the
"Deadstart File" section of the PLATO Configuration
Handbook.
2. Procedure MFNX.
3. Procedure MFDX.
4. Procedure SETPUN.
5. Procedure Z1DAILY.
6. Procedure Z1ENDBC.
7. The PLATO configuration file.
Do not carry over any PLATO binaries or procedures other than
the ones listed above from one operating system to another.
1
page 151
The following is a list of the steps to be taken to reinstall
the PLATO application software. Each of these steps is
discussed in detail in the following sections.
1. Obtain files from installation tape.
2. Reinstall NAM and CCP.
3. Reinstall selected NOS programs.
4. Change NOS validation files.
5. Build new deadstart file.
6. Deadstart on new deadstart file.
7. Load PLATO via PLAINS.
8. Initialize binary master file(s).
9. Post-installation cleanups.
10. Reload PLATO.
1
page 152
6.1 Obtain files from installation tape.
This step will load the files which make up the PLATO
application from the first installation tape.
Mount the first installation tape (the one labeled PLAT1A)
on an available tape drive. Make sure the tape drive is
available by checking the console E,T-display.
Enter the following commands on the computer console:
X.DIS.
FAMILY(family name) if using alternate family
USER(sys,password) sys is the PLATO system
user name (usually SYS)
LABEL(TAPE,VSN=PLAT1A)
GTR(TAPE,UPGRADE)PROC/UPGRADE
BEGIN(UPGRADE,UPGRADE,PPW=ps1,SPW=ps2)
where ps1 = password for user name PLATOMF
(default = "platomf")
ps2 = password for user name SYSTEMX
(default = "systemx")
This procedure creates or replaces the following files.
User sys: PLABINS PLATO release binaries
PLANOS modifications to NOS
PLANAM modifications to NAM
PLACCP modifications to CCP
PLARHP modifications to RHP
LIBDIR LIBDECK entries for PLATO programs
PSRREP PLATO PSR reports
LOADMF procedure to load installation
master file
BKSPRU program used to load installation
master file
User PLATOMF: ISTLF00 terminal resident load file
ISTLF01 terminal resident load file
ISTLF03 terminal resident load file
ISTLF08 terminal resident load file
User SYSTEMX: PLATO PLATO load procedure
PLAINS PLATO load procedure
PLAUPD PLATO load procedure
See the PLATO Bill of Materials section for more information
about these files.
1
page 153
6.2 Reinstall NAM and CCP.
If you are using only CDCNET, you do not need to do anything
with CCP as discussed in this section. You still may need
to reinstall NAM.
Inspect the contents of files PLANAM and PLACCP under the
PLATO system user name. If either of these files contains
modsets, it will be necessary to reinstall NAM and CCP
with these modsets. Refer to the NOS Installation Handbook
for instructions.
The PLATO application requires only the standard asynchronous
TIP in the CCP build procedure.
Save any modsets in PLANAM and PLACCP so they may be used
again if NAM and CCP must be reinstalled in the future.
1
page 154
6.3 Reinstall selected NOS programs.
Inspect the contents of file PLANOS under the PLATO system
user name. If this file contains modsets, it will be
necessary to reinstall the affected programs with these
modsets. Refer to the NOS Installation Handbook for more
information.
By looking at the contents of this file, determine what NOS
programs will need to be reassembled. Only the programs
which have modifications will need to be reassembled.
Be sure that, any time in the future, when these programs
are reassembled, that these modifications are included.
Save the binaries produced for replacement on your deadstart
file after all the PLATO materials are ready to be installed.
Save any modsets in PLANOS so they may be used again if the
affected NOS programs must be reinstalled in the future.
1
page 155
6.4 Change NOS validation files.
Changes to the format or content of the NOS validation files
may affect the user names used by the PLATO application or
by users of the PLATO application.
You should make all changes listed for all NOS levels
beginning with the one following the level you are updating
from through the NOS level you are updating to.
CHANGES FOR NOS 2.5.2 LEVEL 678
There are no NOS validation file changes necessary for
this NOS level.
CHANGES FOR NOS 2.5.3 LEVEL 688
There are no NOS validation file changes necessary for
this NOS level.
CHANGES FOR NOS 2.6.1 LEVEL 700
There are no NOS validation file changes necessary for
this NOS level.
CHANGES FOR NOS 2.7.1 LEVEL 716
There are no NOS validation file changes necessary
for this NOS level.
CHANGES FOR NOS 2.7.1 LEVEL 739
There are no NOS validation file changes necessary
for this NOS level.
CHANGES FOR NOS 2.7.1 LEVEL 750
There are no NOS validation file changes necessary
for this NOS level.
1
page 156
6.5 Build new deadstart file.
Build a new deadstart file which includes the following:
1. The NAM which was reinstalled with the modsets in
file PLANAM, if any were present.
2. The NOS programs which were reinstalled with the
modsets in file PLANOS, if any were present.
3. The PLATO release binaries which were loaded from
the installation tape earlier in this procedure.
The following is a sample procedure which could be used to
build the deadstart file.
X.DIS.
FAMILY(family name) if using alternate family
USER(sys,password)
COMMON(SYSTEM)
ATTACH(nam binary file)
ATTACH(nos binary file)
ATTACH(PLABINS)
UNLOAD(DIR)
NOTE(DIR,NR).*FILE nam binary file
NOTE(DIR,NR).*FILE nos binary file
NOTE(DIR,NR).*FILE PLABINS
PACK(DIR)
REWIND(*)
LIBEDIT(P=SYSTEM,I=DIR)
REWIND(*)
ASSIGN,50,T,F=I. or INSTALL(NEW=EQxx)
COPY(NEW,T,V)
1
page 157
6.6 Deadstart on new deadstart file.
Deadstart using the new deadstart file for this release.
1
page 158
6.7 Load PLATO via PLAINS.
You will now load the PLATO application via the PLAINS
DSD-command.
1. If your system is to use the PLATO ASCII network, NAM
must be brought up at this point.
2. Load the PLATO application by typing the following at
the computer console:
PLAINS.
This console command is used only during PLATO application
installations. It performs the following functions:
a. Alters the "cpspd" configuration entry so that the
PLATO application will allow more foreground processing
time for running installation programs.
b. Prevents groups other than "s", "p" and "convertc"
from signing onto the system.
3. Now, sign on to the PLATO application with a PLATO
terminal, using your "p" sign-on.
1
page 159
6.8 Initialize binary master file(s).
All binary master files should be reinitialized. While the
system will still function properly without doing this, the
"utility" runner program will generate errors for any old
binary file it finds.
1. Execute lesson "ldr".
2. Choose the "Master File Initializations" option.
3. Enter the binary master file name.
4. Press NEXT to leave the master file name the same.
5. Press NEXT to leave the master file type the same.
6. Press "y" to initialize all files on the master file.
7. Press SHIFT-HELP to initialize the master file.
8. Repeat this procedure for all binary master files.
1
page 160
6.9 Post-installation cleanups.
The items listed below are things which may be done fol-
lowing a PLATO reinstallation, but are not critical. If
you do not wish to do these cleanups now, continue on to
the next section.
PURGE INSTALLATION-ONLY DISK FILES
The following NOS permanent files may be purged to save
space since they are needed only during the installation
process.
PLABINS PLATO release binaries
CONFIG PLATO configuration file
MFNX procedure to attach master files
MFDX procedure to dump master files
LIBDIR LIBDECK entries for PLATO programs
LOADMF procedure to load installation
master files
BKSPRU program used to load installation
master files
1
page 161
6.10 Reload PLATO.
The reinstallation is now complete.
Open the system to users by taking the PLATO application
down and reloading it via the PLATO DSD command.
1
page 162
7 Bill of Materials
SECTION 7 - PLATO BILL OF MATERIALS
1
page 163
The PLATO "Bill of Materials" is a list of all central
system programs and files and all PLATO files which make
up the PLATO Authoring and Delivery Application 1 product.
These are the items which each site receives with their
initial release materials.
1
page 164
7.1 Central System
Below is an alphabetical list of the records which are to
be placed on the deadstart file. The usage of programs
listed here is documented in the PLATO Operations Guide or
the PLATO Configuration Handbook.
7.1.1 Records: A - L
ACCPRT (ABS) print file management logs.
ASM1 (ABS) generate sorted billing cycle file.
BACKCPY (ABS) copy "backups" information to PLATO files.
BACKDMP (PROC) dump PLATO master files.
BACKLIB (ABS) list "backups" audit trail.
BACKLST (ABS) list data from "backups" dump directory.
BACKMOD (ABS) modify "backups" parameters.
BACKONE (ABS) execute "backups" database merge, phase one.
BACKTWO (ABS) execute "backups" database merge, phase two.
BKSTART (PROC) reinitialize "backups" communications buffer.
CIRCUIT (OVL) overlay of ABS/NETPRT.
CMDMP (ABS) dump central memory to a local file.
CONDEN (ABS) CONDENSOR main overlay.
CONDEN (ULIB) CONDENSOR overlays.
CONDMAP (TEXT) CONDENSOR load map.
CONDX (PROC) load CONDENSOR.
CONFIGX (PROC) obtain PLATO configuration file.
CONSOLE (ABS) PLATO terminal simulator for computer console.
COPYMF (ABS) dump master files to tape or disk.
COPYPD (PROC) copy PLATO dump files to tape.
COPYPF (ABS) recover individual PLATO file or entire
master file from tape or disk.
DATESCN (ABS) scan raw account file and generate list of
dates on the file.
DDP (PP) called by OVL/DDPT.
1
page 165
DDPT (OVL) on-line diagnostic for DDP/low-speed port.
DOCPRT (ABS) print documentor files.
DPRINT (ABS) print student data files.
DSNCARD (OVL) overlay of ABS/NETPRT.
DUMPPRT (PROC) print PLATO dump tape or file.
ECSTST (OVL) test extended memory.
EFRDUMP (ABS) dump extended flag registers.
EMPRT (PROC) print EM dump from PLATO dump tape or file.
EMDMP (OVL) dump extended memory to a local file.
EMDTAPE (PROC) dump extended memory and submit tape copy
job.
ENDOFBC (PROC) process PLATO raw account file and copy
to tape for royalty purposes.
EPE (PP) process extended memory parity errors.
ESM (ABS) load ESM relocation memory or monitor and
log ESM parity errors.
ESM (PP) called by ABS/ESM.
EXEC (PROC) load additional PLATO executor.
FORMCMD (PROC) format PLATO dump files.
FRAMAT (ABS) FRAMAT/FORMAT main overlay.
FRAMAT (ULIB) FRAMAT/FORMAT overlays.
FRAMMAP (TEXT) FRAMAT/FORMAT load map.
FRAMX (PROC) load FRAMAT/FORMAT.
LURBC (ABS) generate lesson usage report.
7.1.2 Records: M - R
MAS (PP) called by background batch jobs to request
action from MASTOR.
MASJOB (ABS) translate control card for jobs submitted
by MASTOR.
MASTOR (ABS) MASTOR main overlay.
MASTOR (ULIB) MASTOR overlays.
1
page 166
MASTORN (ABS) MASTORN overlays.
MASTORN (ULIB) MASTORN overlays.
MEMPRT (ABS) print central and extended memory from PLATO
dump tapes or files.
MFDX (PROC) dump master files.
MFNX (PROC) attach required master files to MASTOR.
MFPACK (PROC) change master file name, type and/or length.
MFTCOPY (PROC) copy master files from disk to tape.
MFTLOAD (PROC) copy master files from tape to disk.
MFU (PP) called by ABS/MFUTIL.
MFUTIL (ABS) create and maintain master files.
MODPRT (ABS) print PLATO Learning Management (PLM) modules.
MRQ (PP) called by ABS/MASTOR and ABS/MASTORN.
MXX (PP) called by ABS/MASTOR.
NETPRT (ABS) print the "pnet" network database.
NPRINT (ABS) print group and student notes files.
PAFTERM (PROC) process the NOS account log for billing
cycle purposes.
PCDCONV (PROC) convert PCD3 database and write to PLATO
dataset. see "pcd3aids" for information.
PCODE (ABS) set file access password for future file
accesses via PF command.
PDCAT (PROC) catalog contents of a PLATO dump tape.
PDD (PP) called by ABS/CONSOLE.
PDPRT (ABS) print master file directories.
PF (ABS) transfer files between PLATO and batch jobs.
PIO (PP) called by ABS/PLATO.
PLATMAP (TEXT) PLATO load map.
PLATO (ABS) PLATO executor main overlay.
PLATO (ULIB) PLATO executor overlays.
1
page 167
PLATX (PROC) load PLATO executor.
PLMPRT (ABS) print PLATO Learning Management (PLM)
curriculum files.
PMS (PP) called by ABS/MASTOR.
PNA (PP) called by ABS/PNI.
PNI (ABS) PLATO / NAM Interface program.
PNICARD (OVL) overlay of ABS/NETPRT.
PNIMAP (TEXT) PNI load map.
PNIX (PROC) load PNI.
PORAFM (ABS) removes non-PLATO related entries from the
NOS account file for billing purposes.
PORTS (OVL) overlay of ABS/NETPRT.
PORTX (ABS) generate port (station) usage report.
PPACK (ABS) set master file for future file accesses
via PF command.
PPRINT (ABS) convert PLATO print files to ASCII.
PROUTE (ABS) schedule PLATO job at a control point.
RAFPBC (ABS) compact and partially reduce raw account file.
RAFPDD (ABS) generate PLATO availability report.
RECOVAL (PROC) recover all master files on a specific pack
or all master files on the entire system.
RECOVMF (PROC) recover a single master file.
REQPACK (ABS) pause until a desired NOS pack is mounted
and available.
RMFCONV (ABS) convert PCD3 database. see "pcd3aids"
for information.
ROTARY (OVL) overlay of ABS/NETPRT.
ROYALTY (ABS) generates royalty information based on the
billing cycle data.
7.1.3 Records: S - Numeric
SETPUN (PROC) set PLATO user name.
SORTCC (OVL) overlay of ABS/NETPRT.
1
page 168
SPF (PP) called by ABS/REQPACK.
STATS (OVL) overlay of ABS/NETPRT.
SUBMITM (OVL) submit a file for NOS execution.
TFORM (ABS) format NOS output to be written to a PLATO
file with PF command.
TPRINT (ABS) print TUTOR lessons, datasets and namesets.
UURBC (ABS) generate user usage report.
VERSX (PROC) obtains appropriate software version.
WAIT (ABS) wait for specified time or operator action.
Z1DAILY (PROC) process PLATO account summary data, then
copy data to a NOS file.
Z1ENDBC (PROC) copy PLATO account summary data from a NOS
file to tape, then reinitialize NOS file
for coming month.
4PA (PP) overlay of PP/PMS.
4PB (PP) overlay of PP/PMS.
4QA (PP) overlay of PP/MRQ.
4QB (PP) overlay of PP/MRQ.
4QC (PP) overlay of PP/MRQ.
4QD (PP) overlay of PP/MRQ.
4QE (PP) overlay of PP/MRQ.
4QF (PP) overlay of PP/MRQ.
4QG (PP) overlay of PP/MRQ.
4QH (PP) overlay of PP/MRQ.
4QI (PP) overlay of PP/MRQ.
4QJ (PP) overlay of PP/MRQ.
4QK (PP) overlay of PP/MRQ.
4QL (PP) overlay of PP/MRQ.
4QM (PP) overlay of PP/MRQ.
4QN (PP) overlay of PP/MRQ.
4QO (PP) overlay of PP/MRQ.
1
page 169
4QP (PP) overlay of PP/MRQ.
4QQ (PP) overlay of PP/MRQ.
4QR (PP) overlay of PP/MRQ.
4QS (PP) overlay of PP/MRQ.
4QT (PP) overlay of PP/MRQ.
4QU (PP) overlay of PP/MRQ.
1
page 170
7.2 NOS Permanent Files
The following is a list of all NOS permanent files required
to run the PLATO Authoring and Delivery Application 1. The
PLATO system user name is that defined by the "subun" PLATO
configuration file (usually called "sys"). The user names
PLATOMF and SYSTEMX are created when the operating system
is installed.
(DA) indicates a direct access file.
(IA) indicates an indirect access file.
FILES UNDER THE PLATO SYSTEM USER NAME
CONFIG (IA) Release configuration file - used only during
installation.
LIBDIR (IA) LIBDECK entries for PLATO programs - used only
during installation.
MFDX (IA) Release procedure to dump master files - used
only during installation.
MFNX (IA) Release procedure to attach master files -
used only during installation.
PLABINS (DA) Release PLATO binaries - used only during
installation.
PLACCP (DA) Modifications to CCP - used only during
installation.
PLANAM (DA) Modifications to NAM - used only during
installation.
PLANOS (DA) Modifications to NOS - used only during
installation.
PLARHP (DA) Modifications to RHP - used only during
installation.
PLATOD (IA) This file is submitted by MASTOR to load the
other PLATO control points. It must contain
calls to procedures to load the required jobs.
This is a system-unique file delivered only
with the initial release.
PSRREP (DA) Contains prints of PLATO PSRs (problem
reports) resolved during the past release.
The file can be printed on an upper case
only printer by using these commands:
FCOPY(P=PSRREP,PC=ASCII,N=filenm,NC=DIS)
ROUTE(filenm,DC=PR)
or to print it out on an upper/lower case
printer use these commands:
1
page 171
FCOPY(P=PSRREP,PC=ASCII,N=filenm,NC=ASCII8)
ROUTE(filenm,DC=PR,EC=A9)
SETPUN (IA) Release procedure to set PLATO user name -
used only during installation.
Z1DAILY (IA) Release procedure to process daily PLATO
account summary data - used only during
installation.
Z1ENDBC (IA) Release procedure to process monthly PLATO
account summary data - used only during
installation.
7.2.1 NOS Permanent Files (continued)
FILES UNDER THE "PLATOMF" USER NAME
AUDIT (DA) This file contains the audit trail used by
the file dump/backups procedures and programs.
AUDITX (DA) This file is an alternate copy of the contents
of file AUDIT.
BACKDIR (DA) This file is an alternate copy of the contents
of file DUMPDIR.
CND0CM (DA) This is a temporary file used to hold the
CONDENSOR dump file until it is copied to a
tape (also CND1CM and CND2CM).
COMBUF (DA) This file contains the communication buffer
used by the file dump/backups procedure.
CONFIGX (IA) This file contains temporary configuration
file settings when the PLAINS or PLAUPD DSD-
command is used to load PLATO.
DUMPDIR (DA) This file contains the dumped file directory
used in the file dump/backups procedure.
DUMPLOK (DA) This file is used to prevent more than one
job from copying PLATO dumps to tape.
EMDUMP (DA) This is a temporary file used to hold the
extended memory dump file while it is being
copied to a tape.
EX0CM (DA) This is a temporary file used to hold the
PLATO dump file until it is copied to a tape.
FRAMCM (DA) This is a temporary file used to hold the
FRAMAT dump file until it is copied to a tape.
ISTLFxx (DA) These are files which contain the terminal
1
page 172
residents loaded by PNI. The "xx" in the file
name is the load file number in hexadecimal
(00, 01, 03, 08).
MASTCM (DA) This is a temporary file used to hold the
MASTOR dump file until it is copied to a tape.
PLATEM (DA) This is a temporary file used to hold the
extended memory dump file until it is copied
to a tape.
PNICM (DA) This is a temporary file used to hold the
PNI dump file until it is copied to a tape.
PNILOCK (DA) This is a temporary file used to indicate that
PNI is active. It will exist and be attached
in write mode when PNI is running to prevent
another copy from being loaded.
S0BACKC (DA) This file contains parameters and tables
used by the file dump/backups procedures.
FILES UNDER THE "SYSTEMX" USER NAME
ESMRM (IA) This file is used by program ESM to save a
copy of the ESM relocation table.
ORAFMON (DA) This file is the previous contents of file
RAFMON.
PLAINS (IA) This file holds the PLATO load procedure
executed when the PLAINS DSD-command is entered.
PLATO (IA) This file holds the PLATO load procedure
executed when the PLATO DSD-command is entered.
PLAUPD (IA) This file holds the PLATO load procedure
executed when the PLAUPD DSD-command is entered.
RAFMON (DA) This file is used to save the account file
for the current billing cycle.
1
page 173
7.3 PLATO System Files
The following sections list the PLATO files supplied as part
of the PLATO system. All of these files will exist on all
systems, although some of them may be inoperative on some
systems if the corresponding product is not available. These
files are global files, meaning that their content is exactly
the same on all systems. Such global files are included in
all system releases.
7.3.1 Files: a - az
ACCOUNTC part of the user PLATO file management programs.
ACCOUNTP formats information about an account into a
dataset so it may be printed.
ACCOUNTS main lesson for editing PLATO accounts.
ACCOUNTU system maintenance utility for PLATO accounts.
ACCOUNT1 system controller options for PLATO accounts.
ACCOUNT2 user PLATO file management functions.
ACCOUNT2A user PLATO file management functions.
ACCOUNT3 user file archiving options.
ACCOUNT4 user networking options.
AIDS main AIDS package control lesson.
AIDSDSET dataset used by AIDS package.
AINFO system options for AIDS package.
ALARM allows users to set alarm messages to be sent
to them at a specified time.
ALLOCATE assign stations and allocate EM to logical sites.
ARCHIVER system controller file archiving options.
ASK allows users to see and respond to TERM-ask
requests.
AUTHORS main lesson for AUTHORS package.
AUTHORSYS system controller options for AUTHORS package.
7.3.1.1 Files: a0
A0 all files beginning with the characters "a0"
are part of the AIDS package. All these files
are listed below.
1
page 174
A0ACCESS
A0AIDSVOC
A0AIDS1
A0ARRAY1
A0ARRAY2
A0BRANCH
A0CALC
A0CALCTRY
A0CALC1
A0CALC2
A0CALC3
A0CDCPUBS
A0CHANGE
A0CHAR
A0CHARTRY
A0COLOR
A0COMMON
A0COMMON1
A0COMPU
A0CONDERRS
A0CONDIT
A0DATA
A0DATA1
A0DATA2
A0DEFINE
A0DEFINE1
A0DEFINE2
A0DIALOG
A0DISPLAY
A0DISPLAY1
A0DISPLAY2
A0DISPLAY3
A0DISPLAY4
A0DO
A0DOTO
A0ERRORS
A0ERRORS1
A0EXECERR
A0EXECUTE
A0EXECUTE1
A0EXECUTE2
A0EXTERNAL
A0FILEOP
A0FILES
A0FPVAR
A0GETLINE
A0GRAPH
A0GRAPH1
A0GRAPH2
A0HELPOP
A0IF
A0ISTAID
A0JAPANESE
A0JARGON
A0JUDGE
A0JUDGE1
1
page 175
A0JUDGE2
A0JUDGE3
A0JUDGE4
A0JUDGE5
A0JUDGE6
A0JUDGE7
A0JUDGE8
A0JUDGE9
A0JUMPOUT
A0KEYCODES
A0KEYMAP
A0LEFT
A0LESLIS
A0LIB
A0LIBRARY
A0LISTS
A0LVARS
A0MICRO
A0MISC
A0NAMESET
A0NEXT
A0PACK
A0PAUSE
A0PICT
A0PICT1
A0PICT2
A0POINTERS
A0PPTSYS
A0PRINTS
A0PRINTS1
A0PROC
A0QREFCOM
A0QREFNS
A0QREFVOC
A0RANDOM
A0RANDOM1
A0RECORDS
A0ROUTER
A0SEARCH
A0SECURE
A0SHOW
A0SITE
A0SPECS
A0SPECS1
A0STRUCTUR
A0STUDNOTE
A0SYSHELP
A0SYSNIO
A0SYSVARS
A0SYS1
A0SYS2
A0SYS3
A0SYS4
A0TIME
A0TOUCH
A0TTCALC
A0TTCAL2
1
page 176
A0TTDISP
A0TTGRAF
A0TTJUDG
A0TTJUD2
A0TTSEQ
A0TTUTOR
A0TT2
A0USEDAIDS
A0XSYS
7.3.2 Files: b
BACKUPS driver for file backups package.
BIN displays tutor binaries.
BINARY binary master file cleanup.
7.3.3 Files: c
C main consult management lesson.
CATAIDS help program for the CATALOGS package.
CATALOGS retrieves and displays catalog information.
CATDOC documentation of CATALOGS package.
CATTEXT text editor for CATALOGS package.
CATUSE defines and common routines for CATALOGS package.
CAT1 system and director options for CATALOGS package.
CAT2 editor for CATALOGS package.
CDRIVER use file for conversion programs.
CERRORDSET dataset which holds the detailed condense
error messages.
CHARSET character set editor.
CHARSETS charset library for AIDS package.
CHECKPT check points commons, datafiles, student records,
and master file directories to disk; checks for
disk and extended memory errors.
CIUDIAG main index and runner control options for the
CIU diagnostics utility.
CONDERR condense error display driver.
CONSOLE utility to display NOS system displays on a
PLATO terminal
1
page 177
CONSTATS displays consult call statistics.
CONSULT reserved file name.
CONSYS consult system options.
CONTINUE reserved file name.
CONVERTxx PLATO file conversion program ("xx" is the
number of the conversion). Refer to the "File
Conversions" section of the PLATO Operations
Guide for more information.
CONVERT28
CONVERT31
CONVERT33
CONVERT42
CONVERT46
CONVERT47
CONVERT48
CONVERT49
CONVERT51
CONVERT52
CONVERT54
CONVERT55
CONVERT57
CONVERT58
CONVERT59
CONVERT60
CONVERT61
CONVERT63
CONVERT64
CONVERT65
CONVERT66
CONVERT68
CURRICULUM curricula documention for the AIDS package.
7.3.4 Files: d
DATA displays student data collected by instructional
lessons.
DIAG diagnostics for IST and Magnavox terminals.
DIAGUSE use file for lesson "diag".
DIAG2 communications diagnostics; terminal errors,
monitor/master, echo timing.
DINTRO "documentor" users guide.
DOCUMENTOR main document editor.
7.3.5 Files: e
EDIT Author Mode displays.
1
page 178
EDITDEFINE defines used by TUTOR editor lessons.
EDITDS dataset/nameset/common editor.
EDITHELPS help displays for TUTOR editor.
EDITMICRO microtable and leslist editor.
EDIT1 continuation of TUTOR editor.
EDIT2 continuation of TUTOR editor.
ENFORCER prevents use of specified lessons by users at
a logical site.
EXECERR execution error display driver.
EXERRDSET dataset which holds short execution error
messages.
7.3.6 Files: f
FILELIST build and manipulate lists of files.
FILESCAN utility for users to scan files to see if they
meet publishing standards and to search files
for references to other files.
FLOPPY 8 inch flexible disk utility. Allows users to
prepare and edit flexible disks for use with the
Micro PLATO system. Includes options to create
lessons, datasets and character sets on flexible
disks, to destroy, rename, copy and update
flexible disk files and to make copies of flexible
disks.
FLOPPYPC 5.25 flexible disk utility. Allows users to
prepare and edit flexible disks for use with
the Micro PLATO system. Includes options to
create lessons, datasets and character sets on
flexible disks, to destroy, rename, copy and
update flexible disk files and to make copies
of flexible disks.
7.3.7 Files: g
GUIDE main editor lesson for "guide". All displays
are created, deleted and edited via this lesson.
GUIDEAIDS "guide" users guide.
GUIDER general purpose display driver for "guide".
7.3.9 Files: i
IMODE default router for instructor sign-ons.
1
page 179
INDEXAIDS help program for published lesson catalog.
INSTALLU system/courseware installation utilities.
INSTRUCTOR instructor options documention for AIDS package.
IPEDIT installation parameters editor.
7.3.10 Files: j
JOBSTAT lesson used to submit/monitor batch jobs.
7.3.12 Files: l
LDR options to load, unload, inspect, and initialize
master files.
LIBRARY library of coding techniques and routines for
AIDS package.
LINESET lineset editor.
LINESETS lineset library for AIDS package.
7.3.13 Files: m
MAINTCX procedures called by "s0maintx".
MAINTX contains dayfiles from jobs submitted by
"s0maintx".
MEM memory inspect options.
MICROS microtable library for AIDS package.
MLIBRARY library of Micro-PLATO coding techniques and
routines for the AIDS package.
MODIFY disk edit/inspect utilities.
MPROUTER Micro-PLATO router/utility lesson.
MPXLATOR Micro-PLATO translator utility.
MREDIT group curriculum options.
MREDIT1 continuation of curriculum editor.
MREDIT2 continuation of curriculum editor.
MROUTER default student router.
MSYSUSE defines and routines used by "mredit".
MTUTORx Micro PLATO interpreter binary files. The
correspondence between these files and the
1
page 180
terminal type is as follows:
File Name Version Terminal Level
MTUTOR1 1 IST-II 4
MTUTOR2 2 ASCII 4
MTUTOR3 3 unused
MTUTOR4 4 unused
MTUTOR5 5 unused
MTUTOR6 6 unused
MTUTOR7 7 PPT 1
MTUTORA 8 IST-I 1
MTUTORB 9 unused
MTUTORC 10 IST-II 2
MTUTORD 11 ASCII 1
MTUTORE 12 IST-II 1
MTUTORF 13 ASCII 2
MTUTORG 14 ASCII 3
MTUTORH 15 IST-II 3
7.3.14 Files: n
NETMON monitors all sites on the CIU and checks for
problems in the network.
NOSAIDS NOS/PLATO interface program documentation for
AIDS package.
NOTES main general notes control lesson.
NOTESEDIT text editor used by "notes", "pnotes", the
"catalogs" text editor, the condense and
execution message editors, and user programs.
NOTESYS system controller options for "notes".
7.3.15 Files: o
OPCALLS reserved file name.
OPERATOR system account/file options.
OPGUIDE PLATO Operations Guide.
7.3.16 Files: p
PACEDIT print access control editor.
PBOM list of files which make up the PLATO Bill of
Materials used in preparing new installation
and update releases.
PCD3AIDS Central PLATO Courseware Design, Development
and Delivery (PCD3) User's Guide.
PCD3CENT database for "pcd3aids".
1
page 181
PCD3CONV conversion program for PCD3 databases.
PCGUIDE PLATO Configuration Handbook.
PICTURES charset picture library for AIDS package.
PICTURES2 charset picture library for AIDS package.
PLATO initial sign-on sequence displays.
PLxxFIXES MODIFY directives for the current release
program library used to fix problems in the
PLATO software. (xx = PLATO release level)
PLM defines and routines for user lessons.
PLMAIDS driver for PLMAIDS package. Other files in
this package are:
PLMAACCT
PLMACRS
PLMAFEAT
PLMAGPCTL
PLMAGRADE
PLMAINFO
PLMAINST
PLMAIUOP
PLMAMAIN
PLMAMODOP
PLMANAMES
PLMAPHILO
PLMAPLMGC
PLMAQUS
PLMASTR
PLMASTRUC
PLMASTU
PLMASTUVW
PLMATECH
PLMATUTOR
PLMAVMS
PLMA110
PLMCURR PLM curriculum / course editor.
PLMCURR1 continuation of "plmcurr".
PLMCURR2 continuation of "plmcurr".
PLMCURR3 continuation of "plmcurr".
PLMCURR4 continuation of "plmcurr".
PLMDEFINES use file for PLM package.
PLMGEDIT inspect/change student records options
PLMLIBRARY lists of PLM curricula and modules
1
page 182
PLMLREDIT PLM learning resource editor.
PLMMOD PLM module editor.
PLMMOD1 continuation of "plmmod".
PLMMOD2 continuation of "plmmod".
PLMMSG messages used by PLM curriculum editor.
PLMOBJ student objective mastery status.
PLMOLT PLM off-line testing.
PLMQUEST PLM question editor.
PLMQUEST1 continuation of "plmquest".
PLMRECORDS PLM gradebook and summary statistics.
PLMRECS student record initialization.
PLMRETURN student return from CAI tests.
PLMROUTER PLM student router.
PLMRX PLM prescription generator.
PLMSCHED PLM scheduling and group controls.
PLMSCHED1 continuation of "plmsched".
PLMSTAT PLM gradebook summary statistics collection.
PLMSUM PLM gradebook group summary displays.
PLMTEST PLM test driver.
PLMTQA PLM test question item analysis.
PLMUSERS displays PLM statistical information.
PLMUTILITY utilities for PLM authors.
PLMVERIFY PLM module verification.
PNET network configuration database editor.
PNETDOC documentation for "pnet".
PNOTES main personal notes control lesson.
PNOTESYS personal notes system options.
PRINT used to print lessons, datasets, namesets,
documentor files and screen copies using an
1
page 183
online printer.
PRINTS used to request/submit print jobs.
7.3.17 Files: q
Q reserved file name.
QREF "quick references aids" driver.
7.3.18 Files: r
RECORDS main group editor; includes roster management,
editing of individual records, and options to
set the router, data file, etc.
RECORDS1 continuation of group editor.
RECPRINT formats information about groups and student
records into a dataset for printing.
RESUME reserved file name.
RETURN reserved file name.
RSTARTL reserved file name.
RUNNER router for runner programs.
RUNNERSYS system options used to control runner programs.
RUNREXEC runner executive; manages runner programs and
gathers statistics.
7.3.19 Files: sa - sz
S group used by PLATO support personnel.
SEARCH allows searching entire lesson for a string.
SERV1 continuation of TUTOR editor - ID/SD options.
SERV2 continuation of ID/SD options.
SIGNON terminal auto-signon editor.
SITE logical site director options.
STATS displays statistics gathered by "stats1".
STATS1 collects peak terminal usage statistics and
PLATO up time statistics.
STIM start/stop stimulator programs.
SYSAIDS system documentation driver.
1
page 184
SYSLOG used to display the security log ("loglog").
SYSMICRO contains microtables used by system lessons.
SYSMTR monitors system stability.
SYSMTRTST0 dataset used by "sysmtr" for disk tests.
SYSOPTS system operations options (backout, send messages,
reload condensor, etc).
SYSTEM1 statistics displays.
7.3.19.1 Files: s0a - s0c
S0ACCESS contains system access lists delivered with each
release. Subfiles in this file are:
CATACCESS access list used to control access
to system options in "catalogs".
S0CALUTIL common used by "s0calutil".
S0MAINT access list used to control access
to "s0maint".
S0ACCOUNTS use file / documentation for "accounts".
S0ACEDIT access list editor.
S0ACEDN help displays for access list editor.
S0ACED1 continuation of "s0acedit".
S0ASCERS description of the PLATO interface to ASCII
terminals.
S0ASC2 IST-3 ASCII resident for Micro PLATO Level 2.
S0AUTHORSC dataset which contains subject areas in which
lessons have been written.
S0BACKU "backups" system options.
S0BITSYS editor for system table for BITNET link.
S0CALUTIL main driver lesson for inspecting/editing the
custom access lists to control access to system
lessons.
S0CDM utility used primarily by Control Data Course-
ware Services to manage the distribution of
published courseware.
S0CDM1 continuation of "s0cdm".
S0CDM2 continuation of "s0cdm".
S0CDM3 continuation of "s0cdm".
1
page 185
S0CDM4 continuation of "s0cdm".
S0CDRIVER use file for conversion programs.
S0CD3USE use file for "s0pcd3".
S0CECOM common which holds short condense error messages.
S0CFGNS nameset used by "s0config".
S0CIUDA data display options for "ciudiag".
S0CIUER dataset with error messages for "ciudiag".
S0CIUHD history and report generation options for
"ciudiag".
S0CIUHE dataset with HELP displays for "ciudiag".
S0CIUIN installation options for "ciudiag".
S0CIULO log index and options for "ciudiag".
S0CIUL1 log entry display and related options for
"ciudiag".
S0CIUMO network monitor options for "ciudiag".
S0CIURP main report generation lesson for "ciudiag".
S0CIURU runner lesson for "ciudiag".
S0CIUR1 runner lesson for "ciudiag" (continued).
S0CIUSA dataset containing diagnostics information
used by "ciudiag".
S0CIUSU summary report option for "ciudiag".
S0CIUUS use file for "ciudiag" and related lessons.
S0CMPUSE use file for system-unique files "s0cmp0",
"s0cmp1", etc.
S0CONFER main Teleconferencing lesson.
S0CONFIG EM configurator used to see the effect of
changing configuration file parameters.
S0COPY TUTOR editor copy-a-block options.
S0CPSPD used to determine proper setting of "cpspd"
configuration file entry.
S0CPUSTAT gathers / displays stats about CPU usage while
executing or condensing and about lesson usage.
1
page 186
7.3.19.2 Files: s0d - s0l
S0DOCED use file for "documentor".
S0DOCFM continuation of "documentor".
S0DVER2 Micro PLATO level 2 disk verification routines.
S0ECHO key echo tracker lesson.
S0EDIT main TUTOR source editor.
S0EDITU used by "convert68".
S0EMAIL pnotes interface for BITNET mail.
s0EMREC runner for BITNET mail.
S0ERXDNSET nameset which holds detailed execution error
messages.
S0FINFO continuation of TUTOR editor.
S0GEDIT graphics/display editor used with "guide".
S0GHELP help lesson for "s0gedit".
S0GUIDENS nameset used with "guideaids".
S0HOME router for Homelink users
S0HFLOP help lesson for "floppy".
S0INIT initializes system databases at load time.
S0ISTA00 short ASCII resident for IST2 and IST3.
S0ISTB2 resident for level 2 IST-II.
S0IST100 ASCII resident for IST1.
S0IST3A IST3 ASCII resident used when loading the
ASCII resident while on the CIU.
S0IST300 resident for multi-function IST3.
S0LANG system -vocabs- blocks. Lists words which are
not permitted as misspellings of each other.
S0LDH3 Micro PLATO, Level 3, help lesson.
S0LDH4 Micro PLATO, Level 4, help lesson.
S0LDH5 Micro PLATO, Level 5, help lesson.
S0LDI3 Micro PLATO, Level 3, diskette initialization.
1
page 187
S0LDI4 Micro PLATO, Level 4, diskette initialization.
S0LDI5 Micro PLATO, Level 5, diskette initialization.
S0LIB library of routines available to system lessons.
S0LINSET1 continuation of lineset editor.
S0LOADH help lesson for "s0load2".
S0LOAD2 Micro PLATO, Level 2, disk loading utility.
S0LOAD3 Micro PLATO, Level 3, diskette management.
S0LOAD4 Micro PLATO, Level 4, diskette management.
S0LOAD5 Micro PLATO, Level 5, diskette management.
7.3.19.3 Files: s0m - s0o
S0MAINT used by group "s" to generate new PLATO
binaries from source.
S0MENU used by the PLATO Menu.
S0MPDEFS4 use file for level 4 Micro PLM on the CDC 110,
and PPTS.
S0MPLIB3 Micro PLATO, Level 3, unit library.
S0MPLIB4 Micro PLATO, Level 4, unit library.
S0MPRD2 "mprouter", Level 2, German version.
S0MPRD3 "mprouter", Level 3, German version.
S0MPRD4 "mprouter", Level 4, German version.
S0MPRE2 "mprouter", Level 2, English version.
S0MPRE3 "mprouter", Level 3, English version.
S0MPRE4 "mprouter", Level 4, English version.
S0MPRF2 "mprouter", Level 2, French version.
S0MPRF3 "mprouter", Level 3, French version.
S0MPRF4 "mprouter", Level 4, French version.
S0MPRS2 "mprouter", Level 2, Spanish version.
S0MPRS3 "mprouter", Level 3, Spanish version.
S0MPRS4 "mprouter", Level 4, Spanish version.
1
page 188
S0MPRUSE2 use file for "mprouter", Level 2.
S0MPRUSE3 use file for "mprouter", Level 3.
S0MPRUSE4 use file for "mprouter", Level 4.
S0MPR2 "mprouter" author options, Level 2.
S0MPR3 "mprouter" author options, Level 3.
S0MPR4 "mprouter" author options, Level 4.
S0NEDIT general notes text editor.
S0NETPRT network database print program.
S0NETSYS network system table editor.
S0NETUSE use file for "pnet", "s0pnet" and "netmon".
S0NINDEX "notes" index editor.
S0NOTES system TERMs: ask, comment, pnote.
S0NOTRUN inter-system notes distribution runner.
S0ORDER management utility for Homelink
S0ORIENT system TERMs: J, japanese, oriental and code
for the -loadm- command.
7.3.19.4 Files: s0p - s0pn
S0PACER ASCII user stimulator.
S0PCD3 Central PLATO Courseware Design, Development
and Delivery (PCD3) Executor.
S0PCLD4 PC Micro PLATO disk utility, Level 4 V2.2.
S0PCOM database of information defining attributes
of supported terminal types.
S0PDED2 off-line dataset editor.
S0PFE router lesson for the PLATO Menu.
S0PFEH help lesson for the PLATO Menu.
S0PHELP help lesson for "print".
S0PINDEX PLATOSCRIBE system controller options.
S0PLIB auxiliary file for on-line print lessons.
S0PLIST people list editor for Teleconferencing and
the PLATO Calendar utility.
1
page 189
S0PLMDLL PLM 110 conversion program.
S0PLMMTR monitor mode options for PLM off-line testing.
S0PLMOBJ Dataspeed 40 version of "plmobj".
S0PLMPR PLM print instructions.
S0PLMREC Dataspeed 40 version of "plmrecords".
S0PLMRET Dataspeed 40 version of "plmreturn".
S0PLMROUTE Dataspeed 40 version of "plmrouter".
S0PLMRX Dataspeed 40 version of "plmrx".
S0PLMTEST Dataspeed 40 version of "plmtest".
S0PLMUSE use file for PLM.
S0PLMUTIL PLM utility lesson.
S0PLM1 reserved file name.
S0PLM2 reserved file name.
S0PLNDX PLATOSCRIBE Plus system controller options.
S0PLUS PLATOSCRIBE Plus router.
S0PLUSH PLATOSCRIBE Plus router HELP lesson.
S0PNET continuation of "pnet".
S0PNETRN allows automatic repetition of network messages.
S0PNILF used to convert terminal resident binaries to
a form acceptable to NAM and stores them in a
NOS permanent file.
S0PNIMTR displays statistics concerning NAM/PNI network
performance.
S0PNS auxiliary file for on-line print lessons.
7.3.19.5 Files: s0po - s0z
S0PPT library of programmable terminal routines.
S0PREG GUIDE driver connection for Teleconferencing.
S0PREHLP detailed help displays for Teleconferencing.
S0PRESENT presentation driver for Teleconferencing.
S0PRINT prints TUTOR files and datasets when using a
1
page 190
Magnavox terminal.
S0PRINTD on-line print program for notes files and PLM
modules.
S0PRINTU use file for on-line print lessons.
S0RECUSE use file for "records".
s0REL On-line version of the SRB document.
S0RHP 2550-based inter-system link driver.
S0ROSTER editor for PLATOSCRIBE, PLATOSCRIBE Plus and
PLATO Menu groups.
S0ROUTE used by "s0netprt" to route output to printer.
S0SCHED PLATO Calendar utility.
S0SCHEDH help lesson for "s0sched".
S0SCHEDRIV GUIDE driver for "s0schedh".
S0SCHEDSYS database clean-up routines for "s0sched".
S0SCRIBE PLATOSCRIBE router.
S0SCRIBEH PLATOSCRIBE help lesson.
S0SHOWC allows users with a "Taiwan ROM box" to plot
Chinese characters from a Micro PLATO lesson.
S0SPELL TERM-spell database.
S0STEP system TERMs: step, spell.
S0STIMxx files used by stimulator program (1 _ xx _ 10).
+ < <
S0SUBFIL used to deliver subfiles (commons, leslists, etc.)
to remote systems for addition to "sysfile" or
"s0sysfile".
S0SYSCOM contains subfiles which are delivered with
every release, as opposed to those which are
site-specific. Subfiles in this file are:
TTPARAM table of data used by the -showk-
command.
S0TALK system TERMs: talk, confer, busy, reject,
consult, operator.
S0TERMS system TERMs: calc, grid, cursor, local, time,
charset, and the excess processing warning.
S0UFLOP use file for "floppy".
1
page 191
S0ULD3 use file for "s0ldi3", "s0load3" and "s0unit3".
S0ULD4 use file for "s0ldi4", "s0load4" and "s0unit4".
S0ULD5 use file for "s0ldi5", "s0load5" and "s0unit5".
S0UNIT2 Micro PLATO, Level 2, unit editing.
S0UNIT3 Micro PLATO, Level 3, unit editing.
S0UNIT4 Micro PLATO, Level 4, unit editing.
S0UNIT5 Micro PLATO, Level 5, unit editing.
S0USERDS help displays for "user".
S0VIDEO support routines for the Central System
Videodisc Library product
S0V72100 terminal resident for CDC 721 (Viking) terminal.
S0XCOM command list for "mpxlator".
S0XEST used to estimate the work involved to translate
a file via "mpxlator".
S0XLATE PLATO Author Language to Micro PLATO translater.
S0XMIT TRANSMIT feature.
7.3.20 Files: t
TRANSFER used to install system software and courseware.
TRANSMIT TRANSMIT documentation.
7.3.21 Files: u
U general utility routines.
USER shows list of users currently signed on and
allows changing personal information and flags.
UTILITY general debugging tools.
7.3.22 Files: v
VOCABEDIT vocabulary block editor.
7.3.24 Files: x
X reserved file name.
7.3.26 Files: z
ZFROML reserved file name.
1
page 192
Z1REPORT used to convert accounting data stored in file
"z1acnt" and store it in "z1data".
7.3.27 Files: 0 - 9
0 reserved file name.
1
page 193
7.4 System-Specific Files/Subfiles
The following files and subfiles are unique to each system.
They contain system-specific information and are thus not
delivered with each release. Normally, these files are kept
in account "s0files" if they exist at all. Some files are
optional depending on whether the corresponding feature is
available at the site.
7.4.1 Files: a
ACCERRLOG used by "accountu".
type - student datafile
size - 4 parts
ACCFILES used by "accountu".
type - dataset
size - 8 parts
ACCLOG0 file management log.
type - student datafile
size - 18 parts
ACCLOG1 file management log.
type - student datafile
size - 18 parts
ACCLOG2 file management log.
type - student datafile
size - 18 parts
ACCLOG3 file management log.
type - student datafile
size - 18 parts
ACCOUNTCOM accounts database. Subfiles in this file are:
ACCOUNTCOM 8000 word common
ANNOUNCE general notes file used by PLATO system personnel
for special announcements.
Default access:
p director
others read only
AUTHPL account used by Courseware Services.
A0PSOLESS useful files / lessons available to users.
1
page 194
A0SS1 miscellaneous system-specific displays.
7.4.2 Files: b
BULLFILE contains system bulletin board display.
B0rid The "authors" package uses a set of files for
each system for which an index exists. there
is one file named "b0(routing id)" and one
or more files named "b0(routing id)(letter)".
These namesets are automatically created when
the "authors" package is initialized on a new
system and new ones may be created through the
"authors" director options.
For example, assume you are on system "abc" and
that you also have "authors" data for the "min"
and "bru" systems. You would have the following
files:
a. b0abc, b0abca, b0abcb, ....
b. b0min, b0mina, b0minb, ....
c. b0bru, b0brua, b0brub, ....
The actual number of files depends on the number
of authors on each system. These database
files may be exchanged between systems through
the PLATO Inter-system Link or via tape. Refer
to the PLATO Operations Guide for information
on how to do this.
7.4.3 Files: c
CATDS used to hold user routing information for
re-entry to the published lesson catalog from
a lesson which was entered from the catalog.
type - nameset
records - 65
record size - 64 words
names - same as the number of records
name size - 30 characters
CESAVEDSET used to hold user's condense error information
when going to AIDS for a command description so
it may be restored on return to the condense
error display.
type - dataset
size - 3 parts
record size - 160 words
CONDATA contains consult statistics.
type - dataset
size - 18 parts
record size - 64 words
1
page 195
CONVERTC group used for running file conversions.
CONVERTLL used by conversion programs. Subfiles in this
file are:
LIST 2400 lesson leslist
CONVERTLOG used by conversion programs.
type - student datafile
size - 12 parts
COSERV group used for published courseware management.
COSERVF account used by Courseware Services.
7.4.4 Files: d
D0x used for on-line copy of backups dump directory
("x" is a letter). The number of files needed
depends on the number of files on the system.
type - dataset
size - 32 parts
record size - 500 words
7.4.5 Files: e
EXSAVENSET holds execution error information when user
jumps to AIDS to get more information about a
command so it may be restored when returning.
type - nameset
records - 69
record size - 320 words
names - same as number of records
name size - 10 characters
7.4.12 Files: l
LESSNOTES general notes file used by PLATO system personnel
to report problems in published courseware. This
file is attached to almost all published course-
ware; TERM-comments done in published lessons will
automatically go here.
Default access:
coserv director
p read/write
pso director
s read/write
others write only
LOGLOG log of system maintenance activities which may
involve minor security breaches such as inspecting
a user file for which the systems person does
not have normal access.
1
page 196
type - student datafile
size - 18 parts
7.4.13 Files: m
M group used by communications and hardware
maintenance personnel.
7.4.14 Files: n
NARFILE account signon restrictions database.
type - dataset
records - 32 * number of physical sites
record size - 64 words
NS0NDATA new version of "notes" index display. This
file is edited by "s0nindex" and must be
copied into "s0ndata" to be made active.
7.4.15 Files: o
O group used by PLATO/NOS operators.
OPSNOTES general notes file used by users to communicate
with system controllers and operators.
Default access:
p director
o read/write
others write only
OS0NDATA old version of "notes" index display. This
file can be used to hold the last version of
the "notes" index display when "ns0ndata" is
copied into "s0ndata".
7.4.16 Files: p
P group used by system controllers.
PACCNS used by "pacedit" for account print request
access control.
type - nameset
records - same as maximum number of accounts
record size - 64 words
names - same as number of records
name size - 10 characters
PBNOTES general notes file used as a public forum for
topics of general interest to users.
Default access:
p director
others read/write
1
page 197
PLATOUSE contains any configurable sign-on displays.
PLMCOM PLM package subfiles. Subfiles in this file
are:
AIDSCOM 1280 word common PLM AIDS
CMILIBC 1280 word common library of
PLM courses
CMILIBM 1280 word common library of
PLM modules
PLMCOM1 PLM package subfiles. Subfiles in this file
are:
BACKOUT 320 word common user backouts
PLMUSERS 64 word common statistics
PLMHIST statistics for PLM package.
type - dataset
size - 1 part
record size - 64 words
PRINTLOG used by "prints" to store print requests.
type - dataset
size - 7 parts
record size - 320 words
PRTSUB contains NOS CCL procedures for submitting
print requests.
PS account used by the local services organization.
Initial access:
p director
other none
PSO group used by PLATO consultants.
PSONOTES general notes file used for communciation between
users and PLATO consultants.
Default access:
p director
pso director
others write only
PUBLISD account which contains published courseware.
Initial access:
coserv director
other none
PUBLISE account which contains published courseware.
Initial access:
1
page 198
coserv director
other none
PUBLISF account which contains published courseware.
Initial access:
coserv director
other none
PUBLISG account which contains published courseware.
Initial access:
coserv director
other none
PUBLISI account which contains published courseware.
Initial access:
coserv director
other none
7.4.18 Files: r
RUNC group used to monitor runner programs.
7.4.19 Files: s - sx
SINSPECT group used by PLATO support personnel.
SITES station location list.
SPECPL account for special release courseware. These
files are for special demonstrations.
Initial access:
coserv director
other none
SSECURITY security database for "site".
type - dataset
size - 10 parts
record size - 320 words
7.4.19.1 sys - sz
SYS group used to monitor "stats1" runner.
SYSENSET contains debugging information for execution
errors in system lessons.
type - nameset
records - 20
record size - 320 words
names - half the number of records
name size - 10 characters
1
page 199
SYSFILE system lesson subfiles. Subfiles in this file
are:
ALARMX 1280 word common "alarm"
ARCHIVE 320 word common "archiver"
AUTHORS 1920 word common "authors"
ASK 320 word common TERM-ask
BINARY 320 word common "binary"
CLOGCOM 320 word common "c"
CONDND source block "sysopts"
CONSTATS 640 word common "constats"
CONSULT 320 word common "c"
ECSALLOT 2560 word common EM allocation
table
ENFORCER 1500 word common "enforcer"
EXEC source block "sysopts"
FLOPPY 320 word common "floppy"
FRAMDM source block "sysopts"
IPARAMS 320 word common "ipedit"
KIOCOM 2240 word common "netmon"
LESSONS 960 word common reserved
lesson list
LINK 320 word common network system
table
LSLTCOM 320 word common logical site
lesson list
NETMON 320 word common "netmon"
NOTESCLEAN 160 lesson leslist notes file
cleanup list
NOTESTAT 320 word common "notes"
OPERATOR 320 word common TERM-operator
PNET 1280 word common "pnet"
PNETON 320 word common "pnet"
PNID source block "sysopts"
PNOTESCOM 320 word common "pnotes"
PRINTS 960 word common "prints"
RUNNERCOM 2340 word common runner lesson
list
SERVICE 640 word common "serv1"
SIGNONCOM 4160 word common autosignon
list
SITE 1600 word common "site"
SIZECHARS 640 word common sized write
characters
SPELLCOMM 640 word common TERM-spell
STATSCOM 960 word common "stats"
S0RHP 1280 word common "s0rhp"
ZLANG 320 word common "ipedit"
SYSLN general notes file attached to almost all system
lessons; TERM-comments done in system lessons
will automatically go here.
Default access:
p director
pso read/write
1
page 200
others write only
SYSTEM account file which contains all global system
files.
Initial access:
support people/s director
Other/s inspect
Other/system inspect
Other/p inspect
lengthen/shorten
Other/Other none
SYSTEST group used by stimulated terminals.
SYSWORK workspace for support requirements.
SYSWORK1 workspace for support requirements.
7.4.19.2 s0a - s0l
S0ARCH account used as temporary residence for archived
files awaiting off-line copy.
S0ARCHDS archive retrieval requests.
type - dataset
size - 1 part
record size - 64 words
S0BACKA file dumps/backups audit trail.
type - dataset
size - 2 parts
record size - 300 words
S0BACKC file dump/backups parameters and tables.
type - dataset
size - 8 parts
record size - 320 words
S0BCKCOM "backups" subfiles. Subfiles in this file are:
REQUEST 960 word common requests
STATS 64 word common statistics
S0BITPARAM database for BITNET system table.
type - nameset
record size - 128 words
name size - 10 characters
S0CIUNA "ciudiag" database.
type - nameset
records - 622
1
page 201
record size - 64 words
names - 71
name size - 30 characters
S0CMPx one file per CONDENSOR used when condensing
central Micro PLATO lessons (x = 0,1,2).
type - TUTOR
size - 18 parts
S0COMMON system lesson subfiles. Subfiles in this file
are:
CIUDIAG 640 word common "ciudiag"
PNETRUNCOM 320 word common "pnet"
S0CPUSTAT 3005 word common "s0cpustat"
S0NETPRT 320 word common "s0netprt"
S0XMIT 320 word common "s0xmit"
S0XMIT 160 lesson leslist "s0xmit"
UTILITY 320 word common "utility"
S0CPUDATA used to store weekly CPU usage statistics.
type - nameset
records - 8 * number of names
record size - 64 words
names - number of weeks of data wanted
name size - 10 characters
S0EMAILDS dataset for BITNET mail transfers
type - dataset
record size - 128 words
S0EMAILNS nameset for BITNET mail
type - nameset
record size - 320 words
name size - 20 characters
S0FILE system subfiles. Subfiles in this file are:
SYSID 320 word common routing ID
PUBCWARE 320 word common published
courseware
access limits
S0FILES account for system-specific PLATO files.
Initial access:
p director
other none
S0ISTLF used by "s0pnilf".
type - dataset
size - 3 parts
1
page 202
record size - 64 words
S0LINKDATA log file for inter-system link file requests
made through network options of "accounts".
type - student datafile
size - 4 parts
S0LOG log file for "transfer".
type - student datafile
size - 18 parts
S0MON used by "netmon" to log terminal I/O errors.
type - nameset
records - 405
record size - 320 words
names - 39
name size - 10 characters
7.4.19.3 s0n - s0z
S0NDATA "notes" index displays.
type - nameset
records - 2 * number of names
record size - 128 words
names - 5
name size - 30 characters
S0NETWK port information for "pnet".
type - nameset
records - 18 * number of physical sites
record size - 64 words
names - number of physical sites
name size - 10 characters
S0NETWK1 configuration data for "pnet".
type - nameset
records - 682
record size - 64 words
names - 303
name size - 20 characters
S0NOTESET "notes" sequencer.
type - nameset
records - two per user
record size - 64 words
names - one per user
name size - 10 characters
S0NOTESQ Inter-system Link "notes" queue.
1
page 203
type - nameset
records - 138
record size - 128 words
names - 2
name size - 10 characters
S0PLMCOM1 Dataspeed 40 version of "plmcom1".
S0PLMHIST Dataspeed 40 version of "plmhist".
S0RHPDS Inter-system Link to NOS communication.
type - dataset
size - 1 part
record size - 320 words
S0RHPLOG error and data transfer log for Inter-system
Link.
type - student datafile
size - 5 parts
S0RHPNS Inter-system Link data queue.
type - nameset
records - 87
record size - 128 words
names - 5
name size - 10 characters
S0RUNRNS runner statistics.
type - nameset
records - 256
record size - 64 words
names - 32
name size - 10 characters
S0SCHEDATA PLATO Calendar Utility database. This file is
created automatically.
S0SUP account used by PLATO Support personnel.
Initial access: same as account "system".
S0SYSFILE system lesson access lists.
S0SYSMSG messages to the system controllers and operators.
Default access:
p director
pso read/write
o read/write
others write only
S0ULOG "utility" runner log file.
1
page 204
type - student datafile
size - 4 parts
S0XFER account used for inter-system link files.
Initial access:
p director
7.4.26 Files: z
Z1ACNT account summary data.
type - dataset
records - 1 + maximum number of accounts
record size - 320 words
Z1DATA account summary data reformatted by "z1report".
type - dataset
size - 3 parts
record size - 320 words
7.4.27 Files: 0-9
0CACOM courseware access limits table. This file is
delivered with the first courseware release.
0QUESTIONS general notes file used for communication
between users and PLATO Courseware Maintenance.
Initial access:
coserv director
other read/write
3NETINQ Inter-system Link data queue.
type - nameset
records - 100
record size - 128 words
names - 100
name size - 10 characters
3NETOUTQ Inter-system Link data queue.
type - nameset
records - 100
record size - 128 words
names - 100
name size - 10 characters
1
+ Table of Contents
1 Preface 1
1.1 Introduction 2
1.2 Operating System Compatibility 3
1.2.1 Operating System Dependency Chart 4
1.2.2 Hardware Dependency Chart 5
1.2.3 Operating system changes 6
1.3 Organization 8
1.4 Installation Materials 9
1.5 Where to Start 10
2 New System Installation Procedures 11
2.1 Introduction 12
2.2 Determine disk system configuration. 15
2.3 Create PLATO system user name(s). 16
2.4 Obtain files from installation tape. 18
2.5 Modify the ASCII network. 20
2.5.1 Modify network configuration file. 20
2.5.1.1 Sample NDL file. 21
2.5.1.2 Sample CDCNET Configuration file 23
2.5.1.3 Sample CDCNET NDL local config 24
2.5.1.4 Sample CDCNET User Procedure 25
2.5.1.5 Sample CDCNET User Procedure 26
2.5.2 Reinstall NAM and CCP. 28
2.6 Reinstall selected NOS programs. 29
2.7 Modify deadstart file text records. 30
2.8 Modify release procedure files. 32
2.8.1 PLATO configuration file 33
2.8.2 Procedure MFDX 34
2.8.3 Procedure MFNX 35
2.8.4 Submit file PLATOD 36
2.8.5 Procedure SETPUN 37
2.8.6 Procedure Z1DAILY 38
2.8.7 Procedure Z1ENDBC 39
2.9 Build new deadstart file. 41
2.10 Initialize ESM. 43
2.11 Deadstart on new deadstart file. 44
2.12 Load PLATO master files. 45
2.13 Create binary master file. 47
2.14 Load PLATO via PLAINS. 48
2.15 Initialize system files. 49
2.15.1 Installation parameters 50
2.15.2 EM allocation tables 52
2.15.3 System groups 53
2.15.4 Notes files 55
2.15.5 Bulletin board 57
2.15.6 Central print options 58
2.15.7 AIDS package 59
2.15.8 AUTHORS package 60
2.16 Install optional features. 61
2.17 Execute post-installation cleanups. 62
2.17.1 Delete "install" of group "p". 63
2.17.2 Run account cleanup programs. 64
2.17.3 Purge disk files. 65
2.17.4 Convert master files. 66
1
2.18 Install published courseware. 68
2.18.1 Courseware installation - details 69
2.18.2 Courseware installation - details 70
2.18.3 Courseware installation - details 72
2.19 Dump all master files. 74
2.20 Reload PLATO via PLATO. 75
3 Optional Installation Procedures 76
3.1 Archiving 78
3.2 Backups 79
3.3 Central Micro PLATO executor 80
3.4 Network database 81
3.5 Computer Interface Unit network 82
3.6 TRANSMIT Utility 83
3.7 PLATO Inter-System Link 84
3.7.1 Determine accounting method 84
3.7.2 Create NOS user names 84
3.7.3 Modify network configuration file 86
3.7.4 Modify PLATO network system table 88
3.7.5 Create system-specific files 89
3.7.6 Install runner programs 89
3.8 PLATO-BITNET Email Gateway 90
3.8.1 Choose BITNET node name 91
3.8.2 Choose mailer name 91
3.8.3 Register with BITNET 91
3.8.4 Connect with BITNET 91
3.8.5 Install PLATO application 91
3.8.6 Install NJEF application 91
3.8.7 Define BITNET nodes 91
3.8.8 Create mailer user name 91
3.8.9 Create system-specific files 91
3.8.10 Define parameters in s0bitsys 92
3.8.11 Install runner program 92
3.8.12 Customize access lists 92
3.8.13 Define networks in s0bitsys 93
3.8.14 Define nodes in s0bitsys 93
4 Update Installation Procedures 95
4.1 PLATO Operations Changes 98
4.2 Update installation procedures 99
4.2.1 Execute pre-installation cleanups. 101
4.2.2 Obtain files from installation tape. 103
4.2.3 Reinstall NAM and CCP. 104
4.2.4 Reinstall selected NOS programs. 105
4.2.5 Change NOS validation files. 106
4.2.6 Change local deadstart file records. 107
4.2.6.1 Deadstart record changes 107
4.2.6.2 Deadstart record changes 109
4.2.6.3 Deadstart record changes 111
4.2.7 Change PLATO configuration file. 113
4.2.7.1 Configuration file changes 113
4.2.8 Build new deadstart file. 114
4.2.9 Clear operator action queues. 116
4.2.10 Complete file dumps. 117
4.2.11 Deadstart on new deadstart file. 118
4.2.12 Load release master files. 119
4.2.13 Change MFNX procedure. 121
1
4.2.14 Load PLATO via PLAINS. 122
4.2.15 Change existing access lists. 123
4.2.16 Change existing PLATO files. 125
4.2.16.1 Change existing PLATO files. 125
4.2.17 Destroy obsolete files. 126
4.2.18 Install new system lessons. 127
4.2.19 Initialize binary master file(s). 128
4.2.20 Reload PLATO. 129
4.2.21 Run required conversion programs. 130
4.2.22 Run file installation check. 132
4.2.23 Change local AIDS files. 133
4.2.24 Install new optional features. 134
4.2.25 Post-installation cleanups. 135
4.2.26 Dump all master files. 136
5 Mini-Release Installation Procedures 137
5.1 Obtain files from installation tape. 139
5.2 Perform special instructions. 140
5.3 Build new deadstart file. 141
5.4 Load mini-release master files. 142
5.5 Deadstart on new deadstart file. 143
5.6 Load PLATO via PLAINS. 144
5.7 Change existing PLATO files. 145
5.8 Initialize binary master file(s). 146
5.9 Post-installation cleanups. 147
5.10 Reload PLATO. 148
6 Reinstallation Procedures 149
6.1 Obtain files from installation tape. 152
6.2 Reinstall NAM and CCP. 153
6.3 Reinstall selected NOS programs. 154
6.4 Change NOS validation files. 155
6.5 Build new deadstart file. 156
6.6 Deadstart on new deadstart file. 157
6.7 Load PLATO via PLAINS. 158
6.8 Initialize binary master file(s). 159
6.9 Post-installation cleanups. 160
6.10 Reload PLATO. 161
7 Bill of Materials 162
7.1 Central System 164
7.1.1 Records: A - L 164
7.1.2 Records: M - R 165
7.1.3 Records: S - Numeric 167
7.2 NOS Permanent Files 170
7.2.1 NOS Permanent Files (continued) 171
7.3 PLATO System Files 173
7.3.1 Files: a - az 173
7.3.1.1 Files: a0 173
7.3.2 Files: b 176
7.3.3 Files: c 176
7.3.4 Files: d 177
7.3.5 Files: e 177
7.3.6 Files: f 178
7.3.7 Files: g 178
7.3.9 Files: i 178
7.3.10 Files: j 179
1
7.3.12 Files: l 179
7.3.13 Files: m 179
7.3.14 Files: n 180
7.3.15 Files: o 180
7.3.16 Files: p 180
7.3.17 Files: q 183
7.3.18 Files: r 183
7.3.19 Files: sa - sz 183
7.3.19.1 Files: s0a - s0c 184
7.3.19.2 Files: s0d - s0l 186
7.3.19.3 Files: s0m - s0o 187
7.3.19.4 Files: s0p - s0pn 188
7.3.19.5 Files: s0po - s0z 189
7.3.20 Files: t 191
7.3.21 Files: u 191
7.3.22 Files: v 191
7.3.24 Files: x 191
7.3.26 Files: z 191
7.3.27 Files: 0 - 9 192
7.4 System-Specific Files/Subfiles 193
7.4.1 Files: a 193
7.4.2 Files: b 194
7.4.3 Files: c 194
7.4.4 Files: d 195
7.4.5 Files: e 195
7.4.12 Files: l 195
7.4.13 Files: m 196
7.4.14 Files: n 196
7.4.15 Files: o 196
7.4.16 Files: p 196
7.4.18 Files: r 198
7.4.19 Files: s - sx 198
7.4.19.1 sys - sz 198
7.4.19.2 s0a - s0l 200
7.4.19.3 s0n - s0z 202
7.4.26 Files: z 204
7.4.27 Files: 0-9 204
1 full dayfile. 97/11/05. 00.03.44.*00.03.15* page 1
00.03.15.admi.
00.03.15.user,prints,,systfa. admin,s
00.03.15.absc, s.
00.03.15.masjob,input,ss.
00.03.15.pf(pb,print,z,z),mods/prtsub,upperlower
00.03.16.note(param,nr)/77777777777777777777
00.03.16.note(param,nr)/77777777777777777777
00.03.16.pack,param.
00.03.16. pack complete.
00.03.16.note(printit,nr)/.proc,printit.
00.03.16.note(printit,nr)/docprt.install,system,s,admin
00.03.16.note(printit,nr)/*
00.03.16.pack(printit)
00.03.16. pack complete.
00.03.16.block,output.*cybis file*install*admin**s*
00.03.16.print(p0=,p1=$$,p2=$$,p3=$$)
00.03.16.setpr(30)
00.03.16.settl(7777)
00.03.16. tl = 7777.
00.03.16.*route,output,dc=pr,ic=bin,fc=as,def.
00.03.16.printit.
00.03.16.docprt.install,system,s,admin
00.03.44. stop
00.03.44. 043700 maximum execution fl.
00.03.44. 2.138 cp seconds execution time.
00.03.44.*
00.03.44.$revert.ccl
00.03.44.dayfile.
100.04.02.UCLP, OK, 030, 13.568KLNS.
