Fixes are available
APAR status
Closed as program error.
Error description
An API "after connect" exit can trigger unexpected AMQ7216 error messages "An API Exit initialization function returned an error." if an MQ connection attempt fails. One circumstance where you might find a connection attempt repeatedly failing is if you try to connect to a multi-instance standby queue manager.
Local fix
Problem summary
**************************************************************** USERS AFFECTED: You may be impacted by this problem if you have an "after connect" API exit and an MQ connection attempt fails. Platforms affected: All Distributed (iSeries, all Unix and Windows) **************************************************************** PROBLEM SUMMARY: Having an "after connect" API exit can cause logging of unexpected failure messages "AMQ7216: An API Exit initialization function returned an error." if an MQ connection attempt fails. That is due to the API exits being loaded and unloaded during the MQ connection, in order to execute the "after connect" exit. The unload has inadvertently picked up the connection attempt failure code and caused it to be returned as though it was a failure from the API exit unload. MQ then reports the AMQ7216.
Problem conclusion
The unloading of API exits can occur in a variety of circumstances in MQ. In some circumstances any Compcode and Reason values already established for the containing function were being fed into the unload call. The call then returned a possibly revised Compcode and Reason. The logic has been modified so that API exit unload has its own, separate Compcode and Reason, uninfluenced by any already established values of the containing function. The containing function then treats the return from the unload in a similar way to other potential failures within the containing function, to establish a final Compcode and Reason for return from the containing function. The "containing function" is typically an MQI function, e.g. MQCONN. Some small revisions have also been made to the API exit load call to ensure that it consistently establishes Compcode and Reason. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v7.5 7.5.0.4 The latest available maintenance can be obtained from 'WebSphere MQ Recommended Fixes' http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037 If the maintenance level is not yet available information on its planned availability can be found in 'WebSphere MQ Planned Maintenance Release Dates' http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309 ---------------------------------------------------------------
Temporary fix
Comments
APAR Information
APAR number
IV46858
Reported component name
WMQ AIX V7
Reported component ID
5724H7221
Reported release
701
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2013-08-09
Closed date
2013-10-08
Last modified date
2016-11-14
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
WMQ AIX V7
Fixed component ID
5724H7221
Applicable component levels
R701 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSDEZSF","label":"IBM WebSphere MQ Managed File Transfer for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0.1","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
31 March 2023