DSXchange

Request you to plz help.. I'm curious what you think was going on here? Helping. And on a Sunday for me no less. :? I'm assuming you're already getting the string into a Timestamp. There are various functions you can look into to help here: MicroSecondsFromTime to get the part you need to test. Tim...

Tell me about it, we've tried... all four of us on this project came from a DataStage background and have worked together off and on around town on DS projects, funny we all ended up here doing Informatica. "Do you know any good ETL developers?" "Why yes, yes I do. <cough>" :wink...

Or just use the -s approach.

Split your question out to its own post rather than in the 5 year old 7.5 era post that you picked as lots of things have changed since those days. We really need to know your version of DataStage and the O/S it is installed on to be able to help... and the topology , what components you have instal...

What are your source and target? What are the actual data types involved? Mostly wondering if these are actually Timestamps or strings or some mixture of the two. I'd also be curious if you tried anything and what issues you've seen attempting to fulfill this requirement.

Show us what you tried.

Why not simplify things and use the -s test option directly? True if file is non-empty, false if zero bytes. No need for head -1 or other extra steps.

ray.wurlod wrote:In earlier versions you have to do all the coding yourself

It's not really all that hard. You dang kids with your fancy smancy SCD stage, get off my lawn!

All of your substring lengths should be 2 based on your requirement:

mm=[6,2]
dd=[9,2]
yy=[3,2]

You seem to think that substring syntax is [start,end] when in fact it is [start,length]. Correcting that should help.

On Windows? Hmm... UNIX would be trivial but it's harder in a batch file. Try googling for something like "DOS test file size" and code samples should turn up. As Ray noted, all you'd have to do is pass back a non-zero exit code from the batch in that case for the job to notice and abort.

Moved over to the Dark Side... doing Informatica for the DoD now.

Why can't it test the size of the file after it 'extracts' it?

Added that to your example code, Mark. Thanks for the assist, in my fourth year of living DataStage-less so no ability to test a darn thing.

We really need to get past "doesn't work" to what the actual problem is and where it is happening. As noted, let's start with showing us what actually gets logged when the job starts as all parameters in play are logged in one of the first messages. After that, if it looks ok, would be to ...