Fixes are available
APAR status
Closed as program error.
Error description
The following is an example of one occurrence of the failure, but a possible match for this problem could be 'Operation not permitted' seen in any FDC :- The Websphere MQ multi-instance queue manager running on Linux receives error EPERM (1 - Operation not permitted) when opening the master lock file. An FDC is created with Probe ID XY513000 indicating "Operation not permitted" when trying to open file: /var/mqm/qmgrs/QMGRNAME/ master WebSphere MQ First Failure Symptom Report ========================================= Probe Id :- XY513000 Component :- xcsQueryFileLock Program Name :- dspmq Major Errorcode :- xecF_E_UNEXPECTED_SYSTEM_RC Probe Description :- AMQ6119: An internal WebSphere MQ error has occurred ('1 - Operation not permitted' from open.) FDCSequenceNumber :- 0 Arith1 :- 1 (0x1) Comment1 :- '1 - Operation not permitted' from open. --------------------------------------------------------------- MQM Function Stack lpiSPIQueryQMStatus zutQueryQMFileLocks xcsQueryFileLock xcsFFST
Local fix
Problem summary
**************************************************************** USERS AFFECTED: You may be impacted by this problem if the operating system unexpectedly returns EPERM from the fcntl function rather than the traditionally expected EACCES for a permissions failure. Platforms affected: Linux (Power),Linux (s390x),Linux (x86),Linux (zSeries) **************************************************************** PROBLEM SUMMARY: It has recently occurred that on Linux, fcntl appears to return EPERM from the fcntl function when EACCES used to be returned for a permissions failure. There may have been a Linux change causing that to happen.
Problem conclusion
There is only a relatively subtle distinction between EPERM and EACESS. To avoid re-occurrence of this suspected issue, coding of a number of fcntl calls in WebSphere MQ has been revised to treat EPERM and EACCES as equivalent. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v7.1 7.1.0.5 v7.0 7.0.1.12 v7.5 7.5.0.3 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
IV47049
Reported component name
WMQ LIN X86-64
Reported component ID
5724H7230
Reported release
710
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-08-14
Closed date
2013-10-14
Last modified date
2013-10-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 LIN X86-64
Fixed component ID
5724H7230
Applicable component levels
R710 PSY
UP
[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFKSJ","label":"WebSphere MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.1"}]
Document Information
Modified date:
09 March 2021