I see the (dreaded) SQL option. This means that the COBOL compiler will call the DB2 preprocessor, so they are fighting each other for memory and resources.
As much as it's going backwards, go back to the old-preprocessor-in-a-separate-step method and give that a whirl. Good luck! Best regards, Ray -- 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 Alan C. Field > Sent: Friday 03 February 2006 06:00 > To: [email protected] > Subject: Re: COBOL compile time Question > > Thanks for all the responses. > > We tried 0M, we tried 64M, never considered 128M but we'll try. > > As Roland suggested its looking for X'FA0' 4000dec below the line. > > Available region below is about 10.5Mb > > Here are the compiler options: > > PP 5655-G53 IBM ENTERPRISE COBOL FOR Z/OS 3.3.1 INVOCATION > PARAMETERS: > TEST,LIB,NODYNAM,RENT,TRUNC(BIN),SQL("APOST,APOSTSQL"),SIZE(81 > 92K),BUFSIZE(2048) > OPTIONS IN EFFECT: <snip> > SQL('APOST,APOSTSQL') <snip> ---------------------------------------------------------------------- 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
