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

Conference azur::mcc

Title:DECmcc user notes file. Does not replace IPMT.
Notice:Use IPMT for problems. Newsletter location in note 6187
Moderator:TAEC::BEROUD
Created:Mon Aug 21 1989
Last Modified:Wed Jun 04 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:6497
Total number of notes:27359

2152.0. "Mechanism when using MIR?" by DUCAT2::FOUR62::LICAUSE (Al Licause (338-5661)) Tue Jan 21 1992 10:52

I'm running T1.2.4. of DECmcc.

Could someone possibly explain the mechanism DECmcc is using when the MIR
is chosen instead of DNS?

I am unable to register Phase IV DECnet entities.....
I've been able to register STATIONS and SNMP entities, but no DECnet.

When trying to register a Phase IV DECnet node, I get "Node does node support
this system-specific operation".  Can someone explain what system specific
opertion is being attempted by MCC?

thanks,
Al
T.RTitleUserPersonal
Name
DateLines
2152.1Which OS?TOOK::MINTZErik Mintz, DECmcc DevelopmentTue Jan 21 1992 10:5411
>I'm running T1.2.4. of DECmcc.

VMS or ULTRIX?

>When trying to register a Phase IV DECnet node, I get "Node does node support
>this system-specific operation".  Can someone explain what system specific
>opertion is being attempted by MCC?

This does not sound to me like an namespace problem.
Can you issue a show command for the same node4?

2152.2VMSDUCAT2::FOUR62::LICAUSEAl Licause (338-5661)Tue Jan 21 1992 13:3310
This is a VMS system.

Attempting to SHOW something from these nodes only returns the message...
"Insufficient information, entity has only been partially registered"

I understand that MCC tries to do a show command upon registration
and if unsuccessful, then executes a partial registration.  If I can
do an NCP> SHOW EXEC CHAR, should I not be able to register this node?

Al
2152.3try using MIR before blaming DNS !!TOOK::JESURAJWed Jan 22 1992 12:4122
    Ref .0
    
    Do you the same problem when you use LOCAL MIR instead of DNS?
    
    Try the following:
    
       $define MCC_DNS_SELECTION MIR
    
    The invoke MCC and try registering the some DNA4 nodes.
    
    
    If this works ok, then we it is a DNS problem, else could
    be a DNA4 problem.
    
    Let us know how this goes.
    
    
    Jesuraj
    
    
    
    
2152.4This is MIRFOUR62::LICAUSEAl Licause (338-5661)Wed Jan 22 1992 16:2218
Sorry.....I should have explained that I was using the MIR......

(LNM$SYSTEM_TABLE)

  "MCC_COMMON" = "SYS$COMMON:[MCC]"
  "MCC_DNS_SELECTION" = "MIR"
  "MCC_ICONS" = "MCC_COMMON"
  "MCC_MAPS" = "SYS$DISK:[]"
        = "MCC_COMMON"
  "MCC_NODE_IDP" = "49::"
  "MCC_SPECIFIC" = "SYS$SPECIFIC:[MCC]"
  "MCC_SYSTEM" = "MCC_SPECIFIC"
        = "MCC_COMMON"
  "MCC_TDF" = "Using DECdts logical SYS$TIMEZONE_DIFFERENTIAL"
  "MCC_UIL" = "MCC_COMMON"
                               

Al
2152.5please retry with node4 addressTOOK::CALLANDERMCC = My Constant CompanionThu Jan 23 1992 14:423
    please try the node4 command using the node4 address and let us know
    the results. By any chance are you trying to register a cluster?
    
2152.6Still doesn't work....FOUR62::LICAUSEAl Licause (338-5661)Fri Jan 24 1992 08:3040
Ok....I've tried:

register node 36.60

REGISTER NODE4 36.60
Node4 LOCAL_NS:.36.60
AT 24-JAN-1992 08:28:21

Partial registration success. Please retry later to complete the registration.
        Reason for Partial Registration = One or more required arguments are
                                          missing.



then I tried   register node4 dwovax address = 36.60

register node4 dwovax address = 36.60
Node4 LOCAL_NS:.dwovax
AT 24-JAN-1992 08:29:36

The requested operation cannot be completed
                      MCC Routine Error = %MCC-E-INV_IN_P, invalid argument or
                                          attribute

then we always have the old  register node4 dwovax
register node4 dwovax
Node4 LOCAL_NS:.dwovax
AT 24-JAN-1992 08:30:39

Partial registration success. Please retry later to complete the registration.
        Reason for Partial Registration = Duplicate Arguments were found.



Must be something else?

Does this give you any clues as to what could be wrong?

Al

2152.7Are you running V5.5/WaveII?TOOK::GUERTINDon't fight fire with flamesFri Jan 24 1992 09:0210
    Al,
    
    From the logicals, it appears that you have V5.5/WaveII or some
    combination.  I believe the  MCC_TDF logical is saying that MCC found
    DECdts, and is using the "real" Time-Synch Services.  This does not
    happen unless you are running a later version of VMS (or have installed
    some special dtss kit).  We are experiencing some problems on
    V5.5/WaveII systems and are installing the latest kit, even as I type.
    
    -Matt.
2152.8Need all three agruments on Phase V hostsTOOK::BIRNBAUMFri Jan 24 1992 10:2513
    All of the registration attempts described in .6 are syntatically
    incorrect. The release notes give a few more details on registering
    Phase IV nodes from a Phase V system. Try the following command:

    register node4 dwovax synonym dwovax, address=36.60

    If you get duplicate identifier error after you attempt the above
    command, then it is likely that you have a node synonym or
    backtranslation link pointing to a full name different that one you are
    attempting to register.(This could caused by your previous registration
    attempts.) Therefore if the duplicate identifier error message is
    returned, then you should be sure to deregister all of the nodes that
    are using the same synonym and/or address as the desired node.
2152.9Still broken but getting closer.....FOUR62::LICAUSEAl Licause (338-5661)Wed Feb 12 1992 13:4538
Yes .7, this is WAVE II.

Thanks .8, but still not working.....


MCC> register node4 dwovax synonym dwovax, address = 36.60

Node4 LOCAL_NS:.dwovax
AT 12-FEB-1992 13:35:58

Partial registration success. Previously partially registered arguments were
changed. Please retry later to complete the registration.
        Reason for Partial Registration = Node does not support this
                                          system-specific operation.
MCC> sho node4 dwovax all count

Node4 dwovax
AT 12-FEB-1992 13:42:03 Counters

Node is not registered.
MCC> register node4 dwovax synonym dwovax, address = 36.60

Node4 LOCAL_NS:.dwovax
AT 12-FEB-1992 13:42:12

Node4 LOCAL_NS:.dwovax
AT 12-FEB-1992 13:42:57 Counters

Node does not support this system-specific operation.
MCC> sho node4 .dwovax all count

Node4 LOCAL_NS:.dwovax
AT 12-FEB-1992 13:43:05 Counters
  
The entity is already registered with MCC.
MCC> sho node4 local_ns:.dwovax all count
      
                                   
2152.10TOOK::MINTZErik Mintz, DECmcc Development, dtn 226-5033Fri Feb 21 1992 10:372
Taken off line