Verifying the Operation of the Ironstream Agent for IBM i - Ironstream_Hub - ironstream_for_kafka - ironstream_for_elastic - ironstream_for_splunk - 1.3

Ironstream Hub Administration

Product type
Software
Portfolio
Integrate
Product family
Ironstream
Product
Ironstream > Ironstream for Kafka®
Ironstream > Ironstream for Elastic®
Ironstream > Ironstream for Splunk®
Ironstream > Ironstream Hub
Version
1.3
Language
English
ContentType
Administration
Product name
Ironstream Hub
Title
Ironstream Hub Administration
First publish date
2022
  1. Issue the command WRKACTJOB SBS(EVSBS):
    1. These three jobs should be listed in an active (not “Message Wait”) status:

      EVCCTLPROC PGM-EVCCTL

      EVSCMDPROC PGM-EVC050

      EVTCTLPROC PGM-EVCMSG

    2. If the QHST monitoring option was selected in the Configuration Tool (EV400_MONITOR_QHST parameter is “YES”), then verify the additional job is active:

      EVSHSTPROC PGM-EVHSTPGM

  2. If the journal monitoring option was selected in the Configuration Tool (EV400_MON_JOURNALS parameter is “YES”), then verify the additional job is active:

    EVJRNPROC PGM-EVMONJRNL

    There should be one EVJRNPROC job running for each JRNPRMxxx member listed in the EVIEW/MONJRNLPRM file.

  3. If the legacy performance monitoring option was selected in the Configuration Tool (EV400_PERF1 and/or EV400_PERF2 parameter is “YES”), then verify the additional job is active:

    EVSHSTPROC PGM-EVHSTPGM

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

    DSPMSG EVIEW/EVLOGQ

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

    WRKOUTQ EVIEW/EVTRACE

  6. Check the condition of the data queues. Several data queues are used to store requests and messages. Data queue objects may become damaged due to unexpected interruption or system errors, which can cause jobs to fail. Issue the following commands to check the data queues:

    EVIEW/EVSTATUS DQS OUTPUT(*)

    If a data queue has been damaged, an exception message will be generated when displaying the information 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.

    Note: The commands required to delete and re-create the queue are included in the EVSTATUS report.