The NetMaster Activity Log shows masses of these messages:
IPCM2002 TELNET CONNECTION STARTED FROM #.#.#.#..4925 AS TSTCP007 TO TEST1 LOGICAL DEVICE 0006
IPCM2003 TELNET CONNECTION ENDED FROM #.#.#.# AS TSTCP006 TO TEST4, BYTES IN 550
OUT 32665 DURATION 0 DAYS 00.06
OS: z/OS.
The NetMaster for TCP/IP Using tech docs section explains:
IPCM2002 TELNET CONNECTION STARTED FROM #.#.#.#.4925 AS TSTCP007 TO TEST1 LOGICAL DEVICE 0006
IPCM2003 TELNET CONNECTION ENDED FROM #.#.#.# AS TSTCP006 TO TEST4, BYTES IN 550 OUT 32665 DURATION 0 DAYS 00.06.35
As noted, whether or not the messages are written to the log is controlled by /PARMS IPEVENT.
Change this section:
Telnet Event Processing: Telnet Event Receiver, Running
Log Telnet Events? ......... YES (to Activity Log)
Save Telnet Events? ........ YES (in Event History Dataset IPLOG)
to this:
Telnet Event Processing: Telnet Event Receiver, Running
Log Telnet Events? ......... NO (to Activity Log)
Save Telnet Events? ........ YES (in Event History Dataset IPLOG)
PF6 to action the parameter group, which will immediately implement the changes.
PF4 to save changes.
PF3 to exit the parameter group.
-
If an INIFILE is being utilized, be sure to create a new version using /CUSTOM.G .
See also https://knowledge.broadcom.com/external/article?articleId=11935 for general causes of an S722 abend.