IBM Support

PH27480: DFHSJ1109 BUNDLE INSTALL INTO JVM SERVER HAS FAILED WITH REASON CODE NO_BUNDLE_IN_VERSION_RANGE, AND INSTALL OTHER BUNDLES STOPS

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • CICS is not able to install an OSGI bundle with a version that
    is not in the version range of the OSGI bundle file.
    
    DFHSJ1109  An attempt to determine the highest semantic version
               of the OSGi bundle with symbolic name
               xxxxx referenced by bundle part xxxxx of BUNDLE yyyyy
               to install into JVMSERVER
               zzzzz has failed with reason code
               NO_BUNDLE_IN_VERSION_RANGE.
    
    subsequently a system dump SJ0001 is written with the following
    message:
    
    DFHSJ0001 An abend (code 0C4/AKEA) has occurred at offset
              X'6B28' in module DFHSJJS.
    
    
    and the installation of all other bundles is stopped for that
    JVM server.
    
    CICS continues to startup, the JVM server is enabled, however
    all OSGI bundles are disabled.
    
    This problem was caused by code added with APAR PI79692.
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICS users.                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: CICS issues message DFHSJ1109 which is  *
    *                      then followed by an abend S0C4 at       *
    *                      offset X'6B28' in module DFHSJJS.       *
    ****************************************************************
    An OSGi JVM server is being started up and a series of OSGi
    bundles are queued up to get installed when the JVM server
    completes initialising. The bundles are using version ranges and
    one of the bundles is not within the specified range. Message
    DFHSJ1109 is issued with a reason indicating there were no
    bundles in the range, and the bundle gets removed from the chain
    associated with this JVM server.
    The next bundle should now be processed, but instead an attempt
    is made to call DFHRLRO NOTIFY which should should only be done
    if a suitable bundle had been located and a new sjbun created.
    As this is not the case and new_sjbun, from which the domain
    call parameter list is created, does not exist we incorrectly
    pass references from low core instead which leads to the 0C4
    abend. This causes a severe error from DFHSJJS and the
    remaining bundles are not enabled.
    

Problem conclusion

  • The code has been amended to only perform the DFHRLRO NOTIFY
    call if a new sjbun was actually created.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH27480

  • Reported component name

    CICS TS Z/OS V5

  • Reported component ID

    5655Y0400

  • Reported release

    100

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-07-16

  • Closed date

    2020-11-24

  • Last modified date

    2020-12-01

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

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

    UI72744 UI72745 UI72746

Modules/Macros

  • DFHSJBD  DFHSJJS  DFHSJRL
    

Fix information

  • Fixed component name

    CICS TS Z/OS V5

  • Fixed component ID

    5655Y0400

Applicable component levels

  • R100 PSY UI72746

       UP20/11/25 P F011

  • R200 PSY UI72745

       UP20/11/25 P F011

  • R300 PSY UI72744

       UP20/11/25 P F011

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.

[{"Line of Business":{"code":"LOB35","label":"Mainframe SW"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGMGV","label":"CICS Transaction Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.4"}]

Document Information

Modified date:
02 December 2020