[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

4881.0. "TSAM upgrade v1.0.0-->v1.0.3 not working" by SPANKY::WALSH () Wed Apr 14 1993 15:13

    Upgrade of TSAM for v1.0.0 to v1.0.3 not working !!!
    
    I am running bms v1.2.3 on a Vaxstation 4000 model 60 w/ vms v5.5
    When I upgraded TSAM from v1.0.0 to v1.0.3 i had the same problem that
    was noted in note 4144 when the TSAM was upgraded from v1.0.0 to
    v1.0.2.  Also, the install went fine with the ivp succeeding.  
    
    Basically as noted in note 4144 when i run the mcc_ts_am_startup.com 
    the system hangs with the terminal server process never starting up.
    
    I have tried all that was suggested in note 4144.
    
    DIDN'T work.  Any ideas on this one???
    
    regards,
    
    mike walsh
    
    p.s. reason for upgrade was to allow customer partial support for
    management of his DECserver 90L+s (5) of them.
T.RTitleUserPersonal
Name		DateLines
4881.1TSAM upgrade problemCOMBAT::JONSSONTue Jun 01 1993 12:3811
I confronted the same problem as Mike after upgrading
bms from v1.2 to v1.3 and tsam from v1.0.0 to v1.0.3.

A colleague of Mike discovered that TSAM checks for a 
release date of 1994 on the TSM (!) point product. After
installing the TSM license, i could succesfully run the
mcc_ts_am_startup.com.


regards,
Lars Jonsson
4881.2 another : TSAM upgrade problemSWTHOM::NOBREJocelyne Nobre - CST FranceFri Jun 11 1993 12:1773
    My customer is running BMS  v1.2.3
    He is upgrading TSAM from v1.0.0 to v1.0.3 for DECserver 90 L+
    support.
	The installation works fine until :
    	
       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 running.
    DECmcc (V1.2.3)
    
 %MCC-I-ENRDUPLENTRY, enrollment successful; duplicate entries found and
    replaced
    
     MCC 0 TERMSERVER_AM
    AT  9-JUN-1993 18:19:41
    
    then it hangs 
    
    	after 16 hours he pressed CTRL C and had :
    The requested operation cannot be completed
    VMS Routine Error =
    %NONAME-W-NOMSG, Message number 00000000
    
        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.
    
    DECmcc (V1.2.3)
    
    MCC 0 TERMSERVER_AM
    AT 10-JUN-1993 09:53:57
    
    Test successful.
    
     DECmcc Terminal Server AM V1.0.0 Installation Successful
    
    Completing DECMCC TSAM Installation Verification Procedure
    
    Installation of MCCTSAM V1.0 completed at 09:53
    

 Every times he tries to start the product (MCC_TS_AM_STARTUP) 
  or a mcc command :
    mcc> enable mcc 0 termserver_am 
    he gets a  MCC_TS_AM_SRV.DMP  ( I have it ...)
 
  I check what it is suggested in #4144.5 :
     no  logical names mcc_ts_am*
    and SYS$LIBRARY:MCC_TS_AM.EXE 
    				image name: "MCC_TS_AM"
    				image file identification: "DECMCC V1.0-3"
    				link date/time:  7-APR-1993 16:59:47.98
    
    this seems correct.
    
    BUT I does not found where 
    
>    TSAM checks for a release date of 1994 on
>    the TSM (!) point product.
    
    I look for that in MCC_TS_AM_STARTUP.COM and KITINSTAL.COM files.
    
    Thanks in advance for help,
    Regards ,
    	JOcelyne.