Question & Answer
Question
Why was the naming conventions of the Java(TM) output files (stderr, stdout and jvmtrc) changed in CICS Transaction Server for z/OS (CICS TS) V5.3?
When running CICS TS V5.1, the Java output files would be written to the HFS working directory (WORKDIR) with the following default naming convention:
&APPLID;.&JVMSERVER;.Dyyyymmdd.Thhmmss.dfhjvmxxx
where xxx is either err, out, or trc. But after upgrading to CICS TS 5.3, the java output files are written by default to the working directory within a subdirectory (WORKDIR/APPLID/JVMSERVER) with the following naming convention:
Dyyyymmdd.Thhmmss.dfhjvmxxx
where xxx is either err, out or trc. Note that the APPLID and JVMSERVER name are now subdirectories instead of part of the file name.
Answer
The default location for stdout, stderr and jvmtrace was changed from the working directory WORK_DIR to WORK_DIR/applid/jvmserver. And the default file name was changed from &APPLID;.&JVMSERVER;.Dyyyymmdd.Thhmmss.dfhjvmxxx to Dyyyymmdd.Thhmmss.dfhjvmxxx.
CICS TS 5.3 made some enhancements to the CICS Java log management. It now provides a consolidated log output behavior so that all JVMSERVER, OSGi and Liberty log files are located within the same directory tree, so it is consistent with other CICS zFS resources. Some symbolic links have been added for convenience when traversing between the important log artifacts.
A new JVM server option, LOG_PATH_COMPATIBILITY was introduced to provide the consolidated log output behavior. It defaults to FALSE. If you would like to revert to the prior release behavior, you could set LOG_PATH_COMPATIBILITY=TRUE.
An added benefit to using the consolidated log output behavior (LOG_PATH_COMPATIBILITY=FALSE) is that the JVM server option LOG_FILES_MAX can be used to control the number of old log files kept on the system.
Shayla Robinson
IBM CICS/CPSM Level 2 Support
Product Synonym
CICS/TS CICSTS CICS TS CICS Transaction Server
Was this topic helpful?
Document Information
Modified date:
02 April 2018
UID
dwa1395903