|
An approach I use quite often is to have a CL program that can submit
itself to batch. The approach is to RTVJOBA TYPE(&JOBTYPE); if the
job is running interactively (&JOBTYPE = '1'), then SBMJOB CMD(CALL
[same pgm] PARM(&PARM1...) ). The RPG program just calls the CL with
all the required parameters, and it (the CL) handles the submission.
I don't think a little CL program is necessarily a 'waste' if it makes
the RPG code a lot cleaner... just my EUR 0.02...
As for using LDA - isn't that, well, deprecated? There are so many
legacy apps that dump stuff in the LDA, and expect it to still be
there later, that a program using the LDA to pass parameters to a
submitted job really needs to restore it to its previous state
afterwards.
____________________
Paul Cunnane
The Learning Company
______________________________ Reply Separator _________________________________
Subject: Batch Submissions from RPGIV
Author: JFinney@omnia.co.za at InterNet
Date: 11/15/99 8:17 AM
Hi All,
I have a procedure which needs to submit another procedure to batch. Now I
have done simple compile-time tables in
conjunction with calling QCMDEXC but this has been without passing parms.
Now I need to pass +-35 of them and I'm, well,
stumped on this one. I really don't want to have to create a CL proc just
to perform this action ( seems a waste. Call a pgm to call
a pgm to batch). Is there any API which I could use to do this ?
Any help forthcoming would be appreciated
Regards
John.
+---
| 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
+---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.