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

Conference clusta::acms

Title:ACMS comments and questions
Notice:This is not an official software support channel. Kits 5.*
Moderator:CLUSTA::HALLAN
Created:Mon Feb 17 1986
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:4179
Total number of notes:15091

4100.0. "exec and user ASTs disabled" by CSC32::J_HENSON (Don't get even, get ahead!) Tue Feb 11 1997 12:11

acms v4.1, ovms v6.2, vax

I just need a sanity check to make sure that I'm not overlooking something.

I just took a call from a customer (Navistar) who is having problems
stopping a procedure server.  The process running the server shows
to be in com state from either the show system command or sda
sho process.  However, an  attempt to use sho proc/continous
fails with an error saying that the process is suspended.  I
found this very unusual.

Further investigation using sda revealed that both Exec and User
mode ASTs are disabled.  Also, the process is in DELPEN, FORCEPEN
and RESPEN state.  It seems pretty likely that having Exec and
User mode ASTs disabled explains the odd state and why the process
can't be deleted.

What I need to know is if there is any way that the acms code that
runs within the context of a server could disable ASTs?  If not, then
I'll know that this is strictly a user code issue.  However, I
just want to be sure.

Thanks,

Jerry
T.RTitleUserPersonal
Name		DateLines
4100.1OHMARY::HALLBill Hall - ACMS Engineering - ZKO2-2Wed Feb 12 1997 10:2719
    
    The only EXEC mode code that I'm aware of in a prodecure server
    is in the messaging between EXC and the SP.  Once this code
    calls the procedure specified in the processing step, you are
    in USER mode with all AST's enabled.
    
    A process in DELPEN (Delete Pending) will show up as being
    suspended.  Unfortunately once you get a process into this
    state the only way to recover is to reboot.
    
    Was it possible that the user code was in the middle of some
    RDB query and someone attempted to do a STOP/ID on the
    process?  An SQL query is not interruptible from the ACMS
    side so if this was a query that took a long time, ACMS cannot
    gain control of the server until the query is complete.
    
    Bill
4100.2thanksCSC32::J_HENSONDon't get even, get ahead!Thu Feb 13 1997 09:1324
>>   <<< Note 4100.1 by OHMARY::HALL "Bill Hall - ACMS Engineering - ZKO2-2" >>>

    
>>    The only EXEC mode code that I'm aware of in a prodecure server
>>    is in the messaging between EXC and the SP.  Once this code
>>    calls the procedure specified in the processing step, you are
>>    in USER mode with all AST's enabled.

Thanks, Bill.
    
>>    Was it possible that the user code was in the middle of some
>>    RDB query and someone attempted to do a STOP/ID on the
>>    process?  An SQL query is not interruptible from the ACMS
>>    side so if this was a query that took a long time, ACMS cannot
>>    gain control of the server until the query is complete.

The server is doing some sort of remote procedure calls using a
third party rpc product called netwise.  I suspect that the problem
is due to either user code or the rpc code, but wanted to make sure
it's not acms.

Thanks,

Jerry