Conference azur::mcc

712.0. "TSAM IFT on BMS V1.1 - Install Problem" by ZPOVC::RAMARAJ () Tue Feb 12 1991 03:24

Hi,

I had DECmcc BMS 1.1 EFT, SNMP, FDA and TSAM IFT all installed running fine.
With V1.1 Pre-FCS, I installed it.  Then I reinstalled SNMP and FDA.  
They are all working fine now again.  But when I tried to reinstall the
TSAM there was a fatal error.  I have appended the last part of the log 
file below.

Could someone shed some light on it?


Log File
--------
....
....
Cleaning up intermediate files. 
 
 
        The startup procedure for the DECmcc Terminal Server
                 Access Module V1.0 is now running.
 
DECmcc (V1.1.0)
%MCC-I-REPOSEXIST, repository already exists
MCC 0 TERMSERVER_AM 
AT 12-FEB-1991 04:48:26 
The requested operation cannot be completed
                      VMS Routine Error = 
%SYSTEM-F-DUPLNAM, duplicate name

 
 
        The startup procedure for the DECmcc Terminal Server
                 Access Module V1.0 is now ending.
 
                                                               
   Completing DECmcc TSAM Post Installation Procedure ...      
                                                               
                                                               
   Beginning DECmcc TSAM Installation Verification Procedure   
                                                               
 
 
   The IVP for the DECmcc Terminal Server AM will now be run. 
 
DECmcc (V1.1.0)
%MCC-E-NOTFOUND,  unsupported combination of verb, entity, partition
%MCC-E-NOTFOUND,  unsupported combination of verb, entity, partition
                                                               
   *********************************************************   
                                                               
   Fatal DECmcc Terminal Server Access Module T1.0-0 event                    
   occurred during installation                                
                                                               
   *********************************************************   
                                                               
%VMSINSTAL-E-IVPFAIL, The IVP for MCCTSAM V1.0 has failed.

	VMSINSTAL procedure done at 04:48

--------

I tried the MCC_TSAM_IVP, and it gave the same error

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




Raj
SWS Singapore

    This may be an upward compatibility problem with the V1.1 MCS kit.
    One modification we made was to change the message 
%MCC-E-REPOSEXIST, repository already exists
    to be an Informational severity in order to put the message in line with
    the SRM.  This (seemingly innocent) change may have caused TSAM not to
    catch the new message severity, and go down an error path.
    
    We will be investigating this problem further.
    
    -Matt.

   There are actually two problems here.  The first is with the new
   informational message MCC-I-REPOSEXIST.  The Terminal Server AM 
   attempts to create it's MIRs upon enrollment, and displays the 
   informational message.  I am not sure if the enrollment completes
   correctly, and will be investigating this today.

   The second problem is with the cannot commplete, SYSTEM-F-DUPLNAM.
   This is resulting from the directive in the Terminal Server AM
   startup procedure: "ENABLE MCC 0 TERMSERVER_AM", and is resulting
   because the Terminal Server AM was re-installed without first 
   disabling the Terminal Server AM.

   The Terminal Server AM requires a detached server process for managing
   servers.  The ENABLE MCC 0 TERMSERVER_AM directive intializes the
   Terminal Server AM, and starts up this server process.  The DISABLE 
   MCC 0 TERMSERVER_AM directive shuts down the detached process, and
   disables Terminal Server AM commands.

   I am not sure why the MCC_TSAM_IVP gives the dispatch table errors.
   If the Terminal Server AM was not enrolled, I would also expect 
   to have seen this message on the ENABLE directive.  What you should
   do is look on your system for the process MCC_TS_AM_SRV.  If you
   find it, delete it (STOP/ID).  After you've stopped the server 
   process (or, if you didn't see it on the system), then try to enable 
   the terminal server AM with the command: ENABLE MCC 0 TERMSERVER_AM. 

					Lynne 

    Is there a resolution to this problem? I want to upgrade BMS to pre-SSB
    but need to have TSAM working for a demo next week. 
    
    Thanks,
    
    Liz
    

    Liz -

    We are working on building and testing a new kit.  It will be announced
    in note 3 when it is available (most likely today or tomorrow...)

						Lynne

    
    
     The updated kit is available.  Please see note 3.55