DSXchange

Search the forum. This has been answered a gazillion times before.

Basically DataStage needs SELECT privilege on certain system tables to determine whether the table is partitioned, and if so how. TOAD doesn't care - it operates sequentially.

Char to Int would never be implicit! How would you handle "FRED" implicitly? An explicit conversion is required.

DataStage is merely alerting you to the fact that the input value may be larger than is legal for the output column. Design so that this is not the case, or provide explicit data type conversion, to eliminate these alert messages.

The largest possible (signed) integer is 2147483647. Any decimal value coming from Oracle that is bigger than this will cause the error to be generated. You may need to use a BigInt data type.

The developer must manually Add Environment Variable to the job parameters grid for each required parameter. Create a job containing your "standard" set of parameters, and use it as a prototype, and/or create a Template from it. That way at least the manual effort is required only once. If someone d...

A dsx file is an export file, not a job. They can be deleted at the operating system level. You might like to inspect the contents first, to be sure that you're not deleting anything significant. If you're naming jobs with a ".dsx" suffix you deserve all the evil you get. Try using the command DS.CH...

Us a Job Sequence, perhaps with a Wait For File activity to trigger the remainder of the run.

Use a Filter to pre-process the file to remove the \x00 characters, perhaps using a tr command. The Sequential File stage reads stdout of the filter command.

ODBC when you don't have a native stage type, for example extracting from Red Brick Warehouse or dBase. Native stage type when you do.

Active stages have the potential to change the data flowing through them. While simplistic, that's not a bad way to differentiate. You could always inspect the stage type properties in the Stage Types branch of the Repository - the General tab indicates whether the stage type is active or passive or...

Yes, if you're prepared to use a server job to read the row from Oracle, you can load it into the server job's user status area and access that as a Job activity variable in the job sequence. More elegant? It's a matter of taste.

Verify which stage is generating the error, and which input is Input Port #0.

There are three DataStage services that you may (will) need to stop.

DataStage Resource service ("universe" service)

DataStage Telnet service

DSRPC service

Binary or EBCDIC? If the latter, you have an Import As EBCDIC property that you can set.

The examples shown in the manual (Pivot.pdf) are quite clear.