Conference azur::mcc

    I'm guessing you have an old dispatch table around.  Try this:

    $ dir mcc_system:mcc_dispatch_table.dat

    If you have one in MCC_SPECIFIC and one in MCC_COMMON, you probably
    want to delete the one in MCC_SPECIFIC.

If the suggestion in reply .1 is not the situation, look back further
in your installation log for other errors.  (In the section which
builds the TSAM information in to the dictionary.)

-Dave

I checked the dispatch file per .1 and it only shows up in sys$common.

As for .2's suggestion, here's the history of this installation:

1. Tried to install T1.2 a few weeks ago.  I was running the install from a 
PC at the same time as MCC was running on the workstation.  I recall that 
there were errors in adding the TSAM information to the dictionary, but I 
can't specifically remember what they were.  My conclusion at the time was 
that there was some sort of access conflict between the running MCC system 
and the TSAM installation procedure (does that sound possible?).

2. The next day I stopped the MCC processes on the workstation and reran 
the installation.  This time it got to the IVP and had the problem 
described in the base note.

3. In the mean time the SSB version of TSAM arrived, so I tried to install 
it, thinking the maybe the problem had something to do with TSAM FT and MCC 
SSB incompatibilities.  NOT!

What should my next step be?

Thanks in advance,

Rick C

The fact that DECmcc processes were up and running should not have
adversely affected the original installation.

You're probably not going to be happy with this answer, but based on not knowing
what the original dictionary update error was, I'm inclined to suggest
that you re-install the original DECmcc dictionary, and start over with the TSAM
installation.  The dictionary is still a fragile piece, and if your original
TSAM install corrupted it, further TSAM installs will not fix it.

If you have installed many AMs, that means a lot of work.  Before doing that,
I would very much like to see any one (or all) of the three instalation logs.
In interest of space saving, and other notes readers, please mail them to me
instead of posting them in the notesfile.  If you don't have any logs,
it is time you started doing a SET HOST 0/LOG whenever you do an installation.
It is very easy to miss some important error on these long installations.
KITINSTALs are not perfect in catching or stopping when something wrong happens.

I even have a little one-line command file which searches for errors that
works great, this finds all VMS-format error, fatal, and warning messages:

$ search 'p1 "-E-","-F-",-W-"

used like so:

$ @err.com foo.log

-Dave

>>> You're probably not going to be happy with this answer

What would make you think that!

>>> The dictionary is still a fragile piece, and if your original
TSAM install corrupted it, further TSAM installs will not fix it.

Just what I wanted to hear 

>>> If you have installed many AMs, that means a lot of work.

Will my customer loose their domains?  Do I need to specifically delete the 
dictionary or any other files?

>>> I would very much like to see any one (or all) of the three instalation logs.

Dream on ;-)

>>> It is time you started doing a SET HOST 0/LOG whenever you do an installation.

Count on it!

>>> I even have a little one-line command file which searches for errors that
>>> works great, this finds all VMS-format error, fatal, and warning messages:
>>>
>>> $ search 'p1 "-E-","-F-",-W-"
>>> 
>>> used like so:
>>>
>>> $ @err.com foo.log

Is this procedure sufficiently tested?  I don't want to hang the machine...blow it 
up maybe!

Thanks in advance,

Rick 'jagoff' C

Rick-

If you re-instal DECmcc, your customer will not loose their domains
if you are using DECdns as your namespace.  If you are using the local
MIR option, there are some files you need to make copies of, I'm not sure I know
what their names are, so maybe another noter or the CSC can help you there.

Good luck...

-Dave

Hello,

	A customer had the problem referenced in .0, exactly running the IVP,
	and it has been reported to us. 

	The engineer who took the call, saw this note and didn't get any 
	clear vision of how solve it and also he confused the customer.
	I don't know if the problem was the same in both cases, but the
	symptoms are similar.
 
	I'm writing this reply because I think could be interesting for
	other people in the same situation, to see the solution in our case.

	As I said,the error running the IVP was the same, but the customer
	also get an error installing the TSAM. The error was a license check
	error. The license problem is the known problem of the TSAM's SSB 
	release when checking the 'DECmcc EMS' license.

	The workaround is: 1) Temporal license for DECmcc TSAM or better 
	2) the new TSAM's kit.

	Jose Ignacio.
-------------------------------------------------------------------------------	

...
%VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories ...

   Beginning DECMCC TSAM Post Installation Procedure ...	


   Completing DECMCC TSAM Post Installation Procedure ...


	The startup procedure for the DECmcc Terminal Server
		 Access Module V1.0.0 is now runnning.

DECmcc (V1.2.0)

%MCC-E-LMF_FAILED, license check failed
%MCC-E-NOTFOUND, unsupported combination of verb, entity, partition

	The startup procedure for the DECmcc Terminal Server
		 Access Module V1.0.0 is now ending.

   Beginning DECMCC TSAM Installation Verification Procedure ...	

   The IVP for the DECmcc Terminal Server AM will now be run.


   Completing DECMCC TSAM Post Installation Procedure ...

DECmcc (V1.2.0)

%MCC-E-NOTFOUND, unsupported combination of verb, entity, partition
%MCC-E-NOTFOUND, unsupported combination of verb, entity, partition

   DECmcc Terminal Server AM V1.0.0 Installation Failed

%MCC-F-FAILED, fatal DECmcc error

...
    

Jose-

Thanks for the note.  The EMS/TSAM license problem was discovered several weeks
ago, and we have created a fix for it which you will have to get from the
CSC.  (I believe at least one other AM in the EMS kit has the same problem...)

-Dave

For internal user, see note 3.204 for the fix to the EMS kit.