THE NAMESYS MACRO FOR DISCONTIGUOUS SAVED SEGMENTS Use the NAMESYS macro to define the name and location of discontiguous
saved segments. The NAMESYS macro is the same one that is used to
define the name and location of saved systems except that two of the
operands are ignored and another has a mandatory set valuee VSYSADR=IGNORE should be coded when the NAMESYS macro is describing a
discontiguous saved system. For discontiguous saved segments, the
format of the NAMESYS macro is:
label NAMESYS SYSSIZE=nnnnnK,SYSNAME=name,VSYSRES=cccccc, VSYSADR={IGNORE},SYSVOL=cccccc,SYSCYL=nnn, SYSSTRT=(cc,p) ,SYSPGCT=pppp, SYSPGNM=(nn,nn,nn-nn, ••• } , PROTECT = {Q! } OFF is any desired user label. SYSSIZE=nnnnnK is the minimum amount of storage you must have available in
order to load the saved system. K must be specified.
Although you must code this operand, it is not used for
discontiguous saved segments. SYSNAME=name is the name (up to eight alphameric characters) given to the
discontiguous segment to be used for identification by the SAVESYS command and FINDSYS/LOADSYS DIAGNOSE instruction.
The name selected must never be one that could be interpreted
as a hexadecimal device address (for example, "A" or "E"). VSYSRES=cccccc is the real volume serial number of the DASD volume containing
the virtual disk that is the system residence volume for the
system to be saved. This operand is ignored if VSYSADR=IGNORE. VSYSADR=IGNORE indicates that the NAMESYS macro is describing a system or
segment that does not require a virtual system residence vo:ume. Code VSYSAta=IGNORE .heL you are discontiguous saved segment. SYSVOL=cccccc is the volume serial number (up to six alphameric characters)
of the DASD volume designated to receive the saved system.
This must be a CP-owned volume. Part 2. Centrol Program (CP) 137
SYSCYL=nnn is the real starting cylinder of the virtual disk (specified
by VSYSRES and VSYSADR) that is the system residence volume for the system to be saved. This operand is ignored if VSYSADR=IGNORE. SYSSTRT= (cc, p)
designates the starting cylinder (cc) and paqe address (p) on SYSVOL at which this named system is to be saved. During- the
processing of the SAVE and LOAD commands, this is used to
generate the "cylinder page and device" address for the DASD operations. These numbers are specified in decimal.
The number of pages written to this area is the total number
specified via the SYSPGNM operand, plus one information page. SYSPGCT=pppp is the total number of pages (pppp) you specify to be saved
(that is, the total number of pages you indicate via the SYSPGNM operand). This is a decimal number, up to four
digits. The number of pages specified does not have to be a
multiple of the number of pages in a segment, but can be some portion of a segment(s). SYSPGNM=(nn,nn,nn-nn, ••• )
are the numbers of the pages to be saved. Pages may be
specified singly or in groups. For example: if pages 0, 4, and 10 through 13 are to be saved, use the format: SYSPGNM:(0,4,10-13). SYSHRSG=(S,S, ••• ) PROTECT are the segment numbers designated as shared. The pages in
these segments are set up at load time to be used by any user
loading by this name. All segments to be shared must be
= specifies whether CP default value is ON. OFF. is
to protect shared segments. The
turn off segment protection, specify !Qte: For each shared segment specified, 64K of virtual storage is
reserved. The number of pages actually saved (via the SAVESYS command)
can be less than a segment. However, only one saved system name can be
associated with each 64K request. LOADING AND SAVING DISCONTIGUOUS SHARED SEGMENTS Before a discontiguous saved segment can be attached and detached by
name, it must be loaded and saved. The discontiguous saved segment must
be loaded at an address that is beyond the highest address of any virtual machine to which it will be attached. It is the system
programmer's responsibility to make sure the name segment is loaded at
an address that does not overlay the defined virtual machine or any
other named segment that may be attached at the same time.
138 IBM VM/370 System Guide
Previous Page Next Page