Re: Job logs external to job

[Vern Hamberg <vhamberg@xxxxxxxxxxx>]

 How about running DSPJOBLOG OUTPUT(*FILE) OUTFILE(yourlib/yourfile) in 
both jobs? There'll be an identifier set of fields with job information. 
The outfile has message IDS and all, with message data for those that 
have it, or immediate data for other things. You could write a QMQRY and 
QMFORM to generate a report based on this, putting out whatever you 
need. Or a simple QRYDFN. Or an RPG program to write the report. Or...

HTH
Vern

On 10/11/2010 10:01 AM, Mike Amos wrote:
> * Need to generate job logs for Job A from Job B.
> * Need both database output (primary and secondary) and spooled output.
> * Need the spooled output to show Job A job number/user name/job name.
>
> Note that Spooled output format is not guaranteed so I cannot simply
> read in a spooled file and hope to consistently parse out needed
> information. Therefore, my need for both DB and spooled file.
>
> I can use QMHCTLJL to set Job A to output to the DB files using
> DSPJOBLOG OUTPUT(*APIDFN) but "*APIDFN can only be specified if JOB(*)
> was also specified". So, I cannot generate the files from Job B.
>
> DSPJOBLOG OUTPUT(*OUTFILE) "only allows a primary output file to be
> produced".
>
> Specifying DSPJOBLOG JOB(jobName userId jobNumber) OUTPUT(*PRINT) from
> Job B gives spooled output with Job B information in the spooled output
> identification fields:
> QPJOBLOG  2  QDFTJOBD  jobBUser  jobBNumber  10/07/10  12:33:11
> And, the same is true with DSPJOB OPTION(*JOBLOG).
>
> I also get the same information in the spooled file fields if I allow
> Job A to produce the database files via Job End processing, create the
> job log and then spool the job log myself.
>
> I understand why the fields are produced the way that they are, but that
> isn't helping. I've also looked for an exit program that would provide
> what I need without success.
>
> Any help would be appreciated.
>
> Mike