|
Cary T. Kellems wrote:
We are upgrading our hardware from E10's to model 170's and thus from
V2r2 to V4r2. During the testing I uncovered a problem that was due to
using the output from a DSPJOBLOG (*PRINT). I would like to replace
this method with an API. Does anybody know what or if any API would
allow me to extract the 'Request' info from a job log? In particular I
am looking for the parameters for the job submitted.
Then current process is as follows:
I am attempting to find a way to retrieve the parameter of a submitted
job. Currently I RTVJOBA to determine the job then issue a DSPJOBLOG
(*PRINT) to get the data I then CPYSPLF so that I can retrieve the data.
I then read each record for 'RQS' (which has now changed to 'Request')
and then store the data (called pgm and parameters). This was a klugie
way but it worked.
Thanks
Cary T. Kellems
Some Suggestions:
1.- If you have access to the Main Program, Change the Pgm to Save the
parameters to a Data Base File.
2.- If you have access and authority to change the Subsystem in wich the
program runs, ... ,
create a special routing entry for identification and manipulation of
that Job ... etc
3.- Create a command to process your "Called Program" and ....
Create a validation pgm for that command ... the command will in turn
call the progarm with the
parameters ....
4.- A very complicated way .... Create a validation program to the CALL
command (Better NOT !)
Good Luck to you
Regards Jorge Moreno /
Military Car Sales / Woodbury, New York
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@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
+---
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.