RE: Is job x running

Thanks Scott, Bryan, John and Tim
Your hints and thoughts are much appreciated.
So happens current project uses a data area as a 'token' two separate programs
in two separate jobs must be able to lock before processing, and both already use
an API to manage data so the additional code should be a decent fit.
I've never had something this time critical between two jobs, so I'm sweating some . . .

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of John Yeung
Sent: Wednesday, November 19, 2014 3:19 PM
To: Midrange Systems Technical Discussion
Subject: Re: Is job x running

I'll cast another vote for object locks: Not only simple and easy (no APIs needed), but also among the more reliable methods.

Depending on the intended workflow, what is even more reliable is a one-at-a-time job queue. Just submit and forget.

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.