> -----Original Message-----
> From: HP-3000 Systems Discussion [mailto:[log in to unmask]]On
> Behalf Of [log in to unmask]

></rant on>
[snip]
> If the functionality of abortprocess is implemented on the 3000 then the
> question is: Do you want it to work 100% of the time ???  If the
> answer is  Yes, then the answer is also "Yes, I am willing to accept file
> corruption as a result of performing an abortprocess on a system process".
> I personally prefer a kinder / gentler abortprocess... and I am not
willing
> to accept file corruption as a result of abortprocess, kill, abortjob or
> any other action I perform on my system. I guess the 3000 has spoiled me,
> and yes I do run backups on my 3000s!
>
> </rant-off>

</reality on>
The :ABORTPROCESS enhancement for MPE is not being implemented like
"kill -9" and will not be "enhanced" to be that way in the near term.
In MPE there is a very simple memchanism used to protect system data
structure
integrity. It is called setcritical/resetcritical. System code does a
setcritical before beginning a sequence of code that it does not want to
be aborted in the middle of and does resetcritical when it is finished.
MPE reliability would be completely compromised if we ignored the
critical flag for ABORTPROCESS.

Bottom line, :ABORTPROCESS will not abort any process that is critical.
Period.
:ABORTPROCESS will set the abortpending flag (softkill) and the process
will abort when (if) it resets critical. If you do a subsequent
:ABORTPROCESS
when the it will tell you there is an "ABORT PENDING". We have no plans to
change the way this works in the forseeable future.

If a session/job is hung because it is looping or blocked in system code
and the process is critical, neither ABORTJOB or ABORTPROCESS will fix this.

NOTE: "reality" intentionally left on.