Apr1l 1, starter Systems When the nucleus is written on your system residence volume, the
resultant load map is placed in your virtual reader by the CLOSE PRT command. This load map should be read in as a uniquely named CMS file.
After the new system is operational, the disk-resident load map is
required for IPCS. If you have limited space available on the starter system minidisks, read the load map onto the CMS system disk (190). Issue the following commands:
link cmssys 190 190 w write
access 190 a
read cpnuc loadmap
LOADING A CP NUCLEUS WITHOUT A VIRTUAL=REAL AREA
If you responded "no" when asked if you wanted the virtual=real area,
the GENERATE EXEC procedure builds the CP nucleus, writes it to tape,
and loads it from the tape. When the nucleus is written on the system residence volume, the message NUCLEUS LOADED ON volid
is issued, where volid is the volume serial number of your system
residence volume. The volid is the serial number you specified on the SYSRES macro when you prepared the CP system control file (DMKSYS). If
you followed the example in this manual, the serial number of your
system residence volume is VMRELn. The CP load map is placed in the virtual reader of CPGEN. This load
map should be read in as a uniquely named CMS file. After your new system is operational, the disk resident load map is required for IPCS. To save the load map, issue the following commands:
close prt
ipl 190 parm seg=null
access 194 a
read cpipcs map a
If you wish, edit or print the load map. The contents of the load
map are described in Part 5. "Updating VM/370". You may now drain all spooling devices and shut down the system by
entering:
drain all
shutdown
If an error occurs, and you do not receive the "NUCLEUS LOADED ON volid" message, issue the commands
cp spool prt off
close printer
to allow the error load map to be printed and examine the listing of the
load map_ A loader error may be indicated. See the Me§§ggg§ for a list of the loader wait state codes.
248 IB' VM/370 Planninq and System Generation Guide

Page of GC20-1801-10 As Updated April 1, 1981 by TNL GN25-0837 Starter Systems A loader failure may occur as the result of an error in the real I/O configuration (DHKFIO) file or the system control (DKKSYS) file. Check
that the assemblies of these files completed without error. Also check
that these files hqve CSECT cards and that macros are included in the
proper sequence. If an "OVERLAY ERROR" occurs, a common cause is
insufficient virtual storage for your virtual machine.
After correcting the error, you do not have to shut down the system,
but reinvoke the GENERATE EXEC at the point at which the error occurred. (See step 16.) LOADING A CP NUCLEUS THAT HAS A VIRTUAL=REAL AREA
If you responded "yes" when asked if you wanted the virtual=real area,
the GENERATE EXEC procedure issues the following message:
IF YOU HAVE ACCESS TO A DISK WITH THE SAME ADDRESS AS THE SYSRES DEVICE, DETACH IT. IPL THE NUCLEUS JUST PLACED ON THE TAPE AND
THEN YOU WILL BE ABLE TO SAVE THE LOAD MAP AS DESCRIBED ABOVE. YOU WILL RECEIVE AN ERROR MESSAGE BECAUSE YOU DO NOT HAVE ACCESS TO THE SYSRES DEVICE, BUT THE LOAD MAP WILL HAVE BEEN CREATED. TO LOAD THE CP NUCLEUS JUST CREATED, SHUTDOWN THE SYSTEM AND
THEN IFL THE TAPE. ONCE THE NUCLEUS HAS BEEN LOADED, YOU MAY IPL YOUR NEW CP SYSTEM RESIDENCE VOLUME. NOTE: THERE MUST BE ENOUGH STORAGE ON THE SYSTEM (VIRTUAL OR REAL), TO CONTAIN THE VIRT=REAL AREA AND THE CP NUCLEUS. Be sure that there is enough storaqe to load the CP nucleus with a
virtual=real area before you load it. The "Specifying a Virtual=Real Machine" section of Part 1 tells you how to determine the amount of real
or virtual storage you need. You can load a CP nucleus that has a
virtual=real area in either a real or virtual machine. You IPL the tape containing the CP nucleus. The CP nucleus is on the
tape at virtual address 182 for the CPGEN virtual machine. EXAMINE THE CP LOAD MAP Edit or print the load map if you wish. The contents of the load map
are described in "Part 5. Updating VM/370,," Two external names may be listed as undefined on the load map. The
external name DMKSLC is undefined if the virtual=real option is not
specified. The external name DMKRNTBL is undefined if there is no entry
in the system name table for a 370Q/3705 control program (that is, if
you did· not code a NAMENCP macro for the DMKSNT file) • Also, other
names may be listed as undefined if other modules were deleted as
described in the section "Reducing the Size of the CP Nucleus.
1I Part 3. Generating VM/370 (CP, CMS, RSCS, and IPCS) 249