On Friday, 03/14/2008 at 08:31 EDT, "Romanowski, John (OFT)" <[EMAIL PROTECTED]> wrote: > Instead of adding a CP SIGNAL SHUTDOWN option to prevent shutdown > (contrary to the signal name), > it'd be better to extend the CP SIGNAL command to send other types of > signals for other purposes, something like the linux 'kill' command. > kill sounds like it started out as a stone cold killer but was reformed > to deliver many other useful, non-fatal signals. > Something like CP SIGNAL QUIT or SIGNAL STOP > > 'kill -l' lists these types of special-purpose signals > 1) SIGHUP 2) SIGINT 3) SIGQUIT 4) SIGILL > 5) SIGTRAP 6) SIGABRT 7) SIGBUS 8) SIGFPE > 9) SIGKILL 10) SIGUSR1 11) SIGSEGV 12) SIGUSR2 > 13) SIGPIPE 14) SIGALRM 15) SIGTERM 17) SIGCHLD > 18) SIGCONT 19) SIGSTOP 20) SIGTSTP 21) SIGTTIN > 22) SIGTTOU 23) SIGURG 24) SIGXCPU 25) SIGXFSZ > 26) SIGVTALRM 27) SIGPROF 28) SIGWINCH 29) SIGIO > 30) SIGPWR 31) SIGSYS 33) SIGRTMIN 34) SIGRTMIN+1 > ...
So define an external interrupt code to go with each one and update Linux to convert them to one of the above signals. Then a simple SENDSIG exec takes care of it. For example, if you bind SIGPWR to code 3000, then SENDSIG LINUX01 PWR would result in CP SEND CP LINUX01 EXT 5000. You don't need a change in the CP SIGNAL command to do this; SIGNAL is for architecturally-defined events. Alan Altmark z/VM Development IBM Endicott
