DSXchange

You write a custom routine in DataStage BASIC that calls the DSExecute() function, it allows you to call operating system commands which includes scripts. In a transformer, this can be called for every row.

uzl wrote:I have created a new topic :

Code: Select all

http://www.dsxchange.com/viewtopic.php?p=434760#434760

Why?

I didn't ask you to, rather I told you that I had already done that for you.

FYI - I've removed that post and relocated the additional information you put there back in this thread.

Details, please. How did you configure it and what did the output look like?

Get the official answer from your support provider and let us know. The concensus here is that it's not allowed and that your consultant is mis-remembering.

Well... start by looking at the Pivot stage as that's exactly what it does.

That would be a PX answer. For a Server job, create a routine that leverages DSExecute() and call that in your transformer.

Well... technically... I assumed nothing, merely wondered aloud about the nature of the beast. Thanks for the clarification and the whack upside the head. Sir.

So you're saying that mine was incorrect and incomplete?

It makes sense when reading from a sequential source, but a relational one... not so much.

So... under what circumstances would a reject link from a relational source be used / triggered?

So, not really related to the original topic so off you go to one of your own. Now... "same result". Are you saying that a Job Activity where the job completes with warnings does not fire the Otherwise trigger? Can you tell us what compilation options you have enabled in the Sequence and w...

As noted, if the job needs to be changed then you start the cycle over. Otherwise simply reset and then rerun it. Nothing about this topic changes the fundamental way things work.

Hmmm... it's been a while and that's really Wurlod Territory but seems to me that it is selecting records where the key is not empty and ordering the output by the first field. Not sure under what circumstances the key could be empty, however.

Of course triggers work, wouldn't be much point to the Sequence jobs without them.

Rather than pick and choose specific status values, try using an "OK" and an "Otherwise" trigger. Are you trying to implement what Kim posted?

So... basically a checksum?