These options are available for use with the ctgadmin -a trace command.
ctgadmin -a trace -?
Option | Short form | Description |
---|---|---|
-dumpoffset | -of | Specifies the offset from which displays of
any data blocks start, for example 512. If the offset
is greater than the total length of data to be displayed, an offset
of 0 is used. This option applies only to the Gateway trace, not JNI
trace. You cannot use this together with the fulldatadump option. |
-fulldatadump |
-fd | Sets the dumpoffset to 0 and ignores any value specified in truncationsize. This option applies only to the Gateway trace, not JNI trace. |
-jnifile | -jf | Specifies the name of the output file for JNI
tracing. You must specify a value for this option. If you do not,
an error is displayed. JNI trace is output as plain text, and there
is no requirement to use a particular extension for the file name. On Windows if you specify a read-only network drive as the location of tfile, the CICS Transaction Gateway returns an "unknown" error, rather than indicating that the file is not writable. This is due to a limitation in the SDK. |
-jnilevel | -jl |
|
-tfilesize | -ts | Specifies the maximum size, in kilobytes, of the Gateway trace output file, for example 50000. |
-tfile | -tf | Specifies the output file for Gateway tracing, for example ./tracefile.trc on UNIX and Linux or .\tracefile.trc on Windows. If you do not specify a value for this option, trace output is sent to the console. |
-tlevel | -tl | Specifies the Gateway trace level. Permitted
values are:
|
-truncationsize |
-tr | Specifies the byte at which to stop the hex
dump, for example 2000. It defines the end point,
not the number of bytes to display. So if on a dump of size 40 you
set the dumpoffset to 11, and the truncationsize to
25, you will see 15 bytes (from 11 to 25). You cannot use this together with the fulldatadump option. This option applies only to the Gateway trace, not JNI trace. |