DSXchange

Still, as a test hack off the end of the job and land the data. Use your UNIX command line to sort the data appropriately and time it. If it is significantly better then it could behoove you to incorporate it into your processing.

What did you do to recover the DataStage installation before this, anything? Meaning, are you importing into a clean, empty project or something else? For these kinds of things, it is best to directly involve your official support provider, someone who can hold your hand during the process and help ...

:!: First off, it is a Sequence job not Sequencer - an "r" at the end means an object, a stage you use in a Sequence job. A little lost... in the "successor" portion of this, who actually needs to read this flat file that the first job creates - other jobs or the Sequence job its...

"yaar"? Talk Like a Pirate day isn't for several months. :? First thing you'll need to do is keep track of where you are and post your questions in the appropriate forum. This isn't it as this one is for "testimonials" only. So let's try this again - since you've marked this as a...

You can tell your sorting is "working" when rows flow through the Aggregator rather than none coming out until all have gone in.

There are "Sort" columns in the Aggregator, one for order and another for direction. So, you can say "Fred" is the 1st field sorted ascending, etc. Make sure you don't lie to it, it will bust you! :wink: And make sure you sort to match your grouping columns or the Aggregator will...

One thing to try for a check would be to export another folder (ideally one with sub-folders as well) and see if you get everything there. We've seen corruption in the repository indices cause jobs to be skipped like that, but not sure how that plays out in the new 8.x world, though.

Any problems with the disk space where the projects are stored? Wondering if perhaps you ran out of space there and corrupted the repository. Another possibility is Anti-Virus, is that running on your server? We've seen it can eat things at times.

No size limit other than what the O/S may impose and it would crater when it hit it. Perhaps they are "Read Only" and you didn't ask to include those in the options?

Since we're somehow resolved now, can you please post the resolution in the thread as well? It will help future searchers who come here with the same problem. Thanks.

The value or the target field's data type? Your target field will need to be a string in order to retain the leading zeroes you are attempting to put there.

You have to handle both the date and time separately and yes, manage the date change based on what the time was incremented to. Which means you need a routine and can't do it straight in a transformer derivation. I know Ray has some date handling routines freely available on his site and Ken Bland h...

You could always "fix" the update SQL so the format mask matches what you are already doing. There's no reason on God's Green Earth to force it into that particular format.

Sorry, I thought it was done from the command line... never mind.

And you still haven't explained the rule, just shown your single example again. OK, so 68 becomes 58... what about 67? 72? 99? What is the rule?