DSXchange

:idea: If you actually want people who don't know SAS to help (which I would assume is practically everyone here) or who aren't inclined to google that up, it would be best if you could describe in words what the LAG function does. Maybe even throw in an example, if that would help. Then people here...

I have set suggested option but still I am facing same error Just wanted to point something out here. No-one suggested that setting that option would fix anything. It simply removes the ability for the runtime engine to "combine operators" and thus give you more specific information in th...

No. It just means that if it does have quotes, they are doubles. It doesn't mean that quotes are in some way required to be in the file.

That's... interesting. Too bad I don't have any way to play around with or test anything like that.

Thanks. I'm actually working at an 8.6 Informatica site this year and they're allegedly scheduled to upgrade to 9.x in a month or two. Perhaps I'll get to see it in action.

There's one here and another one here. Take yer pick.

Can you describe it please, for those of us who've never seen Informatica 9? How is that different from 'View Data'?

... and one man's round hole is another man's square hole. Or something like that. LOL

Are we talking a DataStage BASIC before/after/Server type routine or one of them new fangled C++ ones for PX?

The sticking point is the bind variable in the select. That makes it only viable in a reference lookup if their "with arguments" requirement means it is being driven by and needs to be applied, row by row, to the input data. I'm trying to determine if that is actually what they need to do ...

This to me sounds like a Really Bad Idea. Either resolve your 'performance issues' with the Oracle lookup or do a normal lookup directly against the flat file. Easy Peasy.

Well... that's a whole 'nuther discussion and really outside of the scope of what was being asked here. All pretty much true, however.

What was wrong with my "in the body text" answer given earlier?

That's not true... all the Director does is read the crontab entries for the logged in user and show any of the "DataStage ones" that it finds. Any proper change on the underside should show just fine, AFAIK.

We're going with "as marked".