In 4.525 tcp3 will unload once all DP4 applications using it have terminated if it is loaded with the −noremain command tail. The tcp3 process may be removed using the UNIX kill command or by running the DP4 utility shutdown, or, assuming tcp3 was loaded under dbdaemon, by running dbdaemon -stop or killing dbdaemon.
If loaded in the foreground tcpmgr can be terminated by pressing Esc when there are no users logged on. If run as a background process using the −detach command tail or under dbdaemon, then the process(es) may be removed either using the UNIX kill command, or , assuming tcpmgr was loaded under dbdaemon, by running dbdaemon -stop, or killing dbdaemon). If clients still have active TCP connections open, they will generate a network error, Fail 7. If the main listening thread is killed, all other threads will terminate. If a thread which has been launched to service a particular client connection is killed, all other threads continue to operate normally. It may not be possible to identify which thread is which from a listing of the running threads, but if the -display_address command tail is used, the ps information may allow you to do so.
When tcpmgr threads are terminated they perform an orderly shutdown, logging off all database users. This does not happen if the UNIX command kill −9 is used. This command should not be used to close DP4 processes unless absolutely unavoidable.
There is no equivalent of the shut_tcp command supplied up to release 4.523
From 4.525 diagnostics produced by DP4 Networking programs are sent to stdout, and the programs no longer do their own diagnostic log management. If you want to collect diagnostics from DP4 network programs run them under dbdaemon, and enable error logging using errlog. See Diagnostics in the Guide to DP4 Configuration for more details.