Tracing in a PPC Gateway server is controlled by the -t and -T parameters of the cicsppcgwy.
-t ppc_sna:0x1f
-t ppc_sna:0x1f:ppc_gwy:0x1f
The -T parameter specifies where the trace information is written to. If you do not specify a -T parameter, the destination for trace is the internal ring buffer in the PPC Gateway server. This is a cyclic buffer so only the most recent trace is kept. You can display the contents of the ring buffer by using the tkadmin dump ringbuffer. The trace information is also dumped to the EncinaBacktrace file that the PPC Gateway server produces when it exits unexpectedly. Using the ring buffer is useful if the PPC Gateway server has to run for a while before the problem that you are trying to trace occurs. If you want the trace to be written to the same file as are the PPC Gateway server messages, specify -T all:stdout. If you want the trace to be written to another file, specify -T all:filename. This command also causes the PPC Gateway server messages to be written to this file.
/.:/cics/ppc/gateway/cicsgwy
/var/cics_servers/GSD/cics/ppc/gateway/cicsgwy/msg
% cicsppcgwy /.:/cics/ppc/gateway/cicsgwy -t ppc_sna:0x1f:ppc_gwy:\
0x1f -T all:/var/cics_servers/GSD/cics/ppc/gateway/cicsgwy/msg