If the size of the user's virtual machine is defined below the end of the CMS nucle
us (refer to labelNUCSIGMA in Figure 35 CMS Storage Map 1), it is not possible
toIPL by device name. This is because the CMS nucleus is too large to be loaded
into the user's virtual storage. Therefore, the user can onlyIPL by system name (e.
g.IPL CMS). The loader table is placed immediately below the CMS nucleus. On the other hand, if the size of the user's virtual machine is defined above the
ending location of theCMS nucleus (refer to Figure 36 CMS Storage Map 2 and
Figure 37CMS Storage Map 3), the user may IPL by either device name or system
name.
IPLing by device name:
TheSand Y-STAT, and the loader table are placed above the CMS nucleus.
If there isn't enough room to contain theSand Y -STAT, they are placed in low
storage. Likewise, if there is insufficient room for the loader table above theCMS nucleus (NUCSIGMA), it is placed below the nucleus. Any leftover free
space above the nucleus is placed on the high DMSFREE chain.
IPLing by system name:
The shared copy of theSand Y -STAT and nucleus is used. The loader table is
placed above theSand Y -STAT (NUCOMEGA) if there is sufficient room. If
there is insufficient room to place the loader table above theSand Y-STAT, it
is placed below the nucleus. Any leftover free space above theSand Y -STAT (NUCOMEGA) is placed on the high DMSFREE chain.
Functional Information 319
us (refer to label
to
into the user's virtual storage. Therefore, the user can only
g.
ending location of the
Figure 37
name.
IPLing by device name:
The
If there isn't enough room to contain the
storage. Likewise, if there is insufficient room for the loader table above the
space above the nucleus is placed on the high DMSFREE chain.
IPLing by system name:
The shared copy of the
placed above the
there is insufficient room to place the loader table above the
is placed below the nucleus. Any leftover free space above the
Functional Information 319