Conference azur::mcc

For terminal server futures, I would suggest contacting 

JONATHAN (MEMIT::) LEWANDOWSKI

For TSAM specific questions, you can also try

LAUREL (MOLAR::) NELSON

    I saw an intriguing entry in a recent notes entry about the DS900 being
    registered to TSAM as DS900_as_DS700.   This made me think about the
    possibility of a special name convention allowing a device to be
    registered using the -template- device type of some other entity, and
    not be expected to fully conform to all -expected- parameters.
    
    Is it possible to register a MUXserver 380, using the TSAM template for
    the MS300 ?   Perhaps the same sort of Syntax?  
    
    MCC>  REGISTER TERMINAL_SERVER .muxserver type = MS380_as_MS300 ...
    
    and would I be able to extract any meaningful data from this device. 
    My customer now uses the MS300's and MS380's in his network, and 
    the phone lines between sites rae notorious for having many CRC errors,
    so I use TSAM rules for polling LINK UTILIZATION, and errors on the
    300's.  The customer would love to have RULES set up for the MS380 as
    well.    Will this work, or should I not bother with a trip to the
    site to try it out ??
    
    Thanks;
    
    JR
    

>    I saw an intriguing entry in a recent notes entry about the DS900 being
>    registered to TSAM as DS900_as_DS700.   This made me think about the

The type name should be DS900TM_as_DS700 which is type code 17. This 
string is defined in the dictionary inside a constructed data type. 
MS380 is not in there and 'self-guessed' type names won't work.

However, out of curiosity, I did a string dump of the TSAM module and 
found "MS_380", "MS380", "MUXserver 380" and "MS3801ENG". So something 
is in the code. I guess you should be able to register it just as MS300 
and it would recognize it. I don't have an MS380 here so I can't try it.

Remember that you'll need the latest version (V1.0.4) for this to work 
at all!

*Robert

P.S.: Here is the data type definition for attribute TYPE:

CREATE ATTRIBUTE Type CODE 50
!       constructor_data_type
SET DEFINITION CODE 23 TYPE T -
        COUNT 1 -
        LENGTH 294 -
        DEFINED TRUE -
        USAGE ILV -
        VALUE -
( -
2="DS100", -
3="DS200", -
4="DS500", -
5="MS100", -
6="MS300", -
7="DS300", -
8="DS250", -
9="DS90L", -
10="Unsupported_type_10", -
11="DS90Lplus_as_DS90L", -
12="DS700", -
13="DS90TL", -
14="Unsupported_type_14", -
16="DS90M_as_DS90TL", -
17="DS900TM_as_DS700", -
18="Unsupported_type_18")

    Thanks for positive thoughts.  Your reply (-.1) mentioned:
    
    > Remember that you'll need the latest version (V1.0.4) for this to work
    > at all!
    
    What version of what code does this refer to.  Is this a revision of
    ROM, or FPROM, or HW in the MUXserver, or is it a reference to a
    specific version of TSM, or a Version of TSAM ??
    
    
    I tried (last week, while I was on the customer site) to register whole
    of the customers' TSM database, using the TSM_CONVERT program that
    comes with EMS023 on the CDROM.   The MS380 did not show up as a
    registered entity when I was done executing the .COM file produced.
    
    I tried to register the MS380  using "TYPE=MS300", but it failed, with
    some sort of unexpected data, or something.  I didn't write down the
    error.  I just recalled that it wasn't supported, and shrugged.
    
    If I need to re-compile a dictionary, or make some impossible-to-
    suport changes, then I would rather tell my customer that he can't
    manage the device yet.  And ask in this forum, when I might be able to
    tell my customer that he CAN manage it.
    
    Thanks for the help.
    
    JR
    

>                  -< Does Version V1.0.4 ship with EMS023 ?? >-

I was referring to Terminal Server AM V1.0.4 which is NOT in EMS023
(they still ship an older version). Just to be sure you get the right
version copy it from 

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

Don't get confused by the filenames (010); if in doubt look at the date
(23-JUL-1993). The kit is VMSINSTALable and will update the dictionary 
and help library (read: this may take a few hours).

*Robert

	Terminal Server AM V1.0.4 
	( ana/ima sys$library:mcc_ts_am.exe gives DECMCC V1.0.4 from 23-jul-93 )

	My customer tries to register a MUXserver 320 ( he has 10 MUXserver to
	manage )

MCC> REGIS TERM term_name ADDRESS=ether_add ,TYPE=MS300
	He get the message : 
	entity not fully registered...

On the iconicmap , when he "double click" into the terminal_server entity
he has child entities :
	LAT
	LINK ...
	STATION ...

But , if he "double click" into LINK ... or STATION ... he has the message :
	register server type MS300 does not match 
	the actual server type : Unsupported_type_14

If he registers the MUXserver 320 using type = Unsupported_type_14 there is no
error message but only LAT child entity is available .
    
     	Is there any workaround ? or TSAM will never supported MUX320,MUX380 ?
	Thanks for reply.
	Regards,
	JOcelyne