starter Systems r L
Real
Cylinder
o
2
3
6-8 9-10 11-15 16-19 20 21-56
57-64
65-554
Number of
Cylinder s
3
2
5
4
35
9 490 contents Unused 191 minidisk for the IVP!!l user
191 minidisk for the IVP!!2 user
191 minidisk for the RSCS user
191 minidisk for the OPERATOR user
191 minidisk for the CE user
191 minidisk for the !!AINT user
191 minidisk for the EC!!ODE user
199 minidisk for the !!AINT user 190 minidisk for the !!AINT user The, nucleus occupies the last cylinder
of the minidisk. (Specify cylinder 34.)
194 minidisk for the !!AINT user
Not used.
Figure 30. Allocation of the Starter System Volume (CPRnLO) When the 3350 Starter System Directory Is Used Step 20. Back Up the Newly Generated VM/370
At this time, back up your new system residence volume. If your real
machine has at least 448K bytes of real storage, the tape created in Step 1A is sufficient backup. However, that tape is not sufficient
backup for real systems with less than 448K of real storage because that
tape cannot be loaded on such systems. It may also be inadequate if you
have a large V=R area. V!!/370 systems that run on a real machine with less than 448K bytes
of storage should use the DASD Dump Restore (DDm service program
to create a backup tape similar to the one created in step 18. The DASD Dump Restore program is described in the !M/310 If
your system residence volume is at address 131 and you labeled it V!!RELn, you could use the following DDR control statements to back it
up:
input 131 device type V!!RELn output 181 device type (tape drive)
dump cpvol
The DUMP CPVOL statement causes cylinder 0 and those disk cylinders
allocated as PERM or DRCT in Step 2 to be dumped onto the tape.
254 IB!! VM/310 Planning and System Generation Guide

Starter Systems If you do not wish to use the DDR program to backup your system, you
can load the tape produced in Step 18 in a virtual machine. If you load
the tape in a virtual machine that virtual machine must have (1) 512K of
storage and (2) write-access to the system residence volume, at the
address defined for system residence in the SYSRES macro of the CP system control (DMKSYS) file.
When you use the DDR program to backup
load map when you restore the tape. You the tape produced in Step 18.
your system, you do not get a
do get a load map if you load Step 21. Format the Operator's Virtual 191 O-isk Before any new minidisk area can be used for CMS files; it must be
initialized with the CMS FORMAT command, which formats the area into
BOO-byte blocks. Take care not to format areas which contain data
restored from the starter system (such as the 190 and 194 minidisks
belonging to the user MAINT). The CMS FORMAT command is described in
the VM/370 CommaDg MacrQ Reference. After you complete this step, a portion of the starter system is
overlaid by the operator's 191 minidisk. If for any reason you wish to
IPL the starter system again, you must start from Step 1.
At this time you are logged on
procedure to format your virtual
already loaded CMS, issue:
as the operator. Use disk 191. First, if
ipl 190 parm seg=null CMS responds with: CMS VERSION n.n -mm/dd/yy hh:mm
Next, enter the following command:
access (nodisk
the following
you have not
The NODISK option prevents CMS from automatically accessing your virtual
disk 191. (Accessing 191 at this time would cause an error message to be
issued because 191 is not yet initialized, and therefore cannot be
used.) After the Ready message is displayed, issue the command:
format 191 a
The CMS FORMAT command prompts you with the following message: FORMAT WILL ERASE ALL FILES ON DISK 'A(191)'. DO YOU WISH TO CONTINUE? (YESINO): If you respond "yes", CMS prompts you with:
ENTER DISK LABEL:
opr1
Q
1
Enter the one-to-six character alphameric label of the virtual disk. You can use whatever label you wish for this virtual disk. In this
example, the label is OPR191. CMS then issues: FORMATTING DISK 'A'. Inn' CYLINDERS FORMATTED ON 'A(191) '.
and a Ready message. Part 3. Generating VM/370 (CP, CMS, RSCS, and IPCS) 255