Re: Weird SQL Problem

[Daniel Gross <daniel@xxxxxxxx>]

Hi Jon,

if you use an indicator for the RESULT column, the natural SQL data type would be BOOLEAN. An indicator can only be *ON or *OFF - a Boolean column can only be TRUE (*ON) or FALSE (*OFF) - an embedded SQL is correctly casting/converting between those 2 data types. 

HTH
Daniel


> Am 02.05.2026 um 20:15 schrieb Jon Paris <jon.paris@xxxxxxxxxxxxxx>:
>
> Apologies if this is a dup but my original was rejected (I think) and I can’t see anything for May in the archives.
>
> I have a table defined as:
>
> REGISTERTIME TIMESTAMP NOT NULL DEFAULT CURRENT_TIMESTAMP,
> WEBINARID DECIMAL(11, 0) NOT NULL DEFAULT 0 ,
> RESULT CHAR(1) NOT NULL DEFAULT '0' ,
> REGISTERDATA VARCHAR(1000) ALLOCATE(300) CCSID 37 NOT NULL
>
> The SQL statement to insert the data is:
>
> Insert into table ( webinarId, result, registerData )
>             values( :webinarId, :result, :request );
>
> Where the columns are all defined as per the table definition - except that “result” in the RPG code is an indicator.
>
> This code has been running for a couple of years but since our move to 7.6 has started to sometimes throw SQLCODE -404 against the “result" column claiming that its length of 4 exceeds the capacity of the column. But it isn’t 4 long it is 1. Running in debug, I can see that the temp variable for “result” created by the pre-processor is char(1).
>
> Not sure where else to look.
>
> I have googled for PTFs or reported errors but am not seeing anything.
>
> Anyone got any ideas on where to look next?
>
> I have a work around - if I face the cast of the indicator to char(1) it works.  Guess there is a bug in the code generated by the pre-compiler.
>
> Insert into partner400/sqlregtest ( result, webinarId,  regData )
>             values(  cast (:result as char(1)), :webinarId, :request );
>
>
> Jon Paris
>
> --
> This is the RPG programming on IBM i (RPG400-L) mailing list
> To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
> or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at https://archive.midrange.com/rpg400-l.
>
> Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.