DSXchange

FYI - In essence they reject "back up" the link and can then be captured in a later link that is marked as a Reject link or has a constraint that checks the REJECTED link variable.

It seems to me that the problem of building dynamic SQL like that would be much easier to solve in a Server job.

Server or Parallel job? You marked it as one and posted in the other's forum.

As long as you don't mind the delimiters it brings to the party. I prefer an unformatted YYYYMMDD date so it sorts 'properly'.

In a Server job the reject link goes on the transformer feeding the target, not the target itself.

Please advise me to create XSD file with the XML Outputfile or XML Stage. You can't. They can leverage them but not create them. As noted, you'd need an XML tool to do that from an existing XML file... there are several out there, some may even be free. Keep in mind the fact that that approach coul...

Ah... thanks for the clarification.

Kryt0n wrote:This and your previous related post got me intrigued, I didn't even know they allowed two input links to a connector so had always split the streams.

This has always been allowed in Server jobs, guess it finally came to the Parallel world with the Connectors.

An exact search here for "scientific notation" turned up a number of matches, many marked as Resolved. Check those out.

eostic wrote:there's another question.....who needs an xsd?

Not xmlOutput.

No, it doesn't need it but it sure makes getting the proper XPath Expressions into DataStage easier... and those it needs.

Whomever you are creating XML for should have given you the xsd to use.

Yes, as long as you have the executable properly installed on your client.

Have the SysAdmin for the ETL Server check sendmail status on that machine.

Ask for an example.

That's not supposed to matter but who knows? Worst case it seems you could do the deletes first from the data and then the inserts as either separate steps or as properly ordered targets.