NetMaster logs flooded with IPCM2002, IPCM2003 messages causing S722 abend
Article ID: 109847
Updated On:
Products
CA CMDB for z/OS
CA NetSpy Network Performance
CA NetMaster Network Automation
CA SOLVE
CA NetMaster Network Management for SNA
CA NetMaster Network Management for TCP/IP
CA NetMaster File Transfer Management
Issue/Introduction
The Netmaster activity log shows masses of these messages
IPCM2002 TELNET CONNECTION STARTED FROM 192.168.2.66..4925 AS TSTCP007 TO TEST1 LOGICAL DEVICE 0006
IPCM2003 TELNET CONNECTION ENDED FROM 192.168.6.127 AS TSTCP006 TO TEST4, BYTES IN 550 OUT 32665 DURATION 0 DAYS 00.06
IPCM2002 TELNET CONNECTION STARTED FROM 192.168.2.66..4925 AS TSTCP007 TO TEST1 LOGICAL DEVICE 0006
IPCM2003 TELNET CONNECTION ENDED FROM 192.168.6.127 AS TSTCP006 TO TEST4, BYTES IN 550 OUT 32665 DURATION 0 DAYS 00.06
Cause
The Netmaster Using Guide explains
Telnet Activity in the Log
The Telnet connections can be logged as they are started and ended.
Note: Logging of Telnet activity is specified in the IPEVENT parameter group. For more information, see Implementing .Example: Telnet Messages
These examples show the Telnet connection start and end messages:
IPCM2002 TELNET CONNECTION STARTED FROM 192.168.2.66..4925 AS TSTCP007 TO TEST1 LOGICAL DEVICE 0006 IPCM2003 TELNET CONNECTION ENDED FROM 192.168.6.127 AS TSTCP006 TO TEST4, BYTES IN 550 OUT 32665 DURATION 0 DAYS 00.06.35
A logged connection start message contains the following information:
- Time that the connection started
- Port number, LU, and device number used
A logged connection end message contains the following information:
- Time that the connection ended
- IP address and LU name of the device where the connection ended
- Application to which the session was connected
- Number of bytes in and out
- Duration of the connection
Environment
Release: SLOPFC00200-12.1-NetMaster-File Transfer Management
Component:
Component:
Resolution
As noted in the Users Guide, 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)
Hit F6 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
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)
Hit F6 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
Additional Information
See also KB000011935 for general causes of an S722 abend.
Feedback
Powered by
