DSXchange

Then I defer to Ray's question.

That is my recollection as well.

ps. There's no flaming here. We were all new once, even Ray.

You aren't actually seeing "control-z" or ^Z characters in your record data, are you? I'm assuming you mean the ^Z is all on its lonesome as the last line in your file. In that case it is a EOF you can find in Windows/DOS files typically. They are not part of the data. So which is it? Can ...

Sorry but doesn't seem like it. There isn't a large Netezza population here that I'm aware of. Best to take this question to your official support provider if you haven't done so already. And just for grins, have you asked your Netezza DBA about this? That may be controlled by the database rather th...

Basically it means a stage variable of the same data type and size as the incoming values you want to compare it to. And then you define one to have an initial value of all low values and another to have all high values as essentially constants during the job run. Then you would compare your incomin...

Yes... and exactly what they are for. :wink: Note, however, that most but not all places require enclosing them in hash signs. Best to use the ellipsis (...) external parameter helper to add them to derivations at first until you learn which do and which do not require them. Me, it's been far too lo...

Technically, Server jobs also allow only one primary input link, any others must be reference links to lookups. As you've seen, those reference lookups are replaced by specific Lookup stages in Parallel jobs. As for best / standard practices for Parallel jobs, you should probably download this free ...

So... the parallel job is in fact NOT 'working fine' if it skips and thus does not load the last record in any given file. And please confirm - if you run the job standalone for a single file (not part of your Sequence) does it skip the last record as well? If it throws an error, you need to post th...

That or I would think you could build equivalent binary stage variables to check against.

So... you are unable to compile the job? And it's just a problem with this job, I assume, not with every job that includes a transformer. The "##E" lines are your Error lines and it doesn't seem to like your function calls. Post your derivations (constraints or otherwise) that involve your...

You never mentioned any such error...

That's just a stage variable in a transformer that you increment by one or reset to one based on the grouping column. A sort stage with a Key Change column makes it easier.

Exactly, so you can get an idea how you should have crafted the SQL based on your column metadata. I suspect the first cause noted here.

See here.

Perhaps...