April 1, 1981 Segments that are to be shared in this manner must be loaded at an
address the normal end of your virtual machine and then must be
saved. The procedure for loading and saving discontiguous segments is
similar to the procedure that already exists for loading and saving
systems. Also, discontiguous saved segments can be attached to your
virtual machine in nonshared mode for testing and debugging. In
summary, a discontiquous saved segment is a segment that:• Has a name associated with it • Contains only reenterable code • Was previously loaded and saved • Can be shared by multiple virtual machines • Can be loaded bV a particular virtual machine in nonshared mode for
testing and debugging
Note: A discontiguous saved segment must not be attached by a virtualmachine executing in the virtual=real area.
An example of a discontiguous saved segment is the segment ofCMS that supports DOS program development and testing under eKS. This
seqment is reenterable and is namedCKSOOS. The VK/370 starter system
includes anEXEC procedure that helps you load and then save this
segment.CMS contains all the necessary linkage to load the CKSOOS segment when it is needed. USER REQUIREMENTS In order to use discontiguous saved segments, you must: • Allocate permanent space on a CP-owned volume to contain the saved
segment.• Assign a name to the segment and specify where it is to be stored on
disk by defining an entry in the system name table(DKKSNTBL) with
theNAMESYS macro. • Load and save the segment. The V"/370 starter system has EXEC procedures to help you load and save the discontiguous saved segments
forCMS (one EXEC procedure to load and save CMS/DOS, one for CMS/VSAM and AMSERV, and one for the CMS Editor, EXEC processor, and OS simulation routines). • Be sure that the proper linkage for attaching and detaching saved segments is in the operating system that needs
the segment.CMS contains the linkage necessary to attach and detach
the discontiguous saved segments it supports.Usually, the direct access storage space is allocated and the system
name table entries are created during system generation.You allocate OASD space as permanent (PERM) by executing the Format/Allocate program.
This program is executed during system generation, but it is a
standalone proqram that can be executed at any time. During system
generation, you designate theCP-owned volumes by coding the SYSOWN macro the DMKSYS file. The system name table (OMKSNT) is also
created durinq system generation. If, at some time after system
generation, you wish to change theDMKSYS or OKKSNT files, you can do a
partial system generation and reassemble those files using the GENERATEEXEC GENERATE is described in the gnd You can also load and save a discontiguous saved
segmentany time after system generation.
136IBM VM/370 System Proqrammer's Guide
address
saved. The procedure for loading and saving discontiguous segments is
similar to the procedure that already exists for loading and saving
systems. Also, discontiguous saved segments can be attached to your
virtual machine in nonshared mode for testing and debugging. In
summary, a discontiquous saved segment is a segment that:
testing and debugging
Note: A discontiguous saved segment must not be attached by a virtual
An example of a discontiguous saved segment is the segment of
seqment is reenterable and is named
includes an
segment.
segment.
disk by defining an entry in the system name table
the
for
the segment.
the discontiguous saved segments it supports.
name table entries are created during system generation.
This program is executed during system generation, but it is a
standalone proqram that can be executed at any time. During system
generation, you designate the
created durinq system generation. If, at some time after system
generation, you wish to change the
partial system generation and reassemble those files using the GENERATE
segment
136