DSXchange

As your syntax looks just peachy, I agree with this:

Sainath.Srinivasan wrote:Try with a space before your backslashes.

Interesting, thanks Shane. I'll need to play with NVL, it seems, see how it affects things.

Hmmm... you should be able to call that 'before sql' I would think. What have you tried and what happened?

So then... what is it called when a node failure does not kill running jobs but rather transparently moves the engine to another node? Really High Availability? :? Serious question, btw, is that not a consideration? It was back in the day when I was goofing with it. I guess that's the ultimate goal ...

A) That KERBEROS message is informational, not an error, just saw the same thing last week. Google for it. B) Use full paths rather than relative ones.

So... "may help resolve" or "has resolved"? I know you marked the post 'resolved' but the message from IBM leaves some wiggle room for them, it seems.

I used lookup to do this from the database (DB2), but the lookup doesnot allo cos the orchestrate value i am passing and the sysibm.sysdummy1 table I am getting the value from is not correct. Perhaps if you explained what the heck this means, someone here could help you get corrected values. Or do ...

OK, so you have XP w/ "SP2" a.k.a. "Service Pack 2". You need to check with your official support provider and see if that patch is still needed in the 8.x version. It definitely is needed for 7.x, fyi. No clue if that actually will fix your problem or not but you need to get tha...

Well... that *is* what the 'default tablespaces' are for, to be used by default when none are specified. :wink: I'm not familiar with the gory details of the DB2 stage, but whatever normal syntax you'd use for this should be perfectly valid there as well. I would assume there's some kind of 'user-de...

Sorry, don't know. Why not ask your official support provider? Once you get the answer, please share it back here.

It is, just not a good one for PX. So attempt to protect your quotes as noted - back-slash, double them up, etc. Or you could load your "inlist" values into a work table and join it into your query. Or (yuck) select everything and filter out what you don't want in the job.

DataStage is stripping your quotes so try escaping them. Searched for "INLIST" with author "kcbland" and easily found it here and here but (as noted) why bring a BASIC gun to a PX gunfight?

That was my thought as well.

It's the "sort of" part that concerns me. Curious what, if anything, others have heard or done recently - especially in the 8.x world.

First, search more better - the BASIC function INLIST is still out there, authored by 'kcbland'. And 'failing the same to write' tells us nothing, post your actual errors or problem details if you expect more detailed help.