Allan,
Rob Scott's answer is probably what is happening to you.
As an example, we just went through the same sort of problem. A vendor
monitor was issuing getmain for some function, and never issuing
freemain when finished with the storage. It built up over time to the
point that the monitor had used a very large percentage of the page
space.
The vendor had a fix for a known problem, and, after applying the fix,
we have not seen the storage leak again.
John
Confidentiality notice: The information included in this e-mail,
including any attachments, is for the sole use of the intended recipient
and may contain confidential and privileged information. Any
unauthorized review, use, disclosure, distribution or similar action is
prohibited. If you are not the intended recipient, please contact the
sender and delete all copies of the original message immediately.
<snip>
You either have not enough local page datasets for your workload or
there are one or more address spaces that are chewing up your auxiliary
storage.
Coupled with that you are dangerously close to full on your common page
dataset.
Plan of action :
(1) Increase size of common page dataset (I would double the size)
(2) Find out if you have some greedy address spaces that are using up
all of your local page datasets
(a) RMF Monitor III can tell you this - see the STORF report
(b) If you don't have RMF III running - there are some freeware
tools that can help (MXI for example from www.rs.com)
(3) If (2) proves that there are no obvious problems - allocate some
more page datasets and PAGEADD them or IPL (remember to update the
IEASYSxx member)
Rob Scott
Rocket Software, Inc
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
