Re: RE: display screen in a program, but not used when program called from batch

I suppose it all depends on what your needs are. We use a lot of
user-controlled opens in our stuff, and they work really well.  Our
typical report program can be opened as either an interactive or batch
program (we use a parm to tell it how it was opened). If interactive, it
pops a screen for the user to select his/her choices, and then it uses
QCMDEXEC to submit itself as batch and promptly ends. All the info
relevant to the choices is passed as parms, and of course it can also be
submitted directly if the parms are know (e.g. for end-of-period batch
processing). 

This method keeps everything in one source member, and I think it's pretty
slick. . . .


MIDRANGE-L@midrange.com writes:
>You can condition the display file F-spec with an "UPSI" switch, U1-U8.
>This has advantages over the user-control (UC) indicator:
>
>1) You don't have to include OPEN/CLOSE stuff for the file in your RPG
>prog.  All the display file operations will simply NO-OP.  No writes to
>a closed file errors, etc. Less to go wrong.
>
>2) You're going to test for batch/interactive mode in the C/L program
>anyway, so all it has to do is set the external indicator on/off via a
>SWS(XXXXXXXX) statement.
>
>3) Indicator purists will choke.
>
>-George Smith



Mike Naughton
Senior Programmer/Analyst
Judd Wire, Inc.
124 Turnpike Road
Turners Falls, MA  01376
413-863-4357 x444
mnaughton@juddwire.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
+---