See suggestions below, prefixed by: sugg-->
You left out some specific commands, but it looks as if you are aware of
them and just wanted more of an overview.
You have the major points covered in good order. Nice memory! (Did I
remember to say "Nice memory!"?).
Mike Walter
Hewitt Associates
Any opinions expressed herein are mine alone and do not necessarily
represent the opinions or policies of Hewitt Associates.
"James M" <[EMAIL PROTECTED]>
Sent by: "The IBM z/VM Operating System" <IBMVM@LISTSERV.UARK.EDU>
05/04/2007 10:01 AM
Please respond to
"The IBM z/VM Operating System" <IBMVM@LISTSERV.UARK.EDU>
To
IBMVM@LISTSERV.UARK.EDU
cc
Subject
Re: Spool Area Full
Now I must put all this theory to work. (my heart's thumping)
I've been ordered to add more spool to a critical second level guest
because of a rscs problem I reported in a new message today.
Before I do it I want to double check to make sure I've got everything
right. (It's been years since I did vm - early esa).
Here's what I think i must do.....PLEASE correct me
att free cuu to 2nd level vm
on 2nd level maint att cuu *
cpfmtxa
label (i.e. spoolz)
format
allocate
0-end spol
Update sysconfig--->
cprel a
link * cf1 cf1 mw
acc cf1 z
sugg--> COPYFILE SYSTEM CONFIG Z -1SYSTEM CONFIG Z (OLDDATE
(Having a backup of the previous SYSTEM CONFIG, with the required
filetype "CONFIG" can be handle in case
of a crisis, and as evidence of what it looked like before the
change)
x system config z
slot 1 vol1
slot 2 vol2
slot 3 reserved --> which I will change to spoolz
sugg--> FFILE ... :-)
sugg--> CPSYNTAX SYSTEM CONFIG Z ( **ALWAYS** check for errors)
rel z (det
link * cf1 cf1 rr
cpacc * cf1 a sr
def cpown slot 3 spoolz
att cuu system spoolz
sugg---> CP START VOLid spoolz ALL
sugg---> Prevent MDISKs from be allocated on that volume, mark that volume
"in use" however you do it (perhaps with VM:Secure, perhaps buy adding a
disk ot $PAGE$, or some other - just as long as no MDISKs can get
allocated thereon).
on the first level system I must..
update direct entry for 2nd level guest adding dedicate cuu
I don't believe I need to update 1st level system config for dedicated
disks - right?
Did I miss anything - any gotchas?
Thanks for any and all help
-James
On 4/30/07, Kris Buelens < [EMAIL PROTECTED]> wrote:
Murphy's law dictates a small change in the order of things.
With the order you propose there is a time window where the SYSTEM CONFIG
does not know the new spool volume, but CP uses it for new spool files. If
CP goes down in that window, all spool files with some parts of the new
volume will be lost after the restart.
The good order to be 100% safe is:
1. Format & allocate (like you say)
2. Update SYSTEM CONFIG
3. DEFINE CPOWNED
4. ATTACH to SYSTEM
To find which spool files have parts on a given volume, get this tool
http://www.vm.ibm.com/download/packages/descript.cgi?SPOOLCHN
2007/4/30, James M <[EMAIL PROTECTED]>:
z/VM 5.2
I'm backing up the vm sys prog and sure enough - bing - a problem
immediately.
Problem solved but I have a couple of questions.
adding a new spool full volume steps - is this correct..
att cuu * as vdev
cpfmta vdev
label vmspxx
done...
format
done..
allocate
spol 0-end
done...
end
Once cpfmtxa ends - att cuu system vmspxx & update cpowned list in
config file.
...and I'm off and running.
Followup question - is there a convenient way to migrate spool files from
that volume without cold starting?
Another spool followup question.
If I query alloc and do the math on the spool numbers I get 80%
If I q alloc spool I get 53%
How come?
Any rexx exec's out there that can monitor spool and send me an email if >
x%?
Thanks
James
--
Kris Buelens,
IBM Belgium, VM customer support
The information contained in this e-mail and any accompanying documents may
contain information that is confidential or otherwise protected from
disclosure. If you are not the intended recipient of this message, or if this
message has been addressed to you in error, please immediately alert the sender
by reply e-mail and then delete this message, including any attachments. Any
dissemination, distribution or other use of the contents of this message by
anyone other than the intended recipient
is strictly prohibited.
