"Spencer, Mike" <mike_spen...@bmc.com> wrote in message
news:<2f58a5338b1c0044abe7d99aac2b6aef3f38c45...@houccrprd01.adprod.bmc.
com>...
> There are many ways.  Creating overflow groups generally get messy
over time because of the nature of the allocations.  There is also
Extended Storage Groups that can be defined in the DFSMS Constructs.
Again, this can become messy over time.  

I don't see anything messy in overflow groups. I use them too. 

Each morming the overflow pool is checked for datasets, a report is
generated and sent to me that data has been allocated in the overflow
pool. Subsequent dasd maintenance (we have CA-DISK) tries to move the
overflown data back to its correct pool, after having archived (migrated
in HSM dialect) the daily data from these pools.

This way, the overflow pool creates a buffer that enables batch to
continue, even over an entire weekend, but alerts us that thresholds
have been reached. This way we are alerted in the morning of the
situation and we have time for our first coffee, a decent evaluation and
cunning solution instead of having to solve this split-second when being
phoned out of our sleep in the middle of the night.

Kees.
**********************************************************************
For information, services and offers, please visit our web site:
http://www.klm.com. This e-mail and any attachment may contain
confidential and privileged material intended for the addressee
only. If you are not the addressee, you are notified that no part
of the e-mail or any attachment may be disclosed, copied or
distributed, and that any other action related to this e-mail or
attachment is strictly prohibited, and may be unlawful. If you have
received this e-mail by error, please notify the sender immediately
by return e-mail, and delete this message. 

Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries
and/or its employees shall not be liable for the incorrect or
incomplete transmission of this e-mail or any attachments, nor
responsible for any delay in receipt.
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal
Dutch Airlines) is registered in Amstelveen, The Netherlands, with
registered number 33014286 
**********************************************************************

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to