Controlling extended tracing

To control the extended trace, enter one of the following:
  MODIFY jobname,DUMP=(option_1,option_2,...,option_n,USERID(filter_name))

  MODIFY jobname,DUMP=(option_1,option_2,...,option_n,IPADDR(filter))
Where options are one of the following:
id
Specifies the ID number of a specific extended trace point that is to be activated in the FTP code. The ID number has a range of 1–99.
?
Displays the status of the extended traces.
ALL
Activates all of the trace points.
NONE
Resets (turns off) all extended traces.
FSC
Activates all of the extended trace points in the file services code. The numbers activated are 20–49.
SOC
Activates all of the extended trace points in the network services code. The numbers activated are 50–59.
JES
Activates all of the extended trace points in the JES services code. The numbers activated are 60–69.
SQL
Activates all of the extended trace points in the SQL services code. The numbers activated are 70–79.
USERID(filter_name)
Filters the trace for user IDs matching the filter_name pattern.

If a client's user ID matches the filter when the client logs into the server, its tracing options are set to the current value of the options. Otherwise, tracing options are not set. Clients can use the SITE command to set their options after login if the initial ones are not appropriate. An example for the USERID filter is MODIFY jobname,DEBUG=(21,USERID(USER33)), which activates the dumpID 21 trace for a user if his user ID is USER33.

IPADDR(filter)
Filters the extended trace for IP addresses matching the filter pattern.

If the client's IP address matches the filter when the client connects to the FTP server, its extended tracing options are set to the current value of the options. Otherwise, tracing options are not set. Clients can use the SITE command to set their options after connect if the initial ones are not appropriate.

An example of the IPADDR filter is MODIFY jobname,DUMP=(JES,IPADDR(9.67.113.57)), which activates the JES extended trace for a client whose IP address is 9.67.113.57. Another example is MODIFY jobname,DUMP=(FSC,IPADDR(FEDC:BA98:7654:3210:FEDC:BA98:7654:3210)). This activates all file services extended traces for a client whose IP address is FEDC:BA98:7654:3210:FEDC:BA98:7654:3210.

If the filter is an IPv4 address, submasking can be indicated by using a slash followed by a dotted decimal submask. For example, 192.48.32/255.255.255.0 allows addresses from 192.48.32.00 to 192.48.32.255.

If the filter is an IPv6 address, network prefixing can be indicated by using a slash followed by a prefix length. For example, FEDC:BA98::0/32 allows all IP addresses from FEDC:BA98::0 to FEDC:BA98:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF.

The specification of the trace on the MODIFY operator command is not additive. That is, the trace setting is that of the last MODIFY operator command. For example:
  MODIFY FTPDJG1,DUMP=(NONE)
  +EZYFT83I Active dumpIDs: NONE
  MODIFY FTPDJG1,DUMP=(21)
  +EZYFT83I Active dumpIDs: 21
  MODIFY FTPDJG1,DUMP=(22)
  +EZYFT83I Active dumpIDs: 22
Guidelines: The following are guidelines for migrating from the old parameters that were used with the MODIFY operator command:
  • MODIFY jobname,DUMP

    This format is rejected. DUMP requires at least one parameter (see above).

  • MODIFY jobname,NODUMP

    This is still accepted and is equivalent to MODIFY jobname,DUMP=(NONE). The old response message EZY2656I is replaced by EZYFT83I.

  • MODIFY jobname,JDUMP

    This is rejected as an obsolete command with a suggestion to use the DUMP parameter. For example, use the MODIFY jobname,DUMP=(JES) command.

  • MODIFY jobname,NOJDUMP

    This is rejected as an obsolete command with a suggestion to use the DUMP parameter. For example, use the MODIFY jobname,DUMP=(NONE) command.