On the IBM i managed node: - ironstream_for_micro_focus_universal_discovery - 6.3

Ironstream for Micro Focus® Universal Discovery for IBM i Administration
Product type
Software
Portfolio
Integrate
Product family
Ironstream
Product
Ironstream > Ironstream for Micro Focus® Universal Discovery
Version
6.3
Language
English
Product name
Ironstream for Micro Focus Universal Discovery for IBM i
Title
Ironstream for Micro Focus® Universal Discovery for IBM i Administration
Copyright
2021
First publish date
2007
Last updated
2023-08-23
Published on
2023-08-23T16:21:59.136387

  1. Enter the EVSTATUS command as described on page 29. Look for any “Note” or “Warning” messages

in the output which may indicate a problem.

  1. Issue the command WRKACTJOB SBS(EVSBS)

The following jobs should be listed in an active (not "Message Wait") status:

EVACMDPROC PGM-EVCCMD 
EVCCTLPROC PGM-EVCCTL
EVSCMDPROC PGM-EVC050 
EVSMSGPROC PGM-EVC010
EVSTCPPROC PGM-EVCHCI 
EVTCTLPROC PGM-EVCMSG

If the QHST monitoring option was selected in the configuration of the IBM i LPAR (EV400_MONITOR_QHST parameter is "YES"), then verify the additional job is active:

EVSHSTPROC PGM-EVHSTCL

If the performance monitoring option was selected in the configuration of the IBM i LPAR (EV400_PERF1 and/or EV400_PERF2 parameter is "YES"), then verify the additional job is active:

EVPERFPROC PGM-EVPERFM

  1. Check the agent message queue for any errors that may have been issued:

DSPMSG EVIEW/EVMSGQ

  1. Check the agent trace files for any error output. The trace files are in the EVTRACE output queue of the EVIEW library.

  2. Check the status of the TCP/IP ports used by the agent using the command NETSTAT *CNN

If the OMW management server processes are connected, the ports configured in parameters EV400_AS400_MSG_PORT and EV400_AS400_CMD_PORT (8000 and 8001 by default) should show as "Established". It is normal for these two ports to also be in a "Listen" state. The port configured in parameter EV400_AS400_SERVER_PORT must be "Established" before any messages or command responses can be sent to the OMW server.

  1. Check the condition of the agent data queues. The agent uses several data queues to store requests and messages. Data queue objects may become damaged due to unexpected interruption or system errors, which can cause agent jobs to fail. Issue the following commands to check the data queues:

ADDLIBLE EVIEW 
DDQ EVIEW/EVSENDQ
DDQ EVIEW/EVAPIQ 
DDQ EVIEW/EVCMDQ 
DDQ EVIEW/EVMRSPQ

If a data queue has been damaged, an exception message will be generated when issuing the DDQ command for that queue. If the data queue properties are displayed, verify that the maximum entry length is not zero, which is another indication of a damaged data queue.