Summary
This article provides suggestions for troubleshooting error return code 10032 (CM_ERR_EPIPE).
Resolution
Error 10032 indicates that a communication pipe or socket was broken.
If the 10032 error is originating from the data movers, then it is probably a networking issue where one process, i.e. disk read, is overpowering another process, i.e. network send. The data movers are using sockets and semaphores.
In this case, try setting -noenh to the data movers to change the behavior. In addition, you can remove the -tnd parameter to incorporate the smaller communication packets with the packets that contain the actual data.
If another module is giving this error, e.g. the event handler, then it could also be trying to send data over the network to the job handler. This would not imply a local problem with system pipes. However, if the event handler is trying to communicate with the data movers, i.e. locally, and the 10032 error is received, then use local pipes over TCP/IP pipes (or vice versa) to tweak the system. This is done with the -lcl flag on SSICMAPI.
You could also try to change the TCP/IP sockets from the default non-blocking behavior to blocking behavior. There are considerable differences in behavior for blocking vs. non-blocking sockets in the literature.
So, the relevant SSICMAPI parameters are -lcl [yes/no], removal of -tnd, and -blk [yes/no]. The relevant parameter for the data movers (SSDMBR, SSDMBS, SSDMRS, SSDMRR) is --noenh.
Additionally, check the disk space on the node.