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

Conference iosg::all-in-1

Title:ALL-IN-1 (tm) Support Conference
Notice:Please spell ALL-IN-1 correctly - all CAPITALS!
Moderator:IOSG::PYECE
Created:Fri Jul 01 1994
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2716
Total number of notes:12169

2567.0. "EXIT from subprocess hangs teminal" by OASS::BURNAMAN_B (And now, live, from Atlanta . . . ) Wed Mar 12 1997 16:20

    Greetings,
    
    I have a customer that called in an interesting problem, which he has
    had for a long time now.
    
    He has a two node VAX cluster running 3.0 ALL-IN-1 in a common en-
    vironment.
    
    On one node only, if the user drops to the subprocess using either
    $ or GOLD $ and then types in EXIT to leave the subprocess, the users
    terminal hangs.  On the other machine, the same steps do not cause a
    hang and the user gets the ALL-IN-1 screen back.
    
    In researching this, I found that on the problem machine, simply doing
    a return while in the subprocess works.  I also found that after the
    user types EXIT, the subprocess actually does go away, but the user
    does not get the ALL-IN-1 screen back.
    
    Control T is of no benefit, Control Y has to be used to free the
    condition, which also blows the user completely out of ALL-IN-1.
    
    All users are affected, including the manager account.
    
    On either machine, the <SPAWN command works with no problem.
    
    Anyone seen this before?  Any ideas on what may be causing this prob-
    lem?  Thanks,
    
    Bruce Burnaman
    CSC/Atlanta
T.RTitleUserPersonal
Name		DateLines
2567.1SWAGIOSG::PYEGraham - ALL-IN-1 Sorcerer&#039;s ApprenticeWed Mar 12 1997 16:414
    Casting my mind back, since this is V3.0...
    
    Something to do with DDS? When we go into the subprocess, we do
    something to stop DDS updates being hung, I think.....
2567.2IOSG::MAURICEBack in the eggThu Mar 13 1997 10:159
    Hi,
    
    This problem was fixed in V3.2. The fix was in code and I don't think
    there was a patch for earlier systems. The random nature of the problem
    is explained by the code doing a test on the wrong memory location.
    
    Cheers
    
    Stuart
2567.3Real ALL-IN-1 programmers use SPAWNSHRMSG::HOWARDWhoever it takesThu Mar 13 1997 22:4926
    In earlier versions of ALL-IN-1, the symbols LOGOUT and STOP were defined
    as "!".  I think EXIT may have been also.  The following is from the
    APR (AA-N324A-TE), p. 60:
    
      Do not use the STOP or LOGOUT commnands.  This deletes the subprocess
      and causes ALL-IN-1 to abort
    
    I believe EXIT did the same thing.  So the customer hasn't exactly
    found a new problem.  In fact, I think that is why SPAWN was invented. 
    
    
    I have been using the following for many years in my default menu:
    
    ;;.GOLD $;;
    
    .IF CLI$PROC_EXISTS EQS "1" THEN GET OA$FUNCTION="ATTACH "
    OA$PROFIL_VMSUSR "_1"
     ELSE GET CLI$PROC_EXISTS = "1" \\
      OA$STAT_GET_STATISTICS \\
      GET CLI$A1 = CLI$LO = 'ATTACH/ID=' STAT$PID \\
      SPAWN \\GET CLI$LO = ''
    
    courtesy of a certain Mr. Barth, who asked for it back when our paths
    last crossed outside the company.   
    
    Ben