RE: Quick question about return-and-stay-active

[Vernon Hamberg <vhamberg@xxxxxxxxxxx>]

The exit() function does what turning on *INLR does - deletes buffers 
and closes files. In addition, it calls programs registered using the 
atexit() function.

The return statement (or using nothing at all) is like leaving *INLR 
off, as I understand it.

Here is an interesting comment from one of the C/C++ Programmer's 
Guide examples:

> /* To leave this program without having the activation group */
> /* end, issue the 'return' statement instead of the */
> /* 'exit()' function. This is sometimes referred to as a */
> /* "soft-leave" as opposed to a "hard-leave". */

Extrapolate from this to your program use vis-a-vis activation groups, etc.

HTH
Vern

At 03:44 PM 12/8/2005, you wrote:

> If you compiled with ACTGRP(*CALLER) and didn't _Rclose your file opened via
> _Ropen, file will remain open until the job ends and your global (static)
> file variable handle (_RFILE *) will remain valid.
>
> Elvis
>
> -----Original Message-----
> Subject: Quick question about return-and-stay-active
>
> My fellow geeks:
>
> I know that if you call an RPG program (that doesn't run
> in its own separate activation group) and it returns
> without LR set, it remains active.
>
> Is there a way to do this with C?
>
> --
> JHHL
>
>
> --
> 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.