I got two hits when searching CSQMPRUM, APAR PI28005 and APAR PI06260 which is a sysroute of the other. APAR text etc is the same.

The APAR text contains the phrase "... and has invoked CSQMPRUM to put the message to the dead-letter queue." This suggests to me that the CSQMPRUM is the routine in Message Manager (CSQM is Message Manager) that handles DLQ-ing a message, that is, building the DLH and filling in appropriate queue names, reason codes and so on, in the header.

If application messages have been placed on the DLQ, there will be a reason in the Dead-Letter Header (DLH) to say why. Can you tell us what that reason code is?

You shouldn't need to be concerned about what CSQMPRUM is, unless it is failing to put the messages onto the DLQ like the APARs above, but instead focus on why these messages ended up on the DLQ. Where did you see CSQMPRUM? Did you get an error message in the MSTR joblog with CSQMPRUM as the csect insert? Or did you see it somewhere else?

The reason why, and where the messages were supposed to go, should all be contained in the DLH. Can you add that information to your question?

Cheers,
Morag

Again, I would encourage you to look in the Dead-Letter Header written on the front of the messages placed on the Dead-Letter Queue. Two of the fields in that header are:

• DestQName (Name of original destination queue)
• DestQMgrName (Name of original destination queue manager)

If you believe that the DLQ-ing routine is putting messages that were destined for a different queue manager on it's DLQ, this will be apparent from the contents of those two fields. However, I would suggest that this is more likely because the original putter was doing a put to Queue @ QMgr where the QMgr was not local, rather than the DLQ-ing routine deciding to DLQ across a QSG. Just a thought.

You didn't say where it was that you saw the "CSQMPRUM" name? Did you see an error message with it, or was it in the DLH?

Cheers,
Morag