RE: Question on determining job(s)

There may also be another way, which, by the way, may answer a few other
posts made over time.

If you know the name of the job , and it is unique, then you may be able to
use the Job Notification exit point. If I understand it correctly (and I
havent used it *yet*), this exit point causes job details associated with a
subsystem to be placed on a data queue.

You could therefore monitor this for the INVOICE job you want and then
submit another job with the appropriate job details.

This exit point (which I just happened to stumble across) would also solve
a number of other posts over the last year or so where various people
bemoaned the fact that you couldn't attach a data queue to a jobqueue.

The exit point sends an entry to the data queue when a job gets placed on a
job queue, when it starts and when it ends, and provides access to the job
details including internal job identifier (which may speed up the
performance on some API's) though I'm not sure of the implications of this
across an IPL.

Details of the exit point are in the Work Management API Manual in the Work
Management Exit POint section.

Hope this assists
Evan Harris
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@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
+---