On Fri, 23 May 2008 10:20:48 -0500, Ward, Mike S <[EMAIL PROTECTED]> wrote:
>Hello all, this started this morning and I don't know why. We had to add >3 additional paging datasets. Is there qnyway to tell who is the >culprit? >thanks > >D ASM >IEE200I 10.16.31 DISPLAY ASM 308 >TYPE FULL STAT DEV DATASET NAME >PLPA 100% FULL 490C SYS1.PLPA >COMMON 57% OK 490B SYS1.COMMON >LOCAL 99% OK 4A19 SYS1.Z7.LOCAL1 >LOCAL 100% FULL 4A18 SYS1.Z7.LOCAL2 >LOCAL 60% OK 4A1C SYS1.Z7.LOCAL3 >LOCAL 60% OK 4A1D SYS1.Z7.LOCAL4 >LOCAL 61% OK 4A1E SYS1.Z7.LOCAL5 >LOCAL 7% OK 4556 SYS1.Z7.SPARE2 > Several ways. RMF III can help. One indication might be SDSF doing a DA ALL and SORT REAL D. There was a rexx program posted to ibm-main on 01/15/2002 that I use. Last time I ran into a problem like that is was ANTMAIN (concurrent copy) and some "hung" jobs. Never found out exactly why it happened though as the same set of jobs ran together all the time (I wasn't the one who looked into this). Canceling the jobs released the storage / page ds slots. Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:[EMAIL PROTECTED] z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html ---------------------------------------------------------------------- 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
