Conference iosg::all-in-1_v30

3244.0. "SDA causes terminals to hang" by KERNEL::OTHENJ () Tue Sep 07 1993 12:48

Hello,

I have found a few notes about this problem, but nothing for ALL-IN-1 
v3.0-1.

The customer used SDA to shutdown ALL-IN-1 when many users were using 
ALL-IN-1. They have 55 users on their system, and 3 users reported that the 
broadcast message appeared when they were in the WPS-PLUS editor, and after 
the message was displayed, their terminals hung. The system manager had to 
kill their process, and therefore the users lost some data from their WP 
sessions.

I have read a few (old) notes, and found references that it could be a 
resource problem, or an FMS patch was required. Can anyone tell me if the 
FMS patch is still required (article below), and whether the resources are 
system/user specific? The customer has seen this problem on a variety of 
different users (does not happen to the same users all the time), and 
bytlm, biolm are all the same per user.

	Thanks,

		Julie


Shutting Down ALL-IN-1 Causes Some Users Terminal To Hang

ALL-IN-1 users see random (LEF process state) hangs. These hangs are
particularly prevalent when ALL-IN-1 is being shutdown.

This problem occurs when users are making use of the /BROADCAST ALL-IN-1
feature. The code associated with broadcast handling uses an AST routine which
calls the FMS routine, FDV$PUTL, to display the broadcast message on line 24. 
It is this use of FMS routines in AST routines that can produce the hangs.

With the advent of faster processors (especially the SMP systems), a timing
window has been revealed in FMS V2.4 where the faster $QIO completion could (in
conjunction with AST-level $QIO activity) cause a $SETEF to not be properly
detected resulting in an LEF process hang.

There is a correction for this problem that can be applied to FMS V2.4 with
ALL-IN-1 V2.3, V2.4 and addresses the problem experienced above in ALL-IN-1.
This can be obtained from the Digital Customer Support Center on request.

    Sometimes a <CTRL/C> will help to continue the session.
    Works for me.
    
    Joerg

    Hi,
    
    The customer has installed the new FMS image, and still found the same
    problem.
    
    I have done some testing here on our v3.0-1 system and found the
    following problem.
    
    1) If you in within the WPS-PLUS editor when ALL-IN-1 actually shuts
    down, the document is in a RESERVED state when you re-enter ALL-IN-1
    after it is started up.
    
    2) I could not reproduce the terminal hanging every time (neither can
    the customer!), but one of the terminals did hang if they were actually
    typing at the same time as the broadcast message was displayed.
    
    Any ideas, anyone?
        
    	Thanks,
    
    		Julie

    Julie
    
    Sorry I can't help about the terminal hang, but re:
    
    > 1) If you in within the WPS-PLUS editor when ALL-IN-1 actually shuts
    > down, the document is in a RESERVED state when you re-enter ALL-IN-1
    > after it is started up.
    
    There is a reason for this. It is kept reserved so that no-one else can
    touch it until you are completely finished with it. You should be able
    to carry on editing from approximately where you left off, if you make
    it current and then edit it again when the session is resumed. This
    works 9 times out of 10, even if the edit session is working on a copy
    of the document (eg if it is remote).
    
    Dick