Functionality of SNTP Logging on the System

Resolving The Problem

The IBM System i products system has an SNTP client starting at V5R2. Logging for the client is enabled through the CHGNTPA CL command or through IBM iSeries Navigator. Logging can be set to *NONE, *CHANGE, or *POLL. When logging is set to *CHANGE or *POLL, a new log file is created for each new day. The created log files will grow in number until they are deleted from the system. It is therefore suggested that *CHANGE or *POLL be used only during initial testing. After SNTP functionality has been verified, the logging level should be set to *NONE. If the logging level is left at *CHANGE or *POLL, it is advisable to determine the number of log files that are existing and delete them as necessary.

The SNTP server function added at V5R3 can also produce a log. Logging can be set to *NONE, *ERROR, or *ALL. Logging for the server acts in the same manner as the client. If logging is enabled, it must be managed to control the number of logs that exist on the system.

The client logs are located in directory /QIBM/USERDATA/OS400/TCPIP/NTP. The files are named QTOTxxxxxxxx (where x = the date).

The server logs are located in directory /QIBM/USERDATA/OS400/TCPIP/NTP/SERVER. The server log files are also named QTOTxxxxxxxx.

The directory path information can be found in the NTP (QTOTNTP) joblog.