jzhardy
Active User
Joined: 31 Oct 2006
Posts: 139
Location: brisbane
|
|
|
|
I have a situation where a delay in operation X spawns a large set of jobs in a wait state (AND where they are past their entry time). It may be something like X -> Y -> Z -> Z1 etc; but I could have another branch spawned from another delayed job.
So .. is there a quick way to identify the 'base set' of predecessor jobs that are causing all the mayhem. I can go via the predecessor menu options but that is time consuming, and doesn't easily identify the minimal set of 'problem jobs'
In addition, I'd like to see any SR (special resource) holds in the mix.
if someone can point me to any OPC supplied batch utitites I need to use then i can prob work it out. Hoping someone has already encountered this problem and fixed it ... |
|
