Conference azur::mcc

    
    What seems to be wrong is that you put in the BY clause but you
    didn't supply any values. What is the name of the proxy account
    that you want to connect to? Try putting the account name in
    (or the username) and see what happens.
    
     MCC> SET NODE4 TARGET MAXIMUM PATH SPLIT 2 , BY ACCOUNT=<my_account>
    
    remember the decnet module isn't going to call the authorize facility
    to figure out what account you mean. The following is a cut and
    paste from a sample run. (This uses our internal baselevel X0.10.1.)
    
    MCC> enroll mcc$decnet_emm
    MCC> 
    MCC> ! no privs 
    MCC> 
    MCC>  show node4 goste all char
    Node4 goste
    Characteristics
    AT 31-MAY-1990 15:41:56
    
    
    Access control information invalid at Node
    MCC>
    MCC> ! privs by useing BY clause
    MCC>
    MCC>  show node4 goste all char, by user=system, pass=xxxxx
    Node4 4.507
    Characteristics
    AT 31-MAY-1990 15:42:26
    
    
    Examination of Attributes shows:
                             Identification = "DECnet-VAX V5.3,  VMS V5.3    "
                         Management Version = V4.0.0
                             Incoming Timer = 45 Seconds
                             Outgoing Timer = 60 Seconds
                             Incoming Proxy = Enable
                                            :
                                            :

    
    Hope this helps
    jill

    
    
    I'm sorry I explained my problem badly :
    I used a correct by user = xxxx , by password = yyyy
    and thus it worked .
    
    from source :
    
    MCC> SET NODE4 TARGET MAXIMUM SPLIT 2 ,BY USER = xxxx, BY PASSWORD = yyyy
    
    But my problem is : 
    
    Is there a mean -without specifying  ,BY USER= xxxx ,BY PASSWORD=yyyy-
    because it is a too complex syntax for a custumer demonstration -
    to get the information ?
    
    The target node NML has no user id no password specified.
    
    I defined a proxy default account on the TARGET for user 
    xxxx with password yyyy whose default privileges are NETMBX , 
    TMPMBX, OPER and SYSPRV from the account on the source node 
    (on target: 
     uaf>add/proxy source::source_account xxxx/default)
    
    from source :
    
    MCC> SET NODE4 TARGET MAXIMUM SPLIT 2
    
    Access control information invalid at node 
    		     
    
    Is there still an ACL on a file ? or ..?
    
    		Catherine 

    
    Hi,
    
    I think that what happened is that you didn't specify your proxy login
    account to be the default proxy login account.
    
    To verify that, try the command with just the By User = "xxx" and no
    password qualifier.  This instructs VMS to try to get you into a
    particular proxy account.  If that works, then you have to get into
    authorize and change your proxy.
    
    Here is what I normally do:
    
    	ADD/PROXY remote::CAREY CAREY/DEFAULT
    
    There is probably a modify command too, but I don't have it on the top
    of my muddled head.  So, unless you want to look it up just delete the
    old proxy entry and add a new one.
    
    This will make VMS quite pleasantly log you into the default proxy
    account when you access the node, instead of failing over to the NML
    default account (which doesn't have the privs you need).
    
    If you have problems with this, let me know, so we can see if there are
    any other potential problems possibly associated.
    
    -Jim Carey, DECnet Phase IV AM
    
    

.2's example does use /DEFAULT.

Catherine, did you try to do something similar outside of MCC?  E.g., use NCP, 
SET EXEC to target node and try to set Maximum Split?  Or even try DIR TARGET::
to ensure the proxy is working as you expect?  Did you make sure the TARGET node
has the name of the source node in its database?

_Mek