Does 'FORCE RSCS' quiesce all non-active links and wait (at least for the shutdown-defined within period) so that the MVS systems don't try to send
new files while RSCS waits for that large printout to finish on that slow network-attached printer? Does 'FORCE TCPIP' bring down all of the TCPIP related servers that TCPIP started up? (I hope that the ~CP EXT entered on the TCPIP console will do that now, yes, # can be disabled as linend and if you like ~ put in its p lace.) There are SVMs that may have outstanding work to do when a system has bee n requested to shutdown. Can you imagine the problems if DATAMOVE were FORC Ed in the middle of moving Chuckie's 191 minidisk? Once you have set out on the road to cleanly shutdown SVMs that may have outstanding work to do (Linux and SFS), why stop there, why not clean up your older SVMs too? I tried the SHUTTRAP program with our HOBBIT client, but I did not get it to work properly before I had to move on. It deserves revisiting. I need to clean up my own SVMs too. /Tom Kern /301-903-2211 On Wed, 7 Nov 2007 12:40:21 -0500, Alan Altmark <[EMAIL PROTECTED]> wrote: >Of course. It's just 1s and 0s, you know? :-) But we already have CP >shutdown commands for RSCS, TCPIP, SFS, and DIRMAINT: > FORCE RSCS > FORCE TCPIP > FORCE DIRMAINT > FORCE VMSERV > >IF the guest supports signals, they will be invoked without having to >explicitly SIGNAL SHUTDOWN. > >Not having tried it, I would suspect that Romney's SHUTTRAP program coul d >be used (loaded as a nucleus extension) to do what needs doing, whether on >GCS or CMS. It could even send a message to your shut-me-down-nicely >virtual machine that would immediately begin the shutdown process for th e >affected server. > >Alan Altmark >z/VM Development >IBM Endicott
