due to the 24x7 nature of our processing, and that all component activity flows thru xmanager (I can remember a time when it didn't) ...please reconsider the ability to invalidate an active executable (forcing a reload) of an (newly-copied) executable so that it is NOT required to stop/start xmanager to introduce a fix (where such stoppage could cause a failure of Fastunload/LogAnalyzer ... or any other batch (or online) component to CA-DB2Tools
now that I have the flexibility from the CA side to install one-off fixes, I need the same flexibility on OUR side to implement that same one-off fix without interruption to our scheduled processing
thank you
chris hoelscher