DSXchange

Hmm.. look on the Job tab of the Job activity - make sure that the parameter values are actually being set correctly. Then look in the job sequence log for a "job run requested" message, which should show the parameter values being passed to the job. Then look in the related log for the jo...

You don't need jobid - that's just there in case you want to establish an alias for the job name. Simply use the job name. Make sure, before attempting to run a job, that it is in a runnable state - that is, compiled, not already running and not aborted/crashed. You can determine this with the -jobi...

Definitely maybe. It depends. How complex are these transformations? How many are there? I wouldn't expect "drastic" changes unless these number differences were orders of magnitude. But, if the expressions are written inefficiently...

4GB is probably not sufficient. I believe IBM suggest a minimum of 8GB.

Local disk is preferred, but the reality is that most pSeries sites use SAN of some kind. The difference is minor, but local disk is preferred particularly for scratch disk.

Given recent acquisitions, I believe IBM will be doing something more with ILOG in a future version. This is based on a wine-fuelled conversation at IOD 2010. Jay, are you listening?

The tool is covered in better depth than in the manual in the IBM class "Advanced DataStage".

Welcome aboard.

You've been relying on a bug in version 7.5 which has been fixed in version 8.1. That value is simply not an integer. You could read it as VarChar and convert from hex within a Transformer stage or, perhaps, an External Filter stage.

Yes, the tokens that describe partitioning are like eAny, eHashed in the score. The rules about what (Auto) gives have been posted in the past on DSXchange. You can Search for them.

The most reliable is Len(InLink.TheString) which returns 0 for "" and a non-zero value for any other non-null string.

Curious to learn the results of your deliberation. Probably the first place to look would be the APT_CONDUCTOR_NODE environment variable definition.

A surrogate key provides uniqueness. What you are requiring is not uniqueness. Therefore the Surrogate Key Generator stage is not the right stage to use. The approach suggested by Manoj will get you close, though generating the 10000 values in parallel on each node. A better solution will involve an...

DataStage is just another client application as far as Oracle is concerned. Therefore what you need to include in tnsnames.ora is exactly the same information as you would have there for any other client.

Add reject handling to the Transformer stage immediately upstream of the ODBC stage. Tell us what error information is thus captured.

You also need to check the uvodbc.config file in the project and, perhaps, in the DSEngine directory.

What you request is impossible as a direct pass. Stage variables occur wholly within Transformer stages in parallel or server jobs. User Variables activities occur in sequence jobs. The one can never occur in the other. The most direct would be to load the job's user status area with the value of th...