×
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.
Rudimentary questions follow. I believe I read the material correctly.
I also believe I have misunderstood what I read. Hence the questions.
This venture in to ROW CHANGE TOKEN territory is because of
recommendations made here. The whole concept is brand new ground for
me. I am looking to solve the "was it changed at another workstation?"
problem.
Is ROW CHANGE TOKEN a reliable solution or do I need to also use a
timestamp column and compare both fields?
Is ROW CHANGE TOKEN a valid solution for V5R4 releases & forward?
This statement gives me SQL 0104:
CHANGE_TS TIMESTAMP FOR EACH ROW ON UPDATE
AS ROW CHANGE TIMESTAMP NOT NULL);
This is a direct copy/paste from an IBM site.
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
