DSXchange

Actually it is answered in the forum and as Ray noted, quite recently.

You do realize why I posted what I posted, yes? There's no table name in the DML you posted. If you've changed it, show us what it looks like now.

If you read the linked posts, you would see that the value is CHAR(128). Check for that rather than nulling out every value with a length of 1 in the column.

So, where do you want to run these commands? Never having been on a Windows version of DataStage, I've never actually seen this stage so don't know where it played. There's the Execute Command stage for working with O/S commands as you noted in a Sequence job. For use inside a "job job" yo...

'We' means all of you, on all of your client PCs, are suddenly seeing this?

Your official support provider, who would first determine if it was indeed a bug in the product, I would imagine.

Perhaps... depending on what exactly is meant by 'the previous 2 months'. How about an example to clear things up for us?

Ah... counter per group, gotcha. Saying 'count per group' made me misunderestimate you.

Well, in all honesty we got even less than half a question. How about some details? Where is this coming from? What is "DS_Perf_Recalc" and what exactly does it do?

INSERT INTO... what?

It is specifically "PADCHAR", it shouldn't be padding a varchar. Report it as a bug, let us know what comes of it.

Hmmm... they want the first five per group, not just groups that have that many.

Not without some clue as to what "sql db" you are trying to connect to.

This database is co-resident with your DataStage server?

Then perhaps there's a difference between what DB2 considers a valid timestamp and what DataStage does. Have you asked your official support provider?

As I noted.