IBM Support

PH64695: A JVMSERVER was disabled after restart. This problem was caused by an empty server.xml

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Customer saw JVMSERVER is disabled after restart and it was
    caused by an empty server.xml.
    
    EYUCMCIJ E ÝRouter-Init-Thread¨ Ýcom.ibm.cics.router¨ ÝRouter¨
    §Error: main() - Problem detected in Router main method
    com.ibm.cics.router.RouterException: Unable to create Liberty
    server
    .at com.ibm.cics.router.Router.initLiberty(Router.java:778)
    .at com.ibm.cics.router.Router.initOSGi(Router.java:401)
    ...
    
    Caused by: java.lang.Exception: Problem parsing the WebSphere
    Application Server Liberty server.xml file
    /cmci/AAAAAAAA/EYUCMCIJ/wlp/usr/servers/defaultServer
    .at com.ibm.cics.router.wlp.internal.LibertyServerImpl.parseCo
    nfig(LibertyServerImpl.java:791)
    .at com.ibm.cics.router.wlp.internal.LibertyServerCmci.configu
    reCMCIServer(LibertyServerCmci.java:140)
    ....
    
    Caused by: org.xml.sax.SAXParseException; lineNumber: 1;
    columnNumber: 1; Premature end of file.
    .at java.xml/com.sun.org.apache.xerces.internal.parsers.DOMPar
    ser.parse(DOMParser.java:262)
    ...
    
    This APAR will improve the diagnostics produced when CICS is
    unable to configure server.xml when a JVMSERVER is enabled due
    to a full file system.
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICS users.                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: JVMSERVER fails to enable and creates   *
    *                      an empty server.xml. A subsequent       *
    *                      attempt to enable the JVMSERVER then    *
    *                      fails due to the empty server.xml.      *
    ****************************************************************
    When starting a JVMSERVER, CICS attempts to populate the
    server.xml. If there is a storage issue, such as a full file
    system, an empty server.xml is created and CICS then disables
    the JVMSERVER.
    
    When this occurs, CICS may not log any useful information to
    explain what went wrong. It also causes any further attempts to
    enable the JVMSERVER to fail due to the empty server.xml.
    

Problem conclusion

  • CICS has been updated to attempt to log any errors that have
    occurred as a result of a full file system when attempting to
    create a JVMSERVER's server.xml
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH64695

  • Reported component name

    CICS TS Z/OS V6

  • Reported component ID

    5655YA100

  • Reported release

    400

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2025-01-03

  • Closed date

    2025-02-11

  • Last modified date

    2025-03-04

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

    PH63038

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

    UI99961 UI99962

Modules/Macros

  • DFJ@H571
    

Fix information

  • Fixed component name

    CICS TS Z/OS V6

  • Fixed component ID

    5655YA100

Applicable component levels

  • R400 PSY UI99962

       UP25/03/04 P F502

  • R500 PSY UI99961

       UP25/03/04 P F502

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.1","Line of Business":{"code":"LOB70","label":"Z TPS"}}]

Document Information

Modified date:
04 March 2025