DSXchange

Out of curiousity, what version of DataStage was your old server running?

That would be pretty trivial in a Server routine. Any chance of using a BASIC Transformer in your job?

Really? Huh, learned something new. Perhaps an "ODBC thing"... could you post the syntax you used for me, please?

That's the nature of sequential media.

You may be able to do something magical under the covers with C or something similar but for a "pure" DataStage solution there's no magic that I've ever seen. Of course, our resident Magician may say otherwise.

You can't. Split the flow and only send the ones needing the SP call down one branch, all others down another. Join the stream back together after that. That or call it each time and conditionally use the result. Of course, that depends on what exactly it is your SP is doing. Another option - code t...

The short answer is no. You read in the file, update whatever needs updating and then write the result out to a new file. Of course, you could rename the new back to the old when you are done.

Which job was this message from - the Sequence job itself or the "split job"? What kind of job is the split job?

QC? As in the Quality Center product from HP?

I was not sure whether I can continue with the old one or not so start a fresh one. Of course you can. It's your topic and the same topic. :? Best way to do this would be via a script, otherwise are you "allowed" to write a BASIC routine and leverage that in your Sequence? It could do the...

Not sure why you felt the need to start a new post. For those following along, this is a continuation of this topic.

Unless something has changed that I'm not aware of, the FileWatcher stage does not support wildcards. Hence the suggestion to watch for a specific 'trigger' file.

Yes indeed, it is! I really should go.

What exactly is in your zip file? 4GB of what? That just means it couldn't find the end of the first record... assuming you even have records in there.

I figured we were having a communication issue and you already had the solution you needed.

Thanks Ray... simple enough.

Seriously? So if 200 records were rejected you'd like to send 200 separate emails?

Now you've got me curious. Since I would never implement any such thing, perhaps Ray can share with us the mailbomb technique? From a purely informational / educational standpoint, of course!

Just want to emphasize there's no "while rejecting records" part to this but doing so afterwards is common and straight-forward.