The CONSOLE_TRACE statement controls whether PowerExchange displays messages to stdout in addition to writing them to the PowerExchange message log file.
i5/OS, UNIX, and Windows
No
CONSOLE_TRACE={
N
|Y}
N
.
PowerExchange writes messages to the PowerExchange message log file. No duplicate logged messages are written to stdout.
Y.
PowerExchange displays messages to stdout in addition to writing them to the PowerExchange message log.
On i5/OS, PowerExchange also writes messages to the QPRINT output in addition to writing
them to the PowerExchange message log.
On UNIX and Windows, PowerExchange also writes messages to the stdout stream in addition to
writing them to the PowerExchange message log. Informatica
recommends setting CONSOLE_TRACE=Y on UNIX and Windows when running
utility processes in the foreground. On UNIX, you cannot view
command session messages written to stdout if the process is run in
the background with the nohup option.
On z/OS, the CONSOLE_TRACE statement does not determine whether messages are written to DTLOUT. If alternative logging is used, PowerExchange does not duplicate messages written to the PowerExchange message log file to the DTLOUT file. If alternative logging is