To start the SNTP / NTP / Daytime server, which is a method for keeping all of your PC's set to the AS/400's time, simply run

STRTCPSVR *INETD The config file is; /QIBM/UserData/OS400/inetd/inetd.conf

Keep in mind that;

Unlike most TCP/IP servers, the INETD server does not provide one single service to clients. Instead, it provides a variety of miscellaneous services that administrators can customize. For that reason, the INETD server is sometimes called "the super server". The INETD server has the following built-in services:  time  daytime  echo  discard  chargen These services are supported for both TCP and UDP. For UDP, the echo, time, daytime, and chargen services receive UDP packets, then send the packets back to the originator. The echo server echoes back packets that it receives, the time and daytime servers generate the time in a specific format and sends it back, and the chargen server generates a packet of printable ASCII characters and sends it back. The nature of these UDP services makes a system vulnerable to a denial of service attack. For example, assume that you have two AS/400 systems: SYSTEMA and SYSTEMB. A malicious programmer could forge the IP header and the UDP header with a source address of SYSTEMA and a UDP port number of the time server. He can then send that packet to the time server on SYSTEMB, which will send the time to SYSTEMA, which will respond back to SYSTEMB, and so on, generating a continuous loop and consuming CPU resources on both systems, as well as network bandwidth. Therefore, you should consider the risk of such an attack on your AS/400 system, and only run these services on a secure network. The INETD server is shipped to not be autostarted when you start TCP/IP. You can configure whether or not to start the services when INETD is started. By default, the TCP and UDP time servers and daytime servers are both started when you start the INETD server. There are two configuration files for the INETD server: /QIBM/UserData/OS400/inetd/inetd.conf /QIBM/ProdData/OS400/inetd/inetd.conf These files determine what programs start when the INETD server starts. If a malicious programmer got access to these files, she could configure them to start any program when INETD started. Therefore it is very important to protect these files. By default they require QSECOFR special authority to make changes. You should not reduce the authority required to access them.