[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

5371.0. "TSAM V1.0.3 requires TSM pak ??" by GIDDAY::CHONG (Andrew Chong - Sydney CSC ) Wed Jul 21 1993 23:44

	I have come across a customer installing TSAM V.1.0.3 where the
startup of TSAM (MCC_TS_AM_STARTUP) hangs  at line "ENABLE MCC 0 TERMSERVER_AM".

	When aborting the startup, it produced an process dump. Analysing the 
dump gives a clue to the problem.....

TLORD::MCCMGR> anal/proc MCC_TS_AM_SRV.DMP;3

Creating a subprocess
Condition signalled to take dump:
%LICENSE-F-NOAUTH, DEC TSM use is not authorized on this node
%LICENSE-F-NOAUTH, DEC TSM use is not authorized on this node
-LICENSE-F-NOLICENSE, no license is active for this software product
-LICENSE-F-NOLICENSE, no license is active for this software product
-LICENSE-I-SYSMGR
-LICENSE-I-SYSMGR
%DEBUG-I-CANTCREATEMAIN, could not create the debugger subprocess
%DEBUG-I-CANTCREATEMAIN, could not create the debugger subprocess
-LIB-F-NOCLI, no CLI present to perform function
-LIB-F-NOCLI, no CLI present to perform function
%DEBUG-I-SHRPRC, debugger will share user process
%DEBUG-I-SHRPRC, debugger will share user process

         VAX DEBUG Version V5.5-023

%DEBUG-I-NOLOCALS, image does not contain local symbols
%DEBUG-I-INITIAL, language is UNKNOWN, module set to SHARE$DEBUG

DBG>


This customer has BMS and TSAM paks loaded. It is not until TSM temporary pak is
installed and loaded that it started without a problem. 
Customer was on V1.0.0 of TSAM and was running fine without TSM pak.

I subsequently found a STARS article that describes the same problem 
" DECMCC-TSAM V1.0.3 installation problem (terminal serveraccess module) "
It says that  MCC_TS_AM_STARTUP.COM checks for correctly  installed TSM and 
DECMCC-EMS licenses.

This pose a problem for the customer as he does not have TSM nor EMS licenses.

Is there a different V1.0.3 TSAM kit that fix this problem ?

Andrew
T.RTitleUserPersonal
Name
DateLines
5371.1Do we loan,do we allowance??SIOG::ODRISCOLLStep to the Music ye HearThu Nov 25 1993 07:345
    My customer has just hit this issue also. How are people handling it
    commercially - ie the customer only wants BMS, we need to supply EMS -
    theres a 25k$ difference.
    
    Regards,
5371.2tsam V1.0.4 ....GIDDAY::CHONGAndrew Chong - Sydney CSC Mon Jun 06 1994 21:1821
It's been a long time since I encountered the problem. 
I post the solution here for completeness. 

TSAM V1.0.4 is supposed to have solved the problem....

extract from the release notes...

7.5.1  V1.0.3 DECMCC-TSAM License Bug Corrected

The V1.0.3 kit did not recognize the DECMCC-TSAM license as it should,  and
would  only work if the node TSAM is being run from has a DECMCC-EMS or TSM
version 2.0 license installed (earlier versions of  TSM  licenses  did  not
suffice).

The symptom for this problem will occured during the  installation.   After
the  majority  of  the installation is completed, the TSAM startup would be
run (if you have chosen to run the IVP).  The installation  would  hang  or
freeze in the middle of the TSAM startup.

This problem has been corrected with the V1.0.4 release.