Re: Cobol Working Storage Size Limit

["Austin, Mark" <Mark.Austin@xxxxxxxxxx>]

Thanks Jon,

I'll have a good look at these articles.

Mark

-----Original Message-----
From: cobol400-l-bounces@xxxxxxxxxxxx
[mailto:cobol400-l-bounces@xxxxxxxxxxxx] On Behalf Of Jon Paris
Sent: 22 May 2008 15:55
To: COBOL Programming on the iSeries/AS400
Subject: Re: [COBOL400-L] Cobol Working Storage Size Limit


On 22-May-08, at 9:17 AM, Austin, Mark wrote:

> I have been changing our OPM Cobol programs to ILE on an ad-hoc basis
> for the last year or so and have not come across any problems in
> crossing the boundary numerous times. ...

Which would indicate that you have no reliance on the COBOL run unit  
within your code.  In that case there is usually not a problem.

> The only issue we have had is with the default activation group of ILE
> programs being QILE. We solved this by changing the compiler  
> default to
> *CALLER.

In my opinion this is a really bad idea.  There's a reason for the  
default - ILE programs were never designed to run in the default  
Activation Group.  While you may well get away with it, in the long  
run it will bite you in the behind big time.  Ultimately, you have to  
be far more familiar with ILE to run ILE programs safely in the  
default AG than if you deal with the issues that running in QILE  
caused you.  You might want to read this: http:// 
www.ibmsystemsmag.com/i5/7923p1.aspx and some of the related articles.

Jon Paris

www.Partner400.com
www.SystemiDeveloper.com