Communications Traces: Difference between revisions
Jump to navigation
Jump to search
new |
m Typo |
||
| Line 9: | Line 9: | ||
prtcmntrc cfgobj(trnline) cfgtype(*lin) sltctld(fiona) fmttcp(*no) fmtbcd(*no) | prtcmntrc cfgobj(trnline) cfgtype(*lin) sltctld(fiona) fmttcp(*no) fmtbcd(*no) | ||
* Delete now unneeded Trace Data. | * Delete now unneeded Trace Data. | ||
dltcmntrc cfgobj(trnline) cfgtype(*lin) | dltcmntrc cfgobj(trnline) cfgtype(*lin) | ||
[[Category: System Administration]] | [[Category: System Administration]] | ||
[[Category: System Internals]] | [[Category: System Internals]] | ||
Latest revision as of 15:52, 7 July 2026
Communications Traces are essentially very much akin to tcpdump or Wireshark on common platforms. It's a multi-step, non-interactive process.
- 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) sltctld(fiona) fmttcp(*no) fmtbcd(*no)
- Delete now unneeded Trace Data.
dltcmntrc cfgobj(trnline) cfgtype(*lin)