>If you have OMEGAMON you can track CSA usage, or, you can take >a dump and use IPCS to see who is using it.
>No need for a dump this can be done using "active". Sorry to disagree, but these points are irrelevant. There is nothing here to suggest that CSA itself is becoming full, but only that the page data set isn't big enough to hold the allocation. Even though the ILR006E message was issued, there was still space available in the PLPA page data set to absorb the overflow, so while it this is not a desirable state, it certainly is not at outage. The real question remains, which is how was the system was running at all with the LOCAL page data sets so full? For all practical purposes, all new processing would have been suspended which would be surprising if it went unnoticed for any period of time. Either there were alot more messages related to an auxiliary storage shortage, or the page data sets have really a difference in their allocation (ie: 7 at 100% full while the eighth is only 27% full?), or the D ASM is incorrect. In any case, while the issue around the COMMON page data set certainly needs to be addressed, the LOCALs represent an active problem, while CSA does not. Adam ---------------------------------------------------------------------- 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
