DSXchange

Hi, How to connect to a MQ cluster to read messages using the MQ Connector stage? I have an MQ cluster consisting of 4 Queue Managers (QM) - to which Message Broker (MB) is publishing. DataStage job has to read the published messages and process them. The messages published by MB is available across...

Hi, I have a Publish job using MQ Connector Stage in Client mode - set to use Publish/Subscribe mode, publishing records/messages with a Topic. When the Message Type is set to Default i.e, Datagram - everything works well and the messages are routed to the subscription queues correctly by MQ. But wh...

Hi, We have just moved over to version 8.5 and I see that $DSHOME/bin has not been included in the dsenv file. Typically I have seen the $DSHOME/bin always included as part of the PATH environment variable. How this was noticed was - a job sequence which was designed to call dsjob in a Routine Activ...

Given that ABAP stage also does not support IN CLAUSE AS OF THIS TIME IN VERSION 8.0.0 ( engineering is working to fix that bug) I am curious if any one had experience of using cluster table and joining it with a transparent table. If you were to do this in a stand-alone ABAP program how would you ...

wow!! That was a lot of information...Helped to set things in the right perspective. Thanks Ernie.

Let me take sometime to digest and think over this. Meanwhile, marking this thread resovled.

Aneesh

Works like a charm!!! Tested it out having the XML Output before the final queue as well, and it worked. Thanks for holding on till the end, Ernie. Now before I mark this as resolved, I have a couple of questions regarding the always-on topology. a) Prior to v8.x - can we not have an always-on Paral...

Ernie!!!!

That seemed to have done the trick!!! :D

The interprocess row buffering, when i disabled it, messages are moving out to the target queue... I am still testing it to make sure that I aint day dreaming...

Will update here in sometime!

Aneesh

Hi Ernie...

I haven't touched anything on the interprocess row buffering settings. And I am not sure how to go about it either... Can you throw some light on it, so that I can check it out here from my side.

Also tried these designs- 1. MQ------>XMLInput---------->Trx-------->Oracle Same result, with no data being written into the database. Had set options in the MQ stage - - Destructive Read - Commit/Backout only once at the end of the job As soon as a message comes into the queue, it disappears (which...

Not sure if i am missing out anything here. My XML message - <?xml version="1.0" encoding="UTF-8"?><root><title>My First XML Document</title></root> XML Xpath for table definitions - only 2 fields defined in XML Output. /root /root/title/text() -------- Set as repeating Element T...

I have another question... more because of a post that talked of an IBM patch causing an issue - almost similar... The Message Limit in the MQ stage if set to 5 - and suppose the queue has only 3 messages, is it supposed to wait till there are 5 messages in the queue to write all of them together in...

If it is only a transformer it works fine and writes the message out. The issue seems to be the transformer in combination with the XML Input stage , as you mentioned.

Also tried out with an Oracle database at the target with commit frequency to 1 - nothing was written into table in the always-on mode. When the job is run with message limit set to 1, the record was written into the out queue as well as into the database. Still not getting a clue as to what is happ...

Ernie, Set everything to 1 - rows per message and rows per transaction. Still the same result - i.e, no output seen in the queue. If I keep another link from the XML input straight to another Queue - the output from the XML input stage is written to this queue - but still nothing shows up in the que...

Thanks for your time Ernie! Thats what I thought! Transformers have been in use for long time and a XMP input+Transformer seemed like quite a normal and regular requirement for an always-on job (any job for that matter). But eow was the only issue I could think off, why messages were not getting wri...