[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

5163.0. "QUESTION - MCC Terminal Server AM" by ZPOVC::VENKAT () Tue Jun 08 1993 03:13

Hello !

I need a small input. What is the latest version of the TSAM for MCC
V1.3 ? Where in Network it is located ? I beleive the earlier versions of TSAM 
used to have lot of problems, is the new version reliable ?

We are planning to takeover CGM network management and the customer is using a 
lot of Mux Servers and Muxs.

Thanks for your help.

Venkat
Asia Pacific Networks Operations Center,
Singapore.

    
    
    
    
             
T.RTitleUserPersonal
Name
DateLines
5163.1FRAIS::ORCHIS::MAASSInformation, that's all I need...Fri Jun 18 1993 19:097
Hi Venkat,

the actual version is still V1.0, as far as I know.



Josch
5163.2V1.0.2 at least for muxserversGIDDAY::DRANSFIELDMike Dransfield, Sydney RSSGSat Jun 19 1993 08:259
    re: .1
    For MUXservers you need V1.0.2 at least.
    Beware that the EMS 2.3 kit contains the older V1.0.0 so you can have
    problems if you upgrade from EMS 2.2 (you end up downgrading TSAM)
    
    I have seen a couple of notes talking about a V1.0.3 although I have
    not seen an announcement for it yet(..but that could be just me)
    
    Mike
5163.3Latest version of TSAM is V1.0.3CUJO::HILLDan Hill-Net.Mgt.-Customer ResidentWed Jun 23 1993 02:237
    Dave Fonseca produced V1.0.3 of TSAM to support DECserver 90L+,
    Muxserver-???, fix bugs, etc.
    
    The location of this kit is somewhere in this notes file.  Contact
    Laurel Nelson or Dave Fonseca for more info. 
    
    -DAN
5163.4Straight from the horse's mouthTOOK::FONSECAI heard it through the Grapevine...Wed Jun 23 1993 17:2744
All versions of TSAM support the MUX 100 and 300 platforms.

Although the V1.0.3 version will allow users to partially manage the DS90l+,
MS380, MS320, and several other platforms not perviously manageable,
it is incorrect and fraudulent to sell TSAM (or EMS) to a customer based
on that support.  The SPD does not mention any of those products,
and I am not going to fix any problems related to those platforms.
They were not tested, and I know of several limitations.

On the other hand if you have a customer who *already* has TSAM and/or EMS,
with one of those platforms, this may make them happy to have
this previously unavailable support.

The latest version of TSAM is V1.0.3.  It was never announced in
note 3.* as previous updates were.  I will be back fixing several
bugs in TSAM and TSM for the next two weeks, and noticed this note,
I don't normally follow this notesfile anymore.  Don't call me, don't
mail me, call the CSC with your TSAM problems.  That is what they are
there for.

I'll place a pointer to the new update when it becomes available,
V1.0.3 has been found to have a bug in its licence checking,
in that it hangs during startup (while enabling the MCC_TS_AM_SRV process)
for customers who have the DECMCC-TSAM license, and not DECMCC-EMS or TSM V2.0.
By the time I'd discovered there was no pointer to the V1.0.3 kit in note
3.* (thought someone else was going to do it...), I knew about this bug,
so I decided not to advertise the kit.

If you are desperate for the kit anyway, here is the pointer:

Directory TOOK""::DSV$KITS$:[SAVESETS.TSAM.V103]

00_V103.READ_ME;1         6
MCCTSAM010.A;10         306
MCCTSAM010.B;11        9612
MCCTSAM010.C;10        5274
MCCTSAM010.RELEASE_NOTES;204
                        127

Total of 5 files, 15325 blocks.

Good luck!

Dave