What you may have done is cut and copied the code that runs the job the first time to run the subsequence instances. This can lead to an incorrect job handle where you end up waiting for the wrong job handle.
When you call the wait command make sure you are passing it the most recent job handle from the last attached job. If you can't find a problem post the code onto this forum and someone may be able to spot an error.
regards
Vincent
Waiting for status
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Participant
- Posts: 18
- Joined: Mon Nov 25, 2002 3:23 am
- Location: Switzerland
Is this multiple instances box in the Designer or the Director. In my version 4.0 I cannot find it.Or check the box on the job properties window that makes your job capable of running as multiple instances, then qualify each run request with an instance name, for example MyJob.Instance1, MyJob.Instance2, and so on.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact: