Mark,
Unless you had a uniquely ill-behaved program gobbling paging space, the
cause is that you don't have enough paging space. The thresholds for
these events are at high levels of page space utilization, far above the
30% utilization guideline for best performance.
Assuming you've eliminated a pathological cause, you should increase
significantly your paging configuration by PAGEADDing one or two large
page data sets. As a standby measure, you should always have another
page data set in reserve, to be PAGEADDed upon receiving the IRA400E
message.
Please follow up on this problem.
Good luck!
Steve Samson
Mark Steely wrote:
Several day ago we received the following messages:
IRA400E 04,PAGEABLE STORAGE SHORTAGE
IRA403E PXXXXXXX SWAPPED TO RECLAIM PROCESSOR STORAGE; 0000001759 PAGES
0000000117 FIXED
etc.......
Then we received:
IRA401E 04,CRITICAL PAGEABLE STORAGE SHORTAGE
IRA403E IOAOSASF SWAPPED TO RECLAIM PROCESSOR STORAGE; 0000002057 PAGES
0000000057 FIXED
etc......
The system locked up and we had to IPL.
We are z/OS V1R4 and we have RMF and CA-SYSVIEW. What can we do to
prevent this from happening again. Are there reports we can run or an
alert we can set-up if an address space goes wild and starts eating up
storage. Any help would be appreciated. If you have an example of a
report we could execute to help determine which task are using an
excessive amount of storage would be helpful.
Thank You
----------------------------------------------------------------------
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
