Job ordering into the queue twice

Tools and several solutions to manage Control-M products
Post Reply
User avatar
Rashid
Nouveau
Nouveau
Posts: 56
Joined: 31 Oct 2009 12:00

Job ordering into the queue twice

Post by Rashid » 05 Aug 2010 4:06

HI all,

JOb ordering into the queue twice eventhough schedeuling is correct.

anyone has any idea, what could have possible reasons?

any help highly appreciated

User avatar
nicolas_mulot
Nouveau
Nouveau
Posts: 149
Joined: 07 Jan 2010 12:00

Post by nicolas_mulot » 06 Aug 2010 10:47

Rashid,

Your job has to be ordered twice for some reason, or it is defined twice by mistake.

To check the multiple order, first check the "Log" option under the GUI against your job. You will see when and by which user/daily your job has been ordered.
If you find for the first log message, which will show whether you job has been ordered by a user daily (ORDERED .. DAILY <a>), by a utility ((ORDERED .. DAILY FORCED), or placed there by ctmcreate (CREATED ....)

Then check the same using an SQL request, like "select * from CMR_IOALOG where LOGDATE='20100806' and JOBNAME='your_jobname'"

This second request will show the JOBNO, which is unique within the CMS_JOBDEF table. If this request returns several JOBNO's, this means your job is defined more than once.
You can then check the CMS_JOBDEF using these JOBNO's to verify whether you job is defined more than once in the same scheduling table, or defined more than once in different scheduling tables.

More probably, your job is defined twice in the same table following an uncontrolled "Copy job" performed under the CTM/Desktop

Cheers
Nicolas Mulot

User avatar
Rashid
Nouveau
Nouveau
Posts: 56
Joined: 31 Oct 2009 12:00

Post by Rashid » 07 Aug 2010 4:46

Thank you Nicolas ,

I got the reason here, checked the box against RUN JOB ON ALL NODES IN GROUP.

Post Reply