n.!"'............ ., , :71..} I 270.2 IBM VM/370 Planning and System Generation Guide
Loading and Saving Discontiguous Saved Segments
Loading and Saving the CMSVSAM and CMSAMS Segments When a VSAM routine is invoked, CMS attaches the discontiguous segments
that contain the VSAM simulation routines. When an access method
services routine is invoked, CMS attaches the discontiguous segments
that contain the access method services routines.
The VSAMGEN installation EXEC procedure helps you load VSAM and access method services segments. The VSAMGEN procedure can be used to: Install VSAM and access method services for DOS users Install VSAM amd access method services for as users Update VSAM amd access method services for DOS users Update VSAM and access method services for as users
Before you invoke VSAMGEN, you must:
and save the
installation Restore a Release 31 (or later) DOS/VS starter tape to disk. The
disks supported by DOS/VS Release 31, 32, and 33 are: 2314/2319, 3330 Modell and 11, 3340, 3344, and 3350. In DOS/VS Release 34 the 3330
Model 11 and the 3350 (native mode) are also supported. For a
description of the procedure for restoring a starter tape, see the
publication System Generate VM/370 and apply the latest level of PLC updates. Install the CMS/DOS saved segment called INSTVSAM. Define the size of your virtual machine so that it is large enough to
contain the six VSAM segments and the eight access method services
segments, plus at least two additional segments: one for the CMS control blocks and free storage used during the generation process,
and one for the CMS/DOS segment called CMSDOS. However, your machine
must not be so large that it overlays the CMS/DOS segment called INSTVSAM. The CMSVSAM and CMSAMS segments must be loaded so that they do not
overlay each other, the virtual machine that is loading them, or ani
other discontiguous segment that will be loaded at the same time. CMSVSAM and CMSAMS also must be loaded at addresses lower than the CMS/DOS segment called INSTVSAM and beyond the area where you loaded
the CMSSEG segment. CMSSEG contains the CMS Editor, EXEC processor,
and as simulation routines.
If you follow the example shown in Figure 31, define your virtual
machine storage size as 2112K. Access your A-disk in read/write mode. The VSAMGEN EXEC procedure
writes DOSLIB files, updated object modules, and (for the as user) CMS text files created from VSAM and access method services object
modules to the A-disk. Before the VSAMGEN EXEC procedure completes,
it prompts you to specify whether you want to save the DOSLlBs created; if not, it erases them. If you are following the example shown, answer "yes" to this prompting message. The amount of space
you need on your A-disk depends on (1) the device type of your A-disk
and (2) whether you are an OS or DOS user. The amount of A-disk
space required is:
Part 3. Generating VM/370 (CP, CMS, RSCS, and IPCS) 271
Previous Page Next Page