DSXchange

Please post the source code if DateTimeDiff(). It is not a function provided with DataStage. Data types are irrelevant in DataStage BASIC.

Welcome aboard. :D

Read the error message.
It is not a DataStage problem.
Your Sybase connectivity has not been configured.

Welcome aboard. :D

Use an Aggregator stage with Last as its aggregate function following the Transformer stage.

Welcome aboard. :D

Curiously you are not the first to have asked this question. Search here can mean that you find the answer without having to ask!

Try Surrogate Key Generator for your initial exact match search.

Correct. You can use PreviousJob.$UserStatus if you chose to store the result in the job's user status area.

Sign up. My previous post explained where the dfloat comes from. We need the funding to help to support the site - none of the premium posters is paid - it all goes to purchasing bandwidth and administration of the website.

Add a Routine activity at the end. Use UtilityMessageToLog() to log a message. See whether the job sequence gets that far.

Review the job logs of the jobs that failed. The first logged event ("job starting") shows the parameter values that the job received. Check that these are correct. If not, you need to discover why not. If they are correct you need to review the job designs themselves to ensure that the parameter re...

If you must do it in a parallel job, prefer to use a Surrogate Key Generator stage. The initial value can be picked up be a previous (server?) job and passed into the main job as a job parameter value.

Then you're not driving it properly. It requires sorted input.

Aggreagator calculated columns are delivered as dfloat.

There is a "Decimal Output" property that you can deploy to manage them as decimal. This is available for the output link as a whole (as Default to Decimal Output), or for individual fields (as Decimal Output).

A job sequence that manages several jobs simply contains several job activities. With or without dependencies. These, in turn, can invoke regular jobs or job sequences. Try to keep your hierarchy from being too deep, or your maintenance people will find it difficult to understand the model.

Use a Message Handler to demote this warning to informational. It's basically warning you that some loss of precision in the least significant digits can occur because the floating point number being delivered is being converted to a decimal data type with a limited number of decimal places (compare...

Remove Duplicates stage?

You might also consider using a parallel Transformer stage if you are using version 7.5.1 or later. That way your constraint expressions may be easier to construct.