BMC wrote:the actual reality of it is that all separated CONTROL-M/Servers become one as each and every time a resource is released by one of them - it should be reallocated either locally or externally - depending on priority and other relevant business rules.
Conceptually, it takes away the independence of each server. As such, I wonder why are these CONTROL-M/Servers separated. Could it be for historical reasons ? If they can coupled at the resource level, why can't they be at the full wider scope ?
Your point of view both about the need and the concerns with respect to the outcome are highly appreciated.
Thanks for answer, and good year to everybody.
All server control-m like it was one ?
No, this is not the bettere solution.
Servers are different for geographical reasons or application reasons or more complex needs like different New Day for control reasons, and so on.
The CTM servers is important that can maintaind the indipendency.
But different jobs on different servers cant run in the same time. For example some tables cant run when others are still running on others servers.
This is done with the global conditions, but the global resources can be more flexible method and more powerfull.
But I thonk to do a global resources like a global condition system: not all the resources shared but only that with PREFIX.
This resouces can by copied in the corresponding table of all related servers.
If the only solution is share all the resource on all servers: dont do it.
Thanks and have a good day