003 - Deadstart New Disks

003 - Deadstart New Disks

Before Proceeding

When deadstarting the updated system, several things should be noted at each interstitial checkpoint. Please be certain to follow the instructions closely. Almost everything is restartable but great attention has been paid to getting the documentation aligned with the current distributions.

3.1 Check Tape Configuration

Ensure that the deadstart tape is still mounted

[YourSystem] Operator> show_tape > Magnetic Tape Status: > --------------------- > 679 C13 E00 U00 r tapes/ds.tap > 679 C13 E00 U01 (idle) > 679 C13 E00 U02 (idle) > 679 C13 E00 U03 (idle) > 5744 C23 E00 U00 (connecting) > 5744 C23 E00 U01 (connecting) > 5744 C23 E00 U02 (connecting) > 5744 C23 E00 U03 (connecting)

3.2 Start CYBIS

Ensure that the control points have all “settled” properly and all supported services have started correctly.

Start CYBIS.

3.3 Check Disk Configuration

Double-Check RTR1 and GEN1

When you first deadstart the system with the new disks in place, they will be “visible” to dtCyber but not to NOS. A quick check of the e,c. NOS console command will show you the following:

Likewise, verifying the state of the disks on the dtcyber console by issuing the show_disks command will display the following:

[YourSystem] Operator> sd > Disk Drive Status: > ------------------ > 885 C01 E00 U00 disks/DQ10 (cyl 0x00010c trk 0x000010) > 885 C01 E00 U01 disks/DQ11 (cyl 0x0000b7 trk 0x000014) > 885 C02 E00 U00 disks/DQ12 (cyl 0x00010b trk 0x000045) > 885 C02 E00 U01 disks/DQ13 (cyl 0x000074 trk 0x000014) > 844 C11 E00 U00 (unmounted) > 885 C03 E00 U00 disks/DQ20_BINARY (cyl 0x000000 trk 0x000000) > 885 C04 E00 U00 disks/DQ21_CYB0 (cyl 0x000000 trk 0x000000) > 885 C03 E00 U01 disks/DQ22_CYB1 (cyl 0x000000 trk 0x000000) > 885 C04 E00 U01 disks/DQ23_PUB0 (cyl 0x000000 trk 0x000000) > 885 C03 E00 U02 disks/DQ24_PUB1 (cyl 0x000000 trk 0x000000) > 885 C04 E00 U02 disks/DQ25_UOL (cyl 0x000000 trk 0x000000) > 885 C03 E00 U03 disks/DQ26_RTR1 (cyl 0x000000 trk 0x000000) > 885 C04 E00 U03 disks/DQ27_GEN1 (cyl 0x000000 trk 0x000000) 2025-03-26 10:15:28 [YourSystem] Operator>

When thinking about the CYBIS packs as distributed, it's best to think of the entire group of them as a point-in-time consistent set:

DQ20_BINARY through DQ25_UOL (for CYBIS Release 1)

DQ20_BINARY through DQ27_GEN1 (for CYBIS Release 2)

Do not attempt to use “some packs” from one installation and “other packs” from another unless you really know what you are doing.

3.4 Connect to CYBIS

You may now connect to the running system using PTerm:

The first thing to note is that the login page has change to the more “CERL-like” look and feel.

Upon logging in as admin/s, you will see the following:

There are several items to note here:

The SYSTEM: ncc identifier appears next to the –> prompt.
You will see a system error message from stats1: $ check date/time Ignore This
The distributions are color coded.
1. Line 1 of the SYSTEM MODE display will indicate Retro1/Repo to assure you of where you are in the process.
2. Line 2 will indicate “Blue/Origin” or “Red/Target” (and others) depending on the distribution you have received ¹⁾.
You should, on the dtCyber console, turn idle off using the idle off command.

SID (system identifier) and RID (routing identifier)

The NCC System defines the SID and RID parameters in the file configx under User Number o377773 (User: PLATOMF Password: PLATOMF). The Retro1 version of CYBIS maintains these system identifiers in the deadstart file config which will be set during the following steps.

Do Not Do The Following Yet

Purging this file requires console access

 NOS> x.dis.
 NOS> user,platomf,platomf.
 NOS> purge,configx.
 NOS> drop.

If you do not purge CONFIGX and have defined the SID and RID in CONFIG, CYBIS may fail. Nothing will be harmed if this happens to occur.

004 - Build New PLATO

¹⁾

These distributions are coded for function/feature tracking purposes.