Receiving several OEVN003I OPSEVENT Status: PROBLEM Reason:

Article Id: 103799

Status: Published

Updated On: 03-07-2018 01:14

Products:

CA Bind Analyzer for DB2 for z/OS , CA SQL-Ease for DB2 for z/OS , CA Sysview Performance Management Option for DB2 for z/OS , CA Database Detector for DB2 for z/OS , CA Plan Analyzer for DB2 for z/OS , CA Subsystem Analyzer for DB2 for z/OS

Issue/Introduction:

Receiving several OEVN003I OPSEVENT Status:
PROBLEM Reason: Xnet TCPok *XMGR* PTCKTok *PXN* noU2X *IDB2* noOFA 06/15/18 08:49:51.876 XNETAPI exit fc(01) rc(205) rs(000) req(00000000) xnr(2216B8A8) x15/1(00000000/00000000)
06/15/18 08:50:51.877 XNETAPI exit fc(01) rc(205) rs(000) req(00000000) xnr(2216B8A8) x15/1(00000000/00000000) 06/15/18 08:51:51.878 XNETAPI exit fc(01) rc(205) rs(000) req(00000000) xnr(2216B8A8) x15/1(00000000/00000000) 06/15/18 08:52:51.880 XNETAPI exit fc(01) rc(205) rs(000) req(00000000) xnr(2216B8A8) x15/1(00000000/00000000) 06/15/18 08:53:51.881 XNETAPI exit fc(01) rc(205) rs(000) req(00000000) xnr(2216B8A8) x15/1(00000000/00000000)
XNETAPI isn't defined in the STC's parms.

Cause:

proc was pointing to the wrong Xmanid

Environment:

z/os DB2

Resolution:

Update Xmanid 1800 to point to the R19 release so should be Xmanid 1900.