Table of Contents
Building PLATO from Source
To perform this procedure, you must be working on a relatively unmodified version of CYBIS(PLATO) via PTERM and all systems must be up and running properly before it can be properly executed.
Overview and Warnings
- It is expected that the implementer has sufficient understanding of
- dtCyber Operation
- NOS2 Commands and Syntax
- The running version of dtCyber is at least
- The running version of PTerm is at least version
- While it is preferable to build from the latest “ready to run” distributions, you may wish to apply these modifications to a running
CYBIS Release 1system. If that is the case, this tape of modifications will be MANUALLY APPLIED during this procedure. The most critical files from this tape CYBIS Lessons contain some required system modifications and tools.
Building PLATO from sources is a little complicated, but having a running PLATO system is essential because some of the configuration information must be taken from within PLATO code files:
- PLMODS Contains “persistent” modifications to
- TPMODS Contains “temporary” modifications to
- GOGOMODS Contains modsets used all assemblies, except the code-sharing full assemblies, and not applied permanently to *platopl*.
The modsets in this file are active during
gogoonly; they are partialled out before the codesharing assemblies are run. The programmers must reactivate their modsets each week after codesharing is finished.
- CYBMODS Contains modsets used in all assemblies and applied permanently to *cybopl* each week. These mods should only contain
It may be more educational to perform many of these steps manually because there is an opportunity to learn more about the process when performing these steps interactively.
- This procedure assumes that you are working from a “ready to run” version of the NCC NOS/PLATO installation.
- You must be running from the deadstart configuration you intend to use as the foundation for building the NEW deadstart configuration.
- BACK UP everything - at least you'll have something to fall-back on if anything gets destroyed
You Have Been Warned
Correct the NET Config
During the NCC automated installation, a tape
PFDUMP format which is used to build and pre-load ALL of the procedures and files necessary to run a DEVELOPMENT version of PLATO.
- As installed, NDL (
cybis-ndl.job) needs to be modified to correct a problem with PNI errors. To correct this, open the file located in
optand locate the input block. Add the parameters
TERMDEVstatement as shown below:
CYBIS *IDENT CYBIS *DECK NETCFG *D 85,86 LI02P: GROUP, PORT=14,L9600,NI=16. TE02P: TERMDEV, TASX364,ABL=7,DBL=5. *I 196 CYBUSER: DEFINE, MFAM=CYBER,MUSER=SYS,MAPPL=CYBIS. *D 220,221 TE02P14: USER, CYBUSER. TE02P15: USER, CYBUSER. TE02P16: USER, CYBUSER. TE02P17: USER, CYBUSER. TE02P18: USER, CYBUSER. TE02P19: USER, CYBUSER. TE02P1A: USER, CYBUSER. TE02P1B: USER, CYBUSER. TE02P1C: USER, CYBUSER. TE02P1D: USER, CYBUSER. TE02P1E: USER, CYBUSER. TE02P1F: USER, CYBUSER. TE02P20: USER, CYBUSER. TE02P21: USER, CYBUSER. TE02P22: USER, CYBUSER. TE02P23: USER, CYBUSER.
Re-Submit the deck at the
dtCyber console. You will need to completely restart
NAM once this job is complete.
Extract Current Configuration
Extracting the current configuration files from the current Deadstart tape and maintaining them in one place will make creation of deadstart tapes much easier in the future.
This procedure assumes that the distribution of baseline masterfiles and configuration parameters have been untouched, but keeping a current copy of them in a PLATO file
dstmods will make the merge process much easier when upgrading in the future.
- On PLATO
- Add file
2parts of space.
- create three NORMAL CODE BLOCKS in code file
dstmodscontaining only a single character (asterisk is fine):
- On the NOS CONSOLE, enter the following commands:X.DIS. SUI,377777 GTR(SYSTEM,EQPDECK)TEXT/EQPD01 GTR(SYSTEM,CONFIG)TEXT/CONFIG GTR(SYSTEM,MFNX)PROC/MFNX PF(W,PB,EQPDECK,DSTMODS,EQPDECK,S) PF(W,PB,CONFIG,DSTMODS,CONFIG,S) PF(W,PB,MFNX,DSTMODS,MFNX,S) DROP.
- The steps above
- obtain the current system file
- retrieves the three decks from the current system file
- EQPD01 the Equipment Deck
- CONFIG the PLATO Configuration file
- MFNX the PLATO Masterfile Configuration file
- writes the three decks from
- ends the
Load the Configuration Files from Tape
On the NOS CONSOLE, enter the following commands:
Verify that PLMODS, WSBATCH, CYBMODS all are correct by viewing them through PLATO.
All of the necessary mods have been partialed-in EXCEPT those found in block
devuol should be partialed
- OUT for Production systems.
- IN for Development system.
At this point, all of the necessary setup is complete and it is now possible to build PLATO.
Make sure the idle throttling is OFF while performing this build.
Automatic processing will continue …
… When it completes:
Examine all files and pay particular attention to the file
ERRS. If the file size is 0, then the procedure was completed successfully.
ERRS is not empty, review its contents to make sure that you may proceed safely.
Retrieve the file from the printer and examine it to ensure that no critical errors occurred.
If all is well, save the listing file “FULL” to “LISTF”
Make Product Distribution Tapes
Product Distribution tapes are made so they may be used to reload the necessary binaries if needed in the future.
CONFIG and MFNX
If you have made customizations to the PLATO pack layout, you must note that the distribution files contain the default
MFNX files which do not contain any locally created masterfiles.
Start a new DIS session to make the new tape files:
When the procedure is complete, you may mount a new empty tape (this procedure assumes that the tape is to be loaded on tape drive 13,0,1 / Unit 51).
Load a **RELEASE** Tape
If you are building DEVELOPMENT Release tape, skip to the next section.
Load a tape on dtCyber:
Load a **DEVELOPMENT** Tape
Load a tape on dtCyber:
Make Distribution Tape
Dismount the tape from dtCyber:
Make New Deadstart Tape
Creation of a new Deadstart tape is a CONTINUATION of the previous step.
Mount a fresh tape to receive the deadstart file:
Mount the CURRENT Deadstart Tape
LIBEDIT output to ensure that everything looks correct.
NEWDS to the new deadstart tape:
At this point, the new deadstart tape should be ready to run.
Edit the new deadstart tape name into
cyber.ini and restart dtCyber/NOS.
Verify that everything works properly.
Apply Local Changes
If your configuration deviated from the baseline configuration, a new deadstart tape will need to be made from the files saved earlier in this procedure.
On dtCyber load up a new empty deadstart tape:
We retrieve the previousy saved configurations from the running system:
Edit the new deadstart tape into
Shutdown everything and deadstart with the new tape.
All masterfiles should be in the right place!