DSXchange

To quote Walt Disney, "Sometimes dreams do come true".
But for DataStage this dream can quickly turn into a nightmare. It depends on the ease of obtaining the changed metadata. Is it from a DBMS? How is the target metadata maintained and updated?

Start simple. Start with an XML file you know is well-formed XML. That is, can a representative XML file be parsed by a tool other than DataStage. For example can the XML file be opened, in Internet Explorer? Your specfic error sounds like you either have more than one root element or the XML file i...

Ah, The Meaning of Job...

"One thing, just one thing. You stick to that and everything else don't mean sh*#."

"That's great, but what's the one thing?"

"That's what you've got to figure out."

If by file you mean a Sequential File stage as input/output then this may save you a step; SELECT DS_JOBS.NAME AS JOB_NAME FMT '35L', DS_JOBS.CATEGORY AS JOB_CATEGORY FMT '35L', EVAL DS_JOBOBJECTS."@RECORD<6>" AS FILENAME FMT '35L' FROM DS_JOBOBJECTS , DS_JOBS WHERE DS_JOBOBJECTS.OLETYPE I...

Naturally, since records partitioned to nodes via Round Robin may end up in "unmatched" or different nodes when the lookup is performed. This means record "A" in node 2 will not find a hit in the look-up if the look-up record "A" is in node 1. Whereas if you key partiti...

RCP and schema file. You'll have to build the functionality to take your metadata file and put it into a EE schema file format. This schema file is then used as the property of the EE Sequential file stage to read your data with RCP enabled. That's it in a nutshell.

If you changed the comma to a semi-colon, you could have more then one per specfication but the Best Practice is to have multiple specifications.

No. I'm pretty sure it is finding the XSD. I believe te validation of the XML is taking place. It is the reject that is not happening. This now goes to Ernie's comment about a patch. If you have mapped the warning/fatal/informational DS log message to Reject, then it should have rejected upon an imp...

You're almost Golden! The XSD is working since it is correctly identifying the element as a date. You need to change the mapping of the warning from warning to Reject and it will work. You don't have to fully qualify the path unless you want to. You probably should but the XML Input stage IS finding...

I didn't ask if the XPath was correct. I asked if the XSD was defined correctly. That is, within the XML as an element with an attribute of schemaLocation. However, since this is 8.0 there may be other ways to validate. The functionality may have changed. I am in 7.5.3 where the XML must contain the...

You can enter the XPaths manually. If you have the XSD defined correctly, then any typos you make in the XPaths will most likely throw a reject. Have you correctly defined the XSD that will be used to validate the XML?

I agree. Can we assume the final tick and a semi-colon are a cut/paste typo?

You need to define a reject link for your reject link. Just kidding! In order for this to work as a reject within the XML Input Stage, you'll need to Validate the Input XML via schema validation. This means you'll need an XSD. Do you have one? The documentation is very good: xmLPACK_20_Designer.pdf ...

I assume you mean importing by selecting them rather then typing them in. This is not an available option. They have to be typed. It is also not an option in the Server versions of these EE jobs. Both sets are imported the same way -- they are manually typed. Server jobs work, EE jobs fail. Perhaps ...

These stage DLLs appear identical to me Server to EE. Server jobs work with Project Environment parameters, EE jobs fail. Can anyone explain why EE jobs that use the Teradata API or Teradata Multi-load stages feel the need to translate Project Environment parameters? What is the technical rationale ...