[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

6361.0. "LOCAL:. namespace why not?" by TNODNS::SYSTEM () Thu Aug 17 1995 17:13

    Hi all,
    
    	my environment is:
    
    system	mVax3600 [Main Memory (64.00Mb)]
    
    platform	VAX/VMS V6.1 
    		DECnet/OSI (DNVOSI_ECO03058)
    		DNS protocol version DNS T2.0.0.0 (DNVOSIMUPB056)
    
    product	DECmcc (V1.4-1)
    
    
    	The system use DEC:. namespace but it isn't Dns server, when I
    runned NET$configure I chosed DECDNS and LOCAL for directory services.
    
    	Now I would like use LOCAL:. namespace for DECmcc, without lose
    dec:. namespace for other services (notes...).
    
    	But setting up the DNS Namespace I got
    *************************************************************************
    * Namespace to use (Def="TRENO_NS:"): local:.
    
    Choose one of the following functions by specifying its function
    number,
    or request help by typing HELP or a question mark (?)
    
      0. Exit
    
      1. Create the initial namespace directories
      2. Create a command file to help register existing Phase IV nodes
      3. Create additional directories in the name space
      4. Create back translation directories for new network IDPs and areas
    
      5. Add members to the access control group
      6. Remove members from the access control group
      7. Show members of the access control group
    
      8. Delete directories in the name space
    
    * Function to execute: 1
    DNS$CONTROL program does not exist on this system.
    To execute this function, make sure that following files exist:
      SYS$SYSTEM:DNS$CONTROL.EXE - DNS control program
      SYS$SYSTEM:DNS$CONTROL.BIN - DNS management command parse table
      SYS$SHARE:DNS$LIB.EXE      - DNS shareable library
    
    If you do not have access to these files, please run this
      command procedure on a system which has DNS Server running.
    **************************************************************************
    
    Effectively I can't found SYS$SHARE:DNS$LIB.EXE in my mVAX.
    
    From MCC_AUDIT I get 
    
    **************************************************************************
     Checking DNS Client Version
      %% error attempting to read version of DNS Client file
    	SYS$LIBRARY:DNS$CLIENT.EXE!
    **************************************************************************
    
	In case, where I failed?, what I've to do?, should my mVAX became DNS 
    server?, of wich namespace (LOCAL:./DEC:. or both?), have I to reinstal 
    DNS?
    
    	It could be those questions are trivial but in this momemt I became
    a little bit confuse  
    
	Thanks for any help
    
    Daniele

T.R	Title	User	Date	Lines
6361.1		AZUR::DURIF	`Fri Aug 18 1995 11:30`	21
	Hi Daniele, If i undertand you weel you need to DEC namespace for DECnet use. So keep your system using DEC namespace. MCC cannot use LOCAL namespace but if you do not want to store MCC information in DEC namespace you have a logical name. $ define MCC_DNS_SELECTION MIR will do the job. That will make MCC stop using DNS and all MCC information will be stored on local node in private files. This define may be done for a process or in system table. Your VAX does not need to become a DNS server. Hope this helps, Benoit
6361.2	YES it's right but I would like more	TNODNS::SYSTEM	`Fri Aug 18 1995 13:04`	23
	Benoit, my wish is to use DNS in all of his fetures (specially DECnet/OSI v6.1), not MIR as work around. In effect, as I works as local area mgr, I would like use MCC to control our LAN using autotopology, autoconfig and so on, without feed the corporate namespace. Why I cannot use LOCAL namespace? I'm installing DECnet/osi v6.1 wich is enhanced in such opportunity and it looks good. I agree to create a xxxx_ns:. namespace if LOCAL is not a good world for MCC, but in this case, could my system be DNS server for xxxx_ns:. namespace without being server for DEC:. namespace? How? just using @sys$system:dns$change_def_file or using $MC DNS$CONFIGURE.EXE? Mer�i beaucoup pour ta rapidit� Daniele Spessato @TRN
6361.3		AZUR::DURIF	`Fri Aug 18 1995 15:25`	29
	Daniele, Now i see what you want to do. > Why I cannot use LOCAL namespace? You may check with someone from DECnet but i think LOCAL namespace has not as much fonctionality as DECdns has. As far as i know you will be the first trying that configuration. > could my system be DNS server for xxxx_ns:. namespace without being > server for DEC:. namespace? Yes you can. You server will handle requests for you namespace only. I do not know how you may keep access to information in DEC:. namespace. Again check for a DECnet feature using DEC: as a second namespace. Using sys$system:dns$change_def_file.com with DEC: namespace and then xxxx_ns: will give two dns$default_file.dat By pasting both in only one file may allow your clerk to see both namespaces. I did not tried this myself. Finally there is a problem in MCC procedure to setup nameserver. Do not use any of the mcc_dns*.com procedures present in mcc_common. They do not run with DECnet/OSI 6.1 or later. I will provide a new one shortly. Bon courage, Benoit
6361.4	LOCAL:. isn' t a true namespace?!!!!	TNODNS::SYSTEM	`Fri Sep 01 1995 11:55`	24
	Hi all, definitively I' ve discovered why I can't use namespace LOCAL:. The command file MCC_DNS_SETUP contains commands could not be applied on LOCAL:. namespace. Effectively the version of DNS I have (DNS T2.0.0.0), does not give you the feature to have a real namespace for your own use inside a global namespace like DEC:. Otherworlds the "namespace" LOCAL:. you can handle with command file NET$CONFIGURE isn' t a namespace as other DNS namespaces, you can' t issue dns$control's commands on it. SO, I' m forced to agree to r. 1 from Benoit and use MIR, "dommage"... next time, could be.... it was looking so nice. Anymore thanks all Daniele P.S. I will continue in another note because I' ve other problems using DECnet Phase IV configurator, See you