| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 161.1 | see note 134 | KAJUN::NELSON | | Wed Feb 17 1993 13:07 | 9 |
| see note 134 in this conference for the DECmcc launch definition file.
For a more complete explanation
. note 4350 in NOTED::MCC
. Chapter 8 POLYCenter Network Manager V1.3 USE manual
...kjn
|
| 161.2 | Automatically done in VMSINSTAL (soon...) | SLINK::HOOD | Just add water | Wed Feb 17 1993 17:37 | 2 |
| In a subsequent release, the HUBwatch installation procedure will do all
the work automatically for MCC launching. Coming soon, but not yet.
|
| 161.3 | Now Working | MAIL::CLAYTON | Merlin Clayton DTN 445-7217 | Thu Feb 18 1993 10:08 | 21 |
| The problem with launching HUBwatch T1.1.8 was related to the method of
envoking HUBwatch from VMS.
The old way was "mcr hubwatch ....."
The new way is "WATCH /AGENT <agent_name>"
I made the necessary changes to the MCC_APPL_HUBWATCH.def procedure and the
launch from mcc now works.
The only problem I had was that I had to hard code the community name because
when I tried passing the variable it could not be found in the agent table.
This is most likely a problem with case sensitivity. Hubwatch also did not
like the format of the IP address, so I just eliminated it from the argument
string.
Maybe someone can shed some light on these issues.
Thanks.
Merlin
|