DSXchange

Even made visible on all nodes with a mount will suffice. This is well explained in the installation manual.

This alert confirms that you are not using entire partitioning on a reference input link to a Lookup stage. It will never, of itself, cause a job to abort. Something else caused the abort.

Try using an ExecuteCommand activity. Execute the command hostname (which is the same on UNIX or Windows) and use the command output, stripped of @FM characters, as the parameter value.

Yuk! Use SEEK to get to end of file quickly, don't read through the file. OpenSeq can take its Else clause even if the file is open for writing - you must also accommodate this possbility. Search the forum for a Routine called OpenSequentialFile that takes all the hard work out of it. And you must, ...

Mainframe jobs generate COBOL and JCL that you must then move to a zSeries machine, compile and run there.

Is the key (set of one or more columns) that identifies duplicates supported by an index in the database? If so, DISTINCT may be quicker.

On the other hand, partitioned data may mean that finish time is faster because each node is only looking after 1/N of the rows (on average).

Errors are prefixed with ##E.

Warnings and alerts are prefixed with ##W.

You have no errors in this output. Just the alert.

No, because I am working on a site that is server only. Perhaps someone else will.

Make sure that the final line is terminated.

The subject can include job parameters. So you can run your job with one or two extra parameters in which these values can be set in the job sequence that runs the job (using a DS Macro), or just let them have appropriate defaults.

No. Don't make it generic. Make it specific.

That way, when the rules change in three years' time, you've got something that's easy to maintain.

There's never time to do it right but there's always time to do it again. Strange, isn't it?

Is there a line terminator on the final line of the db2nodes.cfg file?

Look at the code generated by the Transformer stage, in the RT_SCnnn directory in your project (where nnn is the job number), identify which part of your code has been replaced by the &SYSETCNT reference (it will be obvious in hindsight), then go back and remedy the syntax of where it has been u...

Decompose your date into components, subtract 15 from the year component, and re-assemble. If your source date was Feb 29 then subtract 1 from the day component prior to re-assembly.

Stage variables may prove useful in simplifying what would otherwise be quite a complex expression.

Nothing "pops up" - there is a command button you can click.