DSXchange

Nothing to be sorry about, part of the learning experience of transforms versus routines. I'm sure there's a "full Wurlod" on the subject here somewhere.

Again, you have not explained what "not being showed" means. Transforms trump routines so you need to look under DS Transform rather than DS Routine, is that your issue?

How about you read the documentation first and actually try to use the stage? Then come back with specific questions you may still have.

They're all at your fingertips. A simple search for "certification" here will reveal quite a bit of information on the subject.

Like all things Parallel, there is a specific stage for that. Sequence number = surrogate key, by the way.

It's already compiled. Sorry, but I don't undestand what "but not in the column derivation" means. Do you mean via the ellipsis (...)?

You need .net for the client and a supported compiler for the transformer.

How about the "Please post the exact error message" part, you could see that.

Should? Yes. Must? Not sure. Are you actually running Windows on FAT32?

Right... hashed files utilize "destructive overwrite" for records with the same key value, also known as "last one in wins". As noted, check the uniqueness of your keys.

The only way a Sequence could do something like this to itself is inbetween activities, but that's not necessarily going to handle the "abort right smack at 7:30" part if (for example) it's in the middle of a long Job Activity. What you need is another process to monitor the Sequence job. ...

Any chance that the value that's too large in 'record number 1' is the column header?

True... and then you could use the creation of the file as a process break if needed.

I had to go look up PAKTIME as it was not one I was familiar with.
Odd that this would affect your ability to compile.

Sounds to me like something you'd use an Enterprise Scheduler to control. If you had access to one, of course.