uint64 error using surrogate key generator

[greggknight]

Surrogate_Key_Generator: When checking operator: When binding input interface field "MaxKey" to field "MaxKey": Implicit conversion from source type "int64" to result type "uint64": Possible range limitation.

this is my sql in an ODBC stage
=====================
select cast (ifNull(Max(#Column_Name#),0) as BIGINT)as MaxKey from #JobSeqn_Parms.Update_Lib#.#Dim_Name#

MaxKey is defined as a BigINT in the ODBC stage and the Surrogate Key Generater stage
They are the only two objects in the job which is selecting from a DB2 on iSeries

This is a warning but I do not run code with warnings in prod ????

Any Ideas

[ray.wurlod]

This is an alert message. Negative int64 values will not be correctly represented as uint64. You can force the data type to be int64 everywhere, or demote this warning to informational - because of what you are doing you know it will never be a negative number.

[greggknight]

This is an alert message. Negative int64 values will not be correctly represented as uint64. You can force the data type to be int64 everywhere, or demote this warning to informational - because of ...

I have tried it defining maxkey as an integer, I get the same warning.
What would I have to set to demote the message from warning to info.

[ray.wurlod]

Go into your job log, right click on the warning message, and choose "add rule to message handler". A local message handler is specific to this job. You can also create named message handlers that you can attach to multiple jobs.

[greggknight]

Go into your job log, right click on the warning message, and choose "add rule to message handler". A local message handler is specific to this job. You can also create named message handlers that y ...

Thanks, that suppresses the warning just fine, though that is a jerry rig. The root problem needs fixing.... I have a few others that are like these as well. Maybe I will collect them and submit them to IBM ......

Again thanks for the tip....