DSXchange

Then report it to IBM. Even as first-level support providers you are probably entitled to do that?

So now you have evidence to present to your support provider that parameter values are not being passed from the sequence. There may already be a patch for this. Have you checked?

Use a User Variables activity to remove the final line terminator from the output. Left(CmdActivity.$CommandOutput, Len(CmdActivity.$CommandOutput)-1) This will work on both UNIX and Windows environments because DataStage has translated either kind of line terminator to field mark by the time it get...

The user needs appropriate read/write permission to objects in DataStage. I'd put the user ID into the global DataStage group (which I usually call dstage).

Search DSXchange for "fork join". This is not a task for the Transformer stage.

Have you analysed your logic and written out an algorithm? What have you already tried?

Or are you just expecting us to do your work for you?

Does the design include a sort/merge collector (perhaps on the input to a Sequential File stage)?

Engine credentials must map to an operating system user on the engine tier.

1. It doesn't really matter.
2. Probably not. But it depends on many other factors, particularly on the speed of the network segments between the database servers and your services and (especially) engine tiers.

Show us detail of the following events:
"job run requested" from the sequence log
"job started" from the job log

Each of these should show the parameter values that were used.

Can you capture the value of reconJob$Status before the call to DSExecute()? I'm not of a mind to try to balance your quote characters by eye.

That's because hashing is a very common technique in IT, and has been for half a century. They don't feel it's necessary to document the actual algorithm they use. As a rough guide, a simple hashing algorithm might be to add together all of the code point values (ASCII or Unicode code points, for ex...

Show us the actual syntax that you are using. Your routine code might also be useful.

Sequential execution is controlled by the configuration file. When the score is composed, the node used is a resource allocation exercise; usually sequential operators are allocated to the free-est available node from the default node pool (the node pool whose name is ""). Using a node map...

Can you please try this variant of the command?