DSXchange

Not if you don't want to be. Older versions (up to three back, if I recall correctly) are also supported. So 7.5, 7.1 and 7.0 should still be supported.

There is a PX version of Ereplace() which a Search of the forum should find for you.

Most folks use search and replace on the export file.

You simply can not run the jobs entirely on the database server. At the very least the jobs must be started from a server on which DataStage is installed. You will also need a DataStage license for the other operating system, which will make it quite an expensive proposition.

What does the Transformer do? In particular does it invoke any routines? Have you re-compiled the job?

And, most importantly, what has changed on the system since the job ran successfully?

I don't believe there is any way to suppress this warning with the Wait For File stage. I usually work around it by creating a Routine that performs the same task.

You might replace the Failure trigger with an Otherwise trigger (assuming that you have an OK trigger).

In the Debugger use "Step to Next Link" to follow the progress of a row through the job. The row is only in context if the active stage to which its link is connected is currently executing.

Your only possibility is to store the value somewhere (for example in the job's user status area or in a system variable such as @USER0) while the stage is running, and to retrieve it from there. The links are not opened until the before-stage subroutine returns, and the links are closed before the ...

Welcome aboard.

This would be a good question to put to your support provider. Version 8 is still sufficiently new that there's not a great deal of expertise "out here" for the, shall we say, less well-documented techniques.

Use Char, not VarChar, and specify the display widths.

That list is, in fact, ALL the job status codes. The mnemonics (constants) are defined in the header file JOBCONTROL.H in the DSINCLUDE directory.

Does your configuration file include a default node pool called ""?

OK, the first step (probably in a stage variable) is to convert that to a string. Then you can, based on the length of the string, determine how many thousands delimiters to put in. For example (extend this as far as you need) If Len(svString) <= 3 Then svString Else If Len(svString)...

Only if you are using a suitable radix (number base), such as decimal (base 10) in which to perform the subtraction.

There is no legal way to read a column value in an after-stage subroutine. The column has gone by the time the after-stage subroutine is being executed. The routine is not invoked until all links to and from the stage have been closed.