You need to specify a null indicator for each of the fields that are
null capable. There should be examples in the archives.
Matt
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of
jlowary@xxxxxxxxxxxxx
Sent: Thursday, August 31, 2006 5:55 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: When using a file that has (ALWNULL - Null Capable Field)
getting"22002" in SQLRPG
Has anyone ever done (or can it be done) had an SQLRPG program over a
file
that has fields that allow null values (I'm assuming they have the
ALWNULL
on them as the display of the field definition says they "Allow the Null
Value")? We have a vendor file that uses a null capable field for a
name
field. If I do not include this field in the SQL mapping all is well,
but
if I put that field in then I get a SQLSTT = "22002" and no data for
that
record, all fields are blank/zero.
I've not done a lot with SQLRPG and definitely not with Null Capable
Fields, so I'm at a loss as where to even look for answers (if there are
any other than, it can't be done).
Thanks,
Jim Lowary
System Analyst, Salton Inc.
(573) 447-5500
