DSXchange

I applaud your efforts in digging deeper into it. I haven't had a chance to test any scenarios and unfortunately, am several releases ahead in my environment in both DS and MQ. I have done this in the past, though, so it is strange, but there may be a release dependency that I hadn't run into. The m...

Yeah...let me know what you find out. I _always_ have a transformer in the middle of my jobs... I do it just as a safety gap in case I need to alter a datatype or change something (inevitably, I always need it). What happens if you have only a Transformer? Maybe it's just somethinig odd in combinati...

Well...first of all, for future purposes, xmlInput and Transformer are not going to block end of wave.....only xml OUTPUT stage is the concern. Something else is going on... Set everything to 1..... rows per message, rows per transaction...you want everything if possible to be "1". Questio...

Think of MWB as the "binoculars" into XMETA. If you add various bits and pieces while inside of IA, they will, or should, appear inside of XMETA and therefore, Metadata Workbench. Every once in awhile I find an attribute that is not being exposed in the Workbench, but that is rare, and cer...

Spend some time on the forum here...there are MANY threads on xml....look for the links that talk about the "best practices" document, etc. There's lots on reading and writing of xml.

Ernie

No.

Check out the xml stages...each of them has some degree of ability to run xslt (albeit within the design of the stage, usually for producing columns of output to be sent to a link). Otherwise, search the forum...there are lots of ways to invoke things outside of DataStage, assuming that you can call...

...by the way... xmlOutput is (well...it can be, if you choose aggregate) a blocking Stage, as is the Aggregator, and (usually) Sort. Those are usually the biggest blockers in an end of wave scenario. ....so your original premise may be a concern here. ....even if you resolve the Transformer problem...

Hi Aneesh... I use a transformer all the time in my Server jobs...never have seen an end of wave issue caused "just" by the Transformer....... but there are other things to consider: a) how are you detecting that the messages are written (or not)? b) are you ensuring that you are writing o...

No. Release 7.x requires that the MQ Server is co-installed with DataStage. Release 8.x supports MQ Client API.

Ernie

Exactly as Ray has said.... if you import a Shared Table in IA, it's just "there" in Metadata Workbench. An exception to this are the "results".....results of analysis have to be published for a selected table or column (with notes, etc.)....... results describe details and data ...

In your first post, you say that you already have the queue manager, queue name and userid/pwd for MQ? If so, I assumed it's already installed and available? Where did those values come from? If not, then yes, you will need to have a full MQ configured with it's server and Queue Manager at the same ...

in 7.x, your main requirement is that the MQ Server is installed CO-resident with DataStage.... Other than that you should be good to go....be sure that you are able to use MQ series' own tooling outside of DataStage to put, read and do things to MQ. That will be critical if you need to debug someth...

Hard to say exactly........some things to look at are: a) what "exact" release of 8 are you on? Early release 8 had issues with namespaces...there really aren't any here, but who knows, having them in the namespace area might trigger something on those early releases of 8 (most all of thos...

..I would rephrase this not as a "workaround" but as "acting as designed" :) It's just semantics, but keep means "browse"....multiple readers of the same queue, when using browse, do not lock out other readers........the same behavior will occur if you launch "n&qu...