DSXchange

Check the permissions for every directory on the path. Make sure that every directory and the basename are both spelled and cased correctly.

In a before-job subroutine ExecTCL you could execute the command CHAP DOWN to lower the priority level of that job.

CHAP = CHAnge Priority.

You can not raise your priority. Only a DataStage Administrator can do that with this command.

New requirement, new scope = new billable time. Easy.

Don't EVER let "them" foist a moving target on you - that way lies guaranteed project failure.

There are no conversion tools except the one inside your skull.

Evaluate the logic of the SSIS jobs (if you're really lucky read the documentation produced by the SSIS implementer), and implement that logic as one or more DataStage jobs and job sequence.

This message is indicating that the named key has not been found in the resource table. In version 7 this is a hashed file called DS_RESENU, DS_REDJPN, etc. I do not know what it is called in version 8 - you will need to ask your support provider to solve this one - IBM may have shipped the resource...

Take the apostrophe character out of your STRIPLIST. While it is there, L'ESTRANGE is converted to LESTRANGE. Now you probably need a pattern override, since an apostrophe is not a letter, to get the whole of L'ESTRANGE loaded into the SN field.

If you are using DB2 or Oracle Enterprise stage to feed to reference input link then you could use this SQL.

Otherwise use a Join stage, or upgrade to version 8 in which the ability to perform range lookups is in the Lookup stage. Vincent has created a recent blog on the latter.

As well as keeping track of how far you got, you also need to decide your restart strategy. If you want to restart from the beginning then you need to be able to identify the rows committed to the database on the previous run. If you want to be able to re-start from a "known clean point" then you ha...

Easiest it may be, but there is necessarily a bottleneck as the process of generating the next key is necessarily single-threaded. Any approach using an identity column or sequence will suffer from this dilemma.

That's why you need two separate jobs. The Merge stage (server jobs) reads two sequential files directly (it does not support input links) and forms a join between them based on criteria that you specify.

A full outer join is not possible if a hashed file is involved as one of the sources. Run the hashed file into a sequential file. Then, in a separate job, use a Merge stage to form the full outer join of the two sequential files.

Search the forum for "vertical pivot", which is what you are trying to do. There are several ways to effect this technique.

TargetA | V Source -----> ColGen ----> Lookup ----> Transformer ----> TargetB The Column Generator stage generates a column containing 'X' in every row. The query on TargetA has the form SELECT 'X', MAX(keycol) + 1 FROM targettable and is Entire partitioned. In the Transformer stage keycol is deriv...

Are you using an Oracle Enterprise stage? If so, are you using direct write or Upsert? If Upsert, what upsert mode have you specified? Are there any (many) warnings in the job log? Stored Procedure stage often runs in sequential mode, which means that you're more interested in a collection algorithm...

You could consider tuning the database query, perhaps with an EXISTS clause. Your DataStage job needs two Transformer stages. One to perform this complex lookup via ODBC, and to determine whether zero, one or more than one row was returned (three separate outputs). Downstream on these outputs you ca...