DSXchange

vkhandel wrote:Thanks for the suggestion "Kris".

Not sure what "Kris" implies

Datastage defaults not nullable Integer fields to 0 whenever you use a Join (left outer or right outer) or LookUp stage and the data is coming from the non-master link or reference link. It is always a good practice to use dummy/masked values when you provide examples rather than copying the data fr...

Because you can get multiple updates in one run, a transform stage with stage variables isn't sufficient. A Transformer stage with Stage Variables along with a Remove Duplicates stage should be sufficient as long as we tell the Stage Variables what to do. One input can generate 2 outputs Based upon...

In that case you should see the desired results.

You did not yet answer about the "Do not checkpoint run" option within the Job Activity stage. Apart from that, its time to do your test run and see how it goes and make some adjustments accordingly.

The easier part is to request for additional space from your System Admin. To remove the old files from the Datasets you need to be careful so that you do not remove any descriptor files that actually belong to other datasets within your project. One approach can be, you can start looking at how old...

The error message says it all. You are out of space. You need to increase your scratch disk space or use a join stage instead. What is the volume of the data the job is processing?

harryhome wrote:(in case no change in design). Is that correct?

Is this after you have made/verified the changes I had suggested earlier? The answer depends on what you did after my post.

To be more specific you will have to use YearFromDate function within the Transformer stage and the input should be the future date or your cycle processing date depending on your requirements. You never really specified when you will have to create this "key".

Is the datatype of the output column in the Aggregator different from the one you are using is SQL? Are you seeing major differences or rounding issues?

"Add checkpoint so sequence is restartable on failure" is checked at Seq1 level In first run if J1 is successful and J2 is aborted then Seq1 is aborted. Please guide Are you sure Seq 1 is in Aborted state and not in Aborted/Restartable or Finished state. However, you will need to check &q...

In this case, If JA7 failed for some reason, Will my Job Seq wait until remaining JA gets complete? If so, Will it also wait for corresponding all Exec Command activity gets complete?Poovalingam The Job Sequence will wait until all other jobs that are currently running and then it will abort. In yo...

That depends on what drives your switchover. You can use Year from CurrentDate function and increment it by 1 whenever you need to.

So, if I understand this correct and I think I am , you are required to just pull in the fields from your look up tables which is why you use the LookUp Stage most of the times. All you need to do is to drag the fields (column names) from the reference link into your output link.

What about the other suggestions in my later post and from Craig's post?