DSXchange

That's a workaround rather than a fix. What about your successor? Do spend some time working out why the Administrator client (that is, the user ID used from the Administrator client) could not update the DSParams file.
Is this user a member of the Administrators group on the server machine?

Use a constraint expression on each output link.

For good rows, col1 <> 0 And col2 <> 0.
For the rejects link, col1 = 0 Or col2 = 0.

The best place (imho) to record business metadata is in the long description fields within DataStage jobs, routines, data elements and transforms (and, possibly, table definitions, for business metadata such as ownership, responsibility for authorising changes to table design, and so on). The long d...

Yep, that'll prevent a restart, because the defunct processes remain attached to the shared memory segments.
As superuser, use the following commands to clean up defunct processes and the licensing associated with them:

Good catch. It can't be done in a single server job using Merge stage.

Just make it a single command, using backquotes to capture the output of the pipeline. cat `ls -1t | head -1` > load.txt Why cat? Surely a cp command would be more efficient. cp `ls -1t | head -1` load.txt Maybe you want to remove load.txt first. No problem. rm -f load.txt ; cp `ls -1t | head -1` lo...

Any time you get "could not load xxxxx.so" (or xxxxx.sl), check that your LOAD_LIBRARY_PATH (or LIB_PATH or SHLIB_PATH, the name depends on the variant of UNIX) environment variable includes all relevant library directories, and make sure that the way it's set in dsenv also picks these up.

Did the DB2 DBA change the password?

At worst case, use the Merge stage... twice Alas this can't be done in server jobs. The Merge stage reads two text files; it does not have the ability to be driven by two streams. That's just the way it's written. The hashed file approach is likely to be the best if the keys are unique. There are o...

Alas, all you can do is make copies of the job design. As Craig said, the sequential file delimiter character is not able to be a job parameter. Indeed, none of the properties on the Format tab can be job parameters.

What's the exit status from the start command?

Have you made any changes to the uvconfig file?
What happens if you try to start using ?

How about using one more Boolean operator: ( (NOT(IsNull(DSLink3.NEWCOLA)) OR NOT(IsNull(DSLink3.OLDCOLA)) OR NOT(IsNull(DSLink3.NEWCOLB)) OR NOT(IsNull(DSLink3.OLDCOLB))) ) AND ( DSLink3.NEWCOLA<>DSLink3.OLDCOLA)...

Check the permissions on the DSParams file in your project directory on the DataStage server machine. Whether job administration in Director is enabled is recorded in the DSParams file. It appears that the user ID you used to connect the Administrator client lacks write permission to the DSParams fi...

Yes, that's the one. Thanks for that!

THere are no technical limits; only sensible ones. Don't overload any machine - for example you would not configure 24 nodes on a four CPU machine in general! No scheduling by you is necessary; the PX engine looks after allocation of notes based on the configuration file that you specify. Note that ...