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

[John E. Malmberg]

On 1/22/2013 8:50 AM, Jan-Erik Soderholm wrote:
>
> 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.

The last time I did this stuff with TNA devices was over a decade ago.

Back then, if the network connection to the TNAnnn: port through reverse 
telnet was lost, the only way to get that TNAnnn: port working again was 
to delete it and then recreated it.

But there probably is no reason to delete the TNA ports as part of the 
system shutdown.  They will get deleted.

One configuration error I have seen is to put application and layered 
product shutdown commands in syshutdwn.com.

By the the time syshutdwn.com is run, a lot of VMS is already down, so 
there is not enough left to run the commands.  This can cause hangs and 
delay the shutdown.

About the only thing I put in syshutdwn.com is commands to dismount 
local disks from other nodes in the cluster so that they do not go into 
mount verify timeout.

Application shutdowns should be run before invoking the shutdown.com.


I had to fix one set of systems where the person set up syshutdwn.com to 
call sys$system:shutdown.com and was using syshutdwn.com to start the 
shutdown procedure.

Regards,
-John
wb8tyw at qsl.network
Personal Opinion Only