[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

5777.0. "MCC-TSAM V1.0.3 requires TSM license." by COPCLU::EBC () Wed Dec 08 1993 05:07

    I installed V1.0.3 of TSAM yesterday.
    The startup procedure hung on the "enable mcc 0 termserver_am" command.
    Analyzing the process dump of MCC_TS_AM_SRV.EXE, I found this was
    caused by the new version requiring a TSM (not TSAM!) license.
    Registring a TSM license solved the problem.
    There must be a slight mis-understanding here.
    
    regards,
    Erik B. Christensen
    MCS-COMMS
    Copenhagen

T.R Title User Personal
Name Date Lines

5777.1 Known problem, fixed in V1.0.4 BIKINI::KRAUSE European NewProductEngineer for MCC Thu Dec 09 1993 04:24 114

T.R	Title	User	Personal Name	Date	Lines
5777.1	Known problem, fixed in V1.0.4	BIKINI::KRAUSE	European NewProductEngineer for MCC	`Thu Dec 09 1993 04:24`	114
	Known problem. TSAM V1.0.4 fixes it (see README below). You can copy the kit from my distribution point: BIKINI::MCC_DISK:[BMS013.VMS.PATCH]MCCTSAM010.* Don't get confused by the - never changing - filename. Watch the date! TSAM V1.0.4 is 23-JUL-1993. *Robert ---------------------- DECMCC TERMINAL SERVER ACCESS MODULE V1.0.4 July 23, 1993 7.5 INFORMATION FOR VERSION 1.0.4 UPDATE Several bugs were introduced with the V1.0.3 update release which were not found in the earlier releases. 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. 7.5.2 SET PORT N INITIAL FORW/BACK SWITCH On DS500 Crash Fixed As of V1.0.3, setting this attribute could cause the MCC_TS_AM_SRV process to crash. This has been corrected with this release. 7.5.3 Circuit Search List Problem Corrected As of V1.0.3, if a terminal server had a list of service circuits associated with it, and the first circuit was not avaialble on the node TSAM was being run from, the command might fail. This has been corrected with this release. 7.5.4 DECnet Service Password Problem A problem existsin the TSAM and DECnet4 AM modules which prevents the maintanence password for the terminal server from being propigated correctly to the DECnet database. Although latent support for a fix to this problem has been included in this release of TSAM, it will require a change to the DECnet4 AM to allow this corection to work. For now there is a workaround if you depend on the password in the DECnet database to match the maintanence key and password stored in the server. This work around has not been extensively tested, and it is not fully understood why it works. 1. Pick 8 hex characters which will be the unique portion of the final 16 character password. These 8 characters will be the first part of the password. 2. Take the last two characters and repeat them again. Now you will have the first 10 characters of the final password. 3. Add the chacters '595352' to the end of the above string. This is your final password to be used both from TSAM and NCP. So for example, 1. Pick any hex stirng for the first eight chacters (say '123456AB'). 2. Then take the last two characters and use them again, so '123456AB' + 'AB' 3. Then add the characters '595352', so '123456ABAB' + '595352' gives the final password of '123456ABAB595352' 7.5.5 ECO Portion Of Version Of Server Software Incorrect The last portion of the software version was hard-coded to '0', so that even if the terminal server was running V1.2.3, TSAM would display V1.2.0. This has been corrected. 7.5.6 'Software' Attribute Name Changed To 'Software Name' The previous name of this attribute may have caused ambiguity in the dictionary (with other attributes whose first word was 'Software') This correction should correct that problem. 7.5.7 Counters Partition For System Entity Removed There were no counters for the System entity, so this partition has been removed.

Known problem. TSAM V1.0.4 fixes it (see README below). You can copy the
kit from my distribution point: 

	BIKINI::MCC_DISK:[BMS013.VMS.PATCH]MCCTSAM010.*

Don't get confused by the - never changing - filename. Watch the date! 
TSAM V1.0.4 is 23-JUL-1993.

*Robert

----------------------

                  DECMCC TERMINAL SERVER ACCESS MODULE V1.0.4
                                 July 23, 1993



7.5  INFORMATION FOR VERSION 1.0.4 UPDATE

Several bugs were introduced with the V1.0.3 update release which were  not
found in the earlier releases.



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.



7.5.2  SET PORT N INITIAL FORW/BACK SWITCH On DS500 Crash Fixed

As of V1.0.3, setting this attribute could cause the MCC_TS_AM_SRV  process
to crash.  This has been corrected with this release.



7.5.3  Circuit Search List Problem Corrected

As of V1.0.3,  if  a  terminal  server  had  a  list  of  service  circuits
associated  with  it,  and  the first circuit was not avaialble on the node
TSAM was being run from, the command might fail.  This has  been  corrected
with this release.



7.5.4  DECnet Service Password Problem

A problem existsin the TSAM and  DECnet4  AM  modules  which  prevents  the
maintanence   password  for  the  terminal  server  from  being  propigated
correctly to the DECnet database.  Although latent support  for  a  fix  to
this  problem  has been included in this release of TSAM, it will require a
change to the DECnet4 AM to allow this corection to work.

For now there is a workaround if you depend on the password in  the  DECnet
database  to  match  the maintanence key and password stored in the server.
This work around has not been extensively  tested,  and  it  is  not  fully
understood why it works.

     1.  Pick 8 hex characters which will be  the  unique  portion  of  the
         final 16 character password.  These 8 characters will be the first
         part of the password.

     2.  Take the last two characters and repeat them again.  Now you  will
         have the first 10 characters of the final password.

     3.  Add the chacters '595352' to the end of the above string.  This is
         your final password to be used both from TSAM and NCP.


So for example,

     1.  Pick any hex stirng for the first eight chacters (say '123456AB').

     2.  Then  take  the  last  two  characters  and  use  them  again,  so
         '123456AB' + 'AB'

     3.  Then add the characters '595352', so '123456ABAB' + '595352' gives
         the final password of '123456ABAB595352'




7.5.5  ECO Portion Of Version Of Server Software Incorrect

The last portion of the software version was hard-coded  to  '0',  so  that
even  if the terminal server was running V1.2.3, TSAM would display V1.2.0.
This has been corrected.



7.5.6  'Software' Attribute Name Changed To 'Software Name'

The previous name of this  attribute  may  have  caused  ambiguity  in  the
dictionary  (with  other  attributes  whose first word was 'Software') This
correction should correct that problem.



7.5.7  Counters Partition For System Entity Removed

There were no counters for the System entity, so this  partition  has  been
removed.