Richard, I don't see that on my 5.4 system. Here is how I start it. /* */ say 'loading SHUTTRAP as a CMS nucleaus extension' 'nucxload shuttrap (system' say 'enabling SGNLSHUT exec to process shutdown signal' shuttrap exec sgnlshut exit
And the sgnlshut exec. /* exec to perform some functions before SHUTDOWN' */ say 'Received shutdown signal -- saving "QUERY DASD"' 'pipe cp q dasd | > shutdown dasd a' say 'done! -- waiting for shutdown' address command cp logoff exit I don't really do anything with this data, just a couriosity thing. Tom On Tue, Jun 28, 2011 at 8:59 AM, Schuh, Richard <rsc...@visa.com> wrote: > I just retrieved SHUTTRAP from the download page and tried it. In my > first simpleminded try, the results were mixed. The signal shutdown did > indeed trigger the command included with the shuttrap command. Then I got > this: > > SHUTTRAP: Shutdown in 900 > seconds > DMSITP143T Addressing exception occurred at 81056162 in system routine > WAITRD; re-IPL CMS > 15:07:56 * MSG FROM RSCHUH1 : DMSDIE3550I All APPC/VM and IUCV paths have > been severed. > HCPGIR450W CP entered; disabled wait PSW 000A0000 > 80F3F752 > > There is nothing in the documentation that would lead me to believe that > this is normal; however, the documentation consists solely of the HELP file > and is pretty sparse in this area. I tried reassembling the module with the > same results. > > z/VM 6.1 Service Level 1002 > CMS 25, Service Level 002 > > > Regards, > Richard Schuh > > > >
