Re: Very Lage Page Datasets (was ASM and HiperPAV)

2012-02-18 Thread Walter Medenbach
Two years back we had an issue where the throughput of a database utility dropped considerably (job had to be cancelled because it was too slow) because it decided to not use more memory to do it's processing. This was found to be because the page datasets were more than 50% utilized. The notes

Re: Very Lage Page Datasets (was ASM and HiperPAV)

2012-02-14 Thread Mark Jacobs
On 02/13/12 20:03, Jim Mulder wrote: snip Just to follow up on this, APAR OA38742 has been opened. This problem was introduced in z/OS 1.13. Jim Mulder z/OS System Test IBM Corp. Poughkeepsie, NY -- For IBM-MAIN

Re: Very Lage Page Datasets (was ASM and HiperPAV)

2012-02-14 Thread Barbara Nitz
Just to follow up on this, APAR OA38742 has been opened. This problem was introduced in z/OS 1.13. I tried to look at the apar in IBMLINK and received this error; An error has occurred: * An error occurred accessing the database: RPA0 401. Is it a security/integrity apar? I get the

Re: Very Lage Page Datasets (was ASM and HiperPAV)

2012-02-14 Thread Mary Anne Matyaz
I get the same error on OA38542 and OA37992, so I think it's just SIS itself. I opened a problem. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO

Re: Very Lage Page Datasets (was ASM and HiperPAV)

2012-02-14 Thread Jan Vanbrabant
No problem with me (in Belgium). *OA38742: DIFFERENCE in ASMIORQR / ASMIORQC COUNTS become LARGE ENOUGH to AFFECT FRAME STEAL PROCESSING and ASMIORQR INCREMENTED TOO HIGH* During AUX paging, I/O is scheduled to drive input and/or output I/O to auxiliary page packs. When an I/O

Re: Very Lage Page Datasets (was ASM and HiperPAV)

2012-02-14 Thread Mary Anne Matyaz
SIS seems to be working again. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN

Re: Very Lage Page Datasets (was ASM and HiperPAV)

2012-02-13 Thread Jim Mulder
IBM Mainframe Discussion List IBM-MAIN@bama.ua.edu wrote on 02/03/2012 12:19:04 PM: 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 Just to follow up on

Re: Very Lage Page Datasets (was ASM and HiperPAV)

2012-02-05 Thread Martin Packer
: Barbara Nitz nitz-...@gmx.net To: IBM-MAIN@bama.ua.edu, Date: 04/02/2012 16:35 Subject: Re: Very Lage Page Datasets (was ASM and HiperPAV) Sent by: IBM Mainframe Discussion List IBM-MAIN@bama.ua.edu Charles, I believe you're referring to the ASM_LOCAL_SLOT_USAGE

Re: Very Lage Page Datasets (was ASM and HiperPAV)

2012-02-04 Thread Barbara Nitz
Charles, I believe you're referring to the ASM_LOCAL_SLOT_USAGE check. Yes, I do. 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

Re: Very Lage Page Datasets (was ASM and HiperPAV)

2012-02-03 Thread Vernooij, CP - SPLXM
-Manager 626-302-7535 Office 323-715-0595 Mobile jo.skip.robin...@sce.com From: Mark Zelden m...@mzelden.com To: IBM-MAIN@bama.ua.edu Date: 02/02/2012 07:35 PM Subject:Re: Very Lage Page Datasets (was ASM and HiperPAV) Sent by:IBM Mainframe Discussion List IBM

Re: Very Lage Page Datasets (was ASM and HiperPAV)

2012-02-03 Thread Barbara Nitz
Are you sure that this occurs at 50% Aux. storage utilization? IRA201E defines 'Critical storage shortage' at 85%. See cd command, parm AUXMGMT: SDUMP,AUXMGMT=ON or OFF Specifies when SDUMP data captures should stop. ON: No new dumps are allowed when auxiliary storage usage reaches 50%. New

Re: Very Lage Page Datasets (was ASM and HiperPAV)

2012-02-03 Thread Ron Hawkins
Jim, Thanks. That's exactly the sort of update I needed. Ron -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Jim Mulder Sent: Thursday, February 02, 2012 10:14 AM To: IBM-MAIN@bama.ua.edu Subject: Re: [IBM-MAIN] Very Lage Page

Re: Very Lage Page Datasets (was ASM and HiperPAV)

2012-02-03 Thread Bob Shannon
At around 50%, SVC dump will fail with 'ASM shortage'. I think at some point, maybe 1.13, AUXMGMT=YES became the default which prevented taking dumps at a lower aux storage percentage. You can return to the previous default threshold by issuing this command: CD SET,SDUMP,AUXMGMT=OFF

Re: Very Lage Page Datasets (was ASM and HiperPAV)

2012-02-03 Thread Charles Mari
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

Re: Very Lage Page Datasets (was ASM and HiperPAV)

2012-02-03 Thread Mark Zelden
On Thu, 2 Feb 2012 20:31:12 -0800, Skip Robinson jo.skip.robin...@sce.com wrote: According to conversations at SHARE, the threshold for this condition is too conservative. AFAIK there is no APAR open to fix it. It's especially frustrating if you want to take a dump to find out who's using up

Re: Very Lage Page Datasets (was ASM and HiperPAV)

2012-02-03 Thread Mark Zelden
On Thu, 2 Feb 2012 23:37:06 -0600, Barbara Nitz nitz-...@gmx.net wrote: Mark, this came into z/OS with either 1.11 or 1.12. Some of my pagedels were an attempt to test this behaviour. I could not test it. I saw it on this list of changed messages on z/OS 1.11. Skip, try ipcs active, and

Re: Very Lage Page Datasets (was ASM and HiperPAV)

2012-02-03 Thread Mary Anne Matyaz
Barbara wrote: Skip, try ipcs active, and then the undocumented command (IP) ILRSLOTC. This used to be in the hidden IPCS panel that I have forgotten how to get at 2.6i is the hidden IPCS panel. MA -- For IBM-MAIN subscribe

Re: Very Lage Page Datasets (was ASM and HiperPAV)

2012-02-03 Thread Skip Robinson
: Charles Mari cm...@us.ibm.com To: IBM-MAIN@bama.ua.edu Date: 02/03/2012 05:46 AM Subject:Re: Very Lage Page Datasets (was ASM and HiperPAV) Sent by:IBM Mainframe Discussion List IBM-MAIN@bama.ua.edu Barbara, In regards to: 'I like the ASM health check that tells us that usage

Re: Very Lage Page Datasets (was ASM and HiperPAV)

2012-02-03 Thread Vernooij, CP - SPLXM
I think the health check's way of working, to check each page dataset for its 30%, in stead of the entire page dataset configuration, is not such a bad one. AFAIK and some earlier posts in this thread suggested it too: ASM has one or more groups of page datasets, depending on devicetype, channel

Re: Very Lage Page Datasets (was ASM and HiperPAV)

2012-02-02 Thread Mark Zelden
On Wed, 1 Feb 2012 23:12:48 -0600, Barbara Nitz nitz-...@gmx.net wrote: So if I have 5 3390-27 locals and they are all equally used at 50%, the algorithms (CPU usage, not I/O) are going to pick one of them, then do the page outs. That paging will find contiguous slots and should be efficient.

Re: Very Lage Page Datasets (was ASM and HiperPAV)

2012-02-02 Thread Jim Mulder
Another element of paging that has not been referenced is the ability to handle all of the swap set size in parallel. If the swap set size is 120 pages then the old practice was to have at least four LOCALS so each thirty page block of pages could be swapped-in in parallel. While swapping,

Re: Very Lage Page Datasets (was ASM and HiperPAV)

2012-02-02 Thread Jim Mulder
I wonder what if any studies on this have been done in the lab. It would be nice if an IBM performance expert like Kathy Walsh could weigh in. The last performance studies I remember for paging were around the time of MVS XA/SP2.2.0. Very little has been done in the area of paging

Re: Very Lage Page Datasets (was ASM and HiperPAV)

2012-02-02 Thread Vernooij, CP - SPLXM
Jim Mulder d10j...@us.ibm.com wrote in message news:of15dad2d4.112617be-on85257998.0064c1d8-85257998.0066c...@us.ibm.c om... I wonder what if any studies on this have been done in the lab. It would be nice if an IBM performance expert like Kathy Walsh could weigh in. The last

Re: Very Lage Page Datasets (was ASM and HiperPAV)

2012-02-02 Thread Mark Zelden
On Thu, 2 Feb 2012 13:42:45 -0500, Jim Mulder d10j...@us.ibm.com wrote: I wonder what if any studies on this have been done in the lab. It would be nice if an IBM performance expert like Kathy Walsh could weigh in. Thanks for jumping in Jim! I hoped you or Peter would eventually to clear

Re: Very Lage Page Datasets (was ASM and HiperPAV)

2012-02-02 Thread Martin Packer
I liked Barry's plot the curve approach to this i.e. Relating occupation to performance. Cheers, Martin Martin Packer, Mainframe Performance Consultant, zChampion Worldwide Banking Center of Excellence, IBM +44-7802-245-584 email: martin_pac...@uk.ibm.com Twitter / Facebook IDs: MartinPacker

Re: Very Lage Page Datasets (was ASM and HiperPAV)

2012-02-02 Thread Mark Zelden
On Thu, 2 Feb 2012 21:48:17 +, Martin Packer martin_pac...@uk.ibm.com wrote: I liked Barry's plot the curve approach to this i.e. Relating occupation to performance. What is the SSCH count in VMAC74? SIO74CNT ? With a static environment for the most part (except after IPL when all the

Re: Very Lage Page Datasets (was ASM and HiperPAV)

2012-02-02 Thread Skip Robinson
...@mzelden.com To: IBM-MAIN@bama.ua.edu Date: 02/02/2012 01:02 PM Subject:Re: Very Lage Page Datasets (was ASM and HiperPAV) Sent by:IBM Mainframe Discussion List IBM-MAIN@bama.ua.edu On Thu, 2 Feb 2012 13:42:45 -0500, Jim Mulder d10j...@us.ibm.com wrote: I wonder what if any studies

Re: Very Lage Page Datasets (was ASM and HiperPAV)

2012-02-02 Thread Mark Zelden
On Thu, 2 Feb 2012 16:50:44 -0800, Skip Robinson jo.skip.robin...@sce.com wrote: There is a much lower limit to worry about than the one that prevents new works from starting. At around 50%, SVC dump will fail with 'ASM shortage'. This barrier has been discussed recently at SHARE. IBM agrees

Re: Very Lage Page Datasets (was ASM and HiperPAV)

2012-02-02 Thread Skip Robinson
SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile jo.skip.robin...@sce.com From: Mark Zelden m...@mzelden.com To: IBM-MAIN@bama.ua.edu Date: 02/02/2012 07:35 PM Subject:Re: Very Lage Page Datasets (was ASM and HiperPAV) Sent by:IBM Mainframe Discussion

Re: Very Lage Page Datasets (was ASM and HiperPAV)

2012-02-02 Thread Barbara Nitz
If the reason field shows A CRITICAL AUXILIARY STORAGE SHORTAGE EXISTS, first you need to ensure that enough DASD resource is available for captured dumps to be written out. Then, consider adding additional auxiliary storage (paging) resources, because SVC dumps will not be allowed again until the

Re: Very Lage Page Datasets (was ASM and HiperPAV)

2012-02-02 Thread Skip Robinson
Infrastructure Technology Services Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile jo.skip.robin...@sce.com From: Barbara Nitz nitz-...@gmx.net To: IBM-MAIN@bama.ua.edu Date: 02/02/2012 09:47 PM Subject:Re: Very Lage Page Datasets (was ASM

Re: Very Lage Page Datasets (was ASM and HiperPAV)

2012-02-02 Thread Barbara Nitz
Wow. Very interesting. PFA was just complaining about super hog address space DA20DBM1. Here's what ILRSLOTC shows as the top piggy: VERSION 02/18/2010 ASID=0079 JOB=DA20DBM1 SLOTCOUNT=00029E21 VIO COUNT= I love it when a picture comes together. Yeah, and the DB admins will tell you

Re: Very Lage Page Datasets (was ASM and HiperPAV)

2012-02-02 Thread Mike Schwab
How about a new keyword DUMP=dsn,dsn similar to LOCAL=dsn,dsn for a Local paging dsn used only for dumps? On Thu, Feb 2, 2012 at 10:31 PM, Skip Robinson jo.skip.robin...@sce.com wrote: IEE711I SYSTEM DUMP NOT TAKEN. A CRITICAL AUXILIARY STORAGE SHORTAGE EXISTS From the message manual: If

Re: Very Lage Page Datasets (was ASM and HiperPAV)

2012-02-01 Thread Mark Zelden
On Tue, 31 Jan 2012 22:49:53 -0600, Barbara Nitz nitz-...@gmx.net wrote: Writing to contiguous slots and over allocation is mentioned, but unless I missed it the old ROT (and health check) of not having more than 30% of the slots allocated is not specifically addressed. Certainly with 4K pages

Re: Very Lage Page Datasets (was ASM and HiperPAV)

2012-02-01 Thread Martin Packer
...@uk.ibm.com Twitter / Facebook IDs: MartinPacker Blog: https://www.ibm.com/developerworks/mydeveloperworks/blogs/MartinPacker * Kathy's the real expert to defer to From: Mark Zelden m...@mzelden.com To: IBM-MAIN@bama.ua.edu, Date: 01/02/2012 15:48 Subject: Re: Very Lage Page Datasets (was ASM

Re: Very Lage Page Datasets (was ASM and HiperPAV)

2012-02-01 Thread Barry Merrill
List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Barbara Nitz Sent: Tuesday, January 31, 2012 10:50 PM To: IBM-MAIN@bama.ua.edu Subject: Re: Very Lage Page Datasets (was ASM and HiperPAV) Writing to contiguous slots and over allocation is mentioned, but unless I missed it the old ROT (and health check

Re: Very Lage Page Datasets (was ASM and HiperPAV)

2012-02-01 Thread Barbara Nitz
So if I have 5 3390-27 locals and they are all equally used at 50%, the algorithms (CPU usage, not I/O) are going to pick one of them, then do the page outs. That paging will find contiguous slots and should be efficient. BTW, this is just an example, we still try to keep our 3390-27 local usage

Re: Very Lage Page Datasets (was ASM and HiperPAV)

2012-02-01 Thread Ron Hawkins
All, Another element of paging that has not been referenced is the ability to handle all of the swap set size in parallel. If the swap set size is 120 pages then the old practice was to have at least four LOCALS so each thirty page block of pages could be swapped-in in parallel. While swapping,

Re: Very Lage Page Datasets (was ASM and HiperPAV)

2012-01-31 Thread Mark Zelden
On Mon, 30 Jan 2012 22:35:02 +, Martin Packer martin_pac...@uk.ibm.com wrote: Because of the virtualisation within modern disk controllers robustness favours more, smaller. What 6-9 3390-27 page volumes isn't robust enough? :-) And regardless of PAV and where the physical location is on

Re: Very Lage Page Datasets (was ASM and HiperPAV)

2012-01-31 Thread Vernooij, CP - SPLXM
Mark Zelden m...@mzelden.com wrote in message news:9474272146773836.wa.markmzelden@bama.ua.edu... On Mon, 30 Jan 2012 22:35:02 +, Martin Packer martin_pac...@uk.ibm.com wrote: Because of the virtualisation within modern disk controllers robustness favours more, smaller. What

Re: Very Lage Page Datasets (was ASM and HiperPAV)

2012-01-31 Thread Mark Zelden
On Tue, 31 Jan 2012 08:48:30 -0600, Mark Zelden m...@mzelden.com wrote: On Mon, 30 Jan 2012 22:35:02 +, Martin Packer martin_pac...@uk.ibm.com wrote: Because of the virtualisation within modern disk controllers robustness favours more, smaller. What 6-9 3390-27 page volumes isn't robust

Re: Very Lage Page Datasets (was ASM and HiperPAV)

2012-01-31 Thread Edward Jaffe
On 1/31/2012 7:07 AM, Vernooij, CP - SPLXM wrote: About health checks: I consider at least 50% of them being writen on a lost Friday afternoon, because of some target to just deliver health checks. Sometimes the need for the appearance of an autonomic, self-healing system becomes more

Re: Very Lage Page Datasets (was ASM and HiperPAV)

2012-01-31 Thread Barbara Nitz
Writing to contiguous slots and over allocation is mentioned, but unless I missed it the old ROT (and health check) of not having more than 30% of the slots allocated is not specifically addressed. Certainly with 4K pages (for the most part) and 3390-27 (or bigger) that 30% ROT doesn't apply