DSXchange

Not sure unless it's horked up in 8. I've used the latter syntax without issue in 7.x on a UNIX server and from memory what you posted looks correct to me.

There really isn't supposed to be when you set it to ODBC but sometimes it does seem to work more better. Not sure why.

Order the records properly and check to see if the first value per key is 'FF' and handle accordingly if it is not... assuming that 'fact_value' would always come first per key.

Right... it's in the log because they "used it" but I'm wondering where they found out about it to use it as it doesn't seem to be documented anywhere that I could find, unless it is new for 8.

Sorry I really couldn't help more, but it seems that IBM is still your best bet. Out of curiousity, where did you find APT_PARAMETER_DATA? I can find no mention of it anywhere in my docs or via Google.

Next time, can we start with your actual requirements? We posted solutions for the problem you posed to us. :? You can still use a Sequence job for the 'from completion of main job, we need to schedule other jobs' question, if you want to handle all of the dependancies within the DataStage GUI. If t...

Sainath.Srinivasan wrote:I did not intend to be rude and am not ignorant of the poster profile mechanism.

I know, but many people are - hence my post. It wasn't specifically addressed to anyone.

That's just wanted to be sure we didn't leave you hanging.

Hmmm... the only mention of either APT_PARAMETER_DATA or Illegal flavor keyword in the bajillions of posts here is in this one. Googling for the latter phrase gets me one hit in the 8.0.1 Release Notes where they post the 'workaround' as 'Contact IBM customer support'.

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.

Funny, a quote from 'Airplane'.

What exactly did you export?

ps. There is no 'hash'.

Did you try searching the forums for your message? Your question has been asked several times here, can't imagine there's no answer out there as well.

Unless SAS is using the exact same ODBC connection / driver, then you can't really rule out ODBC as the problem. Can you find anything in common between these few problem fields? Have you posed this problem to your official support provider?

Can you post an image of your job / stage so we can see what you're doing or not doing? Your 'PrtScn' / Print Screen button can capture that, then use any of the free image hosting web sites out there and lastly the Img or the 'image' tags to link to them here.

What do you mean by 'if FF does not exists'... the record doesn't exist? The field is null? Something else?