DSXchange

Could you please explain in detail to us what exactly it was that you tried? And what result you did achieve? We're here to help, not just hand over work. Have you gone through the help documentation on the Transformer Looping concept and the functions that support it? Lots of information there!

I'd start with the documentation. Basically, every time the value in that column changes your current XML output file closes and a new one is opened. Files are numbered using your 'base' pathname.

Is it taking 25 minutes to "establish a connection" or 25 minutes to start returning records? They are not the same thing.

What is in the job's log?

Pretty arbitrary requirement - cut the time in half. Seems to me you'd have to have access to a faster sort, something third party like SyncSort perhaps to accomplish that. How many nodes does the job run on? You could try experimenting with that... if your source file allows parallel reads that may...

Seems like "in order" would be more precise than "in groups".

I can't confirm as I have no documentation access here, but pretty sure that function requires a true time component not a string with a time in it. And your 'source_column' needs to be a date.

Good to know, thanks.

Good to know. I could see either answer being true, thanks for the clarification. I wonder if an instance's USERSTATUS value is lost when the log records for its run get purged? Compiling a job clears them all, FYI.

That's a perfectly valid question! I'm going to take a guess as I don't remember ever actually testing that in my time with DataStage. I believe that since there still is only one job under the covers and one job log that you basically get 'views' into to see the instance logs, the answer will be th...

What about this assertion:

pk7 wrote:I know that with Sequential files there is such an option

Is that some new functionality I haven't seen mentioned before?

I'm not aware of an option of that nature for datasets nor for sequential files. If they're not there when called for as a source, job go boom.

You need to look for DSSetUserStatus and provide a wrapper for it as noted in this post as one example. There are many.

One post on this subject, searching will find others.

viewtopic.php?t=148604

Server job. USERSTATUS. Pass as a Job Parameter to all downstream jobs that need it.