CAIENF SNMP trace service getaddrinfo() rc=1 after IPL
Article ID: 262472
Updated On:
Products
Issue/Introduction
The SNMP trap monitor (PGM=CAW1SNMP), the STC ENFSNMPD, failing to start after IPL (automated with SSM).
E.g.
18:26:52 MAIN: Started on Sat Mar 11, 2023 - asid(005F)
18:26:52 MAIN: Sysname: z/OS
18:26:52 MAIN: Nodename: OX02
18:26:52 MAIN: Version: 02
18:26:52 MAIN: Release: 05.00
18:26:52 mainInit: node name 'OX02' is not valid, getaddrinfo() rc=1
18:26:52 MAIN: main_init return rc=4
The solution is simply to restart it later.
Possibly you are starting it too early in the IPL sequence. We connected the startup of the STC to the EZD1214I or EZD1314I from the TCP/IP started task.
ENFSNMPD has TCPIP as prerequisite and now starting a little later. But to no avail. There is still this error message.
Are there other dependency? How to avoid this error from occurring?
Cause
Network environment not fully initialized prior to startup of ENFSNMPM task
Resolution
The ENFSNMP is not dependent to the TCPIP started task to get fully initialized, but the RESOLVER started task should be fully initialized...
Be sure the RESOLVER address space is fully initialized prior to starting ENFSNMPM
Additional Information
ENFSPNMP only works when ENF is also fully active...Starting ENFSNMP before ENF, or before it's fully initialized is of no use...
The ENFSNMP function only works when ENF is fully active..
Make the startup of ENFSNMPM dependent to ENF being initialized, or add it to the ENF auto command member to allow ENF start it as part of the initialization process.
See this page :
SNMP Monitor
It mentions this startup option.. The rest of the rest of the automation can be left in tact, but let ENF arrange the startup...
Feedback
