Unix Control M, job selection criteria

gforbice · Post by **gforbice** » 21 May 2009 7:04

Hello,
Being new to UNIX and Control-M I've runned in some kind of trouble.

If I'm not mistaking Control M performs job selection upon 3 main criteria:
1- If a Job is or is not critical
2- The job's priority
3- Job's "Time From, time until" parameter

Mi question concerns the following example: suppose you have 4 jobs with the same 3 parameters (not critical, same priority, same "time from, time until"), and they are all sharing an exclusive resource control. In these case UNIX Control M would process JOB 1, then JOB 4, then JOB3, and finally JOB 2. (a LIFO queue).
¿Is this the expected behavior for Unix Control M?
¿Are there any configuration parameters that could change the LIFO into a FIFO queue?

ranger67 · Post by **ranger67** » 21 May 2009 8:04

All things being equal, I believe that ctm/server processes the ajf jobs in order based on the orderid.

Walty · Post by **Walty** » 21 May 2009 8:33

1) In this situation, jobs are submitted by their ORDER ID in the reverse order : Job4, Job3, Job2, Job1
2) No parameter to change configuration from LIFO to FIFO

gforbice · Post by **gforbice** » 22 May 2009 5:12

You're both right. I've made a mistake... The third criteria should be ORDER ID instead of "Time From, Time Until".

I've also tried the same test in the mainframe world, and the result was different: JOB1,JOB2,JOB3,JOB4 (a FIFO queue). That's why I was concerned if there were any configuration issues that I was unaware of. I suppose this works by design then...

Thank you for your answers.

Cheers,
Gastón.

philmalmaison · Post by **philmalmaison** » 25 May 2009 9:54

you're steel wrong there a lot of possible criteria(s), organize for a job's orderid.
your ctrieria(s) are just part of it

regards
philmalmaison

mauriziog · Post by **mauriziog** » 26 May 2009 4:14

gforbice wrote:The third criteria should be ORDER ID instead of "Time From, Time Until

The orderIds are generated when the jobs are ordered and added in AJF.

If all the jobs are egual: why you want that the job1 start before job2 and so on? Is not important: are the same for definition.

If you want that the job1 start ever before, after the job2 and so on: the jobs are not equal !
So use the methods like priority, to have what you desire.