Conference azur::mcc

    
    RE: .0
    
    Could you provide me with the contents of parameters in the
    mcc_dns_read_attr_data()?
    
    	mcc_aes_dump(entity_spec);
    	printf("\n attribute_code = %d\n", attribute_code);
        /* 
         * Print MCC Descriptor - data_buffer 
         */
    
    
        mcc_dns_read_attr_data(entity_spec, &attribute_code,
    			       &data_buffer, &dns_status);
    
    William

    Hi, William,

    The mcc_aes_dump() and printf() just prior to the
    mcc_dns_read_attr_data() produced the following output:-

    entity [0] wild = NOT_WILD class = 171 id = 1 type = 5
    instance = ..+.�im.y&B3......temp..
    %X08002B1DE6696D027926423395000800010474656D700000
    attribute code = 2

    The object registered in the DNS database (dnscp show object .temp) has
    the following information:-

                                    SHOW
                              OBJECT  ds5000_ns:.temp
                                  AT  25-FEB-1992:16:07:32
%X4D43435F1100AB00000000000000000000000 = %xa6820042bf817b820012a082000e810102
8201008301008401008500bf817c820024a1820020810105821808002b1de6696d027926423395
000800010474656d700000830100
                       DNS$ACS (set) = :
                               Flags = none
                              Rights = read, write, delete, test, control
                       (V) Principal = ds5000_ns:.ds5000.root
                           DNS$Class = MCC_
                    DNS$ClassVersion = 1.0
                             DNS$CTS = 1992-02-25-11:11:55.233/08-00-2b-1d-e6-69
                             DNS$UTS = 1992-02-25-11:11:55.726/08-00-2b-1d-e6-69
                           MCC_Class = %xab000000
           MCC_REGISTRATION_ARGUMENT = %xa08200088203676268830101
              MCC_REGISTRATION_STATE = %x01000000
                             MCC_UID = %x92ec454356f3ca010000aa00040003fb
                         MCC_Version = %xa68200089f817d0456010200

Is this what you need?  Pete Shea.

Hello Pete,

From 2414.2, I do not see the attribute data (attribute code = 2)  written to
ds5000_ns:.temp object.

I think that you're using the Registration FM to register the object 
(class 171), and using your AM to call mcc_dns_write_attr_data()
and mcc_dns_read_attr_data().

There are two possible causes of the problem. One is that the MMs have
different environment variable valules.
If you're running your AM as a separate process, make sure that your AM
has environmental variable MCC_DNS_SELECTION set to DNS.
(make sure that you do not re-define the logical in .login or .cshrc.
 If you do, make certain that all MCC processes have the environmental
 varialbles set to the same value.)

Another cause of the problem is that your AM was linked with a dummy
DNS library in the MCC kit mcc_dns_libdns.o-mips instead of /lib/libdns.a.
The dummy library is in /usr/mcc/mmtoolkit/lib/mcc_dns_libdns.a.
If your system does not have /lib/libdns.a, the MCC Toolkit kit installation
creates a soft link /lib/libdns.a pointing to
/usr/mcc/mmtoolkit/lib/mcc_dns_libdns.a.

      (**   
      Dummy DNS library on Ultrix Systems

      Since the DECdns on Ultrix is only avaiable on the systems running the
      DECnet/OSI, and MCC Kernel uses DECdns routines, it is necessary to
      provide a dummy DNS library so that MMs can link with the Kernel when
      the system does not have DECdns.
      **)

You may check the size of /lib/libdns.a library file. Make sure that it is
not a softlink

William

William,

Thanks, it was the dummy library causing the problem.  The AM was rebuilt using
the real libdns.a, and works fine now.

Developers please note ... Some kind of diagnostic/message (perhaps a printed
message when a stub is called, saying that the image was built using a stub
library) would have been helpful.

Pete Shea.