RE: More ILE 101

["Bob Cozzi" <cozzi@xxxxxxxxx>]

Joe, if you do options 2 or 3 your dog will die, and 4 and 5 will make it
very ill.
Also, number 2 is one of those "you can do it, but why would you want to"
features. It was never intended to actually be done or work, but people
started doing it for some reason (too many drugs in the 1970s I suppose).
If you do option 2, and your RPG IV program allocates memory (via any means)
then that memory will not be freed automatically until the job ends, since
*DFTACTGRP does not go away until you endjob.  Of course you can always do a
DEALLOC to make sure you have it freed. However, as you probably know, you
loose the control of the boundary around your app when it is run in
*DFTACTGRP--problems can't be fixed unless the job ends--and I guess that's
the Microsoft way, not the 400 way.
-Bob Cozzi


-----Original Message-----
From: rpg400-l-bounces+cozzi=rpgiv.com@xxxxxxxxxxxx
[mailto:rpg400-l-bounces+cozzi=rpgiv.com@xxxxxxxxxxxx] On Behalf Of Joe
Pluta
Sent: Monday, April 12, 2004 1:57 PM
To: 'RPG programming on the AS400 / iSeries'
Subject: More ILE 101

Alrightie.

I've finally confused myself.  I compile a program with DFTACTGRP(*NO)
ACTGRP(*CALLER).  Do bad things happen if:

1. I call from another ILE program
2. I call from an OPM program
3. I call it from the command line
4. I invoke it directly as my signon program
5. I invoke it as the first program in a submitted job

My guess is that 3, 4 and 5 should be very similar in nature.  For case
one, I simply take on the ACTGRP of the ILE.  I don't even care to guess
at the second option.

Joe

_______________________________________________
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.