Re: How to programmatically submit a job and know its job number

Is it not simpler to SBMJOB the progamme in STATUS(*HOLD).
If there are no conditions to ENDJOB, you can RLSJOB. If the ENFJOB is done while the job is active you may have to reverse all transactions already made (Commitment control).

Just some thoughts.

Carel Teijgeler

On 5-10-2014 20:29, John Yeung wrote:

Vern, exit points are a bad fit for this process model. Think about
the real-life analogies I gave. Let's say you book a flight for next
month. You can receive a notification (and opportunity to cancel) at
(1) the time that you book the flight, (2) the time that the flight
takes off, and (3) the time that the flight lands. How are any of
those going to do anyone any good? You want to be able to cancel at
any random time *between* (1) and (2).

The RCVMSG technique is simple and effective. At the time that I
submit the job, I get a "ticket" for that job. At any time
whatsoever, I can just issue ENDJOB on that ticket, and we're done.

Coincidentally, Alan's first response to my question contained a link
to a thread in the archives, initiated by someone asking essentially
my exact question. The thread contains RCVMSG-based answers from
Scott Klement and *you*. Your answer actually gave a little more
detail than Scott's.

John