DSXchange

Now we wait and see if "ur" shows up to help...

Perhaps this will help:

viewtopic.php?t=147155

Have them correct the file. There's no such thing as a "fixed length file where last field is variable length" unfortunately.

Perhaps someone knows of a workaround, however.

The table is setup incorrectly, talk to your DBA and have them correct the problem.

A little sparse on the details, don't you think?

Can we clarify exactly what it is you are doing, please? This "CDC stage" you are using... I'm guessing that this is not the Change Capture Stage but rather the CDC Transaction Stage and you have InfoSphere Change Data Capture running against your source database - something akin to what i...

No. It's meant to persist data across calls to the routine, not across multiple jobs.

... probably not many people actively using the stage. Worst case contact support. In either case, let us know what you find!

Yes, that would be the reason. You can see some examples here of what a complete FD would look like... or at least the start of one.

Sounds like a support question to me.

Just connect the Notification Activity stage to/after the End Loop, it will fire once all iterations have completed.

That limit is O/S dependent, from what I recall.

And I counsel... patience.

If you do that, make sure you turn off the automatic refresh!

sharmaisha0902 wrote:The Datastage Version,Hardware is same in both the environments,just that the new one is installed on a different server.

Sounds like one might have NLS enabled and the other doesn't.

Correct... check the function I posted, it returns the number of days between two dates.