DSXchange

OK, edited my post to be more specific as to the stage I was referencing.

Sorry but that tells me absolutely nothing.

Define 'read' in this context, please. And tell us your complete job design, what's in there besides the troublesome External Source stage.

There's an option to use a Trigger Column in the XML Output stage, when the value in that column changes the stage closes the current file and opens a new output file.

So... deleting from hashed files... we're talking UV stage wearing, SQL deletes here I assume?

OK... for grins let's recap what we know so far from the thread and the searches I'm sure you've done here: a. 'Reset if required then Run' in a Job Activity stage does exactly what it sounds like it does, allowing an Aborted job to be rerun without a manual reset first. b. Enabling 'checkpoints' in...

What data type did you use for the column in the stage? Char? If so, then the padding is expected and you need to try Varchar.

What are you trying to accomplish with the stage? You cannot simply put a file name there, it will treat it as a command or script that it thinks you want to run, hence your 'need' for execute permissions. Hint: you no need. :wink: If you are trying to emulate examples posted here where the ES stage...

Why not post your 'further information' here?

So, are you actually asking how to know which fields were marked as 'Key' fields in the hashed file?

1. Yes. With new port = 7.5.3, without port = 7.5.1a

2. Yes. You will need to duplicate everything and 'migrate' all code.

The former is the right way while the latter is about as wrong of a way as you can get.

Hmmm... not sure if you stayed in "job type" when you looked but I would think most discussions of sort here, DS v. UNIX, would be for a Server job. The sort there is more of a "poor mans" sort and not really suited for large volumes, necessitating a need to fall back to the O/S ...

Since resources are 'mostly' the cause and it runs fine the next time then any automatic restart of the sequence job will 'mostly' work fine. Me, I would worry about the 'un-mostly' part but it seems like you're not going to. :? Your questions have already been answered, some parts more than once, n...

OK, then let's move on to the time portion. Ignoring the milliseconds, is it really coming over as "24:00:00"? I do not believe that is a valid time value in any system... 23:59:59 + 1 = 00:00:00 AFAIK.

You have to do more than just "turn on" that environment variable, you have to use different names for the columns as per the docs - did you?