JANUS TCPLOG: Difference between revisions
m (1 revision) |
mNo edit summary |
||
| Line 1: | Line 1: | ||
{{DISPLAYTITLE:JANUS TCPLOG}} | {{DISPLAYTITLE:JANUS TCPLOG}} | ||
<span class="pageSubtitle"><section begin="desc" /> | <span class="pageSubtitle"><section begin="desc" />Capture Janus port traffic<section end="desc" /></span> | ||
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== | ==Syntax== | ||
<p class="syntax"><section begin="syntax" /> JANUS TCPLOG ddname | <p class="syntax"><section begin="syntax" /> JANUS TCPLOG ddname | ||
| Line 13: | Line 10: | ||
</p> | </p> | ||
Where: ''ddname'' is the DDname of the sequential dataset to contain the log. | |||
Where: | |||
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. | 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. | The format of the log file is shown below. All values are in binary format except where indicated. | ||
<table class="syntaxTable"> | <table class="syntaxTable"> | ||
<tr><th>d.Bytes</th> | <tr><th>d.Bytes</th> | ||
| Line 41: | Line 38: | ||
<td>Local port number</td></tr> | <td>Local port number</td></tr> | ||
<tr><th>36-36</th> | <tr><th>36-36</th> | ||
<td>Direction (EBCDIC character): | |||
<ul> | <ul> | ||
<li>R (received) | <li>R (received) | ||
<li>S (sent) | <li>S (sent) | ||
</ul> | </ul> | ||
</td></tr> | |||
<tr><th>37-37</th> | <tr><th>37-37</th> | ||
<td>Unused</td></tr> | <td>Unused</td></tr> | ||
| Line 56: | Line 52: | ||
</td></tr></table> | </td></tr></table> | ||
The TCPLOG subcommand is available as of ''[[Sirius Mods]]'' Version 7.2. .im jtrace | |||
==References== | |||
See: [[List of Janus commands]] | |||
[[Category:Janus commands|JANUS TCPLOG]] | [[Category:Janus commands|JANUS TCPLOG]] | ||
[[Category:Sirius commands]] | [[Category:Sirius commands]] | ||
Revision as of 17:02, 2 March 2011
<section begin="desc" />Capture Janus port traffic<section end="desc" />
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
<section begin="syntax" /> JANUS TCPLOG ddname <section end="syntax" />
JANUS TCPLOG command syntax
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