Hi,
We've jus hit a problem where a duplicate job is being submitted at the same time as the original job. No duplicate job is anywhere.
Has anyon seen this before?
Righ Click and rerun and the jobs perfectly only once.
Date Time Code Job Name Job Id ----- Message -----
21/06/2012 12:00:57 CD5065 ORDERED JOB:3827; DAILY SYSTEM, ODATE 20120621
21/06/2012 12:01:18 SL5120 JOB STATE CHANGED TO Wait Time Window
21/06/2012 19:10:00 SL5105 SUBMITTED TO SUBSTITUTE1221
21/06/2012 19:10:00 SL5105 SUBMITTED TO SUBSTITUTE1221
21/06/2012 19:10:00 TR5101 STARTED AT 20120621191000 ON SUBSTITUTE1221
21/06/2012 19:10:00 TR5120 JOB STATE CHANGED TO Executing
21/06/2012 19:10:01 TR5120 JOB STATE CHANGED TO Submitted
21/06/2012 19:10:01 TR5101 STARTED AT 20120621191000 ON SUBSTITUTE1221
21/06/2012 19:10:01 TR5120 JOB STATE CHANGED TO Executing
21/06/2012 19:10:02 TR5100 ENDED AT 20120621191002. OSCOMPSTAT 13. RUNCNT 2
21/06/2012 19:10:02 TR5134 ENDED NOTOK
21/06/2012 19:10:02 TR5120 JOB STATE CHANGED TO Analyzed
21/06/2012 19:10:03 SL5201 SHOUT TO ECS PERFORMED
21/06/2012 19:10:03 SL5120 JOB STATE CHANGED TO Post processed
21/06/2012 19:27:38 CS5404 RERUN BY USER abcdef
21/06/2012 19:27:38 SL5105 SUBMITTED TO SUBSTITUTE1221
21/06/2012 19:27:39 TR5101 STARTED AT 20120621192738 ON SUBSTITUTE1221
21/06/2012 19:27:39 TR5120 JOB STATE CHANGED TO Executing
21/06/2012 19:27:45 TR5100 ENDED AT 20120621192745. OSCOMPSTAT 0. RUNCNT 3
21/06/2012 19:27:45 TR5132 STATUS SET TO OK AS A RESULT OF DO OK
21/06/2012 19:27:45 TR5133 ENDED OK
21/06/2012 19:27:45 TR5120 JOB STATE CHANGED TO Analyzed
21/06/2012 19:27:47 SL5120 JOB STATE CHANGED TO Post processed
Duplicate Job being submitted???
I had a similar problem. The problem occurred when I wanted to move a current job to a new application->group using drag and drop in contolm desktop with the scheduling table locked. Instead of moving the job to the new application->group controlm would make a copy of the job, keeping the original job in its current location. The result was I now had two jobs. I am using 6.4.01. I have reported this issue to BMC.