Re: Row change Timestamp

[Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>]

Hi Gad

I *think* you are seeing what I saw once - if you don't specify the 
timestamp yourself, RPG will put ITS default in there when you insert a 
record. I assume here you are using hative IO and inserting through the 
physical file.

I think you can insert records through a logical file, so if you have 
one that leaves off the timestamp, it will likely use the default set in 
the table.

No row change for user - only timestamp for historical reasons or an 
identity kind of thing - I'm probably off on the latter.

Hope this makes sense - it's coming from dim memory.

Vern

On 6/21/2013 5:09 AM, Gad Miron wrote:
> Hello Rob
>
> Right you are,
> I tested your demo RPG PGM and (after update) the Timestamp was updated
> correctly
> (i.e to the time the prgram was run and not the value in the program's
> buffer).
> However,
> "With default User" did not work for me,
> when inserting a record the change user field was not automatically updated
> to the default USER
> is there a "row change USER" functionality?
>
> Thank
> Gad
>
> message: 2
> date: Thu, 20 Jun 2013 08:44:15 -0400
> from: rob@xxxxxxxxx
> subject: Re: Row Change Timestamp
>
> Let me repeat.  I was initially wrong.  The row change timestamp is NOT
> destroyed by RPG's handling of the I/O.  It works as designed.  You could
> READ a row, set the row change timestamp to some value in the past, and
> UPDATE the row.  It won't care what you set it to.  It will be updated
> with the current timestamp.  This is as it should be.  This is available
> with 6.1.  This is the difference between "row change timestamp" and "with
> default current timestamp".  The latter will be affected by RPG.
>
>
> Rob Berendt
> --
> IBM Certified System Administrator - IBM i 6.1
> Group Dekko
> Dept 1600
> Mail to:  2505 Dekko Drive
>            Garrett, IN 46738
> Ship to:  Dock 108
>            6928N 400E
>            Kendallville, IN 46755