Re: Time Constant Errors

"WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx> wrote on 01/26/2018 01:00:01 PM:

----- Message from Mark Murphy <jmarkmurphy@xxxxxxxxx> on Fri, 26
Jan 2018 11:41:57 -0500 -----

To:

"Rational Developer for IBM i / Websphere Development Studio Client
for System i & iSeries" <wdsci-l@xxxxxxxxxxxx>

Subject:

[WDSCI-L] Time Constant Errors

RDi - 9.6.0.1
IBM i - 7.1

I have the following code

**free
ctl-opt Option(*SrcStmt : *NoDebugIo: *NoUnref)
DatFmt(*ISO) TimFmt(*ISO)
DftActGrp(*No) ActGrp(*New)
BndDir('JCS')
Main(JCUPDFLCYR);

...

dcl-s RunTime Time Inz(t'02.03.00');

. . .
. . .
. . .

If I change my default time format to *HMS, and the time literal to
t'02:03:00', then RDi is happy (it also compiles properly). But I prefer

to

keep my dates and times in *ISO format internally.

I would agree LPEX error checking should be accurate. But just to be clear
. . .

I believe when you specify a time field (or any timedate field), the
system does not store it internally as *ISO, *HMS, or any other string
representation. When the field is 'externalized', it converts the value to
whatever format you've specified. So you can input a field as *HMS, and
move it to *ISO (or any other desired format) and the system handles the
conversion for you.

At least this is true when DB2 (or Db2) stores the data. I believe the
same holds true in RPG and COBOL.

Michael Quigley
Computer Services
The Way International