Re: Retrieving Job Log information prior to job submitting

["Christopher Cook" <ccook@xxxxxxxxxxxxxxxxxx>]

Yes, that is how I thought I could do it, unfortunately the QUSRJOBI API does 
not return the job log information.  So I am looking for another way to 
accomplish this, preferably without doing a DSPJOBLOG to a print file and 
copying the print file to a physical file.



---------- Original Message ----------------------------------
From: Dr Syd Nicholson <sydnic@ccs400.com>
Reply-To: midrange-l@midrange.com
Date:  Tue, 12 Mar 2002 20:46:11 +0000

>The OS/400 work Management APIs are probably what you are looking for.
>Information about thses APIs will be found in the IBM Imformation Centre.
>
>Two of these APIs may be sufficient for your needs.
>First: Program QUSLJOB will generate a list of jobs and place this
>information in a user space.
>Second: Use QUSRJOBI on the individual records in the user space to
>obtain job information.
>
>Search the information centre for QUSLJOB and/or QUSRJOBI for further
>information.
>
>If you create a service program around these APIs you will be able to
>create re-usable code for use in many applications.
>
>Syd Nicholson
>Castlehill Computer Services Ltd.
>
>
>
>Christopher Cook wrote:
>
>>I am trying to retrieve the job log information from jobs that are submitted 
>to a specific jobq, which is on hold.  Depending on parameters that exists on 
>the actual call command, which is only visible in the job log, I then want to 
>move the jobs to different queues.
>>
>>I am writing an application that will monitor a specific job queue and move 
>jobs depending on parameters on the call command.  One way I can do this is to 
>use the DSPJOB or DSPJOBLOG commands to a print file and then copy to a 
>physical file and determine the parameters passed.  However, I am wondering if 
>anyone knows of a better way to accomplish this.  I looked at the QUSRJOBI API 
>but it does not return job log data.
>>
>>I'd appreciate any help!
>>
>>Thanks,
>>
>>Chris Cook
>>_______________________________________________
>>This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
>>To post a message email: MIDRANGE-L@midrange.com
>>To subscribe, unsubscribe, or change list options,
>>visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
>>or email: MIDRANGE-L-request@midrange.com
>>Before posting, please take a moment to review the archives
>>at http://archive.midrange.com/midrange-l.
>>
>
>
>_______________________________________________
>This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
>To post a message email: MIDRANGE-L@midrange.com
>To subscribe, unsubscribe, or change list options,
>visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
>or email: MIDRANGE-L-request@midrange.com
>Before posting, please take a moment to review the archives
>at http://archive.midrange.com/midrange-l.
>
>