JANUS TCPLOG: Difference between revisions

From m204wiki
Jump to navigation Jump to search
(Created page with "{{DISPLAYTITLE:JANUS TCPLOG}} <span class="pageSubtitle"><section begin="desc" />TCPLOG<section end="desc" /></span> The JANUS TCPLOG subcommand lets you capture all input a...")
 
m (1 revision)
(No difference)

Revision as of 17:13, 28 February 2011

<section begin="desc" />TCPLOG<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: :hp1.ddname:ehp1. 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.

  • R (received)
  • S (sent)
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