[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

378.0. "Installation problem VMS V5.4 + DNS V1.1 + DECmcc" by PHONE::LORD () Wed Oct 03 1990 18:39

	I've just installed VMS V5.4 on a 3400 with 64Mb memory and
	a single RF71; I had no problems with the installation of
	VMS, and afterwards the DNS clerk started with no problem.
	
	I'm having a problem with DNS V1.1 now. When I installed it
	I created a new namespace (NMF_NS), and it looked like it
	succeeded (the IVP passed). I then installed the latest FT
	DECmcc (IT1.1.0) and the DECmcc ToolKit (1.0). Now when I
	try to start up DECmcc I get an error message because the
	shared image SYS$LIBRARY:DNS$SHARE.EXE is not installed.
	I looked in the DNS$* DCL files and found that that file 
	is installed by DNS$CLERK_STARTUP.COM, so I stopped and
	restarted the clerk - at this point I get an error:
	"%DNS-E-SOLICITMBXFORMA, Mailbox message to DNS$SOLICIT
	badly formatted", so the shareable images are not 
	installed.

	I have tried shutting things down and restarting them,
	even booting and starting things up one - by - one with
	no success.

	I would welcome *any* suggestions, if not how to fix it
	at least where to look!

	Thanks,

	- Rick Lord

T.RTitleUserPersonal
Name
DateLines
378.1Check your default namespace?NSSG::R_SPENCENets don't fail me now...Wed Oct 03 1990 21:2510
    I believe that you have to modify a file related to DNS startup to
    change your default namespace to be the one you want. I seem to
    remember that you can speicify a list of namespaces but the one that
    you want MCC to use must be the default.
    
    If you use DFS normally, just be sure to make your DFS mount commands
    access a specific namespace (like DEC:.eng.nac.nets.user$98) so the
    DFS mounts don't use the default by accedent.
    
    s/rob
378.2Progress report ...PHONE::LORDFri Oct 05 1990 10:5716
    
    A few more details - I have been corresponding with Roger Z. from the
    DNS group, and he is looking into the problem. Presently it is crashing
    when I do a DNS SHOW DIRECTORY DNA_NODE, but only after I start up the
    MCC director: before that the identical command works fine. I have run
    the MCC file MCC_DNS_BASIC_SETUP, but not MCC_DNS_SETUP, which comes up
    with a menu (I'm not sure what menu items are required for setup, as
    the installation document I'm working from does not mention a menu).
    By the way, it is the system which is crashing, not just the DNS
    process. DNS seems to be setting up the default namespace properly,
    as soon as I start it I can do a DNSCP SHOW NAMESPACE.
    
    	- Rick Lord
    
    
    
378.3DNS configuration errorsTOOK::ZEEName that serverFri Oct 05 1990 16:3217
Basically, most of the DNS clerk that comes with VMS V5.4 was deleted
and replaced with an old DNS clerk that comes with the DNS V1.1 Server kit
(which should not have been installed).  This old DNS clerk would allow
the DNS Server to operate, but not any DNS client application using
the $DNS system service nor DNS rtl routines (like MCC) because DNS$SHARE.EXE
and DNS$RTL.EXE did not exist back then.

So, if anyone installs a DNS V1.1 Server onto a VMS V5.3 (that's when the
DNS clerk began appearing with VMS) or later system, the installation should
detect that the clerk version on the system is equal to or later than the old
clerk in the server kit, and therefore not install it.  No DNS clerk files
in SYS$COMMON should be deleted.

Reference note 413 in the DNS conference if interested (KP7 to add).

--Roger