IBM Support

network issue fixed still omegamon connectivity issue

Question & Answer


Question

My network issues were fixed between zLinux and z/OS but I am still having intermittent connectivity issues between my HUB TEMS on zLinux and my OMEGAMON agents on z/OS. I am seeing these messages in the OMEGAMON XE for CICS log:

(5A0B070C.0000-EB:kpxndmgr.cpp,189,"UpdateStatusForFailedRequest") INFO: Setting node off-line due to failure to start req (5A0B07FD.0000-C9:kpxndmgr.cpp,189,"UpdateStatusForFailedRequest") INFO: Setting node off-line due to failure to start req (5A0B0860.0001-12:kpxreqds.cpp,2832,"timeout") Timeout for .CICSROV. (5A0B086B.0000-12:kpxreqds.cpp,2832,"timeout") Timeout for .CICSROV. (5A0B0899.0000-12:kpxreqds.cpp,2832,"timeout") Timeout for .CICSBNS. (5A0B08A8.0001-12:kpxreqds.cpp,2832,"timeout") Timeout for .CICSROV. (5A0B08CB.0001-12:kpxreqds.cpp,2832,"timeout") Timeout for .CICSROV. (5A0B08E3.0001-12:kpxreqds.cpp,2832,"timeout") Timeout for .CICSROV. (5A0B08ED.0000-2C:kpxndmgr.cpp,189,"UpdateStatusForFailedRequest") INFO: Setting node off-line due to failure to start req (5A0B095C.0001-12:kpxreqds.cpp,2832,"timeout") Timeout for .CICSROV. (5A0B097F.0001-12:kpxreqds.cpp,2832,"timeout") Timeout for .CICSROV. (5A0B0998.0000-12:kpxreqds.cpp,2832,"timeout") Timeout for .CICSROV. (5A0B09BB.0000-12:kpxreqds.cpp,2832,"timeout") Timeout for .CICSROV. (5A0B09D4.0001-12:kpxreqds.cpp,2832,"timeout") Timeout for .CICSROV. (5A0B09DE.0000-F9:kpxndmgr.cpp,189,"UpdateStatusForFailedRequest") *INFO: Setting node off-line due to failure to start req

Why am I still having connectivity issues?

Answer

In this case the customer had mismatched hypersocket MTU sizes between their zLinux HUB TEMS and OMEGAMON XE for CICS agent on z/OS (hypersocket MTU sizes must match on both ends to work). The HUB TEMS and OM CICS agent usually can recover from connectivity issues but in some instances they cannot. In this case, the TEMS and the agents needed to be recycled to clear out any residual issues and that was the cause of their intermittent connectivity problems. Once they recycled the OM CICS PROC, the agent connected to the HUB TEMS and they did not see anymore error messages or timeout messages.

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SS5FZ9","label":"IBM Z OMEGAMON for CICS on z\/OS"},"Platform":[{"code":"PF035","label":"z\/OS"}],"Component":"","Version":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
11 August 2022

UID

dwa1415368

Page Feedback