|
On 16 March 2018 at 20:05, Jay Vaughn <jeffersonvaughn@xxxxxxxxx> wrote:
Charles wrote:
Now put the module into a service program! ;)
Haha Charles.eternity? That means I'll need another binder source member and *srvpgm
Even if it is only to be shared by only two pgm most likely for
object? What benefits will that bring? I know in a tight ship we would
have a srvpgm already to add this to but let's just say this isn't the
strongest ile shop I've ever worked for. So this is a very good step in the
right direction for this shop.
Put it into a service program /because/ your shop is not yet strong
with ILE. Lead by example, give them examples. A limited-use
procedure is the perfect intro to ILE. Simple activation group needs,
simple binding directory needs, simple compilation for the *PGM
objects. We all of us reached ILE at our own pace, and I myself don't
know anyone who jumped in without any examples at all to crib from (I
am so thankful for the Sorcerer's Redbook!)
I believe this is your moment to light a candle, but things look (and
are) different from my side of the glass :-)
Very respectfully,
--buck
--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.