Can IBM MQ do something about errors from the underlying resources such as EIO (Input/Ouput errors from disk)?

+++ Answer:

No, there are no MQ parameters that can be tuned for the MQ queue manager to ignore or overcome unexpected errors from the underlying resources.

.

You will need to consult with your support team for the Operating System, the File System, the Network, etc.

+++ Examples:

a) '5 - Input/output error' from read
FDC with probe XY511000 reporting that "read" calls from the operating system have failed with:
| Comment1:  ('5 - Input/output error' from read.)
or
| Probe Description :- AMQ6118: An internal WebSphere MQ error has occurred
| Arith2            :- 5 (0x5)  

You may have a question: OK, I see that there is an error number 5 ... how do I know what that means?
The following presentation has a good discussion on errno and it can be found in pages 8 and 9 of the PDF:
https://studylib.net/doc/18210057/tcp-ip-configuration-and-diagnosis-with-websphere-mq--par...
TCP/IP Configuration and Diagnosis with WebSphere MQ: Part II, by Justin Fries

The error number 5 is mapped to:
EIO              5      /* I/O error */
An I/O error occurred while reading from or writing to a file system.
.  
EIO errors are serious errors reported from the underlying filesystem.  
They are not caused by MQ, other than MQ making use of calls provided by the operating system.
.  
b) '16 - Device busy' from fcntl
.
| Probe Description :- AMQ6119: An internal WebSphere MQ error has occurred  
|   ('16 - Device busy' from fcntl.)  
| Arith1            :- 16 (0x10)  
| Comment1          :- '16 - Device busy' from fcntl.  

The error number 16 corresponds to:  
 EBUSY            16   /* Resource busy             */  

This OS call "fcntl" is used to manipulate a file descriptor.

+++ Detailed scenario for illustration purposes

.

There is nothing that can be done from an MQ perspective either to investigate further, or to fix this problem.
The problem is due to some fault in the operating system, the file system, the network, etc. 
.

It is worth to explain that MQ does NOT interact directly with the File System.
Instead... 

- MQ asks the Operating System (OS) to read a file.  MQ now waits for a reply from the OS.

 (Note: the following interactions are totally outside the scope of MQ!)
- In turn, the OS interacts with the appropriate components to request to read a file. For example, if the file resides in an NFS mounted directory, then the OS will ask the NFS Client to read the file.  
- In turn, the NFS client will interact with the network layer to talk to the remote NFS server to read a file.  
- In turn, the remote NFS server will interact with the File System.  
- The File System is reporting an error EIO and passes it to the NFS server.  
- In turn, the NFS server passes the error EIO to the NFS client.  
- In turn, the NFS client passes the error EIO  to the OS.  
- In turn, the OS passes the error EIO to the MQ queue manager, which is NOT expecting this error and thus, generates an FDC.

 (Note: after the control is returned to MQ, then MQ proceeds with its operations.)
- In the case of an Active instance of a multi-instance queue manager, the Active instance will terminate allowing for a failover to the Standby instance.

+ Related article for MQ Multi-Instance Queue Managers

https://www.ibm.com/support/pages/node/473409
AMQ7280 IBM MQ queue manager appears unresponsive, Probeid ZX155001 component zxcFileLockMonitorThread error lrcE_S_Q_MGR_UNRESPONSIVE
Common error from file system: EIO

+ tags:
Author: Angel Rivera;

+++ end +++