It's an interesting question, and you might want to re-post it at the MI400
list. I'd like to see how the responses go there, myself.

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
"Fear of becoming a has-been keeps some people from becoming anything."
-- Eric Hoffer


Thanks Dennis.
Then I'll probably resort to another solution. The view thing just
isn't
maintainable. I'm just wondering how this is really handled under the
covers
of an RPG write for instance... I would think there would be a way to
simulate that.

Best wishes,
Erik

2010/9/16 Dennis Lovelady <iseries@xxxxxxxxxxxx>

The only choice I see in that case is that you could create a view
over the
table that excludes the columns you don't want to write. Then write
to
that
view.

Unless I'm missing something, your alternatives are to do that; or to
drop
to SQL for the INSERT; or to generate and write the timestamp.

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
Fear less, hope more,
eat less, chew more,
whine less, breathe more,
talk less, say more,
hate less, love more,
and all good things will be yours.
-- Swedish proverb


If I have DDL defined tables with columns holding DB2 generated
values
such
as ROWID, defaults as CURRENT_TIMESTAMP etc - how do I code a write
to
records like that using _Rwrite? To be overly clear, I don't want
to
generate say the timestamp in my code, I want DB2 to insert the
current
timestamp for each write on these types of columns. Any input
appreciated.


This thread ...

Follow-Ups:
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].