DSXchange

Hi

I am using a comma seperated sequential file as a source. One the columns called "A" in this file has a datatype VARCHAR(30).

The target is database and Column "A" is populating Column "B" of Database.(Size of B: Varchar(30)).

If the length of the incoming field is more than 30, I want to catch that record in to rejected file and continue the processing.

I have tried the option in the sequential File like "Reject Mode"= Output. It is rejected the records for Integer (/ Date Format MisMatch) DataType but not for the varchar datatype.It is reading the Column by truncating the Values.

I changed the datatype to "Char", but then I am not able to read the file.I was searching for the simillar issue in the forum but was not able to find the appropriate.

Can you please guide me on the same?

Thanks
Bob

Did you view the data through the seq file....also check the column ordinalities between the source and the target..

Remove the max length from A and add the check in a transformer in the flow.

Remove the max length from A and add the check in a transformer in the flow.

Thanks

I have mentioned the column size VARCHAR(30) in sequential File. Also I can view data (with Truncated data) in sequential file.

Both Source and Target has same data type.

Also Can you please let me know which function I can use to check the len of decimal, varchar etc...

Please let me know if you need more information.

Thanks
Bob

As noted, you'll need to increase the field size you are using in the Sequential File stage and then do a length check on the string, logically rejecting it if it is longer than 30 characters.

I am using the logic which has mentioned above. Now I am facing one m more challenge. Can you please let me know how to avoid truncation of decimal fields / check lenght of decimal fields (Precision and scale) to fit the exact target definition?

As noted elsewhere (did you Search?) the string requires two extra character positions - one for the sign and one for the decimal placeholder character (unless scale = 0).

Hi,
Is the issue resolved?
I just went through the following writeup in manual.
See if it helps your case.

" APT_IMPORT_REJECT_STRING_FIELD_OVERRUNS
When set, DataStage will reject any string or ustring fields read that
go over their fixed size. By default these records are truncated. "

Let me know once you try this.