jvmerc wrote:I'm not sure. We aren't using MQ. Is it comming up in the log file as a warning or an error?
It is coming in as an error. Below is a snapshot. Is there another option with trace (-T) where you can bypass 2033?
<17854-005>: [m4mqsListen] (rc = 0) OK
<17854-005>: [m4mqsListen]
<17854-005>: | [intm4mqsObtainQueueNode]
<17854-005>: | | Queue node found: N174.ACI.EDI.OUT2
<17854-005>: | [intm4mqsObtainQueueNode] (rc = 0) OK
<17854-005>: | No message found
<17854-005>: | MQSeries error (ReasonCode = 2033)
<17854-005>: [m4mqsListen] (rc = 0) OK
<17854-005>: [m4mqsListen]
<17854-005>: | [intm4mqsObtainQueueNode]
<17854-005>: | | Queue node found: N174.ACI.EDI.OUT2
<17854-005>: | [intm4mqsObtainQueueNode] (rc = 0) OK
<17854-005>: | No message found
<17854-005>: | MQSeries error (ReasonCode = 2033)
<17854-005>: [m4mqsListen] (rc = 0) OK
<17854-005>: [m4mqsListen]
<17854-005>: | [intm4mqsObtainQueueNode]
<17854-005>: | | Queue node found: N174.ACI.EDI.OUT2
<17854-005>: | [intm4mqsObtainQueueNode] (rc = 0) OK
<17854-005>: | No message found
<17854-005>: | MQSeries error (ReasonCode = 2033)