DSXchange

It's no good being in PATH, which is the command search path. It must be in the shared library search path, which is LD_LIBRARY_PATH, SHLIB_PATH or LIBPATH, depending on what kind of UNIX you are using.

And these are?

The "most efficient" way will depend on exactly what you want to achieve, whether the queries are run in the same database, and a number of other factors. For example, can you form the join (or union) of the three queries in the database itself? That would probably be very efficient, and you may not...

"It's failing" doesn't help us to help you. What error message(s) get produced?

I am beginning to believe that job sequences (at version 7.5) can do pretty much anything you need, with a bit of care and forethought. Using job sequences will offer some protection against the day when "they" decide to drop the use of BASIC (though that's not any time soon).

Bonne chance!

Error code 39202 relates to a failure to connect. It decodes (from the InterCall Developer's Guide from IBM) as "slave failed to give server the Go Ahead message", which is an internal coordination-between-processes error. Re-booting the server may help. Otherwise contact your support provider and/o...

No, you said that $DSHOME/lib is in the shared library search path, but you never mentioned that libgciudt6.so was in that directory. That's why I asked the question.

Three problems with that solution. 1. There's no WHERE in the SQL statement (its location should be obvious). 2. There's no column called NAME in the DS_JOBOBJECTS table. 3. It's more appropriate to change the setting on the DS_JOBS table, which does have a NAME column. UPDATE DS_JOBS SET READONLY =...

In the next ("Hawk") release is promised an error code meanings and remedies manual.

Some of the client/server connection error codes that you won't find anywhere else are in the Intercall Reference Guide - this is a UniVerse manual.

The DataStage server itself is not entirely coded in DataStage BASIC, which is a vast superset of Pick BASIC. The server is also coded in other languages, primarily C, for example for those pieces that must deal directly with operating system resources. The ultimate reference for DataStage BASIC is ...

So? Nothing wrong with having 101 stage variables. Call them dalmatian variables.

But is the directory in which libgciudt6.so is located referred to in that search path? Where is libgciudt6.so ?

The uv command does a little more in guaranteeing that you have a clean environment in which to work. It eventually invokes dssh (which is a synonym for uvsh ). Before that, it has failed to find the library libgciudt6.so - could be an issue with how your LD_LIBRARY_PATH environment variable is set,...

Or you can use grep or awk as a filter command in a Sequential File stage either directly or by using the name of your script as the filter. Make sure you output only the rows with which you want DataStage to deal.