Using a DD statement to route JVM server output to JES
You can update the JVM server to redirect output to a specific location.
JVM server STDOUT, STDERR, JVMLOG, JVMTRACE, and messages.log output can be routed to the JES log. This allows JVM server log file output to be managed together with other CICS® logs such as the MSGUSR.
JVMTRACE=JOBLOG is specified, JVMTRACE is routed to the current stdout location. STDERR is routed to SYSOUT if defined or to a dynamic SYSnnn if not, for
example: STDOUT=JOBLOG
STDERR=JOBLOG
JVMTRACE=JOBLOG
JVMLOG=JOBLOG//JVMOUT DD SYSOUT=*
//JVMERR DD SYSOUT=*
//MSGLOG DD SYSOUT=* <--- redirects Liberty messages.logIf the DD statements configured in Liberty are not defined in CICS runtime JCL, these logs are automatically redirected to the specified DD output and are listed in CICS job output when Liberty is started.
stdout and stderr streams to the JVMOUT and JVMERR destinations. If omitted, the JVM server will automatically
create those destinations. A MSGLOG statement automatically redirects messages.log to JES without the need for any JVM profile configuration.STDOUT=//DD:JVMOUT
STDERR=//DD:JVMERRTo establish the origin of the JVM server output, all stdout, and stderr entries that are routed to JES are written with a prefix string of the JVM server name, which is useful if multiple JVM servers are sharing a
destination. This behavior can be disabled by using the JVM profile option IDENTITY_PREFIX, which if set to FALSE disables use of the prefix string.
It is not possible to route IBM Health Center messages to the CICS job log. Consider using zFS as the primary output location if you wish to see detailed IBM Health Center output.
If you choose not to specify a destination, the output will redirect to the zFS default file, however you can set it to send to specific zFS files. See Controlling the location for JVM output, logs, dumps and trace.