we have a resource A that has a "stopAfter" dependency to another resource B, because it should not be allowed to stop this resource A until the other one B is offline.
Now, we sometimes have a special situation where this resource A should be stopped and directly restarted. This should be done without touching the other resources (e.g. B). In SA z/OS I would create a stop request with override dependency in this case or use parm restart=yes.
In TSAMP I don't have these possibilities. So, what can I do?
At the moment we use "rgmbrreq -o stop", "stoprsrc" and "rgmbrreq -o cancel" to perform this task. But, this feels like a workaround. Do you know a better way to do this?
NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
This topic has been locked.
4 replies Latest Post - 2012-10-22T12:22:52Z by nukite8d
Pinned topic Stop-Request with "override dependency"?
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2012-10-22T12:22:52Z at 2012-10-22T12:22:52Z by nukite8d
Re: Stop-Request with "override dependency"?2012-10-16T07:48:38Z in response to thomas.quadfliegHi Thomas,
we have the same issue. Sometimes it is nessecary to overrule the given relationships.
We would just stop the resouorce outside of automation to get it restarted without having a stop-vote on resource B.
To simplify this, you could execute the configed StopCommand under the configured UserName.
With this you can use Copy-Paste from either the ISC/OC or after an "lsrsrc IBM.Application".
But either way, it is still an workaround.
thomas.quadflieg 270001867X27 Posts