IBM Support

PH12685: A monitoring interceptor throws a NullPointerException for an unauthorized z/OS Connect EE user ID.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as unreproducible in next release.

Error description

  • Calling an API under a user ID which is authenticated but not
    authorized to invoke the API in z/OS Connect EE causes a
    NullPointerException to be thrown by the OMEGAMON for JVM
    monitoring interceptor:
    
    com.ibm.omegamon.kjj.zosconnect.KJJ_ExtendedInterceptor
    .postInvoke(KJJ_ExtendedInterceptor.java:417)
    
    and message:
    [KJJ_ExtendedInterceptor] J KJJZC0002E An error occurred in
                                postInvoke: null
    
    The expected BAQR0409W message is issued to record that the
    user ID is not authorized to perform the request, but the null
    pointer errors should not be produced.
    
    Additional search words: msgBAQR0409W msgBAQR0409 BAQR0409 NPE
    msgKJJZC0002E msgKJJZC0002 KJJZC0002
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of z/OS Connect EE V3.0            *
    *                 monitoring interceptors.                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: A null timestamp is passed to           *
    *                      monitoring interceptors during          *
    *                      postInvoke processing when an           *
    *                      unauthorized z/OS Connect EE user ID is *
    *                      used.                                   *
    ****************************************************************
    Under some circumstances no value was provided for the
    TIME_ZOSCONNECT_EXIT data key during postInvoke processing. This
    could cause the monitoring interceptor consuming this data to
    throw a NullPointerException.
    
    The problem was originally reported with OMEGMON for JVM, but
    could be encountered with any z/OS Connect EE monitoring
    interceptor.
    

Problem conclusion

Temporary fix

Comments

  • z/OS Connect EE has been changed to ensure that the
    TIME_ZOSCONNECT_EXIT field is correctly populated and passed to
    monitoring interceptors.
    
    The fix for this APAR is expected to be delivered by the PTF for
    z/OS Connect EE V3.0.23.0 (PH13344).
    

APAR Information

  • APAR number

    PH12685

  • Reported component name

    Z/OS CONNECT EE

  • Reported component ID

    5655CE300

  • Reported release

    000

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-05-31

  • Closed date

    2019-06-17

  • Last modified date

    2019-06-17

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

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

Fix information

  • Fixed component name

    Z/OS CONNECT EE

  • Fixed component ID

    5655CE300

Applicable component levels

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSNPJM","label":"IBM z\/OS Connect"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.0","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
14 February 2023