The test utility in branded_odbc goes to DBF by default; you may get some insight from there. Given that the ODBC driver is properly installed, the theory is that you don't need to care about how the "database" works - you deal with tables, rows and columns. Apart from that I can't really help; it's...
Passing a function reference as a function argument - which is what you are trying to do - is not possible in the DataStage BASIC language.
If there's a small and finite number of functions that might be invoked, you might create a Routine that is in effect a dispatch table for those functions.
On the other hand, there are quite a few self-employed consultants and service providers here who would be happy to SELL a customised and working solution. This is what T42 was getting at with "pay someone".
Haven't seen that one before - it would certainly explain problems registering the DLL's!
Best place to get replacements is your vendor/first line support provider. Mention that you want the larger ones.
I think you'll find that you need the WHERE clause if you use a Dynamic Relational Stage, even if its connection protocol is set to Oracle. I had assumed that the OP required to invoke the sequence for each row processed through the job. I've also done this with generated SQL. My "table definition" ...
Welcome aboard! :D If the muliple files are all in the one directory, all are governed by the same metadata ("table definition") and are moved out of there after processing, you can still use a Sequential File stage. Simply specify a filter like type *.* - output from this command will become the "s...
The intention, as with the entire Websphere suite, is to be as database-agnostic as possible. Don't worry about support for Oracle disappearing; there are just too many DataStage/Oracle shops out there paying maintenance!
Records can not "go missing" from hashed files unless a specific DELETE statement (or command) is issued. It is possible, of course, that the hashed file has become corrupted; you would need to check for this. And your answer to Carter's question might help us to target an answer a little more accur...
You also need to update uvodbc.config in the project directory. DataStage will do this automatically if you even partially import a table definition from your DSN.
It's definitely possible to change the value of an environment variable; it's unlikely that the change will be detected. Think about it in terms of processes; your job sequence is the parent process. You change the value in a child process (shell) via an Execute Command activity, for example. The ch...
First tip: never claim that something has gone through successfully if there are error messages in the log. It confuses things; people might stop reading at that point.
Were you logged in as qsadm when performing this installation? Were you logged in as a member of the Administrators group?
Have the link types (stream/reference) been changed in the job design, whether by you or by the gremlins? Do the "Convert to..." pop-up menu options align correctly with the supposed link type?