Communications Traces: Difference between revisions

From Try-AS/400
Jump to navigation Jump to search
m Typo
Removed spool number, this can change. You're supposed to have only one splf in the outq with the same name for this to work!
 
(2 intermediate revisions by the same user not shown)
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.
Line 7: Line 9:
  endcmntrc cfgobj(trnline) cfgtype(*lin)
  endcmntrc cfgobj(trnline) cfgtype(*lin)
* Format a report from the trace data. Goes to the standard printer queue.
* Format a report from the trace data. Goes to the standard printer queue.
  prtcmntrc cfgobj(trnline) cfgtype(*lin) sltctld(fiona) fmttcp(*no) fmtbcd(*no)
  prtcmntrc cfgobj(trnline) cfgtype(*lin) fmttcp(*no) fmtbcd(*no)
* Delete now unneeded Trace Data.
* Delete now unneeded Trace Data.
  dltcmntrc cfgobj(trnline) cfgtype(*lin)
  dltcmntrc cfgobj(trnline) cfgtype(*lin)
Optionally, this trace can be exported to a database file, to be e.&thinsp;g. downloaded via FTP for further treatment.
crtpf file(mylib/qpcsmprt) rcdlen(132)
cpysplf file(qpcsmprt) tofile(mylib/qpcsmprt)


[[Category: System Administration]]
[[Category: System Administration]]
[[Category: System Internals]]
[[Category: System Internals]]

Latest revision as of 00:03, 27 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)