Better to have overkill than am embarrassing oops!
-----Original Message-----
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
Behalf Of Edward M. Martin
Sent: July 25, 2006 13:18
To: [email protected]
Subject: Re: z/VM paging problem
Hello Richard,
Thanks for the info. I was planning on having a STD, SDF, and
a complete SPOOL. Overkill, maybe.
Ed Martin
Aultman Health Foundation
330-588-4723
[EMAIL PROTECTED]
ext. 40441
> -----Original Message-----
> From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED]
On
> Behalf Of Richard Feldman (WFF)
> Sent: Tuesday, July 25, 2006 12:59 PM
> To: [email protected]
> Subject: Re: z/VM paging problem
>
> Would suggest dumping STD for your rdr, pun, prt, and dumping your SDF
> files separately. That way you can load the SDF first on a
clean/noauto
> start, then reipl, and load in your STD later.
>
> Regards,
>
> Richard Feldman
> Senior IT Architect
> Kelly, Douglas / Westfair Foods Ltd.
> Ph:(403)291-6339 Fax:(403)291-6585
> -----Original Message-----
> From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED]
On
> Behalf Of Edward M. Martin
> Sent: Tuesday, July 25, 2006 10:24 AM
> To: [email protected]
> Subject: Re: z/VM paging problem
>
> Hello Mike.
>
> Ok that explains the performance part.
>
> I am doing a SPXTAPE DUMP 580 SPOOL before we shutdown.
>
> If I can get time (I will have tons of new volumes) I will make
> a new
> spool volume.
>
> Ed Martin
> Aultman Health Foundation
> 330-588-4723
> [EMAIL PROTECTED]
> ext. 40441
>
> > -----Original Message-----
> > From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED]
> On
> > Behalf Of Mike Walter
> > Sent: Tuesday, July 25, 2006 11:58 AM
> > To: [email protected]
> > Subject: Re: z/VM paging problem
> >
> > Ed,
> >
> > As noted in earlier posts, having SPOOL allocations on the same DASD
> with
> > other activity causes a break in CP's "seldom ending channel
program"
> > which supports SPOOL operations (reader, print, punch, NSSes, etc.).
> If
> > you have a DASD to spare, you'd be better off allocating a new SPOOL
> area
> > to a DASD dedicated for SPOOL. Again, z/VM 5.1 and newer
installation
> is
> > performed this way -- with SPOOL and PAGE on their own DASD.
> >
> > Moving SPOOL is trickier than paging, since you really want to
retain
> the
> > SPOOL files across IPLs vs pages that won't matter when the system
is
> > IPLed.
> > The CP DRAIN and START commands (which can be placed in the SYSTEM
> CONFIG,
> > IIRC) can be your friend to get you started, but eventually you're
> going
> > to need to SPXTAPE DUMP and SPXTAPE load all the SPOOL files to get
> them
> > on the new DASD.
> >
> > One would thing that after all the years of repeated questions about
> > moving page and spool volumes, there would be a step-by-step
document
> > showing how to do it for a single volume (and as an example for all
> > volumes).
> >
> > Mike Walter
> > Information Technology Services
> > Hewitt Associates
> > The words herein are mine, not those of my employer.
> >
> >
> >
> > "Edward M. Martin" <[EMAIL PROTECTED]>
> >
> > Sent by: "The IBM z/VM Operating System" <[email protected]>
> > 07/25/2006 10:34 AM
> > Please respond to
> > "The IBM z/VM Operating System" <[email protected]>
> >
> >
> >
> > To
> > [email protected]
> > cc
> >
> > Subject
> > Re: z/VM paging problem
> >
> >
> >
> >
> >
> >
> > Hello David,
> >
> > My spool area is smaller than I like.
> > I am working on more area.
> >
> > q alloc page
> > EXTENT EXTENT TOTAL PAGES HIGH %
> > VOLID RDEV START END PAGES IN USE PAGE USED
> > ------ ---- ------ ------ ------ ------ ------ ----
> > 430RES 0792 257 390 24120 761 810 3%
> > 430W03 075C 1802 1901 18000 240 250 1%
> > ------ ------ ----
> > SUMMARY 42120 1001 2%
> > USABLE 42120 1001 2%
> >
> >
> > q alloc spool
> > EXTENT EXTENT TOTAL PAGES HIGH %
> > VOLID RDEV START END PAGES IN USE PAGE USED
> > ------ ---- ------ ------ ------ ------ ------ ----
> > 430RES 0792 79 256 32040 30205 32040 94%
> > 430W03 075C 200 400 36180 14536 31107 40%
> > ------ ------ ----
> > SUMMARY 68220 44741 65%
> > USABLE 68220 44741 65%
> >
> >
> > Ed Martin
> > Aultman Health Foundation
> > 330-588-4723
> > [EMAIL PROTECTED]
> > ext. 40441
> >
> > From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED]
> On
> > Behalf Of David Boyes
> > Sent: Tuesday, July 25, 2006 11:17 AM
> > To: [email protected]
> > Subject: Re: z/VM paging problem
> >
> > Have you also checked your spool areas? One can overflow into
another
> if
> > your page areas are full, and if all you use the VM system for is to
> > support guests, you may have reached the point where you need more
> space
> > than you have. I?ve also seen this error when a paging area was
> > incompletely formatted (off by 1 error on my part).
> >
> > David Boyes
> > Sine Nomine Associates
> >
> >
> >
> > 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.
The information transmitted is intended only for the person or entity to which
it is addressed and may contain confidential and/or privileged material. Any
review, retransmission, dissemination or other use of or taking of any action
in reliance upon, this information by persons or entities other than the
intended recipient or delegate is strictly prohibited. If you received this in
error, please contact the sender and delete the material from any computer.
The integrity and security of this message cannot by guaranteed on the
Internet. The Sender accepts no liability for the content of this e-mail, or
for the consequences of any actions taken on basis of the information provided.
The recipient should check this e-mail and any attachments for the presence of
viruses. The sender accepts no liability for any damage caused by any virus
transmitted by this e-mail. This disclaimer is the property of the TTC and
must not be altered or circumvented in any manner.
