DSXchange

Ereplace has from three to five arguments. Research it. What you need to replace all instances is

Best practice is to design server jobs so that they never abort, so that you retain control at all times, in my opinion. Etiquette Note Terms like "fast" and "asap" create negative feelings here. This is an all volunteer site; folks post as and when they can. If you want "fast" or "asap" sign up for...

Anyone try the MatchField() function suggestion?

Yes. Provided you have the requisite MetaBrokers installed.

OVERWRITING is an optional keyword. I counsel caution using it.

How are the compiler and linker environment variables (such as APT_COMPILER) set?

Batches are created in Director, and may include parallel jobs. These are ancient technology; you should prefer to create Job Sequences, which give a much richer control environment.

The usual methods are:
(a) use a DB2 API stage and connect via DB2 Connect
(b) install DataStage on USS and access DB2 locally through a DB2 Enterprise stage

It appears that the previous connection might not be being closed properly. Does this environment have tracing tools? You could certainly switch on ODBC tracing to try to diagnose.

This is also possible, and sometimes desirable in parallel jobs. Read the Sequential File as a single column, and use the Field() function in a Transformer stage to parse out as many fields as you need. The remaining fields can be discarded at this point. Your output record schema from the Transform...

Certainly if you can source a UNIX-based ODBC driver that would be one way to go. Does IEX TotalView have a "dump" facility that can dump data into text files? That, scripted in combination with FTP to the DataStage server if necessary, is another possibility.

The "#" sign is a special symbol in DataStage, a matched pair indicates a reference to a job parameter.

Someone here suggested it may be the proximity of "S" and "X" in DSXchange that cause the nanny (Blue Coat) to intercept everything. "S" and "X" are in close proximity in a certain other three-letter word that causes net nanny software to glip.

I probably referred to DSExecute() rather than EXECUTE, but either is OK.

You need to use DSExecute() to capture the value of the environment variable, then use that to construct the path before executing your actual shell script.

Maybe, but I doubt it. It needs to have euid=0 to authenticate logins.