The TS6.1 new msg of "DFHSJ0207 11/21/2025 15:44:14 CICTxxxx JVMSERVER JVMOSGI1 is running Java version 17.0.13." only goes to TDQ; would be easier to see on the CICS JESLOG.

It would be nice to be able to browse the CICS region's JESLOG and immediately see the DFHSJ0207 message showing the JAVA level that each JVM is using.   

Our Operations staff implements 95% of our CICS changes and know how to verify things in the CICS JESLOG.    Additionally, we NO longer have //MSGUSR on our CICS jobs,  as we 'collect' all of the CICS TDQs (CMSG,CSSL....),  push them to a VSAM file and that file can be viewed either using a CICS Transaction or printed off via a Batch job.   (neither method lends themselves to easy Operational use, as CICS writes hundreds of messages to the TDQs...) 

In the Case, I was told that we as a customer, could create our own program (using DFH$XSP6 sample, customized for SJ0207 and TDQ name) and enable it into the XMEOUT exit point.  That would push the DFHSJ0207 message to the CICS JESLOG  and       actually this works fine!!!      

My issue is that DFHSJ0207 message comes out ONCE per JVM used in the CICS region; and comes out in the 1st minute of the region's startup.  After that 1st minute, this exit is useless as we normally never recycle our JVMs----so it now creates alot of overhead, as the XMEOUT exit is called for every TDQ write for the rest of the CICS execution (doing nothing for us).

I'd like to see IBM update the DFHSJ0207 logic, so that it is ALSO written to the CICS JESLOG  (I don't see why IBM would require each Customer to write a pair of pgms to accomplish this).