DSXchange

Set that option as a default in the GUI before you run it from the command line - that changes a registry value the command reads. If you're feeling adventurous you can set it dynamically in a script via regedit.

Are we talking about the 'Watch' window?

By "Sequences" he is referring to the KeyMgmt routines in the sdk branch of the repository.

Not without more information as to exactly what you are doing in the stage and how you have it configured.

If you would answer the last question, we should be able to give you some advice about how best to accomplish that.

That's ok, I think I have a couple of molars left if you look all the way in the back... [choke,gack] Sorry. :wink: If the job crashed or hung and was killed, I can see both logs being incomplete and complicating this. So... these four iterations - are they complete iterations from Starting to Finis...

Not quite sure what you are asking. If your job was run under the control of another job, then you should be able to right-click in the log view and select 'Related log' to see the log for the controller. And from there open the job design.

Well... sometimes we all have to do things we don't really want to do and this looks to be one of those times. So, what should happen to values outside that range?

OK, fair enough. May I ask what's wrong or inappropriate about it? Even if you don't need the looping construct, every other core element seems to be addressed there - sequential source, multiple values, parsing them into individual parameters, etc etc. :? With some idea as to what's wrong with all ...

You mean as a validation, an automated way to check to ensure the values are within a valid range? No, as far as I know you'll need to specifically check in a Transformer and then decide what to do when values fall outside of that range.

Wouldn't that just be a matter of "converting" the Varchar to a Char? And I would think that, even in PX, that doesn't take a function but just a move from one type to the other. :? Are you doing this 'on the fly' to the individual fields or planning on landing the data to a fixed-width fi...

Not necessarily, we've seen other examples here where newer versions do not work and you need to use the version indicated in the docs. Someone on an AIX box (or from IBM) would need to answer that question for us.

Not sure what you're saying here. Perhaps it's fixed in the 8.x release but for anything earlier it is certainly true that a job in a "Stopped/Restartable" status is in fact NOT restartable.

You mean other than the way I already posted?

Nothing wrong with that at all, after all Sequence jobs are essentially Server jobs as well. And don't assume PX always equals "maximise performance", especially for small volumes. There are plenty of circumstances where a Server job can be more appropriate for the task than a PX job. :wink: