| Thanks Al,
I'll fix the EZ device section.
>I should say that I was able to start the listener, however it
>did fail on a SYS$QIO return. This was a small private Ethernet
>segment with no bridges. Sorry, but I'm not on that system.
>
>If needed, I can try again and get more detail.
>
>In addition, it appears that the first time this procedure is run, if
>it does not find the datafile containing the device name,
>MCC_STM_LISTENER_NI.DAT, the procedure fails.
You need to select choice 1 from the listener menu
to assign the ethernet port. This choice
will create the file MCC_STM_LISTENER_NI.DAT if it doesn't exist. Then
you can start the listener with choice 3. See page 5-10 of the
Autoconfiguration and Autotopology Use Guide for details on how to use
the STM listener.
As an aside. Why do you want to run this listener on a network with no
bridges? It isn't going to find anything.
Bob
|
| Bob,
My curiosity was peaked more than anything. I had quickly installed the
software on my local systems and was helping someone else at another location
to prepare for a DECmcc demo.
While this site had no bridges, I had noticed a few anomolies and wanted to
experiment a little further while at that site. Also a good chance to see if
the software would break, as it might, at a customer site in which no bridges
existed, or none were available for what ever reason....broken line/wire......
whatever.
I've tried to re-create the first error that I saw when I first ran the utility
from the iconic PM, but can't. Perhaps it was my error that I thought the
data file containing the ethernet device could not be created.
Have another idea though and would like some general comment on same so I'll
enter another note.
Regards,
Al
|