V6R1 - If the Telnet server is not ended prior to the ending of subsystems, it might not automatically restart

I know someone who has a CL program in WRKJOBSCDE to perform these END*
commands at month-end. He meant to suspend this program but forgot,
leaving it scheduled.
On the next Sunday, it ran, making the system inaccessible.
And no one could contact him for many hours because he did not have his
cellphone with him
Sigh . . .

"System I i5/OS Memo to Users, Version 6 Release 1 (July 2012 Update":

ENDTCP before ENDSBS *ALL *IMMED
If the Telnet server is not ended prior to the ending of subsystems, it
might not automatically restart. To
circumvent this and other potential problems it is suggested that prior
to ENDSBS *ALL *IMMED these
steps be taken:
1. ENDTCPSVR *ALL
2. ENDHOSTSVR *ALL
3. Allow the commands to complete and the servers to end. If issuing the
commands from a CL
program include a DLYJOB DLY(300) to allow the commands to complete.
4. ENDTCP

"IBM i Memo to Users 7.1 (April 2012 Update)"
Backup and recovery changes
GO SAVE, GO RESTORE, GO LICPGM changes
In IBM i 7.1, the GO SAVE (options 21-23, 40), GO RESTORE (options
21-23, 40), and GO LICPGM
(option 40) menus were enhanced to end TCP before ending the subsystems.
Commands that are issued
as part of these options are:
v End TCP/IP Server (ENDTCPSVR)

End TCP/IP (ENDTCP)
To allow time for these commands to process, two Delay Job (DLYJOB)
commands are issued. A total of
10 minutes delay is added before the End Subsystem (ENDSBS) command is
issued.
SAVLIB and SAVCHGOBJ changes for library QUSRSYS
+++++++++++++