Various server DD statements are used to address system
output such as, console output, trace output, and dump output.
Because WebSphere® Application Server controllers
and servants are z/OS® started task address spaces, they can produce
a variety of output:
- Server output and error messages
- Trace records
- System dumps
This output can be written to a variety of destinations:
- JES2 print and punch files (referred to as STDERR or job output)
- Files written to the configuration file system or other file systems
- z/OS log streams
- Component trace datasets
Starting with Version 8.5.0.2, you can also
use the redirect_server_output_dir WebSphere environment
variable to redirect output to files on the Unix Systems Services
(USS) file system. The value specified for this variable is the absolute
path of the existing directory that contains the files to which you
want output redirected. If a value is not specified for this variable,
output continues to be directed to DD statements. Refer to the topic Application
server custom properties for z/OS for a description of
how to specify a WebSphere environment variable.
![[8.5.0.2 or later]](../images/ng_v8502.gif)
If you decide to use USS redirecting, the
new file naming scheme for standard output and standard error is as
follows:
cellName.nodeName.serverName.jobName.jobId.asType.date.time
followed
by either
.SYSPRINT.txt or
.SYSOUT.txt respectively.
![[8.5.0.2 or later]](../images/ng_v8502.gif)
You can use the
ROLL_LOGS parameter
of the modify command to automate the use of the
redirect_server_output_dir.
When you issue the following modify command, a new set of ouput files
is created for the specified server and its respective servants. Messages
are then appended to the end of the previous output file and the beginning
of the new file, thereby linking them together.
f <server>, ROLL_LOGS