I have created a very simple load job where I am passing a Key field and a date field into a DB2 table. I am simpling wanting to expire any records where the Key ID's are the same and the REC_EDT within the DB2 table is set to '9999-12-31'.
I didn't recognize the UserId, but I did recognize the pPARAMETER format plus this is the only place I know of with a major field being ARRG_ID. We'll continue this offline. :D
I was a strange error. Everything in the job looked correct. I made a copy, retyped in the identical manual SQL clause (which was just the default generated UPDATE clause with one added constraint put in) and -poof- the job ran. I couldn't get the original to run and since everything is now in order we've gone on to other things without further attempting to analyze the cause.
If there are two parameter markers in the SQL there must be two columns in the Columns grid. Could someone accidentally have created a column called " "? Columns that are to appear in the WHERE clause of an UPDATE statement must be marked as key, columns that are to appear in the SET clause are not marked as key.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.