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

Jim,

I don't think one suggestion is any more involved than the other, but I've been doing this for so long maybe I've lost perspective.

I would assume either suggestion would be black boxed prevent code replication and promote ease of use.

One solution does, as we both pointed out, assume a certain level of security auditing.

Thanks,

Gary

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim Oberholtzer
Sent: Monday, October 06, 2014 9:22 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: How to programmatically submit a job and know its job number

Gary:

You are dead on about the security journals capturing that data, IF auditing is turned on with the proper attributes, AND the program doing the work has the authority to read the audit journal receiver.

In either case retrieving the journal entry is way more involved than simply receiving the submission message after you do the submit job.

--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Monnier, Gary
Sent: Monday, October 06, 2014 11:05 AM
To: Midrange Systems Technical Discussion
Subject: RE: How to programmatically submit a job and know its job number

If the system is journaling job information all you need to do is retrieve the last T-JS entry for the current job. It will have all the information you are looking for.

Choose your flavor to get the journal receiver: RCVJRNE command or the Retrieve Journal Entries (QjoRetrieveJournalEntries) API (which is found in service program QJOURNAL).


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of John Yeung
Sent: Saturday, October 04, 2014 9:10 PM
To: Midrange Systems Technical Discussion
Subject: How to programmatically submit a job and know its job number

I am wondering how (if there is a way at all) to programmatically submit a job in such a way that the submitting program knows the submitted job number. The purpose of knowing the job number would be to save it for later, in case the submitted job (scheduled to run potentially far in the
future) needs to be ended/canceled, again programmatically.

The reason I'm hoping to know the number is that it would be convenient to submit jobs with the same job name, but distinguish them by number. If there isn't a (sufficiently convenient) way to do this, then I can come up with a scheme to submit jobs with unique job names.
But before going that route, I thought I'd check with the experts.
This sounds like something other folks would have had occasion to do.

John Y.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx 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@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx 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@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.