Richard,
You could lose any existing CP dump files that are still in SPOOL when
you reallocate. AFAIK, VMDUMP files go on regular SPOOL volumes, so
they shouldn't be affected. If the existing dump volumes are becoming
regular SPOOL volumes, with the same volsers and slots, I would expect
existing dumps to be intact. If you keep your dump volsers the same,
but move them to new slots, you'll lose the pointers to the dump files.
Just make sure you SPXTAPE or DUMPLOAD existing dumps before you shut
down, and you'll be fine.
Dennis O'Brien
"No government deprives its citizens of rights without asserting that
its actions are "reasonable" and "necessary" for high-sounding reasons
such as "public safety." A right that can be regulated is no right at
all, only a temporary privilege dependent upon the good will of the very
government officials that such right is designed to constrain. --
Herbert W. Titus and William J. Olson, attorneys for Gun Owners of
America
________________________________
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
Behalf Of Schuh, Richard
Sent: Monday, March 24, 2008 14:13
To: IBMVM@LISTSERV.UARK.EDU
Subject: [IBMVM] Adding Spool Volumes
My current CP Owned list looks like this:
Slots Use
1-10 Spool
11-15 Reserved
16-17 Dump
18-39 Page
40 T-Disk
41-50 Reserved
I need to double the spool space for upcoming events (z/TPF dumps). I
know that I can use slots 11-15 and 5 slots from the 41-50 range. I
would rather keep my Spool space in one range. Would anything break if I
changed it so that slots 1-20 are spool and everything else pushed down
to higher slot numbers, as below? I know that changing the slot numbers
for page is no problem, and I cannot think of a good reason for the
system to care about the placement of T-disk, but what about the Dump?
It is a part of Spool, but it gets reallocated at IPL. Is there anything
that would break if the dump disks moved from slots 16 and 17 to 31 and
32?
Slots Use
1-20 Spool
21-30 Reserved
31-32 Dump
33-54 Page
55-64 Reserved
65 T-disk
Regards,
Richard Schuh
