DSXchange

From the server command line you can use dsjob to both detect and reset jobs. You could also create a job to do the same. For dsjob look into the -ljobs and -jobinfo options and the run mode of RESET, from job control the function DSPrepareJob() will do the 'reset if required' part of the equation.

I'm a little lost. You play the Universe game typically because you want to return a 'mult-row result set' and you do that by creating a hashed file with X number of keys and then doing the lookup with less than X. The other reason is because you want to use SQL to access the data in some manner oth...

First off, clarify how you built this hashed file - was it created in an 'account' or is it a pathed hashed file that you manually created a VOC record for? Or something else entirely?

Those jobs don't need to be compiled, they need to be reset. Anyway, search for dscc here for discussions on this.

My thoughts?

Hmmm... I wonder what "not working" means?
Hmmm... I wonder what trying to connect "from datastage unix server" means?

I posted a direct link to the thread, but you can search for "KeyRollup" with an author of "kcbland" and you should only get one hit.

So, this is a column name in a database table? What database? Your documentation should include a chapter called "Handling $ and # Characters". For an Oracle example, in 8.x that would be in the "Connectivity Guide for Oracle Databases" pdf, for 7.x in one of the OCI pdf files fr...

A field name where?

I'm sorry to hear you are a SQL error. :wink: Did you have the stage generate the SQL or did is it user defined? If you've got something like: SELECT TestNullValueLookup_HF.KEY1, TestNullValueLookup_HF.KEY2, (and it seems you do) try removing the "owner" from the query and see if it works ...

As posted above, there's three records not just one... not sure I can delete all of them.

If I were you, I would seriously consider this technique posted by Ken Bland back in the day for using hashed files to do range lookups. I've implemented it in the past and it is sweet once it all clicks for you and you grok what is going on, that and the actual lookup itself is fast as well. Seems ...

From what I've read here, I think you need to handle that manually, perhaps even by declaring the sign as a separate field and explicitly setting it if your number is less than or greater than zero.

That sounds reasonable. Have you been able to rectify the space issue?

Are you sure it's not a multiple of 3? Does your new data warehouse use a multi-byte character set?

That's why we do it.