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
Job ordering into the queue twice
- nicolas_mulot
- Nouveau
- Posts: 149
- Joined: 07 Jan 2010 12:00
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
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