Another reason not to do 0M - not having below-the-line LSQA for RTM to do its magic in a runaway situation (S40D/S whatever the other one is (S0F something I think)? ).
-- M. Ray Mullins Roseville, CA, USA http://www.catherdersoftware.com/ http://www.mrmullins.big-bear-city.ca.us/ http://www.the-bus-stops-here.org/ German is essentially a form of assembly language consisting entirely of far calls heavily accented with throaty guttural sounds. --ilvi > -----Original Message----- > From: IBM Mainframe Discussion List > [mailto:[EMAIL PROTECTED] On Behalf Of Patrick O'Keefe > Sent: Thursday 20 April 2006 12:55 > To: [email protected] > Subject: Re: PK09700 for High Level Assembler > > On Thu, 20 Apr 2006 21:25:34 +0200, Schiradin,Roland HG-Dir > itb-db/dc <[EMAIL PROTECTED]> wrote: > > >What is 128M virtual memory in these days? > >... > >I always use REGION=0M for my assembly. > >... > > While I agree that 128M is not significant these days, I > wouldn't recommend REGION=0 (as if anybody cares what I > recommend). First, its effect varies from shop to shop > depending on an exit. (IEFUJI?) And if the exit does let > you have unlimited storage, I don't trust ANYTHING to not > have a runaway storage allocation bug. It's certainly > unlikely, but a really big fixed region size would eliminate > the worry (where "big" > varies depending on the program) 500M would probably do it > for the assembler. ---------------------------------------------------------------------- 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
