We'll, if the Panvalet subsystem is cancelled, you can't edit Panvalet
members until the subsystem is restarted.

If their started subsystem is looping or not responding, etc and you
have to cancel, you need to capture a dump and send it to the vendor
and they need to fix the cause.

If files are not properly close and can't be opened, you need to
restore to the last backup and use logs to reapply updates to the
checkpoint before the failure.

If you are shutting down for backups, maintenance, IPL, etc, you
should follow their instructions for normal shutdown.

On 5/14/07, David.L.Hansen@...
<David.L.Hansen@...> wrote:
>
> Group,
>
> We had an issue the other day when an stc was cancelled. After the job was
down mvs issued a dump in regards to a timer task. I called the vendor
> and they said at termination time they check the type of termination when
performing cleanup. According to the vendor they don't cleanup timer tasks
> etc. if you cancel their job. Tomorrow we will be having a meeting about a
vendors responsibility when we cancel their job. There is a camp here
> that believes that if you cancel a subsystem that you should suffer no ill
fate. After talking to the vendor they report that cancelling a subsystem
> can cause subsystem corruption. Because we belive that no ill fate should
come our way when we enter CANCEL a STOP command was never attempted. In
> this case the stc was an mvs monitor that runs as a subsystem.
> My questions: Is cancel dangerous? Should a vendor be responsible for an
abend if their subsystem is cancelled?
>
> TIA, Dave Hansen
> Sr. System Programmer
> Hennepin County

--
Mike A Schwab, Springfield IL USA http://geocities.com/maschwab/ for
software links