Conference clusta::acms

4137.0. "phase V and distributed processing?" by CSC32::J_HENSON (Don't get even, get ahead!) Mon Mar 31 1997 18:24

Is there anything tricky about Decnet phase V and distributed acms?  When
my customer attempts to select a remote task on node x, it fails.  She can 
select remote tasks on other nodes.

On the submitter node, the following message is logged in swlup.

-acmsacc-w-remcallerr, remote call error to NODEX::"49="

When I saw that error, I checked NODEX to see if it was configured correctly, 
and discovered that the acmsgen node_name parameter was not defined.  So,
I had her do that and cycle acms.  That didn't make any differenced.  I had her 
do it  again.  This time, I checked for acms desktop servers and other agents, 
and killed them.

This still didn't help.  The errors on the submitter node are the same.
To make matters worse, I don't know how to check Phase V decnet for the 
presence of obj_49.  I tried using NCP, but that didn't show an obje_49.


So, any suggestions?  With Phase V, how can I determine if the ACC
is coming up in a distributed mode?  We used sda, and saw that it
had 2 channels assigned to netxx devices, one of which was busy.  And,
there was nothing in swlup or atr to indicate any sort of problem.
Could I be chasing the wrong thing?

    
    	On Phase IV, an NCP SHOW OBJ OBJ_49 CHAR should give you a
    	PID that points to ACC.
    
    	On DECnet-Plus (aka DECnet/OSI), the object 49 doesn't
    	appear until the first connection (from what I've seen
    	in my testing).  To see the object:

NCL>sho ses con port * all, with Local End User Address = number = 49
    
    or you cann see all of them with
    
    	NCL SHOW SESS CONN PORT * ALL
    
    Again, the display should show an entry that points to ACC.
    
    The customer has to make sure that the parameter file is being
    reloaded properly, with the node name, otherwise distributed
    ACMS will never start up.
    
    	They can check this by shutting down all of ACMS, and then
    do an INSTALL LIST/GLOBAL  and look for the ACMS$PARAMETERS
    global section (which shouldn't be there if everything shut
    down properly).
    
    Bill
    

    

Thanks, Bill.

Do you know if there are any log files such as netserver.log that
might contain helpful information?

Thanks again,

Jerry

    
    	No, there are no logs to look at.  It's usually pretty easy to get
    it working, as long as the ACMSGEN parameter is set and it is loaded
    when ACMS starts up. 
    
    Bill