Commerce Manager 7.6

Formally known as "Mercator Inside Integrator 6.7", DataStage TX enables high-volume, complex transactions without the need for additional coding.

Moderators: chulett, rschirm

Post Reply
edi1fmj
Participant
Posts: 3
Joined: Tue Nov 07, 2006 2:06 pm
Location: new jersey

Commerce Manager 7.6

Post by edi1fmj »

Is there a documentation or procedure on how to add an Inbound MQ connection to Commerce Manager using the StampandSort map?
jvmerc
Participant
Posts: 94
Joined: Tue Dec 02, 2003 12:57 pm

Post by jvmerc »

Look at the adapters PDF should be something there.
edi1fmj
Participant
Posts: 3
Joined: Tue Nov 07, 2006 2:06 pm
Location: new jersey

Post by edi1fmj »

jvmerc wrote:Look at the adapters PDF should be something there.
Thanks.

I was able to modify the stampandsortqueue to do an MQ GET successfully with the SourceEvent turned to ON and with the Trace ON (-QN <queue name> -QMN (queue manager> -T). Since it is always ON, it keeps on looking at the queue for messages. If there is no message it returns an error code 2033 and the logs keeps on getting bigger. Is there a way of bypassing the error code 2033 from generating into the log?

Thanks.
jvmerc
Participant
Posts: 94
Joined: Tue Dec 02, 2003 12:57 pm

Post by jvmerc »

I'm not sure. We aren't using MQ. Is it comming up in the log file as a warning or an error?
edi1fmj
Participant
Posts: 3
Joined: Tue Nov 07, 2006 2:06 pm
Location: new jersey

Post by edi1fmj »

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)
jvmerc
Participant
Posts: 94
Joined: Tue Dec 02, 2003 12:57 pm

Post by jvmerc »

I guess my question was related to -- were you talking about the trace or log file? As far as I'm aware the trace file gives you the best adapter error messages.

Have you googled the error code?
Post Reply