RE: SQL 22023 but data is valid

Thanks for the suggestion, Elvis.

However, the problem persists. Again, running the statement in STRSQL
succeeds. I'll wait until after updating to V5R4 and see how it goes.


Row # 153
"T16-00012","INK BLACK RESISTOR 4242-20K
O","GRAM",88958,"",-1000,126,12/18/2007,"C","218","","","",0.9574,0,-957
.4,"IDG","70-12","IDG Associate"


SQL insert command:
insert into PROD_DTA/IDGIMPIST
(ITEMNUMBER,ITEMDESC,UOM,REQNUMBER,CHGNUMBER,ISSUEQTY,INVNUMBER,INVDATE,
MATTYP,DEPARTMENT,PROJECT,WO,EQUIPNBR,UNITPRICE,TAXAMOUNT,NETAMOUNT,HOME
DEPT,ACCOUNT,EMPNAME) values('T16-00012','INK BLACK RESISTOR 4242-20K
O','GRAM',cast(88958 as numeric(10,0)),'',cast(-1000 as
numeric(15,5)),cast(126 as
numeric(10,0)),date('12/18/2007'),'C','218','','','',cast(0.9574 as
numeric(15,5)),cast(0 as numeric(15,5)),cast(-957.4 as
numeric(15,5)),'IDG','70-12','IDG Associate')


The same error message.
Message ID . . . . . . : CPD4374
Message . . . . : Field HVR0016 and value 16 not compatible. Reason
2.
Cause . . . . . : The attributes of variable field HVR0016 in query

record format FORMAT0001 are not compatible with the attributes of
value
number 16. The value is -957.4. The reason code is 2. The reason
codes
and their meanings follow:

1 -- The variable field and the value are not both character,
numeric, or
double-byte.

2 -- The variable field is too small to hold the value. If the
field is
of type character, the length of the value must not exceed 32,766
bytes. If
the field is of type variable length character, the length of the
value must
not exceed 32,740 bytes.



Loyd Goodbar
Senior programmer/analyst
BorgWarner
TS Water Valley
662-473-5713
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Elvis Budimlic
Sent: Wednesday, December 19, 2007 16:51
To: 'Midrange Systems Technical Discussion'
Subject: RE: SQL 22023 but data is valid

There may be a V5R2 PTF that would help... but finding it would probably
involve getting in touch with IBM support.

I've ran into similar issue on V5R2 and had luck casting values
explicitly
to a type they ought to be, i.e.:

CAST(157.325 AS NUMERIC(15,5))

It may be worth a try in the short term.

HTH, Elvis