RE: Calling a sub-procedure from a service program with a CL program

[<lgoodbar@xxxxxxxxxxxxxx>]

Seconded. We're an Aldon shop too. No "system" changes required to use
ILE, just need to define the correct object and source types to the CMS.

In Aldon, when we move (RPG or CL) programs from OPM to ILE, we "retire"
(that's the Aldon terminology) the old OPM object, then create separate
*module and *pgm objects. The *module object contains the source code,
while the *pgm is "non source" and is just the container to hold the
final compiled object.

BTW, Aldon's "extended attribute" corresponds to the PDM "Type" column.

HTH,
Loyd

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Charles Wilt
Sent: Tuesday, November 04, 2008 2:07 PM
To: Midrange Systems Technical Discussion
Subject: Re: Calling a sub-procedure from a service program with a CL
program

Jeff,

For the last time.....

YOU SHOULDN"T HAVE TO CHANGE ANYTHING IN MKS ITSELF!!!!

You simply need to define the objects to MKS correctly.

Instead of telling MKS you want a CLLE *PGM object, tell it you want a
CLLE *MODULE.

Next, tell it you want an additional object ILE *PGM.  I don't know
how to do this with MKS, with Aldon, there's an "Extended Attribute"
that I set to ILE.

This is what I'd see in Aldon:
 Object      Type      Attribute
 MYCLLE      *MODULE   CLLE
 MYCLLE      *PGM

If it's not obvious, the RTFM or call MKS.

Charles