IBM Support

PH65227: JVMLOG DOES NOT CONTAIN INFO LEVEL DIAGNOSTIC OUTPUT FROM CICS' JAVA CODE DESPITE LOG_LEVEL=INFO

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • CICS is running with the SJ trace level set to OFF, 1, 2 or 1-2.
    
    A JVMSERVER is enabled with LOG_LEVEL=INFO in the JVM profile,
    or without LOG_LEVEL specified causing it to default to INFO.
    
    The JVMSERVER's JVMLOG file is created but only populated with
    output from CICS' C code that runs in the JVM.  The "info" level
    tracing from CICS' Java code is not written to the JVMLOG file.
    
    CICS needs updating to ensure the LOG_LEVEL option is respected
    when writing to the JVMLOG.
    
    If SJ tracing levels 3, 4 or 5 are enabled then this problem
    does not occur.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICS users.                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: The JVMLOG output for a JVM server is   *
    *                      incomplete.                             *
    ****************************************************************
    A JVMSERVER is enabled with the CICS region's SJ tracing set to
    OFF, 1, 2 or 1-2.
    
    Regardless of the LOG_LEVEL JVM profile option, the dfhjvmlog
    file will be incomplete.  The file will only contain output from
    CICS' C code that runs within the LE enclave of the JVM.  The
    file will not contain output from CICS' Java code.
    
    The same problem occurs if the JVM server's JVMLOG output has
    been redirected to the JOBLOG or a DD card.
    

Problem conclusion

  • CICS has been updated to ensure that the LOG_LEVEL JVM profile
    option is respected when determining the output to be written
    to a JVM server's dfhjvmlog file.
    
    Additionally, the "Version History" section within the javadoc
    package summary of com.ibm.cics.server (JCICS) has also been
    updated to remove an IBM internal story number and to fix
    alignment of the text.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH65227

  • Reported component name

    CICS TS Z/OS V6

  • Reported component ID

    5655YA100

  • Reported release

    500

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2025-02-12

  • Closed date

    2025-03-31

  • Last modified date

    2025-04-02

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    UO02646

Modules/Macros

  • DFJ@H239 DFJ@H356 DFJ@H361 DFJ@H427 DFJ@H581 DFJ@H596
    

Fix information

  • Fixed component name

    CICS TS Z/OS V6

  • Fixed component ID

    5655YA100

Applicable component levels

  • R500 PSY UO02646

       UP25/04/01 P F503

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSGMGV","label":"CICS Transaction Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.2","Line of Business":{"code":"LOB70","label":"Z TPS"}}]

Document Information

Modified date:
02 April 2025