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

Apr 11 1, 1981 St art er Syste ms Step 19. IPl the Newly Generated VM/370
If you plan to keep the CPRnLO volume as allocated when using the
various system directories, you should use the IPL FMT deck that you
punched in step 14 to reallocate the space on the volume. Put the deck
in your card reader, set the load unit switches appropriately, and IPL the reader. Respond to the format/allocate messages as shown in the
following example: VM/370 FORMAT/ALLOCATE PROGRAM RELEASE n
ENTER OR ALLOCATE:allocate ALLOCATE FUNCTION SELECTED ENTER DEVICE ADDRESS (CUU):130 ENTER DEVICE TYPE: device type
1
ENTER DEVICE LABEL:CPRnLO ENTER ALLOCATION DATA FOR VOLUME CPRnLO TYPE CYL CYL 23i4 drct 000-000 perm 001 202 perm2
end 3330 000000 001 403 404 807 ALLOCATION RESULTS 33,+0 000000 001 348
349 697 000-000 001 554 DRCT 000 000 000 000 000 000 000 000 PERM 001 202 001 403 001 348 001 554 DEVICE 130 VOLUME CPEnLO ALLOCATION ENDED ENTER FORMAT OR ALLOCATE: IPL the newly created system residence volume by setting the load
unit address dials to the real address of the VMRELn system residence
volume and pressing the LOAD button. The userid OPERATOR (or whatever
userid you specified as the system operator on the SYSOPER macro) is
logqed on when you IPL. The following messages are issued. Respond as
shown. VM/370 VERSION vv LEVEL 00 PUT nnnn; mm/dd/yy hh:mm:ss NOW hh:mm:ss EDT day mm/dd/yy CHANGE TOD CLOCK (YESINO):no hh: mm: ss START «(COLD IWARMI CKPT I FORCE) (DRAIN» I (SHUTDOWN) : cold
hh:mm:ss AUTO LOGON *** OPERATOR USERS=OOl BY SYSTEM hh:mm:ss nnnnK SYSTEM STORAGE DMKCPI957I STOR sssssK, NUC nnnK, DYN dddddK, TRA tttK, FREE ffffK, V=R vvvvvK
hh:mm:ss FILES: NO RDR, NO PRT, NO PUN hh:mm:ss FORMATTING EFROR RECORDING AREA
hh:mm:ss
lDevice types accepted by the Format/Allocate program are: 2314, 2319, 3330, 3330-11, 3340-35, 3340-70, 3350, 2305-1, and 2305-2. 2This line gives the required specifications for the 3330 11 and
the 3340 Model 70. 250 IBM VM/370 Planninq and System Generation Guide