DSXchange

I considered running with that too, but had a little niggle that a null intermediate result in a stage variable might cause a problem. Didn't have the chance to experiment with it.

Yes (to your actual question), but prevention is better than cure.

What you should have done in the first place is to make sure that both (all) users are in the same group, the group associated with the project, and that both (all) users' umask setting is 002 rather than 022.

A sequencer doesn't have that option. The only option available to a sequencer is Any/All.

That's not what sequencers do.

That's what sequences do.

See if you can get the corrupted XMETA repaired.

Why not use the Sample stage?

Right tool for the job, and all that.

There is no COALESCE function in the Transformer stage. But you could use nested If..Then..Else operands. For example:

There is none.

Use a Sample stage.

While you can use a Transformer stage, you need to understand how the Rnd() function works and, possibly, how to seed it. The Sample stage already includes random sampling.

Beware null values. Null concatenated to anything will result in null. You must handle this. For example:

Slow compared to what?

It will also reveal that the source code you need to examine is in or around line 202 of file BP4364\JOB.1496282158.DT.1576745862.TRANS1 in your project.

Their best answer is correct - you can't. In versions prior to 8.0 you could report via the DS_LICENSE table, but that has now become the login and security service. Similarly, prior to version 8.0 project roles for DataStage were stored in hidden files in the project (such as .operator.adm and .dev...

The versions are compatible. Can you please verify that server jobs are licensed on the target machine?

Congratulations for finding the correct (and only) solution. It's a business problem that can only be resolved by the business.