DSXchange

Doesn't Search work for you? This question has been answered a bazillion times (to steal one of Craig's non-words).

You still haven't answered my question about why you believe you need sequential execution.

Remove Duplicates stage will remove duplicates without needing any other stage.

You do, however, need to ensure that the data are key-partitioned and sorted on the keys being used to identify duplicates.

You need to determine what operating system you are using (not just "UNIX" - I suspect it's Solaris) then what the appropriate shared library search list environment variable is for that operating system, whether it's LD_LIBRARY_PATH, LIBPATH or SHLIB_PATH. Then make sure that the requisite librarie...

The first problem is we have no idea what stage type you are using in each job, nor what the property settings of that stage type might be.

Too many "it" and not enough detail. How - precisely - does the script work? Does DataStage invoke the script or vice versa? How do you transfer values, once read, into the job parameters? What's different when the different behaviours are observed?

You can, of course, query the repository tables to find out what's recorded there. You can do this from a TCL command prompt or from the Administrator client command window. A suitable query is (and we should be well into the premium area by now): SELECT EVAL "@RECORD<31>" FMT '32L' COL.HD...

What you see in the job properties is precisely what is in the repository tables at the time the job is opened.

A variable in a shell script or a variable in a DataStage BASIC routine, or a variable in some other setting?

Whatever the error was in the data browser it has prevented the return of rows from the table, hence the "is empty" message. You need to involve your support provider who can ascertain what action #3 for the helper routine DSD.Browse is, and thereby narrow the focus of your investigation.

Are you using a custom before-job subroutine or one of the out-of-the-box ones? If the latter you can easily queue as many commands as you like, with @FM between them. If you are using, say, ExecTCL, then you need a workaround. The easiest is to execute each of the commands in turn in Administrator ...

uvconfig file. But a better way to check the value actually being used is

That you are wrong when you assert that nothing had changed.

By recompiling you've destroyed all the evidence.

Find somebody who does have the requisite authorization, and have them clear the status file for this job.

Welcome aboard. Please do not ask for ASAP here, as it offends. DSXchange is an all-volunteer site; people post as and when they can. If you want urgent help sign up with your support provider for premium service and learn the true cost of "urgent" or "ASAP". 7.5.2 and 7.5.3 should be interchangeabl...