Charles, My suggestion would be to add PA/PD to the set of conditions that redrive the ASM_LOCAL_SLOT_USAGE check. I know that I've occasionally added space in an attempt relieve a shortage and been dismayed that my effort *at the time* appeared not to have helped.
BTW if you have not already seen it, please look at our PMR 81276.227.000 for an agonizing saga of RSM/ASM misadventures. . . JO.Skip Robinson SCE Infrastructure Technology Services Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile [email protected] From: Charles Mari <[email protected]> To: [email protected] Date: 02/03/2012 05:46 AM Subject: Re: Very Lage Page Datasets (was ASM and HiperPAV) Sent by: IBM Mainframe Discussion List <[email protected]> Barbara, In regards to: >> 'I like the ASM health check that tells us that usage is 30% or more. (In fact, I send an automated exception email every time this happens.) I hate that ASM does not recognize that a new page data set was added. That health check stupidly doesn't recognize a changed config and still spits out the warning.' I believe you're referring to the ASM_LOCAL_SLOT_USAGE check. If so, this check runs at a 30 minute interval and checks the slot usage for each in-use local paging data set regardless of whether it was defined 'statically' or added via PAGE ADD. So... it does eventually recognize a changed configuration. Some of the ASM checks are set to re-run when a PAGE ADD/DELETE is issued, but ASM_LOCAL_SLOT_USAGE is currently not one of them. Open to suggestions.... Regards, Charles Mari - IBM RSM/ASM Development ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
