DSXchange

How often are you doing it? Develop a loop in a script with a list of necessary Jobs and you'll have what you need, running multiple exports in sequence........it might take a awhile, but so what? It's unlikely that you are running something like this on every Job, every 5 minutes. I suspect you are...

Check to see if it is a volume issue and not an environment or Oracle issue......send the exact same data to a flat file. ...btw....what binding are you using? I will assume SOAP or XML for now... Write another Job that reads from that flat file and goes to ISDoutput. Publish it as a Service. I will...

I looked into this awhile back, when I was writing a parser in DataStage to read the export as "xml"..... as far as I know, there is no "command line" way to do a wholesale project xml export. You may have to do individual Jobs, by first obtaining a job list, perhaps via dsjob. E...

This "sounds" like an Information Services Director question, and the desire to perform an enable/disable of a particular application at the command line instead of doing it at the "Deployed Applications Workspace" of the Information Server Console (not the Web Console, the conso...

Indeed....the new XML Stage is far faster.....how much faster will depend on a lot of things, like the number of tags, their size, etc. As for your existing Job, consider breaking it up via EE as well as via functions in the Stage itself...I've had success (again, it depends on the document) improvi...

Don't. Best practice is to not format it...it only causes problems for other software and creates wasted space on disk or on the wire. Nowadays just open your xml with a tool (IE, firefox, most editors, etc.) that makes it pretty for you....

Ernie

They should have come along with it. Did you try using the "Export to Metadata Server" directly from IDA?

Ernie

Assuming that the bridge in the Import/Export Manager imports your objects correctly (look at the documentation in the bridge for specific pre-requisites, etc.), you should see, in the WB, a new set of "Host" information (host/database/schema/table/columns) as well as BI model information ...

You can get ODBC via the Import/Export Manager at the client, as well as metadata from things like ERwin.....however, I would encourage you to get the Server connections working, either for ODBC, or more preferably, for native APIs....and then use the "Connector Import Wizard" (as opposed ...

What was meant by that is "use your creative juices"....... If you have your own methods of providing in memory tables and lookups, and are an expert in using Java or C++ and building/manipulating and managing such structures, go for it. DataStage is very extensible. But the code will prob...

Not easily. The sequential stage cannot consistently pick up a "whole" file.....if it has variable length text with stray embedded CRLFs anywhere, it is likely to fail......and maybe not in test, but at some future time....

Ernie

Check out the lineage entries at my blog below. I have lots more in my head and in posts throughout the forum here, or ask other more pointed questions and I'll share what I can think of. There is a team working on a redbook for WB and metadata guidelines too, but that effort is still in the oven. E...

There's nothing automatic, but take a look at "Extension Mapping Documents".....this is a very good way to get data lineage for any kind of process that you may want to represent..... you can make it as detailed as you need to, with column info and transformation rules, or just keep it hig...

hmm. A couple of thoughts and questions about the steps.... a) I believe that IDA 7.5.3 and above will import COBOL to create a Logical Model.....did you import "that" directly from IDA, or did you first create a formal physical model? If you imported the logical, then it will have come in...

Sparse lookup is probably the only easy way (assuming you aren't crafting your own in-memory objects using Java or some other technology)....so that each time you commit a new entry to the database, it will be found by your lookup stage... of course, that means you have to return to the database for...