Make sure that the decimal separator is the same in both environments. It
can be set in the ACS connection AND in the RUNSQLSTM command.
If you are dealing with a decimal comma, you always have to add a blank
after the separator in scalar functions etc. the only place where you do not
need a blank is, in numbers.
For example if your environment uses a decimal comma, DEC(11,2) is
interpreted as DEC(11.2) which is wrong. If you specify DEC(11, 2) then it
is interpreted as 2 different numbers.
If you are working on PUB400 the default decimal separator might be a comma
(European Standard and RZKH is a German Company).
That's why I always preach, you cannot have too much blanks but not enough!
Mit freundlichen Grüßen / Best regards
Birgitta Hauser
Modernization ? Education ? Consulting on IBM i
IBM Champion since 2020
"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"
"Train people well enough so they can leave, treat them well enough so they
don't want to. " (Richard Branson)
"Learning is experience ? everything else is only information!" (Albert
Einstein)
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Sam_L
Sent: Wednesday, 6 September 2023 23:06
To: midrange-l@xxxxxxxxxxxxxxxxxx
Subject: A Difference between iACS and RUNSQLSTM on INSERT statement
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 ",". I 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?
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
midrange.com
