On Tue, 23 Jun 2009 04:22:35 -0500, Barbara Nitz wrote: > >So how are other installations handling system shutdown when there are >active USS users (or at least their leftover processes)? For a 'pure' MVS, I >can >shutdown TSO and the Initiators, cancel any running batch jobs, and I am >done. But how do I stop the USS things from multiplying? > >(An OMVS ignoramus is asking this, so please be gentle with me) > a conventional UNIX system's shutdown procedure sends SIGTERM to all user processes.
o Those that catch SIGTERM can perform orderly shutdown. o For those that don't catch SIGTERM (the default), SIGTERM is immediately fatal. After a minute or so, it sends SIGKILL. This is very similar to Andy Robertson's script. This is like STOP or MODIFY to all STCs. Superuser processes are brought down later. BSD and Linux are more elaborate, with a "runlevel" characteristic to bring down daemons in approximately the reverse order they started in. I once suggested in MVS-OE that MVS shutdown should likewise send SIGTERM to all dubbed processes to accommodate the prevailing UNIX custom. The suggestion received strong disapproval because so many address spaces nowadays get dubbed inadvertently and would suffer badly from an unexpected and uncaught SIGTERM. So, which to use: STOP, MODIFY, or SIGTERM; and in what order? Oil and water. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
