Hello,
I probably should have provided more of an explanation. . .
Many places allow developers to cancel their own "things" (in non-production envronments). I see no problem with this. If there is a process in place to equate the pc user to the mainframe "thing" to be canceled, i have no problem with this - especially if this process logs who canceled what. I do have a problem with someone being able to enter "some command" at a pc prompt and cancel "something" on the mainframe.
Personally, i believe that if "they" have to get assistance to cancel somthing sloppy that "runs away", "they" need to receive some flack. . . As with puppies, kittens, and small children this negative reinforcement can positively influence their behavior. If it remains trivial (and with no penalty) to do sloppy work and then never hear about it, what might encourage some kind of improvement in the way they work?
I believe time would be much better spent showing the "not ideally competent system analysts" better ways to do their work. Admitedly, i expect a lot from IT people, but i've found that most can learn to work more effectively and only follow poor procedures because they have not been taught anything better . . .