DSXchange

Can you be certain theat the Col2 value coming into the Modify stage is NULL? Insert a Peek stage into this link to see what's actually happening (or compile in debug/trace mode).

It usually gets logged, so you can include calls to DSGetLogSummary, DSGetNewestLogId and DSGetLogEntry to retrieve the same.

You might find this information enlightening. The same question was asked all those years ago.

Do not re-compile the job. Reset the job in Director or using dsjob. Inspect the log, particularly the entry "from previous run...". Tell us what information appears in that entry.

I have serious doubts that such an old version is supported on Server 2003. Check with your support provider. Maybe the best solution is to install version 7.5.2 instead.

As they say in register arithmetic... shift happens.

DataStage BASIC does not support optional arguments, so you could not use a routine in this language (e.g. from a job sequence). You did not indicate whether your routine is a server or parallel routine; I will assume the latter. Even though C++ supports optional arguments, the interface from DataSt...

Why do you need to run them "in DataStage"?

DataStage is an ETL tool, not a reporting tool.

Run them in a script, under control of a job sequence if needed. You can retrieve the output from the script within the job sequence and do whatever you like with it afterwards.

Use a Routine activity in a job sequence. This routine uses DataStage BASIC. Within this language the STATUS statement can retrieve the date/time created or modified, file size and other items of information. The routine can also execute a wc -l command to determine the line count. And, of course, t...

The -ljobs options requires a project name. Your final paragraph suggests that you provided it, but your sample command did not.

And, as Arnd notes, only the correct option tokens are supported.

Simpler, and probably faster, would be two lookups.
One where Column5 = 1 (lookup failed rule = Continue).
The other where Column5 = 2 conditional on the previous lookup having returned NULL.

Search the forum for the term loopback adapter - you will find instructions for installing it. This is part of TCP/IP - nothing to do with DataStage.

Or connect your machine to a network component that can serve a network address.

Welcome aboard. Where possible, join at extract. There are two main reasons. First, the join may be able to be assisted by indexes and so be achieved faster. Second, the result of the join will contain fewer rows than the unjoined contents of the source tables; this is even more important if these r...

Marketing-speak, and nothing to do with DataStage.

Or maybe it is. If "accelerator" simply means a rapid application development environment then DataStage, in the hands of a competent developer. is exactly that.

What function are you using?

There is an error in the Parallel Job Developer's Guide where it gives the Transformer stage function NullToValue() for the Modify stage.

The Orchestrate Operators manual correctly identifies the function as handle_null() for the Modify stage.