DSXchange

If what Josh stated should be all you need, if that doesn't work you can try this solution. If you are looking to capture the time that the job aborted, you can write this to a data table. In a server job source this database using the max timestamp. In the server job transform you can execute your ...

Unless I'm missing something.

Your Stage Variable is being incremented with each record processed, the constraint test that value during that same process. The Transform Stage doesn't have to complete before you can test the SV value.

Charlie

Use the Complex Flat file stage for your source flat file - see PJD manual

charlie

Try StringToDate(inputdatefield, '%mm%dd%2000yy")

Try StringToDate(inputdatefield, '%mm%dd%2000yy")

a few questions first:
How many rows are in the input files

Are there any constraints present

What is your taget file environment

In your first tranform use a stage variable to count the rows, then have that value tested in a constraint. You can then eliminate the other transform and the aggregator stage.

In your first tranform use a stage variable to count the rows, then have that value tested in a constraint. You can then eliminate the other transform and the aggregator stage.

work backwards, meaning test for all 3 fields to be empty first, then test for 2 then the 1. if col1 isnull and col2 isnull and col3 isnull then if col1 = isnull and col2 is null then values else if col1 isnull the value else '' else " I think this should give you the results you are looking fo...

I had a similar requirement, where the sur-key was incremented in one process and had to used in another. I wrote the Sur-key value to a work table, then in a Server job did a select max on that value, passed it to a variable and executed the next job through the server transform. The job executed f...

If you are unable to view the data from the input source, try a different delimiter setting eg Tab. You may have to try different setting to find the one that works. You mentioned that your source is a flat file. check to see-if you can- what it looks like from where it's created.

I thought that the Display column in the Teradata transform was for viewing the data through DS, and not how the field would be loaded to the table.
So if I understand you, the Teradata Display column length would have be the same as the actual Teradata field column length. Interesting....

Thanks for the reply Ray. The third portion is :00, no mille-secs and there is a delimeter to allow for the date/time space. The developer said he changed the Display on the TD Column tab to equal the column length field and it he can load to TD without any invalid timestamp error. :?: I haven't had...

After concatenating 2 string fields a date field:time field:('00') to a StageVariable, then a StringtoTimestamp conversion, we received the Invalid timestamp error when loading in TD using Tpump. The TD TimeStamp field is defined with a TimeStamp(0) therefore mille-seconds not used and Nulls Yes. In...

I had this problem in the past and I thought I remembered the solution, but nothing I have tried has resolved the problem. The source is Teradata usig Fastload and the fields in the query match to the columns, order and SQLtype. This is the error: SRCE_VNDR_PO,0: Field type must be either an int8, i...