Hi Jon,
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. The only reason I have done this
is so I can use the additional facilities in WDSC which only work for
ILE (the Ctrl-Space & SEP's etc.).
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.
Best regards,
Mark Austin
IT Consultant
Universal Music Publishing International
-----Original Message-----
From: cobol400-l-bounces@xxxxxxxxxxxx
[mailto:cobol400-l-bounces@xxxxxxxxxxxx] On Behalf Of Jon Paris
Sent: 22 May 2008 09:32
To: COBOL Programming on the iSeries/AS400
Subject: Re: [COBOL400-L] Cobol Working Storage Size Limit
On 21-May-08, at 1:22 PM, Rod Verity wrote:
Have you ever dealt with a mixed set
of programs ...ie ILE calling OPM and/or OPM calling ILE. ... and
even worse when
relying on inexperience programmers doing compiles. So I am a
little gun
shy to go partial ILE. Any comments?
It depends on how much reliance the programs place on the Run Unit.
ILE and OPM programs do not share the same run unit and so the run
unit based behaviors of GOBACK (for example) can cause issues. In
terms of compiler compatibility there are very few problems. The
design criteria was "If we can't make it work the same way, stop it
from compiling".
I would not worry about the inexperienced programmer. The source
member types are different and PDM and/or WDSC take care of the type
of compile to run based on the member type.
They are safe to mix as long as once you cross the boundary you stay
the "other side" until you return. OPM calls ILE calls OPM calls
ILE ... is asking for trouble. OPM calls OPM calls ILE calls ILE ...
is fine. So Ad hoc conversion (as you can do with RPG) is not a good
idea. Changing a subsystem at a time is no problem.
The language is better, plays nice in ILE so you can call utility
functions written in RPG or C and it tends to perform better as well.
Jon Paris
www.Partner400.com
www.SystemiDeveloper.com
midrange.com
