Hi Mark, thanks for your question. I have had a look at our Support System and found a number of matches to your error messages. These messages come from the XNET started task which is only used in a Chorus, or Wily-APM, or SYSVIEW DB2 environment. If you do not use these applications or don't access DB2 information from SYSVIEW you need not spawn the XNET started task. You also will want to make sure that the XNETAGT parm in the Insight IDDCPRMS member is commented out or says XNETAGT=NO. If you do not use the CA OPS/MVS product specify CALL-OPS=NO and then restart the IDB2 DC. Also make sure that the XNET STC is using the correct XManager ID(also at the same release level as XNET) if indeed you need it to be running.
See this knowledgebase technical article:
XNETAPI exit - CA Knowledge
See the doc about XNET
Manage the Xnet Started Task - CA Database Management Solutions for DB2 for z/OS - 20 Incremental - CA Technologies Docu…
Hope this helps,
Lucio