[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

5456.0. "Compatibility from V1.3 back to V1.2.1 ????" by PLUNDR::LOWEG (WANTED!! A modern day Robin Hood.) Tue Aug 10 1993 11:05



	Could anybody clear up an uncertainty about backwards compatibility
	from V1.3 back to V1.2 using an Ultrix o/s.

	The reason why I ask is that whilst looking at notes to truobleshoot
	a customer problem I read in note 4606.2 that it wasn't. However,
	this note was rather ambiguous, in that the author of the note said
	he was told this information, and I need to be sure..

	The problem I am looking is that the customer has written his own
	access module which works ok with MCC V1.3 using the local namespace.

	He is now trying to port this access module to a MCC V1.2.1 system
	using DNS V2.0. He can use the registration fm ok but his management
	module will not work in his environment. The error message he has
	given me as an example is "MCC_DNS UNMAPPED ERROR" which doesn't
	seem to give a lot away.

	Anybody any ideas ??

	Gary Lowe NUK CSC comms..


T.RTitleUserPersonal
Name
DateLines
5456.1Not the mcc version but the namespace option.PLUNDR::LOWEGWANTED!! A modern day Robin Hood.Wed Aug 11 1993 12:2313
    
    The customer has now upgraded to V1.3 and it still fails.
    
    As I explained before their module was written using our MCC_DNS
    functions on a system using LOCAL_NS. When ported to a system using DNS
    it fails with the ambiguous error "MCC_DNS UNMAPPED ERROR". As an
    example this error message occurrs when using the call
    MCC_DNS_FULLNAME_STRING.
    
    Anybody any ideas as it now seems that the swap from LOCAL_NS to DNS
    is causing the module to fail.
    
    Gary Lowe NUK CSC comms..
5456.2Here is the reason...PLUNDR::LOWEGWANTED!! A modern day Robin Hood.Thu Aug 19 1993 06:4061
    
    The answer which was eventually found by the customer himself moments
    before receiving a mail from William Kwak MCC engineering looking in
    the exact same direction.
    
    Here is the answer for future reference;
    
    This is the mail I received from William:-
    
    In order to find out what the problem was in using DECdns,
    please do the following:
        $ setenv MCC_LOG 1
        $ manage
        MCC> enroll "the customer's MM"
        MCC> ! invoke the command which caused the error
        MCC> ! MCC will print some info about the error
    
    My first guess of the customer's problem is that the customer
    might have linked his/her Access Module on a Ultrix system
    which did not have DECdns library. The DECdns library is only
    available on DECnet OSI systems.
    Please check the library for SIZE and date. Our build machine has
    the following:
        # ls -l /usr/lib/libdns.a
        -rw-r--r--  1 root      3949184 Jun 11  1992 /usr/lib/libdns.a
    
    
    The DECmcc toolkit does not include the DECdns library.
    However, the toolkit includes a dummy DECdns library which is copied
    and
    soft-linked by /usr/lib/libdns.a at toolkit installation IF the system
    does not have DECnet-OSI. (The dummy DECdns library allows for an MM
    to be linked with MCC Kernel without using real DECdns library.)       
    
    
    William.
    
    
    This turned out to be exactly where the problem lay. In fact without
    DECnet-OSI and using LOCAL_NS any development uses a dummy file called
    mcc_dns_libdns.a. The purpose of this file is for the following
    reasons, again details supplied by William :-
    
    The MCC kernel routines (e.g. mcc_dns_fullname_string()) call DECdns
    routines (e.g. dnsCvtOpqFullToStr()). When linking an MM, the reference 
    to the DECdns routines have to be resolved. However, the DECdns routines 
    do not exits on non-DECnet-OSI Ultrix systems. Linking without the dummy 
    dns file will cause many link errors.
    
    The mcc_dns_libdns.a contains a set of DECdns routines referenced by
    MCC_DNS_* routines. But the dummy DECdns routines just return 
    MCC_S_NOT_IMPLEMENTED.
    
    William..
    
    The customer pipped us to win the solution race this time, but hopefully
    with the help of this note we will be victorious next time..
    
    Thanks to William Kwak..
    
    Gary Lowe NUK CSC comms..