This comes in as a surprise but whenever we are running a DS job with a QS plugin in it, we get a hung QS job if we cancel the run from the DS side.
To be exact, the DS job doesn't kill the QS job that is running in the server. The support people came back to us with "QS Plugin is there to kick off the job, not to control the successful end of it" argument but I won't buy it.
Has anyone experienced the similar problems?
QS Plugin question
-
ray.wurlod
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
You know how the doctor says "it hurts, does it? well don't do it"?
The same applies here - there appears to be something in the interface between the QS plug-in stage and the underlying Quality Stage (INTEGRITY) componentry that is failing to handle notification to shut down.
Have you notified your support provider and, if so, what response did you get?
In the meantime, try to avoid stopping jobs with QS plug-in in them.
The same applies here - there appears to be something in the interface between the QS plug-in stage and the underlying Quality Stage (INTEGRITY) componentry that is failing to handle notification to shut down.
Have you notified your support provider and, if so, what response did you get?
In the meantime, try to avoid stopping jobs with QS plug-in in them.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.