Conference azur::mcc

    I just verified note 3.197. It tells no dictionary update is needed if
    v1.0.0 was already installed.
    Any harm if the dictionary was updated twice (first with v1.0.0 and
    second with v1.0.2)?
    
    -Geert-
    

    As test I've installed TSAM v1.0.2 on my station running BMS v1.2.0.
    I've also done an update of the dictionary with exactly the same
    messages as the other installation. The IVP worked fine and after
    the reboot TSAM started normally.
    So I think there's a problem with the combination of BMS 1.2.3 and TSAM
    1.0.2.
    Is there a way to deinstall BMS v1.2.3 and go back to v1.2?
    
    -Geert-

I'd be very surprised if it was BMS V1.2.3 which is causing your problems
with TSAM.  (Of course I have not tried V1.2.3, so I am not absolutely
sure.)

If you saw errors during the dictionary update which were not documented
in the release notes, there may be cause for concern, since I think I
included all of the commonly seen non-problem errors in my example.  If
you have a log still of that installation, please mail it to me or post it here
for me to look at.

I've seen instances where if the MCC_TS_AM_STARTUP is run from one account,
and then run from another account, two seperate MCC_TS_AM_SRV processes get
started up, which could cause problems.  As you have prossibly noted, the
startup spawns a command to kill the previous process.  The ENABLE command
which it then executes requires some privileges.  If the account does not have
enough quota to spawn one process (unlikely) I don't know what would happen.

If you go into FCL and type
MCC> DISABLE MCC 0 TERMSERVER_AM ABORT TRUE

and then exit back to the dollar sign, the MCC_TS_AM_SRV process should no
longer be there, and there should not be any logicals begining with MCC_TS_AM*
If the process is still there, stop it.  If the logicals are still there,
deassign them, then SET VERIFY and execute the MCC_TS_AM_STARTUP again.
Keep a log of it, and send it to me if it hangs.

Regards,

Dave

Hello Dave,
    
    Below you find the part of the installation that was different with
    the example of the release notes. The difference are the warnings.
    
Processing file SYS$COMMON:[MCC]MCC_CIRCUIT_AM.HELP
Processing file SYS$COMMON:[MCC]MCC_COLLECTION_AM.HELP
Processing file SYS$COMMON:[MCC]MCC_CONC_AM.HELP
Processing file SYS$COMMON:[MCC]MCC_DNA4_AM.HELP
Processing file SYS$COMMON:[MCC]MCC_DNA5AM_HELP.HELP
Processing file SYS$COMMON:[MCC]MCC_DOMAIN_FM.HELP
Processing file SYS$COMMON:[MCC]MCC_ENET_AM.HELP
Processing file SYS$COMMON:[MCC]MCC_EXPORTER_HELP.HELP
Processing file SYS$COMMON:[MCC]MCC_FDDI_AM.HELP
Processing file SYS$COMMON:[MCC]MCC_FDDI_FM.HELP
Processing file SYS$COMMON:[MCC]MCC_GENERAL_HELP.HELP
Processing file SYS$COMMON:[MCC]MCC_HISTORIAN_HELP.HELP
Processing file SYS$COMMON:[MCC]MCC_KERNEL_AM.HELP
Processing file SYS$COMMON:[MCC]MCC_NOTIFICATION_FM.HELP
Processing file SYS$COMMON:[MCC]MCC_PA_BRIDGE_FM.HELP
Processing file SYS$COMMON:[MCC]MCC_PA_FM.HELP
Warning - Duplicate Key: 2PAPA
Warning - Duplicate Key: 2PAPAzCHAR
Warning - Duplicate Key: 2PAPAzCHARzCOMPONENTzIDENTIFICATION
Warning - Duplicate Key: 2PAPAzCHARzCOMPONENTzVERSION
Warning - Duplicate Key: 2PAPAzSHOW
Warning - Duplicate Key: 2PAPAzSHOWzCHAR
Warning - Duplicate Key: 2PAPAzTEST
Warning - Duplicate Key: 2PAPAzTESTzEXAMPLES
Processing file SYS$COMMON:[MCC]MCC_STM_FM.HELP
Processing file SYS$COMMON:[MCC]MCC_TCPIP_AM.HELP
Processing file SYS$COMMON:[MCC]MCC_TS_AM.HELP
Sorting character cell help topics.
Sorting windows help topics.
Verifying hierarchy...

    -Geert-
    

    
    After reading the release notes and 'known problem'-solutions of the
    TSAM AM v1.0.2 a bell started to ring...
    These documents told me about the creation of 2 mailboxes instead of 1
    to solve some performance problems and a reply from Dave on this note
    (.3) told me to investigate the logicals beginning with mcc_ts_am*.
    When I did a show logical mcc_ts_am*, I found 3 mailboxes (v1.0.3?).
    
    		MCC_TS_AM_SRV_MBX
    		MCC_TS_AM_USR_MBX
    		MCC_TS_AM_MBX
    
    So I presumed there was one mailbox to much (the last one) and was
    created by an v1.0.0 TSAM image. I investigated all executables and
    found in SYS$LIBRARY the MCC_TS_AM.EXE with a image version 1.0.0 and
    a file version of 3. On my working system it was version 1.0.2.
    Apparently the installation procedure of TSAM v1.0.2 assumes all
    TSAM files have a file version of 1 and makes all new images file
    version = 2. Because version 3 existed the installation purged the new
    executable. 
    After I extracted this image from the kit, TSAM started normally and
    worked ok.
    Please note that this kit was installed at a customer site to solve
    some problems with the performance of MCC which manages a network
    of DECnet nodes, bridges and terminal servers. The new kit didn't
    solve the problems. We now found that the user account of DECmcc on
    that system runned out of BYTLM and needed to increase it from 64000
    to 100000. We found a use of over 70000 Bytlm! Maybe the installation
    and/or release notes need be updated if DECmcc is used with TSAM and
    ELM AM's to specify this quota as minimum.
    
    -Geert-

RE: 4144.4  BACHUS::FOLENS
    Title:  Installation log

> Processing file SYS$COMMON:[MCC]MCC_PA_BRIDGE_FM.HELP
> Processing file SYS$COMMON:[MCC]MCC_PA_FM.HELP
> Warning - Duplicate Key: 2PAPA
> Warning - Duplicate Key: 2PAPAzCHAR
> Warning - Duplicate Key: 2PAPAzCHARzCOMPONENTzIDENTIFICATION
> Warning - Duplicate Key: 2PAPAzCHARzCOMPONENTzVERSION

The above messages are caused by duplicate keys in the two PA Help files.
The messages are "harmless", and should actually be documented in the
ELM Release Notes.

We may be able to eliminate the messages by adding additional code to the
ELM installation procedure (but probably not for V1.3).

					Chris Brienen

Geert-

I'm glad to hear that you found out what was causing your immediate
TSAM problem.  Although your explaination for how you got an incorrect
image version on your system sounds plausible, I just can't believe
that VMSinstal would function that way when copying files during an
installation.  The TSAM install does the same thing that all installs
do when placing images.  If what you described  actually did happen,
it would be impossible to reliably install new versions of any software
using VMSinstal.

As for not having your performance problems solved with this new version,
I bow my head.  This has been the number one complaint since before
TSAM went to ship.

-Dave