Re: Row Change Timestamp

[Gad Miron <gadmiron@xxxxxxxxx>]

Hello Rob, Vern, Raul

THANKS.

I guess I knew that DDS is not up to it but one always hopes...
As to the RPG Update/Write to the record format,
Raul,
 If I'm not mistaken you wrote that your demo PGM updates the entire
record and still the Row Change Timestamp field *does not* get overwritten.

I'll run my own tests

Thanks again
Gad


On Wed, Jun 19, 2013 at 8:00 PM, <midrange-l-request@xxxxxxxxxxxx> wrote:

> Send MIDRANGE-L mailing list submissions to
>         midrange-l@xxxxxxxxxxxx
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         http://lists.midrange.com/mailman/listinfo/midrange-l
> or, via email, send a message with subject or body 'help' to
>         midrange-l-request@xxxxxxxxxxxx
>
> You can reach the person managing the list at
>         midrange-l-owner@xxxxxxxxxxxx
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of MIDRANGE-L digest..."
>
>
> *** NOTE: When replying to this digest message, PLEASE remove all text
> unrelated to your reply and change the subject line so it is meaningful.
>
> Today's Topics:
>
>    1. Re: Row Change Timestamp (rob@xxxxxxxxx)
>
>
> ----------------------------------------------------------------------
>
> message: 1
> date: Wed, 19 Jun 2013 12:53:08 -0400
> from: rob@xxxxxxxxx
> subject: Re: Row Change Timestamp
>
> I do stand corrected.  That other thread led me astray, or I read it
> wrong.
> This table:
> CREATE TABLE ROB/RAULDATE
> (MODDATE TIMESTAMP NOT NULL for each row on update
> as row change timestamp,
>  crtuser char (18) with default USER,
>  MYDATA CHAR (5 ) NOT NULL)
> RCDFMT RAULDATER
>
>
> with three rows inserted, A, B, C
>
> with this program (caution, cycle!!);
> FRAULDATE  UP   E             DISK
>  /free
>   select;
>   when mydata='A';
>     mydata='D';
>   when mydata='B';
>     mydata='E';
>   when mydata='C';
>     mydata='F';
>   when mydata='D';
>     mydata='A';
>   when mydata='E';
>     mydata='B';
>   when mydata='F';
>     mydata='C';
>   endsl;
>   update rauldater;
>  /end-free
>
> Updated the row change time stamp to the current timestamp.
> If I used sql to
> UPDATE RAULDATE SET CRTUSER='PETE'
> and rerun the program it does not change CRTUSER from 'PETE' to 'ROB'.
> I guess that's a difference between "as row change" vs "with default".
>
>
> 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
> http://www.dekko.com
>
>
>
>
>
> From:   "Raul A. Jager W." <raul@xxxxxxxxxx>
> To:     Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>,
> Date:   06/19/2013 09:47 AM
> Subject:        Re: Row Change Timestamp
> Sent by:        midrange-l-bounces@xxxxxxxxxxxx
>
>
>
> Please verify, I think the "row change timestamp" will be set by the db2
> to the correct value regardless of what the RPG sends.
>
> rob@xxxxxxxxx wrote:
>
> > Gad,
> >
> > Vern's right, you'll have to use DDL instead of DDS.
> >
> > Now, on part b; yes you can update it with RPG and it will autofill the
> > row change time stamp providing you do one of a few things:
> > 1 - Use sql to update/add a row and do not specify the column containing
> > the row change timestamp.
> > 2 - Use an index that does not include the row change timestamp.  Or if
> > you're just stubborn enough to create a DDS LF over a table defined with
> > DDL you can but just don't include that row change timestamp into that
> LF.
> > 3 - Internally define the file and only output certain columns omitting
> > the row change timestamp.
> >
> > Otherwise, once you update/add the row with RLA then the row change
> > timestamp will be in the I/O buffer and will get overridden.
> >
> > This was the topic of a very recent thread.
> > http://archive.midrange.com/midrange-l/201305/msg00934.html
> > You'll have to thread down through it to get the right thread.
> >
> >
> >
> >
> > Rob Berendt
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>
>
>
> ------------------------------
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) digest list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>
>
> End of MIDRANGE-L Digest, Vol 12, Issue 1328
> ********************************************