DSXchange

If it's exactly four times you could simply emplace four Job activities in the sequence.

Reinstall seems to be your only solution.

Please mark this thread as Resolved using the green button at top.

The obvious answer seems to me to be "from the one sequential file", since you've already created it. Otherwise, provided certain conditions are met such as you have an ODBC driver for Excel on your DataStage server machine, you can refer to each worksheet as a separate table and request t...

Welcome aboard. What Arnd is alluding to is that you are unclear about your business rules. If you subtract 15 months from 31 May 2009, what date do you get? (31 Feb 2008 is not a valid date.) If all you need is the month and year, then it's a simple arithmetic problem. If the month is April or late...

Welcome aboard. DSD.BCIPut() is the function used by the ODBC stage when doing Insert or Update. So it's nothing to do with the reading from DB2. You have an ODBC stage writing to SQL Server, and that's where the problem lies. ODBC stage requires that you conform to ODBC standards. One of those is t...

Just using the environment variable reference ($SKEY) alone does not work. You either have to supply the environment variable value through a job parameter (which can be a reference directly to the environment variable and which must be added from the parameter helper in the Expression Editor) or yo...

Basically the jobs and sequences have to be "grid enabled" so that they can use a dynamically-generated configuration file rather than the static one specified by the value of $APT_CONFIG_FILE.
There are a couple more minor reasons, but that's the main one.

Schema files can only provide constants as defaults. It is not possible to provide "current date" as a default. It is, of course, possible to provide "1967-12-31" as a default date, since "1967-12-31" is a constant.

Do you own an ODBC driver for Teradata? If so, is it installed and configered on your DataStage server machine? If the answer to either of those is no, then the first thing you need to do is obvious.

But this will be the slowest-performing method for accesing Teradata.

What are other ways to link all child jobs in series one way can be using UTILITY.RUN JOB and what are other ways? The old way is to write the whole thing yourself in code using the DataStage API. "They" introduced the sequence job so that you would not need to. From version 7.5 the seque...

The workaround is, as you surmised, to compile the jobs individually.

Every job activity?

Please post the entry from the sequence's log "summary of sequence run".

In your opening post you suggested that you already knew that you could do that.

Welcome aboard. Yours seems a strange requirement, given that there are several Teradata-specific stages from which to choose.