On Fri, 9 Nov 2007 10:15:36 -0600, Thomas Kern <[EMAIL PROTECTED]>
wrote:
>Is this PSW code (x0FFF) the
>indicator to CP that SHUTDOWN has completed? If it is, how can I nicely
load
>the same indicator when my SVM has completed its shutdown processing?
Sorry, I mis-read your question the fi
A CLASS G linux guest only needs to signal CP that ITS own shutdown
processing has been completed and apparently the x0FFF in the PSW does th
at.
An SVM or Operator or Sysprog that issued the SIGNAL SHUTDOWN command wil
l
get the HCPSIG2113I message when the target SVM has completed its shutdow
n
Logging off seems like a pretty good signal. :-) You can put any CP
command you want in the VMPOFF, so you could use MSG or SMSG to send a
signal back to a shutdown SVM, which could wait until all guests have
reported in before it issues the real CP SHUTDOWN.
Brian Nielsen
On Fri, 9 Nov 2007
My current linux setup works just fine without adding the VMPOFF=LOGOFF
. If
it is DISCONNECTED when SIGNAL SHUTDOWN arrives, it shuts down, loads tha
t
disable wait PSW and CP logs it off. When I am logged onto it and use the
CLASS G version of SIGNAL SHUTDOWN, linux shuts down, loads the disable
On Fri, 9 Nov 2007 10:15:36 -0600, Thomas Kern <[EMAIL PROTECTED]>
wrote:
>Now I have to clean it up just a bit more. Which brings up the next
tangent
>on this discussion. When I signal a linux SVM to shutdown, CP reports th
at
>the linux SVM has signalled its termination. When I am logged onto
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 SMS
On Nov 9, 2007 2:33 PM, Kris Buelens <[EMAIL PROTECTED]> wrote:
> I added a trace myself and I think I understand: when you have some SFS
> direcory accessed, and something changes in it (a file added/removed a Grant
> affecting you), the SFS server tells you once "something has changed",
> involv
I added a trace myself and I think I understand: when you have some SFS
direcory accessed, and something changes in it (a file added/removed a Grant
affecting you), the SFS server tells you once "something has changed",
involving an EXT4000. The SFS client code will later pool the server to
find o
Thanks, I will look into it when I get into the office.
I don't think the Hobbit code actually accesses any directories itself
and I have mine installed on a minidisk. But I will have to check it
when Hobbit is installed in an SFS allocation.
/Tom Kern
/301-903-2211
Kris Buelens wrote:
I'd s
I'd say: test it, look at subroutine Extrn_event: and code a SAY when you
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 that
one
Well, at least I did not make some silly error.
When you use WAKEUP to trap the EXT interrupts, do you get alot of the
EXT 4000 interrupts queued up when some exec that gets called as a TIMER
event needs to query an SFS server via CSL calls? Hobbit client DISK
function reports on CP allocation
I've been reading and testing:
- I get WAKEUP's RC 6 too, but when calling WAKEUP again, it directly
exist with RC 1. So, the SHUTTRAP signal triggers 2 WAKEUP events: COSN &
SMSG. Removing the CONS option doesn't do anything.
- SHUTTRAP does not work like ADDRESS CMS, (so an eventual
The SIGNAL SHUTDOWN command was issued from another authorized user. Ther
e
is no CP EXEC. I thought that having TERMIAL LINEND OFF might have affect
ed
it, but I reset it to LINEND # and it did not change the result. I will l
ook
inside my test copy of VMUTIL to see if I can use SHUTTRAP there and
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 st
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,
15 matches
Mail list logo
