IBM Support

IT16629: MQCXP.SecurityParms returned by exit must remain usable by MQ until MQXR_TERM

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as documentation error.

Error description

  • If the security exit does not leave the MQCXP.SecurityParms
    pointer it gave to MQ addressable and with valid contents until
    the moment it is called with MQXR_TERM, then unpredictable
    results may occur.
    
    For example:
    AMQ9557: Queue Manager User ID initialization failed for 'xyz'.
     EXPLANATION:
     The call to initialize the User ID 'xyz' failed with CompCode 2
     and Reason 2595.
    
    Such a problem can happen if the user code invalidates the
    storage at a pointer via MQCXP.SecurityParms or reuses it for
    some other purpose.
    
    The MQ product documentation did not explicitly state that the
    user is expected to leave the contents of that memory stable,
    until the time when it is called wtih MQXR_TERM.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users who write security exits for use with MQ.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    The writer of the exit must ensure that, if they pass a MQCSP
    data block to MQ via the MQCXP.SecurityParms, that this memory
    area remains good until MQ calls the final call to the exit,
    with MQXR_TERM.
    
    The MQ documentation was not clear on this point, and a user
    found a problem when they freed the block too early.
    
    http://www.ibm.com/support/knowledgecenter/SSFKSJ_9.0.0/com.ibm.
    mq.con.doc/q016800_.htm
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    IT16629

  • Reported component name

    WMQ BASE MULTIP

  • Reported component ID

    5724H7251

  • Reported release

    800

  • Status

    CLOSED DOC

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-08-25

  • Closed date

    2016-09-22

  • Last modified date

    2016-09-23

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

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

Fix information

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0.0.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
23 September 2016