× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Because every prior message [of those quoted below] had already gone askew from what was originally asked, I figured possibly it was a snipe directed at those who had hijacked the thread for their own seemingly unrelated discussion. Seen that way, that indecipherable message was quite hilarious :-) but hardly productive.

Regards, Chuck

On 24 May 2013 04:43, rob@xxxxxxxxx wrote:
What am I looking at here?

Hoteltravelfundotcom on 05/23/2013 07:00 PM wrote:

I don't see this create view
Commitment control . . . . . . . *NONE
Naming convention . . . . . . . *SYS
<<SNIP>>

On Thu, May 23, 2013 at 4:27 PM, <rob@xxxxxxxxx> wrote:

Ah, but does one REALLY need to create the view or index which
omits this field in order for it to be updated automatically even
by RPG RLA? Keeping in mind that the original thought was that if
you do not then RLA will slap an initial value in there. One
workaround was to use the initialize with external default.
<<SNIP>>

Charles Wilt on 05/23/2013 04:01 PM

Seems like a silly request...

It's done so often that IBM has made it even easier to do at
6.1 with the ROW CHANGE TIMESTAMP <<SNIP>>

On Thu, May 23, 2013 at 3:23 PM, aec wrote:

A word of caution, I recently discovered if you have a
DDS-defined or SQL-defined DATE or TIMESTAMP or TIME field
in a file, and insert a record using a field list but do not
include that field name in the list for the values, the write
will automatically use the current timestamp. <<SNIP>>

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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

This mailing list archive is Copyright 1997-2024 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].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.