Conference azur::mcc

Relative to the TS AM,  here's the latest information I have:

<<< NOTE WELL:  AVAILABILITY AND FUNCTIONALITY OF THE TS AM HAS
NOT BEEN ANNOUNCED YET.  THIS INFO IS COMPANY CONFIDENTIAL. >>>


   Here are the latest dates for the Terminal Server Access Module.  

     EFT Start                            1/14/91
     FRS:                                 6/10/91

   This includes support for two new terminal servers: the Puritan (POTS-
   Plain Old Terminal Server) server and Clearwater (DECserver 300 V2.0 -
   LAT/Telnet server).  Current plans have us tied to Clearwater.

   The TS AM V1.0 will provide most of the functionality provided by TSM.
   However,  several features have been deferred.
   Not planned to be implemented in V1.0 of DECmcc/TSAM are:

    1.  PASTHRU mode -  PASTHRU mode is a mode you can enter in TSM to 
        allow for direct communication with the server (ie, it is like
	NCP CONNECT.  The user may do a SPAWN NCP CONNECT from DECmcc).

    2.  Keyboard mapping - Keyboard mapping is a utility in TSM which 
        allows a user to modify files which provide translations for the
	keys on an 3270(IBM)-style terminal connected to a server. This 
	is only applicable to DECserver 500s, with the CXM software. 
	The DECserver 500 software includes the TSC (Terminal Server 
	Configurator) program, which does include the keyboard mapping
	utility, so the user will not loose the functionality, it just
	won't be available in TSAM.

    3.  Command procedures -  The current servers software kits contain
        TSM command procedures to set up the terminal servers/ports to
	perform certain functions (ie, to configure a port for a dial-in
	modem, or a printer, etc.)  There are no plans in place to 
	provide similar command procedures to run under DECmcc using
	TSAM.

   .-1    Thank you for entering that info Mark...
 
   .0  To answer your third question, yes, you will be able to 
       use the Terminal Server AM with the Iconic Map PM.

					Lynne Izbicki

    Who would we talk to about providing replacement funtionality for what
    the command files in TSM are used for? This is a key componant in TSM
    when you have a large base of servers to manage and need to deal with
    bringing replacement servers up with the correct characteristics
    quickly.
    
    s/rob

    RE .1 and .2  -- Thanks for the info.
    
    A final question -- when will the IFT version be available ?
    
    _adrian.
    

	Re .1

>>>	Scheduled FRS 6/91

	If the  TS  AM  is  an  async  release, then it can be released
	whenever it is  ready.    If  it is bundled with the BMS (Basic
	Management System), then it  must  wait  for  the  V1.2 release
	(planned  for Q1 FY92).   The  last  conversation  I  had  with
	product management was that it was  going  to  be  bundled with
	BMS.  I, personally, disagree with the  strategy  but will work
	with  product  management  and  marketing  to ensure the  right
	decision is made.
								JCE

   The Terminal Server AM will not be part of the Basic Management
   System; the decision has been made to ship asynchronously.  It
   makes more sense for TSAM to be tied to the terminal servers it
   supports, than to DECmcc releases.

   With regards to the command files to configure servers for certain
   applications; we realize that they are important, but that
   functionality has been traded off in favor of an earlier time
   to market.

				Lynne

438.1 states:

>    3.  Command procedures -  The current servers software kits contain
>        TSM command procedures to set up the terminal servers/ports to
>        perform certain functions (ie, to configure a port for a dial-in
>        modem, or a printer, etc.)  There are no plans in place to
>        provide similar command procedures to run under DECmcc using
>        TSAM.


IMHO, the TSM command procedures are a crucial component.  The above paragraph
indicates that "There are no plans in place . . .".  I trust that only applies
to the first release and not to subsequent releases.  As a customer,
the only reason I pruchased TSM was for this capability.  As a suggestion for
a future release, it would be nice if the TS AM could analyze the NVram and
build the configuration database instead of the user creating a configuration
for existing servers.

John

    re .-1
    
    Exactly. The actual need is to be able to capture current
    characteristics (read settings) of any or a set of servers and store
    it such that the server (or it's replacement) can easily be set up
    in the desired way with minimal effort and or errors.
    
    s/rob
    

    Better late than never.  I feel it would be a drastic mistake to have a
    TSM AM with out the command file functionality. The use of command file
    is the only!! reason most customers bought it the first place.  
    Without the command procedures at best you will have is a glorified NCP
    CONNECT NODE.  
    
    From One Who Has to Has to Support it.
    Steve Woestemeyer
    CSC/CS - NSU/LAT

   You can write and use command files with the Terminal Server AM...
   These command files, however, must contain DECmcc FCL commands, not
   TSM commands (server local-mode commands).

   What is not supplied with the Terminal Server AM V1.0 software is the 
   command files which are shipped with the server software, which contain 
   TSM commands for configuring ports for different applications.  Also, 
   we are not supplying any type of conversion utility to translate existing 
   TSM scripts into DECmcc scripts.  

   This decision has already been made for the first version of the product.
   The comments here will certainly be used as input to the product 
   requirements for future versions.

>>  Without the command procedures at best you will have is a glorified NCP
>>  CONNECT NODE.  

    Really??  What about all of the added-value of DECmcc?  What about the 
    ability to use other management modules modules such as the Alarms FM, 
    Historian FM, etc?   What about the Iconic Map interface?

Re.438.1

>>   This includes support for two new terminal servers: the Puritan (POTS-
>>   Plain Old Terminal Server) server and Clearwater (DECserver 300 V2.0 -
>>   LAT/Telnet server).  Current plans have us tied to Clearwater.

Does this mean currently the Terminal server AM is not supporting
the Puritan server (DECserver 90L)?  If so, are there any plans to
include it in future releases, and when?

thanks 
Lillian

    
    No, the Terminal Server AM does not currently support the DS90L.  It
    will in the future, but the schedule is not yet decided.
    
     - Linda