April 1, 1981
label is any desired user label. SYSSIZE=nnnnnK is the amount of storage you must have available in
order to load the saved system. K must be specified. SYSNAME=name is the name (up to eight alphameric characters) given to the
system to be used for identification by the SAVESYS command.
The name selected must never be one that could be interpreted
as a hexadecimal device address (for "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. VSYSADR=cuu is the virtual address of the virtual disk that is the system
residence volume for the system to be saved. SYSVOL=cccccc SYSCYL=nnn 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.
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. SYSSTRT= (cc ,p)
designates the starting cylinder (cc) and page address on SYSVOL. at which this named system is to be saved. During the SAVESYS and 1PL processing, this is used to generate the
"cylinder page and device" address for the DASD operations.
These numbers are specified in decimale
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 paqes
(that is, the total number SYSPGNM operand). This is
diqits.
(pppp) you specify to be saved
of pages you indicate via the
a decimal number, up to four
The STSPGCT operand is not required when assembling the NAMESYS macro VM/370 Release 3 MACLIBs. The macro
itself will calculate the number of pages to be saved. 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 throuqh 13 are to be saved, use the format: SYSPGNM=(0,4,10-13). Part 2. Control Program (CP) 133
Page of GC20-1807-7 As Updated April 1, 1981 by TNL GN25-0829 SYSHRSG=(s,s, ••• ) are the segment numbers designated as shared. The pages in
these segments are set up at load time to be used by any user
that uses this name. All segments to be shared must be
reenterable. PR OTECT = {§Jp} specifies whether CP is to protect shared segments. The
default is ON. To turn off segment protection, specify OFF. For example, a DMKSNT module to create a named C"S system could be
coded as follows: DMKSNTBL CSECT FSTNAME NAMESYS END SYSS1ZE=384K,SYSNAME=C"S,VSYSRES=CPDSK1, VSYSADR=190,SYSCYL=100,SYSVOL=CPDSK2, SYSSTRT=(400,1),SYSPGCT=35, SYSPGNM=(O-34) ,SYSHRSG=(l) Using the SAVESYS Command
x X X The system to be saved must first be loaded by device address in the
traditional manner. Before its page-format image can be saved, the
system to be saved must have its execution stopped. The point at which
the operatinq system is stopped should be determined by the installation
system programmer. The SAVESYS command must then be issued; its format
is:
r---- , SAVESYS systemname L-- systemname corresponds to the identification of the saved system. This
is identical to the SYSNAME entry in the NA"ESYS macro. The user must have a CP privilege class of E to issue the SAVESYS command. Next, he should 1Pt the saved system. The virtual machine
will attempt to resume execution and immediately encounter a paqe fault.
The required page is brought into storage and execution continues. As
execution continues, subsequent page faults will bring the required
paqes into storage. A system should be saved as soon after 1PL as possible. All pages to
be saved must be resident at the time the SAVESYS command is issued.
Also, before issuing the SAVESYS command, be sure that the system is
stopped. CMS was designed to run under CP and it was.also designed so that it
could easily be saved by CP. See "Savinq the CMS System" in "Part 3.
Conversational Monitor System (CMS)" of this publication. ]Qig: The system being saved should not exceed X'79COOO' bytes. Unpredictable results may occur if you save a larger system.
134 VM/370 System Programmer's Guide
Previous Page Next Page