×
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.
On 9/16/2010 5:38 PM, M. Lazarus wrote:
Barbara,
I was hoping that it wouldn't work that way, but thinking about the way
RPG handles initializations, that behavior makes sense. I wonder if an
additional keyword value would be in order, e.g. INZ(*CURRENT) or
INZ(*CURRENTADD).
-mark
That wouldn't really fit with the notion of "initialization".
But aside from that, the problem is when to update the timestamp. Every
time the subfield or data structure is used? What if it's passed as a
parameter - assuming the callee is another RPG procedure, should it know
that the timestamp field has to be updated before it's used?
Just thinking aloud now ... one way to do this would be to have a
special value in the actual timestamp field like "*CURRENT". Then,
whenever the timestamp was evaluated it would use the current timestemp.
Date, time, and timestamp fields would have to be tagged with
something like ALWCURRENT(*YES), so that an assignment could copy over
the "*CURRENT" rather than just assigning the then-current timestamp.
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.
midrange.com
