|
SoftTree Technologies
Technical Support Forums
|
|
Author |
Message |
seanc217
Joined: 23 May 2007 Posts: 272
|
|
Job name conflict |
|
I am seeing an issue where I had 2 jobs that had the same name.
I was using job notification to kick off the next job. It looks like if 2 jobs have the same name, that the scheduler gets confused and does not know which one to kick off. Since a job is assigned an ID I figured it would use the ID to identify the job, but I changed the job several times to kick off the appropriate job and found that it would get changed back somehow. I think the scheduler gets confused when 2 jobs have the same name. I know it's probably not a good idea and I have since changed the 2 jobs in question to have slightly different names. This is for the multi-platform edition, latest version of the scheduler and should be a rather easy thing to setup a test case and see if there is some confusion going on here. Let me know what you find out.
Thanks.
|
|
Wed Dec 22, 2010 2:21 pm |
|
|
SysOp
Site Admin
Joined: 26 Nov 2006 Posts: 7847
|
|
|
|
I don't want to say that duplicate job names are ok, but I can confirm that all internal job references work by ID. Would you please elaborate a bit more on "It looks like if 2 jobs have the same name, that the scheduler gets confused and does not know which one to kick off?"
|
|
Thu Dec 23, 2010 10:21 am |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|