DSXchange

swades wrote:and we dont have time to make macros for that.

Make time.

Why is it there's never time to do it right, but always time to do it again?

It will require the same amount of work no matter which way you do it - DataStage is not a magic bullet.

Incidentally, none of this is possible in a sequencer.

It is, however, possible in a job sequence.

A sequencer is a component in a job sequence that makes an "any or all" decision based on whether its inputs have fired.

Read the error message. Your Data Direct ODBC driver, used outside the context of an ODBC stage, gives you a 30 day grace period in which to purchase a licence. That time has now elapsed. Possible remedial actions are to be found in another post where this very same question was asked, about four ho...

... or even a filter in the find command itself, both for level searched and for file name(s). If you can see the directory to use the find command, then you can see the directory to use a Sequential File stage, and should not need to be concerned about using FTP.

It's quite like the table in the DataStage Essentials class, though missing the row that indicates whether sorted inputs are required.

Don't know if it exists on Linux or not. But even if it does, it may be in a directory not mentioned in your PATH environment variable (which specifies the directories to be searched when looking for a command).

What error message is generated?

The method you're using (via a file) is adequately efficient.

Even a job's user status area involves writing to and from disk, so there's no big gain there. The main additional cost is the additional file opens and closes (a total of four operations, and thus negligible).

Unusual to see this message with uvsh - it's usually encountered with the uv command but not the uvsh command. Are you certain that the shared library search path environment variable (LD_LIBRARY_PATH for example, or LIBPATH or SHLIB_PATH) includes the DataStage libraries? Check that these are being...

The Sort stage (or input link sort) should be as early as possible in the job. The Join stage, further, will require that both its inputs are identically key-partitioned on the join keys. Even so, the framework will insert a tsort operator (and generate this message) if there is no specific sorting ...

My reading was that Job_B and Job_D had to run irrespective of the exit status of Job_A and Job_C respectively, so as to write the audit entries, hence I designed in that way.

Get your DBA to put a trace on it, to determine whether the input parameters are being received correctly.

Yeah, otherwise we might have to advise you to send twice as much money to Data Direct. They'd like that, but your budget probably wouldn't.

It is practically impossible to create a lookup in a server job without at least one key.

The reason is that the key expression associated with the key has to be evaluated as part of triggering the lookup operation (which, for example, does not occur if the expression evaluates to NULL).

And the reason it's worked so far is that you get a 30 day "grace period". Like a "try before you buy". Now you need to send some $$$ (actually quite a lot) to Data Direct to buy a licence for the ODBC driver, or find some other way to achieve your result (such as using a DataStage stage rather than...

Arun, answers to all your questions in this thread were to be found in on-line help and in the manual. You may have been able to save some time by consulting them.