DSXchange

If you are using "ls" in the External Source Stage, it is unlikely to split the document into individual strings. ....meaning that the problem, if you are truly sending in filenames, is somewhere else. Test it separately by just having a transformer in front of the XML stage and send the f...

also...check if you have accidentally set the "collect operational metadata" setting to "on" at the project level (not recommended).

Ernie

Look thru here for entries on "Information Services Director" or "ISD" or "WISD"..... ...there is also a special category for such threads...

Ernie

Do a lot of searches in the forum here --- there is a lot of rich info..... Also...are you interested in having DataStage/QualityStage "be" a web service, or having a DS/QS Job "call" some external web service? Knowing that will help in your searches and review of many existing t...

I have a draft entry for my blog on this subject, but never got around to finishing it and publishing it. If you use a Transformer in Server with ODBC, as Craig notes, and get yourself very familiar with the "Transaction" settings, you can set up (for example) four links coming from your T...

There is currently no command line for performing enable/disable.

Ernie

This is one of those things that EE historically cannot do without a custom Operator. The new "DTS" helps, but there are still scenarios, such as non-Oracle and DB2 sites that need explicit Rollback and Commit functionality. If you need this, use a Server Job with ODBC and a single Transfo...

No...I thought you meant a true HTTP based "url" .....remotely at a web site somewhere......so I passed in (in my case, from a transformer) the full blown url itself ---- "http://<host>:<port>/myDocs/myDocument.xml", just as I would in the address bar of IE.

Ernie

Hi Craig... Haven't done this in a long time, but went back and dug up a job, and then put an xml document on a local web server and...... ....it worked like a champ. I'm sure there are 100 caveats, from HTTPS authentication issues, firewalls, etc. that could thwart you....but from a pure-play persp...

Data Elements are a concept whose usage was never fully appreciated and now they are like your appendix.....has a little bit of value, but goes mostly un-used. They started as "application data types" and provided a way to include "automatic" transformations or to apply functions...

I simply meant to make sure that MQ Client is working just fine on that machine, outside of DataStage....that way, once you get past the datastage libpath issues, you know that MQ will be working ok. You'll know it's working when you put in a bogus queue name or queue manager and get a variety of 20...

It seems that it's not finding the Connector info itself (way before trying to locate MQ), so looking at libpath is probably a good direction for your debugging. You of course also need to have the MQ Client software installed, configured and working at your DS server.

Ernie

I haven't tried anything like this, but I tend to think that it will be very difficult if not impossible, because the CFF underpinnings combine a lot of stuff. ...been awhile since I've looked under the covers, but when it was first written, the EE CFF was ultimately reaching out to the already exis...

Could be many things. Do other jobs deploy? What is different about "this" job? Does it use special stages? Does it die at deployment?...or not until you send it a row? If it dies for a row, what are you sending it? ...does it matter what type of data you send it? What about the datatypes?...

Hard to say. Assuming that you are current with patches and things, one potential scenario is that you are in need of more memory. EE Jobs generate a lot of processes. 5 to 7 Stages apiece is not a lot, but when you start adding things up, it can become large. There are things you can investigate......