I see a compile of a legacy program as one step.

With a program made from *MODULE objects I see:
A step to create the *MODULE(s), which I see as "equal" legacy program compile(s).
A step to create the *PGM object, which I count as an "extra" step.
Additionally, I create a simple CL to contain the CRTPGM command, which I count as extra code.


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Monnier, Gary
Sent: Friday, April 03, 2015 2:50 PM
To: Midrange Systems Technical Discussion
Subject: RE: CLLE *MODULE question

"the extra code and steps"? I don't understand. You say you have a *MODULE object so I would assume you were planning on binding it with another program to make an executable. How is creating an executable from your *MODULE an extra step over recompiling it as a program?

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Gary Thompson
Sent: Friday, April 03, 2015 1:27 PM
To: Midrange Systems Technical Discussion
Subject: RE: CLLE *MODULE question

Gary, no good reason, but I did mention "the extra code and steps" . . .
I'm also looking at Alan's suggestion of creating a service program (new to me) but seems to offer some relief from "extra code and steps".
Thank you for the CRTPGM example, I've not used some of the parameters shown.

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Monnier, Gary
Sent: Friday, April 03, 2015 2:15 PM
To: Midrange Systems Technical Discussion
Subject: RE: CLLE *MODULE question

Why not just use the CRTPGM command?

CRTPGM PGM(YOURLIB/YOURCLLE) ENTMOD(YOURCLLE) ACTGRP(*ENTMOD) ALWUPD(*NO) USRPRF(*USER or *OWNER your preference)


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Gary Thompson
Sent: Friday, April 03, 2015 1:04 PM
To: Midrange Systems Technical Discussion
Subject: CLLE *MODULE question

I have a *MODULE created from CLLE code which is used to create several RPGLE program objects.

I'm thinking of compiling that same CLLE code as a *PGM to make it easy to call from a CL program I am changing for another project.

I could convert this different CL to a CLLE *MODULE and bind it to the other CLLE *MODULE, but don't want the extra code and steps . . .

Is it a bad idea to have the same code as both a bind-able *MODULE and callable *PGM ?


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.