| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 4303.1 | Partial answer... | 2582::CHRISB::BRIENEN | Network Management Applications! | Wed Dec 23 1992 15:16 | 21 |
| > Why does it take considarably longer to access servers using TSAM
> as compared with TSM ?
The Terminal Server AM "layers" on TSM.
Specifically, TS_AM uses TSM ("callable TSM") to communicate with
Terminal Servers.
TS_AM might be, via TSM, CONNECTING TO / DISCONNECTING FROM the
target Terminal Server with each mcc_call request (i.e. SHOW ALL ATTR
= multiple connect/disconnects).
Also, TS_AM parses the ascii text returned by TSM (/terminal server),
mapping this text into MCC attribute values (and into the management
model that TS_AM provides). It translates MCC directives (e.g. SET)
into TSM commands. It provides translation between real Terminal
Server identifiers and MCC ones (e.g., FullName).
Dave, correct me if I'm off base...
Chris
|
| 4303.2 | | TOOK::FONSECA | I heard it through the Grapevine... | Wed Dec 30 1992 13:00 | 22 |
| Thanks Chris, what Chris describes is correct. In fact one of the
things which makes TSAM so much slower than TSM is that it actually
must establish and break the connection with the terminal server
every time a single command is executed. Thus every time a SET or SHOW
is executed, the following is done:
1. USE SERVER XYZ
2. SHOW SERVER ! For TSAM's own internal use
3. SET PRIV ! If you have provided a password
<password>
4. The SET or SHOW requested
5. USE DIR
Thus, if you are going to do a getchar, or any continuous stream of
commands through TSAM, the results will not be as fast as bare-back
TSM.
This along with all of the other DECmcc oriented code makes TSAM slower
than you would like. I hope knowing this will help, I know that for
your customer (and others) this can be very frustrating.
-Dave
|
| 4303.3 | use both | PHDVAX::COMFORT | | Mon Jan 04 1993 13:17 | 17 |
|
For my part, I have been recommending both products for those customers
who need to make large scale changes against a large number of terminal
servers. If the customer can definitively say that the amount of
re-configuration is limited to say replacing a terminal server with a
new one, then they might get by with TSAM and some crafty scripting.
By this I mean that there are 255 characters on an MCC command line,
and I have have noticed that, in accordance with the previous
discussions, when one places many items in one set command line, things
process accordingly faster because of a single connect.
My main point is to present TSAM as a monitoring tool and TSM as the
management tool and I have had excellent success with this approach.
Regards,
Dave
|