[Info-vax] Abnormal DECNET proxy behaviour

[Marc Van Dyck]

Robert A. Brooks brought next idea :
> On 1/22/2021 12:10 PM, Marc Van Dyck wrote:
>> Answering to myself - in case anyone else would get into the same
>> problem.
>> 
>> The following incantation did the trick - don't ask me why/how.
>> 
>> $ MCR NCL SET SESSION CONTROL NAMING SEARCH PATH {}
>> $ MCR NCL FLUSH SESSION CONTROL NAMING CACHE ENTRY “*”
>> $ MCR AUTHORIZE REMOVE/PROXY NODE1.VMS.MYCOMPANY.COM::USER1
>> $ MCR NCL DO SYS$MANAGER:NET$SEARCHPATH_STARTUP.NCL
>> 
>> With all my thanks to VSI support.
>
> A caveat with that above process . . .
>
> When the naming search path is cleared, outgoing connections may fail due to 
> not being able to translate
> the target node’s name to an address so you will want to do this during off 
> or low usage hours.
> The process below should be pretty quick though.

Yes it is immediate. I tried it on a test system. I will chose a very
quiet moment to do the same in production. Most of our applications 
talk
directly to TCPIP anyway.

-- 
Marc Van Dyck