27.12.2012 Views

z/VM: CP Commands and Utilities Reference - z/VM - IBM

z/VM: CP Commands and Utilities Reference - z/VM - IBM

z/VM: CP Commands and Utilities Reference - z/VM - IBM

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

DEFSEG<br />

Usage Notes<br />

208 z/<strong>VM</strong>: <strong>CP</strong> <strong>Comm<strong>and</strong>s</strong> <strong>and</strong> <strong>Utilities</strong> <strong>Reference</strong><br />

The LOADNSHR oper<strong>and</strong> cannot be used with the RSTD oper<strong>and</strong>. It also<br />

cannot be used with the SC page range descriptor code.<br />

SECURE<br />

indicates that the userid that created the DCSS will be the only userid allowed<br />

to SPXTAPE DUMP or SPXTAPE LOAD that DCSS file.<br />

SPACE<br />

specifies the definition of a segment space. Use this oper<strong>and</strong> to make the<br />

dcssname that you are defining a member of this segment space.<br />

spacename<br />

is the name of the segment space (a one- to eight-character alphanumeric<br />

string). You must specify this if you use the SPACE oper<strong>and</strong>. The spacename<br />

must be different from any dcssname known to <strong>CP</strong>.<br />

1. <strong>CP</strong> can process only one DEFSEG or SAVESEG comm<strong>and</strong> at any given time.<br />

If <strong>CP</strong> is already processing a DEFSEG or SAVESEG comm<strong>and</strong>, for any name,<br />

processing of a subsequent DEFSEG or SAVESEG comm<strong>and</strong> is delayed.<br />

2. A saved segment defined at a high storage address that is shared by many<br />

virtual machines may affect real storage availability. For every virtual machine<br />

larger than 32 MB, <strong>CP</strong> creates a segment table in real storage to represent the<br />

virtual machine storage. Because <strong>CP</strong> dynamically exp<strong>and</strong>s the size of a virtual<br />

machine to incorporate a saved segment loaded at an address outside the<br />

virtual machine, the segment table for the virtual machine also exp<strong>and</strong>s. If the<br />

dynamically-exp<strong>and</strong>ed virtual machine is larger than 32 MB but less than or<br />

equal to 1024 MB, one real storage frame is allocated for the segment table. If<br />

the dynamically-exp<strong>and</strong>ed virtual machine is larger than 1024 MB, two<br />

consecutive real storage frames are allocated for the segment table. <strong>CP</strong><br />

creates the segment table at the start of the real storage frame, <strong>and</strong> any<br />

storage remaining beyond the end of the segment table may be used for <strong>CP</strong><br />

free storage. But in the case of the dynamically-exp<strong>and</strong>ed virtual machine, the<br />

portion of the segment table between the defined end of the virtual machine<br />

<strong>and</strong> the start of the saved segment represents real storage that is unavailable<br />

to the system for other uses. However, the virtual machine may load other<br />

saved segments there.<br />

3. Pages either defined as, or defaulted to, the no data saved attribute are<br />

initialized to a page of zeros when first referred to. If the pages are in an<br />

exclusive segment, changes are seen only by the one user. If the pages are in<br />

a shared segment, any changes previously made by any sharing user (if<br />

allowed) are visible to all other users sharing that same page.<br />

4. Storage keys are not saved for pages defined as, or defaulted to, the “no data<br />

saved” attribute. When first referred to, they have keys of zero.<br />

5. A segment space has a range that may span one or more physical megabyte<br />

boundaries. The beginning address of a segment space is rounded down to<br />

the nearest MB boundary of the member having the lowest page value. The<br />

ending address of a segment space is rounded up to the last address of the<br />

last page within the MB occupied by the member having the highest page<br />

value.<br />

6. Each member saved segment has a range that may span one or more pages.<br />

The beginning address of a member saved segment is determined by its<br />

lowest page value. The ending address is determined by the last address of<br />

the highest page value.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!