The collection name consists of 1 through 18 characters.
The connection type consists of 1 through 8 characters.
The correlation information consists of 1 through 18 characters.
The luname consists of 1 through 8 characters.
The level consists of 1 through 3 numeric characters.
The default trace level value is 2.
Trace level indicators 0, and 4 through 127 are reserved.
The netid consists of 1 through 8 characters.
Specifying NET requires the specification of the LU keyword.
The package name consists of 1 through 8 characters.
The plan name consists of 1 through 8 characters.
The proc name consists of 1 through 18 characters.
The process information consists of 1 through 32 characters.
The subsystem information consists of 1 through 18 characters.
The transaction class information consists of 1 through 8 characters.
Although the transaction name has specific meaning to many subsystems (those that exploit WLM classify), the transaction name identifies the name of the work request desired to be traced across the set of components that may handle it. See z/OS MVS Planning: Workload Management for information on transaction name and jobname.
The transaction name consists of 1 through 8 characters.
userid is the name of a single userid for whom the tracing is to be done.
The userid consists of 1 through 8 characters.
If WTR= is not specified, the trace data is saved in the TTRACE data space and can be obtained by dumping the data space.
The external writer may be started on the first invocation of the TRACE TT command or on any subsequent TRACE TT command prior to the TRACE TT,OFF command. Only one external writer may be started on any instance of transaction trace.
The external writer proc name must be the same on every system in the sysplex that is participating in transaction trace. Each system may define a proc with the same name or share a common writer proc.
If trace is already running, the writer may be started with a TRACE TT,WTR= command without specifying any filter parameters.
Trace entries are recorded in the external writer data set from the time the external writer is started until the external writer is stopped with a TRACE TT,WTR=STOP or trace is turned off with a TRACE TT,OFF,ALL. When the end of the data set is reached, it starts writing from the top of the data set, overlaying the oldest entries. Specifying a "membername" when transaction trace is not active (that is, no filter has been specified) results in an error message.
Any trace records currently in the buffers are written prior to stopping the external writer. An error message is issued if WTR=STOP is issued when no external writer is active.
nnnK is the buffer size in kilobytes, where nnn is a decimal number from 16 to 999.
nnM is the buffer size in megabytes, where nn is a decimal number from 1 to 32.
The buffer size may be changed anytime when trace is active. This includes when the initial TRACE TT command is issued. Specifying a buffer size when transaction trace is not active (that is, no filter has been specified) results in an error message. The default size is 1M.
The scope of this buffer size change affects TTrace processing until the buffer size is changed on a subsequent command or after a system IPL. That is, the buffer size persists if TTrace is turned off and turned on at a later time.
The buffer size is rounded up to a page boundary (that is, multiples of 4K).
This is an optional keyword.
Y specifies that latent transactions, if any, can continue to be traced. Y is the default value.
N specifies to not trace latent transactions. Any current active transactions that do not have an active filter will not be traced from this point on.
The scope of the latent parameter setting affects TTrace processing until the parameter is changed on a subsequent command or after a system IPL. That is, the parameter value persists if TTrace is turned off and then turned on at a later time.
nn is an integer from 1-99 that identifies a particular transaction trace filter set. Use DISPLAY TRACE,TT to display the active TTrace filter sets.
No additional trace entries are recorded. Any data in the trace buffers is written out to the data space and external writer data set. The external writer, if it was started, is also stopped.
A message is issued to the operator console to indicate that transaction trace is no longer active on the system and a DUMP command may be issued to access the trace in the data space.