[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference iosg::all-in-1_v30

Title:*OLD* ALL-IN-1 (tm) Support Conference
Notice:Closed - See Note 4331.l to move to IOSG::ALL-IN-1
Moderator:IOSG::PYE
Created:Thu Jan 30 1992
Last Modified:Tue Jan 23 1996
Last Successful Update:Fri Jun 06 1997
Number of topics:4343
Total number of notes:18308

4259.0. "ALL-IN-1 shutdown: user processes stay in ALL-IN-" by COPCLU::ELIN (Elin Christensen @DMO, DTN 857-2406) Wed Jun 15 1994 10:55

Our ALL-IN-1 manager at COPCLU has difficulties running housekeeping 
procedures that shut down ALL-IN-1 because not all users get thrown out of 
ALL-IN-1.

Last weekend a user who stayed in ALL-IN-1 during run of housekeeping, had 
4 sessions logged into ALL-IN-1, 3 of them with /REENTER, and besides she 
had 3 subprocesses all from one ALL-IN-1 session.

Can ALL-IN-1 only stop one ALL-IN-1 process per user?

How does ALL-IN-1 treat /REENTER processes and subprocesses during shutdown 
for housekeeping?

We are running ALL-IN-1 v3.0A on VAX/VMS v5.5-2.

Elin
T.RTitleUserPersonal
Name		DateLines
4259.1Fixed in next releaseIOSG::MAURICESix Programmers in search of an analystWed Jun 15 1994 13:2410
    Hi,
    
    The problem is that the shutdown AST is not delivered to users in the
    sub-process. This problem is fixed in V3.1 where the shutdown program
    will kill off processes still in ALL-IN-1 even if they are in the
    sub-process.
    
    Cheers
    
    Stuart
4259.2How do we kick the users off now?COPCLU::ELINElin Christensen @DMO, DTN 857-2406Wed Jun 15 1994 14:0913
    Thanks Stuart,
    
    I knew that there was a problem with subprocesses in earlier version,
    but I had hoped that it had been solved in v3.0.
    
    Is there any recommended (preferably automated) way of throwing these
    users off in the current version?
    
    Or should I tell our ALL-IN-1 manager to log in at 1:50 every Friday,
    Saturday and Sunday night, do $SHOW DEVICE/FILES and $STOP PROC/ID on
    users who lock ALL-IN-1 data files?
    
    Elin
4259.3IOSG::MAURICESix Programmers in search of an analystWed Jun 15 1994 14:2310
    Hi Elin,
    
    If you look at an EFT kit of the next release you will see in there
    command procedures called OA$LIB:OA$SM_USER_KILL_ALL.COM &
    OA$LIB:OA$SM_USER_KILL_NODE.COM. What the rules are about you giving
    these to a customer, I don't know.
    
    HTH
    
    Stuart
4259.4thanksCOPCLU::ELINElin Christensen @DMO, DTN 857-2406Wed Jun 15 1994 14:567
    Thanks,
    
    It is our inhouse production cluster in Digital Denmark that has the
    problem, so the rulse should not be a problem this time.
    
    Elin
4259.5What this rulse all about ? :-)COPCLU::GLARGAARDAllan Glargaard, DS @DMOThu Jun 16 1994 12:338
    >> It is our inhouse production cluster in Digital Denmark that has the
    >> problem, so the rulse should not be a problem this time.
    
    Elin, what is a "rulse" - anything relating to p�lse?
    
    Just kidding, of course,
    Allan
4259.6What I didSHRMSG::HOWARDYes it isThu Jun 16 1994 18:3414
    It sounds like you have the solution.  But I used the technique in .3
    about a year ago in batch with great success.  I just did a 
    $ SHOW DEV/FILES/OUT=FILE.TMP DISKNAME, then looked at the process id
    for each one, checking it for "0000000" and my own process id.  There
    was some issue that if the process id was null:
    
    $STOP/ID= 
    
    then the current process (the batch job) was killed. I believe that I
    also checked to see if the user was still active, as most had multiple
    files open and might have been killed for having an earlier file open. 
    As far as I know, nobody ever escaped being killed. 
    
    Ben