RE: Suddenly I have SQL Insert errors?

I hear what you're saying, but I'm not so sure that is the case.
Following that logic, the message would occur any time the value of "city" was longer than 20 (which occurs a lot).
This has been in use for many years.

What are the chances that the severity of the message id changed?

-----Original Message-----
From: RPG400-L <rpg400-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of John Yeung
Sent: Wednesday, April 6, 2022 3:47 PM
To: RPG programming on IBM i <rpg400-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: Suddenly I have SQL Insert errors?

On Wed, Apr 6, 2022 at 3:39 PM Greg Wilburn
<gwilburn@xxxxxxxxxxxxxxxxxxxxxxx> wrote:

Now I'm getting this error:

SQL0404
Message . . . . : Value for column or variable CMCITY too long.
Cause . . . . . : An INSERT, UPDATE, MERGE, SET, VALUES INTO, or GET
DIAGNOSTICS statement specifies a value that is longer than the maximum
length string that can be stored in CMCITY. The length of CMCITY is 20 and
the length of the string is 30.
Recovery . . . : Reduce the length of the string from 30 to a maximum of 20
and try the request again.

Seems maybe a PTF or something has tightened up the syntax on the SQE??

That doesn't sound like a syntax issue. If it were a syntax issue, it
wouldn't run at all. Particularly if this is static SQL.

The message suggests a classic data error. The program works as well
as it ever did, but your data is worse now.

John Y.