[Info-vax] A 5 minutes hang during early stage of a shutdown.

[Jan-Erik Soderholm]

Stephen Hoffman wrote 2013-01-22 15:31:
> On 2013-01-22 13:50:28 +0000, Jan-Erik Soderholm said:
>
>> OK, I guess that is simply defining SHUTDOWN$VERIFY, right?
>
> Edit the file(s) involved and stick the proverbial SET VERIFY at the top,
> if you have to.  Revert when done.  This is VMS and not rocket science,
> after all.
>
>>> Sort out the particular trigger for the mutex, as those can cause various
>>> secondary problems.  <http://labs.hoffmanlabs.com/node/231>
>>
>> This has been "up" in at least one thread before. I never menaged
>> to find any information. I'm today confident that this happens
>> if one try to run "telnet delete" or "telnet create" against
>> a TNA device that is already in "waiting for delete".
>>
>> After a "telnet delete", it takes 10-15 seconds before the TNA
>> device is removed.
>
> Confidence is not equivalent to a reproducer, and a reproducer will usually
> gain the attention of support folks.  This given it is much harder to deny
> there's an issue when you are handed a reproducer, and it's much easier to
> test a fix with a reproducer.  Whether you get anywhere with that
> reproducer is another matter and another discussion — the (mis)behavior
> demonstrated by the reproducer could still be declared a "feature" and not
> a "bug", for instance.
>
> If you're doing a whole lot of that and OpenVMS and TCP/IP aren't reacting
> quickly enough or aren't reacting appropriately enough — and HP support
> isn't providing you with a solution sufficient for your needs — then write
> some tools to manage and allocate your application TN device access yourself.
>

Of course. :-)

Earlier, before TCPIP, the LTA ports was created at boot-time and
never re-created. I guess that they (before me) saw some troubles
and decided to add port re-creation when the COM files was
ported from LAT to telnet.

Now, I'm not sure that this is needed. I have to run more
tests/simulations with restarting terminal servers and
use the /timeout=(noidle,recon=hh:mm:ss) switch in the
telnet create command and see what happens.

Well, never mind. I just thought some technical content
could be of some amusement...

Jan-Erik.


>
> ps: Standard caveat whenever mixing Internet discussions of clustering and
> DECnet in the same posting or same IRC chat: DECnet is not the
> underpinnings of clustering. DECnet is not related to clustering.
> Clustering does not use DECnet.

Yes, you've mentioned this several times.

I have not mentioned clustering.
We do not run any cluster.

FWIW, I have never managed a VMS cluster.

Jan-Erik.