DSXchange

I'd suggest getting your official support provider involved in this.

They all use the same tsort operator, from what I understand.

<wink>

So... resolved?

Terminal Control Language. Plenty of other references out there in the wild to both UniVerse and TCL, no need to just look here. And why do I feel like I may just have given a gun to a small child?

Write the files out using a Folder stage, it will create data-driven separate files for you automatically if you set it up properly.

Take the actual error message and do an exact search for it here. You wouldn't have been the first person to ask this question.

Please post in the correct forum going forward. I've moved your two posts here, any other questions specific to the EE/PX poduct belong here as well.

Define the fields as Timestamp in the job and let the stages generate the sql. Both ends.

If that's truly what it happening I'm not sure that anyone here could help as that sounds like a bug with either the ODBC stage itself or the drivers you are using. In any case, my advice would be to involve your official support provider to see if this is a known issue in your version.

kduke wrote:Who is Ken?

Why, you are of course.

More of a workaround in my mind since we didn't find a DataStage solution but glad you got it worked out, regardless.

Why not just have the wrapper check the time and stop looping?

eostic wrote:...but it "can" generate 7.5 jobs as a .dsx

Which wasn't the question but thanks for pointing that out.

Actually, he did... he confused the two but then later confirmed they are indeed in two different instances.