I do not get any EXT 4000 interrupts for the CSL calls to query the SFS
servers.
I like this work around. Just use SHUTTRAP to enable for SIGNAL SHUTDOWN
and
let WAKEUP and the driving exec handle the rest. Much nicer, cleaner.
Here is what it looks like:
89 *-* 'WAKEUP +5 ( RDR CONS SMSG FILE(HOBBIT TIMES *) EXT'
>>> "WAKEUP +5 ( RDR CONS SMSG FILE(HOBBIT TIMES *) EXT"
DMSCYW2246I 10:54:20 WAKEUP in (120 sec).
SHUTTRAP: Shutdown in 30 seconds
DMSCYW2245I *EXT 2401
DMSCYW2246I* 00070 ==/==/== +2 10:54:20 EXEC HOBVMDSK DISK
+++ RC(8) +++
90 *-* select
91 *-* when rc = 1
113 *-* when rc = 2
114 *-* when rc = 3
144 *-* when rc = 4
184 *-* when rc = 6
190 *-* when rc = 8
*-* then
*-* do /* External Interrupt */
191 *-* sentries
>>> "SENTRIES"
+++ RC(2) +++
1 192 *-* if rc > 0
*-* do i = 1 to rc
193 *-* pull var1
194 *-* say var1
* 00070 ==/==/== +2 10:54:20 EXEC HOBVMDSK DISK
195 *-* parse value var1 with int_type int_code .
196 *-* if int_type ^= '*EXT'
*-* iterate
192 *-* do i = 1 to rc
193 *-* pull var1
194 *-* say var1
*EXT 2401
195 *-* parse value var1 with int_type int_code .
196 *-* if int_type ^= '*EXT'
197 *-* if int_code = '2401'
*-* do
198 *-* 'EXEC HOBVM disable * 24 System Maintenance'
>>> "EXEC HOBVM disable * 24 System Maintenance"
199 *-* 'CP MSG U8803KT Shutting Down'
>>> "CP MSG U8803KT Shutting Down"
200 *-* 'CP LOGOFF'
>>> "CP LOGOFF"
CONNECT= 00:02:38 VIRTCPU= 000:00.04 TOTCPU= 000:00.05
LOGOFF AT 10:54:57 EST FRIDAY 11/09/07
Now I have to clean it up just a bit more. Which brings up the next tange
nt
on this discussion. When I signal a linux SVM to shutdown, CP reports tha
t
the linux SVM has signalled its termination. When I am logged onto a linu
x
SVM and the shutdown signal comes in, linux terminate and loads a disable
d
wait PSW (x0FFF) but does not log off. Is this PSW code (x0FFF) the
indicator to CP that SHUTDOWN has completed? If it is, how can I nicely l
oad
the same indicator when my SVM has completed its shutdown processing?
/Tom Kern
/301-903-2211
On Fri, 9 Nov 2007 13:07:09 +0200, Kris Buelens <[EMAIL PROTECTED]>
wrote:
>I'd say: test it, look at subroutine Extrn_event: and code a SAY when yo
u
>get a 4000 interrupt, than you can see how often it happens in your
>environment. I know we can live with the number. You don't get an EXT
4000
>interrupt for each SFS call, far from that. From what I tested, I see t
hat
>one gets an EXT 4000 when you have an SFS dir accessed and someone issue
d a
>GRANT AUTH for you for a file in that subdirectory (the SFS server has t
o
>broadcast this to you). Maybe if you'd use Asynch CSL calls to SFS you'
ll
>get much more.
>
