Allows the user to capture the DRDA® data stream exchanged between a DRDA Application Requestor (AR)
and the DB2® DRDA Application Server (AS). Although this
tool is most often used for problem determination, by determining
how many sends and receives are required to execute an application,
it can also be used for performance tuning in a client/server environment.
Command syntax
>>-db2drdat----------------------------------------------------->
.---------.
.-on-. V |
>--+-+----+----+- -r-+-+--+------------+------------------+----><
| +- -s-+ '- -l=length-' |
| +- -c-+ |
| '- -i-' |
'-off--+-------------------+--+-------------+--+-----+-'
'- -t--=--tracefile-' '- -p--=--pid-' '- -f-'
Command parameters
- on
- Turns on AS trace events (all if none specified).
- off
- Turns off AS trace events.
- -r
- Traces DRDA requests
received from the DRDA AR.
- -s
- Traces DRDA replies
sent to the DRDA AR.
- -c
- Traces the SQLCA received from the DRDA server
on the host system. This is a formatted, easy-to-read version of not
null SQLCAs.
- -i
- Includes time stamps in the trace information.
- -l
- Specifies the size of the buffer used to store the trace information.
- -p
- Traces events only for this process. If -p is
not specified, all agents with incoming DRDA connections
on the server are traced. The pid to be traced can be found
in the agent field returned by the LIST APPLICATIONS command.
- -t
- Specifies the destination for the trace. If a file name is specified
without a complete path, missing information is taken from the current
path. If tracefile is not specified, messages are directed
to db2drdat.dmp in the current directory.
- -f
- Formats communications buffers.
Usage notes
Do not issue db2trc commands
while db2drdat is active.
db2drdat writes
the following information to
tracefile:
- -r
- Type of DRDA request
- Receive buffer
- -s
- Type of DRDA reply/object
- Send buffer
The command returns an exit code. A zero value indicates
that the command completed successfully, and a nonzero value indicates
that the command was not successful. If db2drdat sends
the output to a file that already exists, the old file will be erased
unless the permissions on the file do not allow it to be erased, in
which case the operating system will return an error.