RE: Question on determining job(s)

Chuck,

If you use WRKJOB DUPJOBOPT(*MSG) and RCVMSG *DIAG - this will tell you the
qualified job name in the message data.

But consider trying it from a different angle; at the end of the daily run,
list all the reports in the output queue(s) and duplicate them. Then it
wouldnt matter about job names, and you wouldnt have to change the program
every time the dayend, monthend etc. is changed.

The only disadvantage to this is that it assumes that all the reports from
the previous day are gone - but this must be the case, or your WRKJOB
command would fail for the same reasons.

Another way, always useful in changing third party applications, is to use
the job routing entries. This allows you to call your own program just
before the job is run. A simple example fo this would be to submit a new job
in the same job queue with a low priority, which has the job name as
parameters:

Job INVOICE starts
        Your program is a routing entry, runs command:
        SBMJOB CMD(DUPSPLF JOB(THISJOB/THISUSER/THISJOBNAME) JOBQ(DAYEND) 
JOBPTY(9)
        Your program then rrts the job to QCMD and carries on as normal.

The new job will start when the first one has finished (it depends on how
you have set up your job queues) and will always have the correct job name.
It will work with dayend or monthend, and doesnt matter how many changes you
make.


Brendan Bispham

Black and Blue Software Engineering
http://www.black-and-blue.com

~
~ That WOULD be nice AND make the most sense, except that it is a 3rd party
~ product...
~
~ Rob Berendt wrote:
~
~ > The simple way to do this is have it be part of the same job.
~

+---
| 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
+---