DSXchange

Welcome aboard.

That sounds very much like an interview question. How do you define efficiency? Each stage type has its own particular purpose - that is why there are three of them, not one. You choose the appropriate tool for the particular task.

Your increment is one second. Therefore, the second iteration of the loop will fail to start the job if it hasn't finished within that second. Further, if the first iteration of the job hasn't finished within one minute, it will throw a -14 error (or, possibly, abort with "job not in a runnable stat...

Can you please post the entire error message, so we can discern whether these are Teradata blocks or DataStage transport blocks?

Create a stage variable, let's call it svNewLine. In Windows, of course, the line terminator is actually two characters (carriage return and line feed), so initialize the stage variable to Char(13):Char(10) Don't assign any new value to this stage variable during per-row processing. ...

Then please post the actual errors (not the ones from APT_CombinedOperatorController).

The score would be used to identify whether DataStage had inserted any tsort or buffer operators. Had it?

The currently mapped drive's root is considered to be "/" for UNIX purposes*. Therefore, if the DataStage project is on D: drive, then /tmp in UNIX is D:\tmp in Windows. You may need to fudge things a little, using relative pathnames rather than unqualified pathnames, but "UNIX" commands like ls do ...

Yes it would. 7.5x2 installs on top of MKS Toolkit, so you have the full gamut of UNIX commands available.

jmarutz wrote: you can't setup one connector with that information and use it in another job.

You can indeed. That is what the (new) Connector stage is for.
A Connector can, of course, use parameterized connectivity values.

No. Job parameter values are read, and locked in, when the job starts.

Use the "Type 19 hashed file" solution in your other thread.

A Type 19 "hashed" file is, under the covers, a directory. Its keys, therefore, become file names in that directory. The non-key fields become lines in those files.

You've got it. Look also for traits such as attention to detail, accuracy, initiative and the ability to complete tasks with minimum supervision (but willingness to seek clarification in cases of uncertainty rather than ploughing ahead).

Let's try to get one thing clear from the outset - by "loading SAP data" do you mean loading data from SAP into DataStage, or loading data from DataStage into SAP?

Should have asked this question earlier.

There are plug-in stages (and other techniques) for each operation.

You need to keep track in DataStage of where you got up to. It would be the same for any source - MQ is not part of it. Of course, if you were doing destructive reads from the queue, then you can just pick up where you left off (except that the read that caused the abort may have been lost if you ha...