DSXchange

It's possible that we are chasing the wrong problem.....the directory you see in the error is what the xml stage produces..... First, re-write your Job. Delete the xmlInput Stage and just have a Sequential Stage. Make sure you are getting a proper list of files from that subdirectory in your Externa...

Then treat the data as character, which is what it is. Don't let the software do any kind of interpretation for you. Take 100% control. Make all of your columns char or varchar, pull out the pure strings from the xml tags...... ...focus on the "parsing", and get the strings "as they a...

I haven't tried it in windows in a long time, but memory tells me that it just assumed C: ....pretend that it is Unix, leave out the C: entirely, switch your slashes the other way, and try ls /DataStage/.../.../.../

Ernie

are you using the XML Stage or the xmlOutput Stage?

Ernie

Hi John... Some further detail... The key with lineage for BI reports is finding out whether or not the bi objects were "imported" with already connected database information. That database information becomes the simplest "linkage point" for tying individual reports to something...

There are steps that have to be carefully followed.... Assuming you imported your Cognos metadata successfully, then as Ray notes, you should have lineage from reports and various BI items, back thru the tables in the Implementation Model. A key thing to check is to be sure that the "database c...

Hi Everyone.... The new XML Redbook was published today! I had the pleasure of reviewing it along the way. My colleagues did an excellent job outlining how reading and writing XML content with DataStage and QualityStage was dramatically enhanced (initially in 8.5).... Check it out when you can or be...

this this....number is not contained by type....

.../customers/customer/number/@encrypted

afaik, no.

PS.... I haven't tried it in quite a few releases, but I did a research project years ago where I traced the path of a single row and value, using the debugger, with breakpoints all over the place and then turning inter-process row buffering on or off.....it was very insightful, showing how and wher...

It's a setting at the Job level (job properties) ...OR...might also be at the Project level (something I do NOT recommend). It implements pipeline-style parallelism by default for Server Jobs....there are quite a few threads in here on the subject if you do some searching. As it relates to this part...

Hard to say. There were a variety of patches to the xml Stage in early 8.5....be sure you are at least at 8.5 with FP1 or preferably 8.7.

also check interprocess row buffering...that will dramatically impact the normal default "process each link thru completion" behavior.

Ernie

if they are nested, it can be done with either Stage, and in a single output link...if you use the new Stage, be sure you have at least FP1, and you need the xsd. If you don't have the xsd, you'll need to generate one, or use the xml Input Stage. With the new Stage, initially have a parsing step tha...

are the 5 levels independent of each other? ...meaning, not nested, but entirely independent in meaning and number of occurrences (imagine a company with a node for employees and another node for products). If they are truly independent, then it can absolutely be done with one single Stage, in the o...