#
Type the RETURN key
Type the date in format shown Type the RETURN key
Before the DIALOGUE query is answered, the disk to be used as the RSTS/E system disk should be mounted and write-enabled. In the case of an RK, RP~2, RP~3, or RP~4 system disk, an RK cartridge or an RP pack must be mounted on drive unit~. No special action is required for an RF system disk. SYSLOD does not recognize any device which is not mounted and ready when the DIALOGUE query is answered. The RETURN key is sufficient response to the DIALOGUE query. SYSLOD responds by printing the pound sign (#) when i t is ready to accept a command. A single command string is sufficient to create and load the elL onto the system disk and bootstrap the RSTS/E Initialization code into memory_
The exact command which must be entered depends on the type of system disk. If any error messages are printed by SYSLOD, consult Appendix E for the proper procedure to follow. The following command strings are used for the several types of system disks.
#DF:/NS:256:49/TO:4/HO/BO<DT0:RSTS.LCl
(RFll System Disk < DECtape)RSTS/E System Generation
#DK.0: /NS: 256: 4g/FO/TO: 4/HO/BO<DT.0: RSTS. LCL (RKll System Disk < DECtape)
#DK.0:/NS:256:49/FO/TO:4/HO/BO<MT.0:RSTS.LCL (RKll System Disk < TUl,e1 Magtape)
#DK.0: /NS: 256: 4g/FO/TO: 4/HO/BO<MM.0: RSTS. LCL (RKll System Disk < TU16 Magtape)
#DP.0: /NS: 512: 25/FO/TO: 4/HO/BO<DT.0: RSTS. LCL (RP,e12 or RP,e13 System Disk < DECtape)
#DP.0:/NS:512:25/FO/TO:4/HO/BO<MT.0:RSTS.LCL (RP,e12 or RP,e13 System Disk < TU1,e1 Magtape)
#DP.0: /NS: 512 : 25/FO/TO: 4/HO/BO<MM.0: RSTS. LCL (RP,e12 or RP,e13 System Disk < TU16 Magtape)
#DB.0: /NS: 1.024: 13/FO/TO: 4/HO/BO<DT.0: RSTS. LCL (RP,e14 System Disk < DECtape)
#DB.0: /NS: 1.024: 13/FO/TO: 4/HO/BO<MT.0: RSTS. LCL (RP,e14 System Disk < TU1,e1 Magtape)
#DB.0: /NS: 1.024: 13/FO/TO: 4/HO/BO<MM.0: RSTS. LCL (RP,e14 System Disk < TU16 Magtape)
Messages are printed at the console terminal when SYSLOD starts and ends formatting. If any other messages appear, consult Appendix E for possible recovery procedures. Upon completion of the load opera-tion, the RSTS/E initialization code is bootstrapped into memory
signalled by the printing of the OPTION query.
To load the CIL onto a non-zero unit, include the unit number in the output device designator (that is, DKn:, DPn:, or DBn:) and omit the /BO switch from the command string. After loading the CIL, SYSLOD reprints the # character. Although SYSLOD will load onto a non-zero unit, the pack or cartridge must be bootstrapped once from unit ~ to install a new bootstrap. Halt the processor and move the system disk to unit~. Bootstrap the device using the hardware loader to load the initialization code into memory.
After the OPTION query appears, proceed to Chapter 3 to initialize the system disk. If the OPTION query fails to appear, refer to the consistency errors described in Appendix B for possible recovery.
2.9.1.2 Disk Cartridge Procedures Using CILUS - When the disk cartridge distribution medium is used, the DOS program CILUS is used to load the RSTS/E CIL onto the system disk. CILUS does not format an RK cartridge, RP~2, RP~3, or RP~4 pack. Refer to Section 2.3.3 for procedures to load SYSLOD and format disks.
Mount the copy of the System Generation DECpack used for the system generation on RK unit~. Write enable the drive and bootstrap the cartridge to load the DOS/BATCH monitor. Refer to Appendix A for DECpack bootstrap procedures. When the DOS monitor identifies itself,
RSTS/E System Generation
DOS/BATCH V9-20C DATE: Il-JAN-75 TIME: 16:15 DIALOGUE?
!LO 1,1
DATE: Il-JAN-75 TIME: 16:15
!RUN GILUS CILUS V08-06A
#
Type the date in format shown Type the time in format shown Type the RETURN key
CILUS prints the pound sign (#) when it is ready to accept a command. The CILUS comnand string used to create and load the RSTS/E CIL depends on the type of system disk. If the RSTS/E system is con-figured for an RP~2, RP~3 or RP~4 system disk, mount a newly formatted
\pack on unit ~ and write-enable the drive. If the system is configured for an RK system disk, mount a newly formatted RK cartridge on RK
unit 1. No special action is required for an RF system disk. One of the CILUS commands shown below is then used to load the CIL.
#DF: /NS : 256: 4 9/TO: 4/HO/BO<DK0: RSTS • LCL/LO (RFll System Disk < RK cartridge)
#DK1: /NS: 256: 49/TO: 4/HO<DK0: RS'tS. LCL/LO (RKll System Disk < RK cartridge)
9~ '\:
Z
y~([J#DPW': /NS: 512: 25/TO: 4/HO/BO<DK0!: RSTS. LCL/LO (RP,02 or RP,03 System Disk < RK cartridge)
#DB0: /NS: 1024: 13/TO: 4/HO/BO<DK0: RSTS. LCL/LO (RP,04 System Disk < RK cartridge) If the system disk is an RF11, RP~2, RP~3, or RP~4, the CILUS com-mand loads the CIL and then bootstraps the RSTS/E initialization code
into memory. The INIT code prints the system name followed by the OPTION query. The system manager should proce~d to Lnitialize the sys-tem disk as described in Chapter 3.
The command to load the CIL onto the RK cartridge mounted on unit 1 does not bootstrap the RSTS/E Initialization code. When the
load operation is complete, CILUS reprints the pound sign (#) and waits for another command. The system manager exits from CILUS and terminates the DOS monitor as shown below.
RSTS/E System Generation
#"C
\KI ( $FI
\
-)
TIME: 16 : 16 : 16
, DOS/BATCH V9-20C
1
CONTROL/C exit from CILUS
"KILL" required by DOS FInish for an orderly exit
Halt the processor by moving the HALT/ENABLE switch to the HALT position. Dismount both cartridges and move the RSTS/E system disk to RK unit~. When the disk is ready, write-enable the drive and bootstrap the disk cartridge (see Appendix A) to load the RSTS/E initialization code into memory. Proceed to Chapter 3 to initialize the new system disk.
To load the CIL onto a non-zero unit, include the unit number in the output device designator (that is, DKn:, DPn:, or DBn:) and omit the /BO switch from the command string. After loading the CIL, CILUS reprints the # character and awaits another command. Although CILUS will load onto a non-zero unit, the pack or cartridge must be boot-strapped once from unit ~ to install a new bootstrap. Halt the processor and move the system disk to unit~. Bootstrap the device using the hardware loader to load the initialization code into memory.
Proceed to Chapter 3 to initialize the system disk.
RSTS/E System Generation
2.9.2 Replacing the RSTS/E System Code
It is possible to replace the RSTS/E CIL on the system disk with-out destroying the file structure. This capability is important when a new system is generated to add or change hardware support or soft-ware features. The SYSLOD or CILUS command strings used for this pur-pose are similar to those in Section 2.9.1 but several precautions should be taken to ensure a successful replacement. Careful adherence to these procedures is critical to avoid destroying the existing file structures (system and user files) on the system disk.
It is impossible to determine the exact size of the new CIL until i t is loaded onto a disk. The first step in replacing the CIL, there-fore, is to load the new monitor onto a scratch disk using the standard system generation procedures or the SYSLOD or CILUS commands described in Sections 2.9.1.1 and 2.9.1.2. The scratch disk must be initialized using the DSKINT initialization option (see Section 3.3) to create the RSTS. CIL fi-le. When a disk is initialized, pattern checking for bad blocks is normally done. However, requesting zero patterns causes DSKINT to bypass the pattern checks, saves time, and is a reasonable shortcut for the scratch disk.
The REFRESH initialization option (Section 3.4) is used after DSKINT to check the required size of the new RSTS.CIL file. REFRESH can be stopped by typing CONTROL/C after the file status table is printed. Since the scratch disk is used only to determine the size of the new RSTS.CIL file, i t is of no further use after these opera-tions are performed. The loading of the new system onto a scratch disk and the DSKINT and REFRESH operations take a total of about l~
minutes.
The next step is to determine the size of the CIL to be replaced.
Simply obtain a directory of the system files account [~,l] under time sharing or print the file status table using REFRESH (see Section 3.4.3.2). The important item is the current size of the RSTS.CIL file on the system disk. The REFRESH procedures of Section 3.4 recommend that this file be made larger than the required size when the system disk is initially built. If the system manager planned for a future replacement of the system code, the current size of the old RSTS.CIL
RSTS/E System Generation
If the old CIL is larger, the replacement can proceed as de-scribed in subsequent paragraphs. Otherwise, the system manager can attempt to increase the size of the old RSTS.CIL file using REFRESH before attempting the replacement. If the REFRESH is suc-cessful, he can proceed. If REFRESH cannot increase the size of the old RSTS.CIL file to at least the required size of the new RSTS.CIL file, the replacement cannot be performed. All library and user files must be transferred to another disk or external medium and the system disk must be initialized (destroying the existing file structure).
Assuming the RSTS.CIL file on the system disk is large enough to accommodate the new CIL, the next step is to transfer all library and user files from the system disk to a secondary storage medium.
This is a time consuming but important precaution since a typograph-ical error or a hardware malfunction while replacing the old CIL could be disastrous. The transfer is performed under time sharing using the old system. The next two sections present the SYSLOD and CILUS command strings which replace the old CIL.
2.9.2.1 DECtape and Magtape Procedures Using SYSLOD - The tape created during system generation contains a copy of the stand-alone program SYSLOD. SYSLOD is loaded from DECtape or magtape using one of the hardware bootstrap loaders described in Appendix A. When SYSLOD is bootstrapped into memory, it identifies itself by printing the following lines.