T.R | Title | User | Personal Name | Date | Lines |
---|
353.1 | Not without private MIB(s). | TOOK::D_NELSON | Dave Nelson LKG1-3/A11 226-5358 | Thu Aug 26 1993 16:03 | 12 |
| RE: .0
Terminal Server specific (e.g. message codes) and LAT specific (e.g.
group codes) variables would require private MIBs, which we have not
yet implemented. Thus you can't expect HUBwtach to manage these
variables. You are then left with (a) Telnet remote console, (b) MOP
remote console, (c) TSM (VMS, MOP), or (d) TSAM (VMS, MCC).
Regards,
Dave
|
353.2 | customers want group code management... | GIDDAY::DRANSFIELD | Mike Dransfield, Sydney RSSG | Sun Aug 29 1993 09:01 | 7 |
| re: .1
Be aware that customer want to be able to manage group codes.
I was at DECUS in Adelaide this week and a couple of people
noticed this omission....so customers not only can , but DO expect
to be able to manage these things from HUBwatch and aren't real
excited by reasons why it might be difficult...
Mike
|
353.3 | Translate the "want" to $$$. | TOOK::D_NELSON | Dave Nelson LKG1-3/A11 226-5358 | Mon Aug 30 1993 13:49 | 13 |
| RE: .2
> ...and aren't real excited by reasons why it might be difficult...
It's not difficult. I didn't say it was. It's just a low priority
compared to other features on the product managers' list of things to
implement. (So now you know in which direction to complain...)
Regards,
Dave
|