Does it work like this? If it is a simple batch program then memory allocation totals (including hiperspaces) can be controlled by IEFUSI. I mean, if for some reason hyperspace usage becomes a problem on the system.
But what if that address space is dubbed as an OMVS address space? Do the BPXPRM memory options then impose the final limits? Like ASSIZEMAX/MAXASSIZE? Another way of asking, if for some reason hyperspace usage became a problem and the problem program ran in a UNIX address space, would BPXPRM limits (or corresponding RACF OMVS segment) be a way to tune things? Regards, Lindy -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Vernooij, CP (ITOPT1) - KLM Sent: Tuesday, November 24, 2015 4:21 PM To: [email protected] Subject: Re: z/OS and hiperspaces In impacting the system, there is no difference in whatever storage a user consumes largely. It can/will result in heavy page-outs, which are not necessarily bad if the pages are old, and consequently heave page-ins which will impact your system performance. Hiperspaces can be much larger than dataspaces, but you can have many of both. The structure of hiper- and dataspaces are quite different and the techniques to use them are evenly different. The same is true for 64-bit storage. Kees. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
