Re: Service program not using LIBL

I was wondering if anyone knew of a dummy's guide to this sort of thing.

In my company we have kept all our old RPGIII. Instead of converting the
sources, we have encapsulated them whenever needed by an RPGIV.
All our programs are compiled with ACTGRP(*CALLER) and we use RCLRSC
systematically in the CLP that call our RPGLE.

RCLRSC and its different parmeters is difficult to understand and sometimes
doesn't do what we expected (or hoped).



----- Original Message -----
From: "Scott Klement" <rpg400-l@xxxxxxxxxxxxxxxx>
To: "RPG programming on the AS400 / iSeries" <rpg400-l@xxxxxxxxxxxx>
Sent: Wednesday, October 10, 2007 11:43 PM
Subject: Re: Service program not using LIBL

It's only *ELIGIBLE that's not recommended. There's nothing wrong with
RCLACTGRP in general -- though IMHO, you should only use it on
activation groups that *you* created. For example, I personally would
never recommend using RCLACTGRP QILE in a production program. But,
RCLACTGRP KLEMACC1 (which is short for 'Klements Accounting') I wouldn't
have a problem with, since it's unlikely to be used by any software that
my company didn't develop.

Lim Hock-Chai wrote:

Sorry, RCLACTGRP is what I meant. I've heard some of the experts said
that RCLACTGRP is, sometime, unpredictable. I couldn't remember if that
statement only apply to RCLACTGRP ACTGRP(*ELIGIBLE) only or just
RCLACTGRP in general. Sorry if I miss-stated this.

--
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.