Re: What's wrong here?

[Peter Dow <petercdow@xxxxxxxxx>]

Hi Rob,

That's kind of interesting.  In your working statement

    values cast(15.2 - 2.1 as numeric(15, 3))

it didn't complain about the 15.2 or the 2.1.  I tried

    values cast(15,2 - 2,1 as numeric(15, 3))

and it had no complaints with that either.

The help for

    Decimal point  . . . . . . . .   *comma

says

     *COMMA
         The representation for the decimal point is a comma.

but it obviously takes either. (v7r3)

-- *Peter Dow* /Dow Software Services, Inc. 909 793-9050 
petercdow@xxxxxxxxx pdow@xxxxxxxxxxxxxx /

On 9/29/2022 9:43 AM, Rob Berendt wrote:
> If I go into STRSQL and run this:
> values cast(15.2 - 2.1 as numeric(15,3))
> it works.
> Then I try F13
> 1. Change session attributes
> Decimal point  . . . . . . . .   *comma
> And try this
> values cast(15.2 - 2.1 as numeric(15,3))
> I get:  SQL0104 Token ( was not valid. Valid tokens: ).
> But if I try this:
> values cast(15.2 - 2.1 as numeric(15, 3))
> it works.  It just looks funny to this Yank as:
> VALUES
> 13,100
>
> See also
> RUNSQLSTM ... DECMPT(*PERIOD)
> But it's best to just get into the habit of adding the space instead of relying upon adding stuff like DECMPT.
>
>
>
> Rob Berendt