Discontiguous Saved Segments handles a call for as simulation routines in a similar manner. first attempts to attach the named saved segment. Again, you can
indicate an alternate segment for loading or avoid loading a named saved
segment by specifying a nonexistent segment as the alternate. If a
named saved segment is not available, searches all accessed disks
for the as simulation load modules and loads them into high user storage
when they are found. The routines are kept in storage until CMS is
reloaded or until a SET SYSNAME command is issued for CMSSEG. Note that there is overhead associated with controlling saved
segments and ensuring their integrity. In small systems, the overhead
associated with using the CMSSEG saved segment may not be offset by the
benefits of sharing storage among users. Therefore, each must decide whether the use of CMSSEG is appropriate for its own
environment.
84 IBM Planning and System Generation Guide

Page of GC20-1801-10 As Updated April 1, 1981 by TNL GN25-0837
Attached Processor Systems
Attached Processor Systems
To produce an attached processor system it is necessary to reply "YES" when asked
ARE YOU GENERATING AN AP SYSTEM?--RESPOND (YESINO) by the GENERATE or VMS ERV EXECs. A response of "YES" will cau se D MKRnA CNTRL and APLOAD (or APVRLOAD for a system with a virtual=real area) to
be used in place of DMKRnO CNTRL and CPLOAD (or VRLOAD) EXECs. O
I\IIKAI\IIAr' I\III1CIIR .Vi. ,"",IVi "'" iV .......... _.- DMKAMAC MACLIB contains one member, OPTIONS COPY, which is identical to OPTIONS COPY in DMKMAC MACLIB except that the variable n&AP" is set to
1, causing AP support to be included in the module you are assembling.
The DMKRnA CNTRL file uses this MACLIB and creates a TXTAP rather than
the usual TEXT, if necessary; that is, the module is affected by
attached processor support. Modules Containing AP Support
To find the modules that have attached processor support TXTAP decks,
use the following procedure:
1. List all modules from the Release 6 source tape that have a
filetype of TXTAP. 2. List all modules from the system PUT that have a filetype of TX'TAP. 3. Combine the lists. You should then have a complete list of the TXTAP decks which include all modules containing AP support.
six modules have been created for AP support. The nucleus-resident
modules are DMKEXT, DMKIOK, and DMKMCT. The pageable modules are
DMKAPI, DMKCLK, and DMKCPU. These modules have only a TXTAP and their
names are contained only in the AP loadlists (APLOAD and APVRLOAD). Part 1. Planning for System Generation 85