I wouldn't know why it would become a console interrupt; my RxServers support SHUTTRAP, and they work well.
How did you send the SIGNAL SHUTDOWN command. My guess is that you typed it in on the console of user HOBBIT2, hence the stop with RC 6 of WAKEUP. Or, you have an CP EXEC in HOBBIT2 that stacks something (the "CONS" on WAKEUP means that WAKEUP should stop when something is in the stack ( I wouldn't be surprized if SHUTTRAP interprets its commands as if they are sent with ADDRESS CMS). 2007/11/8, Thomas Kern <[EMAIL PROTECTED]>: > > I am trying to get SHUTTRAP to nicely stop a HOBBIT client. By nicely, I > mean it has to do some work to notify the HOBBIT server somewhere on the > network that this system is going down and then it can CP LOGOFF. I have > > SHUTTRAP set in the PROFILE EXEC and when I issue the SIGNAL SHUTDOWN > command, SHUTTRAP does get control. When SHUTTRAP issues either an EXEC > command or a CP MSG command, it works properly. But when I have SHUTTRAP > issue a 'CP SMSG * STOP' command in order to have the main exec get an SM > SG > interrup in WAKEUP and process the command properly, WAKEUP doesn't see i > t > as an SMSG interrup but as a CONSOLE interrupt. If I send the SMSG from > another privleged userid, it gets through WAKEUP as an SMSG. > > Does anyone see if I have set something wrong here? > > /Tom Kern > /301-903-2211 > > In PROFILE EXEC: > 'NUCXLOAD SHUTTRAP ( SYSTEM' > 'SHUTTRAP CP SMSG * STOP' > > When I issue a 'SIGNAL SHUTDOWN USER HOBBIT2 WITHIN 30' command: > > 89 *-* 'WAKEUP +5 ( RDR CONS SMSG FILE(HOBBIT TIMES *)' > >>> "WAKEUP +5 ( RDR CONS SMSG FILE(HOBBIT TIMES *)" > DMSCYW2246I 14:20:56 WAKEUP in (300 sec). > SHUTTRAP: Shutdown in 30 seconds > DMSCYW2246I* 00078 ALL 23:59:55 01/14/07 MSG02 > +++ RC(6) +++ > 90 *-* select > 91 *-* when rc = 1 > 115 *-* when rc = 2 > 116 *-* when rc = 3 > 146 *-* when rc = 4 > 186 *-* when rc = 6 > *-* then > *-* do /* Console Interrupt */ > ... > Ready; T=0.01/0.02 14:21:18 > HCPSIG2112I Signal timeout interval has expired > CONNECT= 00:00:51 VIRTCPU= 000:00.01 TOTCPU= 000:00.02 > LOGOFF AT 14:21:48 EST WEDNESDAY 11/07/07 AFTER SIGNAL > > When I issue an 'SMSG HOBBIT2 STOP' command: > > 89 *-* 'WAKEUP +5 ( RDR CONS SMSG FILE(HOBBIT TIMES *)' > >>> "WAKEUP +5 ( RDR CONS SMSG FILE(HOBBIT TIMES *)" > DMSCYW2246I 14:30:27 WAKEUP in (300 sec). > DMSCYW2245I *SMSG U8803KT STOP > DMSCYW2246I* 00078 ALL 23:59:55 01/14/07 MSG02 > +++ RC(1) +++ > 90 *-* select > 91 *-* when rc = 1 > *-* then > *-* do /* SMSG */ > ... > -- Kris Buelens, IBM Belgium, VM customer support
