In
<03ff351977a6114a9e3bc166d58e936d03a7d90...@dfw1mbx18.mex07a.mlsrvr.com>,
on 07/22/2012
at 03:17 PM, David Boyes <[email protected]> said:
>How can I go about submitting a requirement for z/OS to acknowledge
>and handle the same external interrupt as VM, VSE and Linux use to
>trigger a controlled shutdown (or at least acknowledge it by
>printing a message we can capture via console automation and
>trigger the shutdown ourselves)?
1. Provide a business case
2. Give the requirement free of any implimentation detail,
then provide suggestions as to what interfaces would be
preferred.
The resistance to the global SIGTERM suggestion was probably due to
unintended side effects. If you want a SIGTERM generated on shutdown,
it should only go to those dubbed applications that have registered
for it. Such a registration service belongs in a suggestion rather
than in the statement of requirements, although it might be reasonable
to submit a separate requirement for it.
--
Shmuel (Seymour J.) Metz, SysProg and JOAT
ISO position; see <http://patriot.net/~shmuel/resume/brief.html>
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
