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, and JVMTRACE 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.

Using the JOBLOG parameter results in STDOUT and JVMTRACE being routed to SYSPRINT if defined or to a dynamic SYSnnn if not. If only 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

Output can also be routed to any MVS™ data definition (DD) defined to JES, for example if the CICS region JCL specifies the DD statements JVMOUT and JVMERR.

//JVMOUT   DD SYSOUT=* 
//JVMERR   DD SYSOUT=*

The following JVM profile options can then be used in the JVM profile to route stdout and stderr streams to the JVMOUT and JVMERR destinations.

STDOUT=//DD:JVMOUT
STDERR=//DD:JVMERR

To 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 stdout, stderr, JVMTRACE, and dump output.