Conference azur::mcc

Entered as QAR 2124 at priority 1

	Hi Merlin,

	Well the good news is that I can reproduce the crash! The bad news is
	I am not quite sure what causes it. Let me give you my findings first.
	
	Okay the crash I observed happens under following situation. Please 
	verify that your situation is identical.

	1. IP is invoked from Iconic map.
	2. The account had all the privileges enabled.
	3. option -p and -h were specified in the cf file.
	5. The option host-permit was specified too.

	Under the above condition UCX software causes the VMS operating system
	to crash. Merlin, since you have the dump file, is it possible for
	you to run SDA and let me know the image that caused the crash?


	I also found that IP runs to its completion when the process  has the
	following privileges. 

		NETMBX, TMPMBX, OPER

	The above privileges are all that the software needs. I am still puzzled as
	to why a software should run fine with less privs and run wild if the privs
	are turned on! But then again I know what happens when you leave the kids home 
	alone!!

	I will post here my findings as I know better about the problem.

	- Anil 

Anil,

I was running MCC with full privs originally.  I turned off all but the 
necessary privs for UCX (OPER, BYPASS, SYSPRV) and it did NOT crash!  Is 
this an undocumented feature?

However, after running the config and registration process from the IMPM,
the procedure still did not populate the targeted domain eventhough it 
completed with success and said it found 20 nodes in two networks.  Is 
there another step I need to run to populate the domain?

I'm also working without documentation.  Last time I looked, I didn't see any
documentation for the Autoconfig function on WORDY.  Is this documentation
available elsewhere?


Merlin

Crashes are not a feature, regardless of your privs... :-)

>I'm also working without documentation.  Last time I looked, I didn't see any
>documentation for the Autoconfig function on WORDY.  Is this documentation
>available elsewhere?

There is some draft documentation at the end of the release notes.
The final documentation is still being written, so it is not
available on WORDY.

-- Erik

Hello Merlin,

> However, after running the config and registration process from the IMPM,
> the procedure still did not populate the targeted domain eventhough it 
> completed with success and said it found 20 nodes in two networks.  Is 
> there another step I need to run to populate the domain?

A few thoughts...

It is not necessary for you to create a domain before invoking the
Autoconfiguration application.  Autoconfiguration will create domain(s)
for you, starting with the top level domain you specify when you run
the utility.

The Autoconfiguration chapter of the release notes discusses namespace
planning and mentions a prefix file, MCC_AUTOCONFIG_PREFIX.DAT.
Autoconfiguration uses the prefixes specified in this file to generate
fullnames for all entities to be registered.  This includes domains.
The default prefix for the DOMAIN entity class is .MCC.DOMAIN.

Thus, if you have not modified MCC_AUTOCONFIG_PREFIX.DAT, the full
specification of the domain created by Autoconfiguration would be
".MCC.DOMAIN.STO_TCPIP".

Try opening ".MCC.DOMAIN.STO_TCPIP" and see what happens.  If this domain is
not populated, it is possible that Autoconfiguration ran into problems
registering entities in the domain.

If this is the case, the file TRACE_REGISTRATION.LOG in the directory
[<top dir>.IP.STO_TCPIP] would offer hints as to what went wrong.

Let us know what you find!

Regards,

Ulla Figwer

	Re: .3

	I am running IP autoconfig with the following three privileges.
	TMPMBX, NETMBX, and OPER. I don't need any additional privileges.

	I am still trying to see what the problem is with full privileges.
	I do not plan on considering this as a "feature". Crashing
	VMS is no small offense.

	Re your problem about notes not getting registered, have 
	you checked if the DNS has the directories indicated in the 
	prefix file (MCC_AUTOCONFIG_PREFIX.DAT)? The command to be 
	used for checking the presence of the default dirs indicated in
	the prefix files is as follows:

	$ mcr dns$control

	DNS> SHOW DIR . known child
	:
		The output should indicate MCC as  one of the children.
	DNS> SHOW DIR .MCC know child
	
		This command should indicate (at least) two children.
	.ip
	.DOMAIN


	If you have the above dirs defined, and you are still experiencing a
	problem, let us know.

	

	Regards,

	- Anil

	Re: .6

>	I am running IP autoconfig with the following three privileges.
>	TMPMBX, NETMBX, and OPER. I don't need any additional privileges.

	UCX would not run unless I added SYSPRV and BYPASS to my process
	privs.

>	Re your problem about notes not getting registered, have 
>	you checked if the DNS has the directories indicated in the 
>	prefix file (MCC_AUTOCONFIG_PREFIX.DAT)? The command to be 
>	used for checking the presence of the default dirs indicated in
>	the prefix files is as follows:

	Remember, I'm running with a local namespace, not DNS, so the above
	is N/A.

	Regards,

	- Anil

Anil,

When I first tried to run the IP auto config with the minimum privs that 
you suggested, I got a UCX error something to the effect of insufficient
privs.  I went back and scanned the UCX release notes for required privs
and found a reference to obne functions requiring BYPASS and SYSPRV, so 
I added these privs to my process privledges.

Next time I did the auto config, it worked.

Merlin