Communications Traces: Difference between revisions
Jump to navigation
Jump to search
Local copy |
Note |
||
| Line 1: | Line 1: | ||
'''Communications Traces''' are essentially very much akin to ''tcpdump'' or ''Wireshark'' on common platforms. It's a multi-step, non-interactive process. | '''Communications Traces''' are essentially very much akin to ''tcpdump'' or ''Wireshark'' on common platforms. It's a multi-step, non-interactive process. | ||
<blockquote>'''Note:''' Command are examples and must be tailored to your particular environment!</blockquote> | |||
* Start trace. Network traces are always taken from a line description object. | * Start trace. Network traces are always taken from a line description object. | ||
Latest revision as of 13:05, 11 July 2026
Communications Traces are essentially very much akin to tcpdump or Wireshark on common platforms. It's a multi-step, non-interactive process.
Note: Command are examples and must be tailored to your particular environment!
- Start trace. Network traces are always taken from a line description object.
strcmntrc cfgobj(trnline) cfgtype(*lin) maxstg(16M) usrdta(*max) trcfull(*stoptrc)
- Run your commands for generating traffic.
- Stop trace.
endcmntrc cfgobj(trnline) cfgtype(*lin)
- Format a report from the trace data. Goes to the standard printer queue.
prtcmntrc cfgobj(trnline) cfgtype(*lin) fmttcp(*no) fmtbcd(*no)
- Delete now unneeded Trace Data.
dltcmntrc cfgobj(trnline) cfgtype(*lin)
Optionally, this trace can be exported to a database file, to be e. g. downloaded via FTP for further treatment.
crtpf file(mylib/qpcsmprt) rcdlen(132) cpysplf file(qpcsmprt) tofile(mylib/qpcsmprt) splnbr(1)