Use EVTRACING Command to Dynamically Activate Debug Tracing - Ironstream_Hub - ironstream_for_elastic - ironstream_for_kafka - ironstream_for_splunk - 1.3

Ironstream Hub Administration

Product type
Software
Portfolio
Integrate
Product family
Ironstream
Product
Ironstream > Ironstream for Elastic®
Ironstream > Ironstream Hub
Ironstream > Ironstream for Kafka®
Ironstream > Ironstream for Splunk®
Version
1.3
Language
English
ContentType
Administration
Product name
Ironstream Hub
Title
Ironstream Hub Administration
First publish date
2022
ft:lastEdition
2024-04-15
ft:lastPublication
2024-04-15T10:44:03.897025

On the IBM i LPAR, use the EVTRACING command to start and stop debug tracing without restarting a job. Use this tracing facility at the direction of Precisely Support.

The trace output will be written to the EVIEW/EVTRACE output queue.

Issuing the CALL EVIEW/EVTRACING command with no parameters displays the current trace level for each job.

The syntax is:

CALL EVIEW/EVTRACING [PARM('jobname' '[x]tracelevel')]

where:

jobname

The name of the job running under the EVSBS subsystem. The valid jobname values for EVTRACING are:

EVCCTLPROC

EVJRNPROC

EVMSGQMON

EVPERFPROC

EVSCMDPROC

EVSHSTPROC

EVTCTLPROC

tracelevel

A decimal value 0-65535 (or hexadecimal 0-FFFF if preceded by an “x”) indicating the trace level.

A tracelevel of “0” turns off job tracing.

Examples:

To turn on the tracing for Journal Monitoring call:

CALL EVIEW/EVTRACING PARM('EVJRNPROC' '7')

To turn the trace back off, once it is no longer needed, call:

CALL EVIEW/EVTRACING PARM('EVJRNPROC' '0')

These values can also be set before the EVSBS subsystem starts by editing the appropriate “_TRACE” parameter value in the EVIEW/EVPARMS parameter file.

Note:

Trace files can grow very quickly, so it is recommended to activate the tracing only for limited periods of time. After it has been offloaded, use this command to clear the trace file(s) from the output queue:

CLROUTQ EVIEW/EVTRACE.