DSXchange

You just need a null handling mechanism. Do an exact search on 'Null string argument'.

one more help...i need that i should read the date field and pass it as a stage variable to load it into the table.. i want to read only the records not the company name,the ********s and the blank line... how should i do that I thought i gave you the solution in your other post . You will have bla...

You lost me there Kim.

I am running out of ideas now. Build another simple job. And see if that compiles. Do any of your px jobs with a transformer compile?

Need more info, what is your job design? What is this stage thats aborting? Reset the job and get any additional warning messages fromt he directors log and post it here.

Once again. Stick to DataStage. You will have much lesses pieces to bind and maintain.

And now now you will be punished Just Messing with ya!

Use the Matches function in the transformer. You dont need a routine. Something like

If you get a 1 that means email is in the format xyz@xyz.com else if you get a 0 that means its not in xyz@xyz.com

I gave you a complete solution as a welcome. The stage variable will take care of the second, third and so on, all the generation values. Make sure the first line in your file is Generation Date.

You guys make me laugh

You can do this by reading the entire record as one column and then split it inside the transformer as Whale suggested. Define a stage variable GenDate | if in.Link Matches 'generation...' then Field(in.Link,":",2) else GenDate Now your columns will be Col1 | Field(in.Link,&quo...

chulett wrote:
That's just me being anal, ...

O c'mon Craig. Your just being technically correct

Are you getting that error while viewing data or while running? I know for viewing data, $PROJDEF was to be replaced by its true value in 7.5. But while running, it runs fine. This functionality was enhanced in 7.5.2 or 7.5.1A

Modularization my friend. Build the text files in one job. Cat them and load in the second job.

Exception handler only fires if anything goes wrong in the sequence job and it is not handled. Thats when the Exception handler fires.