We are using OPUSSLG1 to manage SYSLOGD and have run into issues when attempting to migrate maintenance to our development environment. z/OS 2.3 RSU 2007 and OPS/MVS 13.5 CAR2007
When starting OPSSLGP received the following error:
EDC6257C THERE IS A SOCKET PROBLEM, SYSLOGD MAY NEED TO BE RESTARTED. UNTIL THE CONDITION IS RESOLVED, ALL MESSAGES WILL BE LOST
and TCPIP tasks like SNMP, SMTP, OMPROUTE can't write messages to SYSLOGD.
OPSSLGP3 produced a dump during startup. Also have output from slgout.
We ended up backing out RSU2007 because we couldn't move forward not knowing the effect of this.
Release : 13.5
Component : OPS/MVS
The problem occurs when too many debug messages are written to stdout i.e. the joblog.
Two options to resolve this.
1. Turn debug off - OR -
2. Define a debug dataset and write debug messages to it instead.