RE: A Difference between iACS and RUNSQLSTM on INSERT statement

Sam -

When I was doing work on a system located in Europe which had the comma specified as the decimal separator, I had errors when running code which I copied over from a US-based system which had the decimal separator specified as a period.

I believe it compiled ok but bombed when I ran the program. I believe that when I ran the program in debug that the low-level messages that got issued were something to do with invalid decimal values, so I did some Google searching and found this:

https://www.ibm.com/docs/en/i/7.3?topic=constants-decimal-point


Sam wrote:

I have a table like this:
CREATE TABLE custmast (
CustID NUMERIC(4, 0) NOT NULL
,Name CHAR(40) NOT NULL
,PRIMARY KEY (Custid)
)
This insert statement works in iACS but fails in RUNSQLSTM:
INSERT INTO custmast (CustID,Name) VALUES (1,'John Smith');

However, this one works in RUNSQLSTM and iACS:
INSERT INTO custmast (CustID,Name) VALUES (1, 'John Smith');

The difference is the extra space after the ",".
had some more extensive code that I ran with RUNSQLSTM back in 2022 (I think) on
PUB400 but it broke today.

Is this a known bug or feature?