This doesn't surprise me.

If you really want the ROW CHANGE TIMESTAMP functionality from an RPG
RLA program, just use a logical that doesn't include that field.


On Fri, May 22, 2009 at 1:36 PM, <rob@xxxxxxxxx> wrote:
I submitted a DCR that IBM add %fields bif to write and not just update.
Hope was that this would use default field values on adding new rows to a
table.  IBM said they can do that and 'may' do so in a future release but
won't add support for ROW CHANGE TIMESTAMP

User Group Number - MR0514094047
Document Status - Suggestion
Title - Add %fields to the WRITE statement in RPGLE

This is a reasonable requirement. IBM will consider implementing the
request in a future release.

Additional comment:
The request would not fulfill the background requirement of supporting the
ROW CHANGE TIMESTAMP feature on an RPG WRITE operation.

Using %FIELDS for WRITE would work in a similar way to coding individual
fields on Output specifications.  Any output field not listed in the
%FIELDS list would be output with the RPG default value.  The RPG WRITE
operation is a record-level-access operation.  It is not possible for RPG
to pass only some of the fields in the record to database.

Rob Berendt
Group Dekko Services, LLC
Dept 01.073
Dock 108
6928N 400E
Kendallville, IN 46755

This is the RPG programming on the IBM i / System i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].