| Title: | DECmcc user notes file. Does not replace IPMT. |
| Notice: | Use IPMT for problems. Newsletter location in note 6187 |
| Moderator: | TAEC::BEROUD |
| Created: | Mon Aug 21 1989 |
| Last Modified: | Wed Jun 04 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 6497 |
| Total number of notes: | 27359 |
When doing an autoconfig of DECnet Phase IV nodes on a LAN, the tool
attempts comm with each node found in the seeds data base.
It spends approximately 2 minutes waiting for I assume a response.
During this time task MCC_STM_LSTNR is running in a tight loop using
all available cpu.
Why was this method used to wait for an interrupt which would allow
continuation of the process?
Also, is there any way to shorten the amount of time the process waits
for a timeout to occur?
Thanks,
Mark
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 4365.1 | DECnet sets the timeouts | FARMS::LYONS | Ahh, but fortunately, I have the key to escape reality. | Mon Jan 11 1993 12:34 | 4 |
To shorten the timeout, go into DECnet (NCP) and set the timeout you
would like. The utility just gets a "normal" decnet link, and hence
will use the timeouts and retries that any DECnet user would get for
a Connect Initiate (CI) packet.
| |||||
| 4365.2 | Thanks. | DPDMAI::DAVIES | Mark, SCA Area Network Consultant | Mon Jan 11 1993 14:38 | 8 |
I assume you are referring to the OUTGOING TIMER under the EXECUTOR.
I will give it a try.
Regards,
Mark
| |||||