DSXchange

The Query Type is: Custom SQL The root of your problem. Allowing the stage to generate the sql would avoid the vast majority of the problems you are having and allow you to cut back on your high blood pressure medication. ps. The fact that it 'runs fine' from the SQL prompt is pretty much irrelevan...

Please don't post the same question in multiple forums. Your answer, of course, is yes. There are other ways to remove it after selection, but I'm sure there's a way to keep it from being generated in the first place. Problem is, I don't remember what in the heck how to do that. One of the Ubers lik...

You only got one thread when you searched for what? Are you still looking for 'multi-row' information or VOC entry help now? If still the former, did you try some of the keywords I suggested? Oddly, it was made at a time when the clock on the server was borked, so it shows up before your original po...

Ray has a Server version of the IsValid function available for download from his site from what I recall.

First question - have you configured DataStage for DB2? We don't "do" DB2 here but from what I've seen here it can be a little tricky to configure properly. There's an official document floating around that helps explain the process, above and beyond the official documentation. And if it's anything ...

It doesn't help to post the same question in multiple forums.

For PX jobs, you are going to want to use 'Enterprise' stages.

So, in either case the first data record in the file was 'ignored', eh? Then there must be something about the data in that record causing that, a mismatch between the data and the metadata which automatically rejects that record.

How about a poll to see if people would like to take a poll on interesting ideas for polls?

For example, for the derivation of the 'Description' field: If @INROWNUM = 1 Then Lookup.Description Else @NULL Now, that assumes a single row will have the 'maximum date' and is all you need to populate. If you are saying that multiple rows could have this max date and every 'max date' row needs do...

What do you mean by 'it ignored the first row'? Are we still talking about importing the metadata or are we now off to where you are trying to use the metadata in a job?

Search the site for 'is already kept'. One post is marked as having found a workaround for the problem, see if that helps.

As you've asked the question, it does "Delete, Insert, Commit". The delete is transactional and will be performed before any rows hit the target stage. They will be 'committed' with your first commit, so the exact behaviour will depend on what you have specified for Transaction Size. For example, wi...

Like most problems, I'm sure this has multiple solutions. Off the top of my head, you could run the data through a sort stage or use an 'order by' in your sourcing sql to get the data coming in by 'TDate desc' - that way you know the first row you encounter will have the 'max date' on it. Then take ...

Everything works fine after you get this message? I could only find one other post with this error in it and that person couldn't open jobs in Designer. I'm assuming this is only an issue for you from your PC and that others aren't having the problem, yes? If that's true, the first thing to try wou...