Hi,

currently ROW CHANGE TIMESTAMP works only with SQL, not yet with native I/O
or update data.
I also opened a call at IBM.

Mit freundlichen Grüßen / Best regards

Birgitta Hauser

"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"

-----Ursprüngliche Nachricht-----
Von: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] Im
Auftrag von rob@xxxxxxxxx
Gesendet: Friday, 22. May 2009 19:37
An: RPG programming on the AS400/iSeries
Betreff: %fields in write op code will NOT support 6.1 ROW CHANGE TIMESTAMP
function.

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

This thread ...

Replies:

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].