JANUS TCPLOG: Difference between revisions
Jump to navigation
Jump to search
(Automatically generated page update) |
m (→References) |
||
| Line 53: | Line 53: | ||
The TCPLOG subcommand is available as of ''[[Sirius Mods]]'' Version 7.2. .im jtrace | The TCPLOG subcommand is available as of ''[[Sirius Mods]]'' Version 7.2. .im jtrace | ||
== | ==See also== | ||
<ul> | |||
<li>[[List of Janus commands]] | |||
</ul> | |||
[[Category:Janus commands|JANUS TCPLOG]] | [[Category:Janus commands|JANUS TCPLOG]] | ||
Revision as of 20:15, 16 April 2013
Capture Janus port traffic
The JANUS TCPLOG subcommand lets you capture all input and output streams for a particular Janus port. The captured streams are written to a sequential file.
Syntax
JANUS TCPLOG ddname
Where: ddname is the DDname of the sequential dataset to contain the log.
One suggested use for a file of captured streams is to provide "playback" for customer-written applications that simulate real workloads during testing of new system or application code.
The format of the log file is shown below. All values are in binary format except where indicated.
| d.Bytes | d.Description |
|---|---|
| 0-1 | Record length |
| 2-3 | Unused |
| 4-11 | TCP unique connection number |
| 12-15 | Record number |
| 16-23 | TOD value (in STCK units) |
| 24-27 | Remote IP address |
| 28-31 | Local IP address |
| 32-33 | Remote port number |
| 34-35 | Local port number |
| 36-36 | Direction (EBCDIC character):
|
| 37-37 | Unused |
| 38-39 | Length of binary data |
| 40-n | Binary data (ASCII characters) |
The TCPLOG subcommand is available as of Sirius Mods Version 7.2. .im jtrace