DSXchange

Look in the Job Properties, Parallel tab. Click on Help while there.

Welcome aboard.

To use a Pivot stage you must name at least the pivot key column and the pivoting columns. Therefore a "pure" RCP solution is not viable.

You need to pre-parse your data. That is, you can not rely on a schema file in this case.

Read about Teradata Utilities Foundation (TUF). That's basically what you need to have installed on your DataStage server machine (and also on any other machine in a cluster/grid from which you intend to access Teradata).

Be more precise about "doesn't work". What actually happens? What output is generated? Add a WHO command between the LOGTO and the SELECT.

Add the required terminator (";") to the SQL statement - it's prompting you to supply it, you supply "Q" which tells the SQL statement not to execute.

Be more precise about "not working". What error code/message do you get?

Talk to your Oracle DBA. This error is being generated by Oracle, only reported by DataStage.

There are some issues in some 7.x versions where it cannot. In these versions you can use the DB2 Enterprise stage for connecting databases on the same platform as DataStage, but have to use the DB2 API stage to connect to DB2 on other platforms (such as xSeries or zSeries - AS/400 or mainframe).

Transformer stage downstream of the Sequential File stage.

SQL data types such as VarChar and Decimal require that precision (maximum length) be specified, and Char requires that length be specified. But the delimiters in the file specify the actual sizes (which must be correct for Char data type). Display width governs the initial display width in the data...

If all 12425 records have the same key value, the hashed file will have only one key value, and that record will be the most recently written one. That's what Craig's hint about "destructive overwrite" was trying to get at. Another possibility is that someone has put FIRST 1 or SAMPLE 1 into the Sel...

2. Using a job sequence.

Can you be more specific about the names of the parameters that are displayed in the Job Run Options dialog but (by your claim) are not in the parameters grid?

Can you list the job parameters for this job using dsjob -lparams projectname jobname and post the results here?

Not sure WHERE you're doing these things. You use $PROJDEF only in the Job Parameters grid, as a default value token for an environment variable that you have added to the job parameters grid. Within activities, click the Add Job Parameter button to add parameters; they will be added in a way that i...

What does the error message suggest?