CA7 - Case where Jobs must NOT run in parallel

thisak · New User Joined: 09 Jun 2006 Posts: 14

Hi,

In my project, there is a scenario where we will receive 8 load files from different external systems between certain time range. We have around 8 DB2 Loader jobs to load the content into a single table (no partition made) in DB2 database. As DB2 Load utility has a constraint that it cannot run concurrently, we see to that no 2 jobs are running at a time.

Moreover, we DO NOT KNOW which of these files will be received first; meaning the 8 files can reach our system in any order on a day. So, as and when the files are received respective jobs should start running and job dependency should be made to avoid parallel running. Is there any built-in feature in CA7 to handle this?

Robert Sample · Posted: Fri Oct 25, 2013 3:09 pm

Talk to your site support group. You need a job class that has only one initiator running, which would limit you to one job at a time. This does not require anything in CA-7 to implement, either.

expat · Posted: Fri Oct 25, 2013 3:46 pm

Or you could read the CA7 manuals for negative dependency

don.leahy · Posted: Fri Oct 25, 2013 6:51 pm

MUTEX ? I am not a CA7 guy, but I've heard our production support folks use that term.

Vishnupriyan Pandiyan · New User Joined: 26 Apr 2011 Posts: 16 Location: India

Yes Thisak, you can use Negative dependency(prevents jobs from executing at the same time).

You can set that up using a slash (/) beside the dependent job.
For example Jobs B and C have the requirement as job A,once job A is done you can avoid B and C running parallel by setting /B as a requirement for Job C.