DSXchange

bhargav_dd: just exactly how "new" to DataStage are you? You say you are here and yet in your profile you rank yourself a "3" which means "Confident to go solo" - something which implies a certain level of training and time with the product. Which is it? It would help ...

If you are new to DataStage, why are you tasked with putting together such a 'performance tips and coding standards document' !!?? Exactly my thoughts! Truly mind boggling. How can anyone new to any tool/product be expected to put together any kind of 'tips' or 'best practices' document? You need t...

'Special libraries'? That's... interesting.

Anyway, glad you got it figured out and thanks for posting the resolution!

Meaning, there are "include" files under the DSEngine directory where these are all cataloged. Check for them there.

The Sequential File stage supports a 'Filename' column it can add for you. Do you need to wait for all three before you process? How are you planning on doing that?

They posted the same question in another group/site and then did a sloppy copy & paste of it here, I'd wager. In any case... what all this?

I've been assuming the delimiter must be properly set, otherwise the whole dang list would get sent to the 'loop job' as the first filename and it would blow sky high. However, that was why I asked if everything ran ok.

I don't recall having any such problem, it should continue to write out all records to your target until the field controlling the name changes. You are sorting the data first by order_id, yes?

Is this a problem for all jobs or just one job in particular? For the former, post your syntax.

'Loop job' means the server job called inside the loop? The one that actually processes a file at a time? :? Does everything run normally, just not as you expect? Meaning it only makes one loop and then exits cleanly with neither job aborting or having warnings? If that's the case then it would seem...

That's the full error? And you get it when exactly?

Start by doing an exact search here for "between two dates", you're not the first to have been tasked with something like this.

Just as a curiosity, would it be worthwhile to attempt a similar load outside of DataStage and compare timing results?

Yes, the stage and link names need to be hard-coded in the Routine Activity stage. And try pointing 'stage' to the transformer and 'link' to the output link that goes from there to the dataset. See if that works more better. Those functions really come from the Server world and work very nicely ther...

Make sure you understand that the convention is "<JobActivityStageName>.$JobName", it's still unclear to me if that is what you are doing or not.

Can you detail out all of the stages in your job, please?