DSXchange

Then your lookup either isn't a CHAR(3) or perhaps the padding character was different when created. You might be able to solve this by simply calling your input field a VARCHAR(3) instead.

Then as long as both sources are space padded, there shouldn't be an issue matching "30 " to "30 ". What do they look like in your lookup source?

Forgot to come back and update this with the resolution. Got this back from IBM Engineering: Do you have the ability to monitor the system resources while the job is running? I think what we might see is the a process butting up against the 4gb size limit on 32bit OS'es. I suspect if you can run top...

That's how CHAR fields work, they are always padded to their full length and that typically with spaces (0x20). Is your lookup field a CHAR(3) as well or a different size CHAR?

Here's one but don't think it's the one I was actually remembering, will poke around again later.

viewtopic.php?t=128688

While you don't "have to" partition / sort for the lookup stage, there are times when it is best to explicitly do that yourself rather than hoping the "auto" partitioning will get it right. Just went through that here. Ray has a post here somewhere where he explains what "au...

From the manual: Each SCD stage processes a single dimension and performs lookups by using an equality matching technique. If the dimension is a database table, the stage reads the database to build a lookup table in memory. There's also this: Input data to SCD stages must accurately represent the o...

Ah... I knew I could count on Da Boyz to bat cleanup for me.

I thought all that was explained fairly well in the Parallel Job Developer Guide pdf entry for that stage.

And the default is bytes. And yes, was... getting there.

For any of the 'combo' actions, the first action is executed and if it fails, then the second is executed. The update "fails" if it updates zero records.

You need to convert it into another string in that format, or you need to convert it into a date? There's a difference.

Here's the clarification I was after, I asked if there was any possibility of a line count limit as well or if it was strictly a byte / character limit: The specified limit really represents the number of bytes that can be stored in the buffer for the corresponding UI edit box. So whitespace charact...

Yes, that's exactly what $PROJDEF is for in a job, takes the project default whatever it is when the job runs. $ENV allows you to set the value to what it currently is in the environment, giving you the ability to override that value, if needed.

Google for "sendmail uuencode attachment" to get the syntax needed. I used to use "mailx" in the past, found it a little more friendly but either should work.