Re: Return vs LR

[PaulMmn <PaulMmn@xxxxxxxxxxxxx>]

You need to use both--

I like to code a parameter between the calling and the called programs to
tell the called program what's happening--

When the calling program intends to make the call another time, the
parameter indicates "Keep running."  The called program uses RETURN only.

When the calling program is finished with the called program, call the
program again with the parameter set to "Quit."  The called program doesn't
process anything, and SETONs both RETURN and LR.  The called program then
ends, closes its files, etc.

This lets the called program run efficiently while there is more to do, and
quit gracefully, cleaning up after itself when you're done with it.

You can also code the called program to do a 'process one and quit' when
the parameter says Quit.  This depends on what you need.

--Paul E Musselman
PaulMmn@ix.netcom.com



>Hi,
>
>Can any body let me know, what should I use to optimize interactive
>processing LR indicator or Return operation code.
>
>Thanks
>
>
>_________________________________________________________
>DO YOU YAHOO!?
>Get your free @yahoo.com address at http://mail.yahoo.com


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---