DUMP subcommand—Set extended trace options
Purpose
Use the DUMP subcommand to enable
or disable extended internal tracing.
Note: Extended tracing has the
potential to generate a large amount of trace data and should not
be set unless requested to debug a specific problem in the code.
Format
Parameters
One or more of the following options can be specified:
- ?
- Displays the status of the traces.
- n
- Specifies the ID number of a specific extended trace point that is to be activated in the FTP code. The number has a range of 1–99.
- ALL
- This parameter is used to set all of the trace points.
- FSC
- Activates all of the extended trace points in the file services code. The ID numbers for FSC are 20 to 49.
- NONE
- This parameter is used to turn off all of the traces.
- SOC
- Activates all of the extended trace points in the network services code. The ID numbers for SOC are 50 to 59.
- SQL
- Activates all of the extended trace points in the SQL services code. The ID numbers for SQL are 70 to 79.
- Xyyy
- This syntax is used to turn off (reset) a trace that is named
by yyy. For example,
DUMP X21 X22 XSQL
will reset the extended trace points 21 and 22 and all of the SQL trace points.
Examples
The following is an example of
a dump trace.
dump 21 22
Active client dumpIDs - 21 22
get a 'user33.abc111' (replace
12:38:31 MV0456 (21) TU_DSN ...:
0A31D1E4 00020001 000DE4E2 C5D9F3F3 4BC1C2C3 *......USER33.ABC*
0A31D1F4 F1F1F100 00000000 00000000 00000000 *111.............*
0A31D204 - 0A31D223 All zeros (0x20 bytes)12:38:31 MV0512 (21) TU_STATS ...:
0A31D150 00040001 00010100 *........ *
12:38:31 MV0521 (21) TU_DISP ...:
0A31D158 00050001 00010800 *........ *
12:38:31 MV2113 (22) RN PA=
0A3296C0 14070000 00000000 0A3296D8 00000000 *..........oQ....*
0A3296D0 00000000 *.... *
12:38:31 MV2115 (22) RN DD=
0A3296B0 00010001 0008E2E8 E2F0F0F0 F0F94B4B *......SYS00009..*
0A3296C0 14070000 0000 *...... *
12:38:31 MV2117 (22) RN DSN=
0A3296EC 00050001 000DE4E2 C5D9F3F3 4BC1C2C3 *......USER33.ABC*
0A3296FC F1F1F14B 60614B4B 4B4B4B4B 4B4B4F6B *111.-/.........,*
0A32970C 6C6D6E6F 4B4B4B4B 4B4B4B4B 4B4B7A7B *%_>?..........:#*
0A32971C 7C7D7E4B *@'=. *
>>> PORT 9,67,113,57,4,59
200 Port request OK.
>>> RETR a
125 Sending data set /u/user33/a
250 Transfer completed successfully.
820 bytes transferred in 0.005 seconds. Transfer rate 164.00 Kbytes/sec
Usage
The setting of the traces is additive.
This is demonstrated by the following example:
dump none 21
EZA2850I Active dumpIDs: 21
dump 22
EZA2850I Active dumpIDs: 21 22
Entering dump
with no parameters is the same as entering dump with the ?
parameter.
The range of 99 extended trace points is defined to allow easy extension of the trace points by the TCP/IP service team. Additional trace points can be added to the code without any changes to the external mechanism to control the traces.
See Diagnosing FTP client problems with tracing in z/OS Communications Server: IP Diagnosis Guide for more information about FTP client tracing.