APAR status
Closed as program error.
Error description
An application which connects using isolated bindings and performs MQGET processing may generate the following failure data capture (FDC) record: +--------------------------------------------------------------- --------------+ | | | IBM MQ First Failure Symptom Report | | ========================================= | | | | [...] | | License Type :- Production | | Probe Id :- ZC023030 | | Application Name :- MQM | | Component :- zcsSendV | | SCCS Info :- /build/slot1/p900_P/src/lib/zc/amqzcsbx.c, | | Line Number :- 1007 | | [...] | | UserApp :- TRUE | | Last HQC :- 4.0.0-56192 | | Last HSHMEMB :- 0.0.0-0 | | Last ObjectName :- | | Major Errorcode :- zrcC_E_INVALID_HANDLE | | Minor Errorcode :- OK | | Probe Type :- INCORROUT | | Probe Severity :- 2 | | Probe Description :- AMQ6125: An internal IBM MQ error has occurred. | | FDCSequenceNumber :- 0 | | | +--------------------------------------------------------------- --------------+ MQM Function Stack MQPUT zstMQPUT zisMQPUT zcsSendV xcsFFST Within the data blocks of the FDC record, there are references to an EFAULT signal ("Bad address") being returned by the operating system.
Local fix
Change the application or queue manager configuration to use shared bindings
Problem summary
**************************************************************** USERS AFFECTED: This issue affects users of MQ applications which connect using isolated bindings and perform MQPUT Platforms affected: MultiPlatform **************************************************************** PROBLEM DESCRIPTION: A programming error meant that when passing an MQPUT request from an MQ application to the queue manager using isolated bindings, it was possible for uninitialized data to be passed to the operating system. If this uninitialized data was non-null, EFAULT was returned by the OS.
Problem conclusion
The MQ isolated bindings logic, used by isolated bindings applications and the queue manager, has been corrected to prevent this use of uninitialized data. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v8.0 8.0.0.14 v9.0 LTS 9.0.0.6 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
IT28495
Reported component name
IBM MQ BASE M/P
Reported component ID
5724H7261
Reported release
900
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2019-03-18
Closed date
2019-03-18
Last modified date
2019-09-19
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
IBM MQ BASE M/P
Fixed component ID
5724H7261
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":"9.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
19 September 2019