Re: RPG Display program and processing

[Jim Langston <jlangston@xxxxxxxxxxxxxxxx>]

What you speak of here was done in the S36 days on this box.  Generally it 
worked
pretty well, but people started kludging it and it got to be chaos.

Basically, you would have a procedure that was called, would check to see if it 
was
running in batch, if not, it would submit it self after a display screen.

The problem is, someone decided to get "cute" and make modifications so they 
would
copy the program, and modify the changes, but leave the original procedure to 
be called,
and just change the procedure it was submitting.

So, you would be looking for a problem, open the procedure and look at the code 
and have
a hard time figureing out why it wasn't doing what it was supposed to, until 
you realized this
procedure wasn't being called after it was submitted to the job queue.

I think for simplicities sake, it is better to keep them as separate CLs.

The only thing I don't like about creating a CMD for the RPG is that is yet 
another piece
of the puzzle that has to be looked at when someone decides to modify this 
thing in the
future.  One more source object that has to be kept current and kept tract of, 
etc.. just
to do somethign that is not that hard to do, as long as you understand how CL 
handles
strings and numbers.

Regards,

Jim Langston

"James W. Kilgore" wrote:

> Jim,
>
> Just as a side note, you can handle this is a single CL.
>
> Use RTVJOBA to determine if a job is interactive (type=1) do the prompting 
>then
> do a SBMJOB and return, if batch (type=0) GOTO the actual process, skipping 
>the
> prompting.
>
> In the SBMJOB submit a command instead of a CALL to the CL, IMHO it makes the
> parameter passing a whole lot easier.
>

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