DSXchange

I am not sure If I can do that but I can certainly explain you all the properties i set. FOr column meta data I created a file with your sample data and imported it. Fixed the length and precision. Under Properties, for options I had First Line is Column Names = True Keep File Partitions = False Mis...

Ok, then post the sample contents here and also tell me the number of columns present. Make sure you copy paste the contents here.

I just recreated a sample job similar to your situation and its working fine provided you are not giving a default value. Can you confirm that the value is infact not space and just empty.

I failed to see Craig's reply as we both posted at the same time. He is so right. All you need to do is go talk to that person.

Open your file as a text document. Copy and paste a few records here enclosed in "code" tags. Lets see how we can tackle this using just DataStage. Also , how many columns are supposed to be in your file?

According to my understanding, if the hashed file gets null as a key, it looks for a valid key and doesnt complain about the null. Just works with the second key. Next time you get the same composite key, the previous one gets over written. But if you have all keys as null, the record will be reject...

If the category was imported using Version Control then it is possible that the person doing the import, marked them as read only. You can re-import the jobs and this time make it writable.

Did you try searching on your error message?

How about you save the xls sheet as tab delimited file. See if that works.

Cant he stick a transformer before the database stage and then choose combinability mode as "combinable" from the transforme stage properties ? But as noted by others, this will still not ensure how the record is stored in the database. But if you are loading to a file then by setting the combinabil...

If it doesn not have IN or OUT parameters then you can just call it in either before or after sql tab of DRS stage.

When you say its nothing, you mean not even a delimiter? If thats the case then you can read the entire line as one record, do an INDEX() on delimiter and if its equal to 0 then reject it. You cannot exactly check for NULLS in a flat file.

In the properties tab of sequential file stage, what have you set the "Reject Mode" to?

I guess then an export, find and replace and finally import would be the way for you. Otherwise you can purchase Kim's PNav to get this done for you in a much cleaner fashion.

You can use it in after job subroutine or after stage subroutine. It should work fine. Where are you currently using it?