| 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 | 
    
    
Hi there,
we have two strange problems at customer site : 
1) We cannot set LOCATION reference information on NODE entities. DECmcc
   gives the message : "You are not authorized to perform this Directive" 
   if we try to do it. Other reference information works fine. See below :
   The user account used has explicit access to the object and corresponding
   softlink in the namespace. The same results come up, if we use the SYSTEM
   account (which has no access in the namespace).
MCC_>   set NODE .dtb.develop.BAVARO location = "TS4"
Contents of the IN_P buffer:
[  0 ] (
    [  1 ] (
        [  31 ] (
            [  1 ]             06
            [  2 ]             54 53 34  -- TS4
            [  3 ]             00
            )
        )
    )
IN_Q is empty
Contents of parse_ilvs value_desc: :
  MAXLENGTH :1024
  LENGTH    :4
  CLASS     :1
  TYPE      :14
d0 99 19 00
QIO P4 Node Name Descriptor:  :
  MAXLENGTH :6
  LENGTH    :6
  CLASS     :1
  TYPE      :14
62 61 76 61     72 6f
ops_dna5_ENTITY_REQUEST return status code = 209c
[  261 ] (
    )
Node DTBDEV:.dtb.develop.BAVARO
AT 13-JUN-1994 14:36:31 Characteristics
You are not authorized to perform this Directive
-------------------------------------------------------------------------------
Setting for example IMPLEMENTATION reference is fine :
MCCMGR-BAVARO_MCC_>   set NODE .dtb.develop.BAVARO IMPLEMENTATION = "TS4"
Node DTBDEV:.dtb.develop.BAVARO
AT 13-JUN-1994 14:37:16 References
Modifications completed successfully
                    Implementation Desc = "TS4"
MCC_>
-------------------------------------------------------------------------------
The following OPCOM Events are recorded, if we try to set LOCATION reference :
SYS-BAVARO_>
%%%%%%%%%%%  OPCOM  13-JUN-1994 18:13:48.82  %%%%%%%%%%%
Message from user AUDIT$SERVER on BAVARO
Security alarm (SECURITY) and security audit (SECURITY) on BAVARO, system id: 50
838
Auditable event:        Network login failure
Event time:             13-JUN-1994 18:13:48.81
PID:                    0000008E
Username:
Remote nodename:        BAVARO          Remote node id:         0
Remote username:        MCCMGR
Status:                 %LOGIN-F-NOTVALID, user authorization failure
SYS-BAVARO_>
%%%%%%%%%%%  OPCOM  13-JUN-1994 18:13:49.07  %%%%%%%%%%%
Message from user SYSTEM on BAVARO
Event: Access Control Violation from: Node DTBDEV:.DTB.DEVELOP.BAVARO Session Co
ntrol,
        at: 1994-06-13-18:13:49.059+02:00I0.188
        NSAP Address=49::00-31:AA-00-04-00-96-C6:20,
        Source=UIC = [0,0]MCCMGR,
        Destination=name = CML,
        Destination User="",
        Destination Account="",
        Node Name=DTBDEV:.dtb.develop.BAVARO
        eventUid   33EAA137-86DB-11CD-827A-AA00040096C6
        entityUid  2732085F-86B7-11CD-8001-AA00040096C6
        streamUid  F8E846E7-86B8-11CD-800C-AA00040096C6
SYS-BAVARO_>
-------------------------------------------------------------------------------
Any suggestions ???
2) I register NODE4 objects, with OPERATION=COMPLETE, who's namespace objects
   and softlinks are available in DNS. NODE4's which are not reachable, or 
   access control does'nt match loos her NODE-SYSNONYM'S !!!!!
   Has anyone seen this before ?
   Thanks for help
   Ralf Wiessner
   (Technical Support for German Options and Futures Exchange, DTB)
    
| T.R | Title | User | Personal Name | Date | Lines | 
|---|---|---|---|---|---|
| 6017.1 | Node has 2 Location attributes | TAEC::LAVILLAT | Wed Jun 15 1994 05:53 | 25 | |
| Re .0: What you see is not so strange. It is simply because the Node entity has two attributes with name "Location". What you see here : >Node DTBDEV:.dtb.develop.BAVARO >AT 13-JUN-1994 14:36:31 Characteristics > #########################^^^^^^^^^^^^^^^^ >You are not authorized to perform this Directive > > is a response for a set characteristics, which require root privileges. I am afraid that the only way to set the Location *reference* attribute is to set it via the Iconic Map PM, which explicitely give you the choice for set char or set reference. Regards. Pierre. | |||||
| 6017.2 | Two Location attributes ??? | FROCKY::WIESSNER | Ralf Wiessner, Solution Integration Center FRS | Wed Jun 15 1994 08:15 | 48 | 
|     
    Thanks Pierre,
    
    that's new to me, because I'am working mainly with FCL. We run DECmcc
    on VAX/VMS and I tried to set the attribute with all privileges, (which
    is equivalent to root on Unix : 
    
    MCCMGR-BAVARO_MCC_> set  node .dtb.develop.bavaro location="TS4 KMR",BY
    USER SYSTEM, PASS <password>
    
    Node DTBDEV:.dtb.develop.bavaro
    AT 15-JUN-1994 12:55:38 Characteristics
    
    Problems modifying attributes
                                   Location = -- No Such Attribute
    
    
    The same is returned from Iconic-Map.
    
    Oh, I just see another problem. If I do a show characteristics I get an
    error : Inconsistency between dictionary and information returned in
    outp !
    
    From commandline I see : 
    MCCMGR-BAVARO_MCC_> show node .dtb.develop.bavaro all char
    
    Node DTBDEV:.dtb.develop.bavaro
    AT 15-JUN-1994 13:29:23 Characteristics
    
    Examination of attributes shows:
    
    MCCMGR-BAVARO_MCC_>
    
    The same with other NODE objects. 
    
    I installed the new FDICTIONARY.* files, which provides additional
    support for DECnis. I assume there must somethink broken.
    
    I'll check that with the old DICTIONARY.
    
    
    I still have the problems of loosing .DNA_Nodesynonym softlinks for
    nodes, which are not accessable at the time of registration. 
    
    regards
    
    ralf.
    
 | |||||
| 6017.3 | Use old MCC_FDICTIONARY.* | FROCKY::WIESSNER | Ralf Wiessner, Solution Integration Center FRS | Thu Jun 16 1994 05:34 | 22 | 
|     
    I check'ed the dictionary and found out, that it just doesn't work for
    my NODE objects. 
    I reinstalled the old MCC_FDICTIONARY.* files, and it worked again. But
    now I have probably lost the enhancements for DECnis. But managing
    DECnis is the customers reason using DECmcc (mainly), cuz there is no
    other VMS based managment (NCL is not adequate).
    
    Have I missed a step ? Do I have to do anything when I like to use the
    new dictionary ?
    
    
    Please help. 
    
    
    Btw. with the old dictionary, I'am able to set the reference attribute
    LOCATION !!!!!!
    
    
    thanks
    ralf.
    
 | |||||