SYS OWN Macro SYSOWN Macro Use the SYSOWN macro to generate the list of up to 255 CP-owned DASD volumes. A CP-owned volume is either the CP system residence volume, or
a volume that contains VM/370 paging, spooling, or temporary disk space.
It must contain a CP allocation table at cylinder 0, record 4 allocating
these areas. Even if a volume has a VM/370 allocation table at cylinder 0, record 4, allocation data is ignored unless the volume appears as an
operand in the SYSOWN macro instruction. The SYSOWN macro must appear before the SYSRES macro in the
assembly listing. !;;2nside!:at,i.2!!§ !or !lIQ£ating on CP-Qwned Vol,gj!es: The
following considerations should help you to allocate space efficiently
on CP-owned volumes: • If a volume is specified in a SYSOWN statement but is not mounted when the system is Inad@d (via the IPL c0mmand). that volume is considered unavailable to VM/370. Processing continues, if
possible. The operator can mount and attach the volume later, if it
is needed. • Only those volumes that contain paging and spooling space or TDSK space need be identified as CP-owned volumes. All other volumes are
described either by directory entries or by logically attaching the
entire device. • If you add another volume to the SYSOWN list, you must add it at the
end of the list. (Otherwise, if you attempt a warm start after
regenerating and loading CP, the relative entry number used to locate
system spool buffers is incorrect.) Then reassemble DMKSYS, rebuild
the CP nucleus, and reload it on the system residence volume. Use the GENERATE EXEC procedure to reassemble D8KSYS and reload the CP nucleus. • If your installation has saved systems (systems that can be loaded by
name, thus bypassing the initial program load procedure), you must
reserve space on a CP-owned volume to hold the named systems you want
saved. The DASD space you reserve, for each named system you wish to
save, should be enough to contain the number of pages specified in
the SYSPGCT operand of the NA8ESYS macro, plus one page for system
use. • If your V8/370 system has a 3704 or 3705, you must reserve space on a CP-owned volume to contain the 3704/3705 control program image. See the "Generating a V8/370 System that Supports the 3704/3705" section
of Part 1 for information about how much DASD space you should
reserve.
The name field must not be specified for the SYSOWN macro. The
format of the SYSOWN macro is:
r I Name , Operation I Operands 1---1-------1 I I , r, r, I I SYSOWN I (volid I ,TEMP I) [, (volid I I) • • • ] I I I I,PAGEI I,PAGEI I I I L J L J L
166 IBM V8/370 Planning and System Generation Guide

volid
Page of GC20-1801-10 As Updated April 1, 1981 by TNL GN25-0837 SYSOWN Macro
is the CP-owned volume identification of from 1 to 6 alphameric
characters. r , I, TEMRI I, PAGEl L .J indicates to VM/370 how allocatable space on the specified volume
should be used. TEMP indicates that this volume is to be used primarily for
spooling space and it viII also be used for paging space if all
volumes normally used for paging allocation are full or
unavailable. TEMP is the default option. (TEMP space must be by the CP Format/Allocate service program. At this time
areas for user TDSKs and directory are allocated.) If no volume is specified as being preferred for TEMP space
allocation, no spooling operations may be performed. Thus any data
transfer channel program started to a virtual unit record output
device ends with UC status in the virtual CSW and the intervention
required bit set in the virtual sense byte.
PAGE indicates that this volume is to be used primarily for paging,
(this does not include spool space). Note that TDSK requests from
this volume occur only when a request for space cannot be satisfied
on a volume with a TEMP allocation.
Example:
The following SYSOWN macro designates the CPDRM1 volume as paging space
and the CPDSK1 and CPDSK2 volumes as spooling space and paging overflov: SYSOWN (CPDRM1,PAGE), (CPDSK1,TEMP),CPDSK2
Part 2. Defining Your VM/370 System 167