TS Supplement (Includes RFC-1006 Support)

PTrace Records Changed to Support RFC-1006

RFC-1006 Changes to the SCF, SPI, and PTrace Subsystems

3–48 107751 Tandem Computers Incorporated

New NetIO operation types, representing TCP/IP socket functions, are shown in

the PTrace displays. In cases where the socket operation includes a copy of the

SOCKADDR_IN structure as a parameter, PTrace produces a formatted display of

the TCP port number and IP address if the PTrace user has requested DETAIL ON.

Sample NetIO records are shown below.

A new internal file-system operation, the No-Wait process-file OPEN operation, is

shown in the PTrace displays. A sample record is shown below.

All buffer allocation and deallocation trace entries that specify the buffer size in

bytes now use a double-word (INT(32)) to indicate the length of the buffer.

These are the new trace display formats:

NetIO IO

This trace record is generated when the TSP process binds a TCP/IP socket to the well-

known server port number.

04/22/94 11:40:28.808292 >000.000000 #42 Net IO

Bind Req Cnt: 8 FE: 0 Tag: 3551716 File: 3 SU: #Private

Port No: 102 IP Address: 0.0.0.0

Operation

shows the operation performed, in this example, a BIND_NW request.

Cnt

shows the length of the request buffer (in bytes).

shows the file system error returned against this request. For possible values, see

the Tandem TCP/IP Programming Manual.

Tag

shows the I/O tag.

File

shows the file or socket number.

shows the NSP SU name. In this case, #Private indicates that this socket is a

special socket for internal use only by the TSP process.

The next two fields appear only if you specify DETAIL ON.