×
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.
My point is that if we consider the DBMS the part of the OS that
handles triggers, referential integrity, constraints, and has ACID
properties. Then blocking via SEQONLY parameter and the BLOCK
keywords must be done (or controlled) by RPG and/or the OS above the
DBMS.
If it was done by the DBMS, there would be no reason to disallow it,
as evident by the the CPF4028 message, when a file has triggers,
referential integrity and constraints. Nor would we ever have the
situation where a record was written by one program yet not seen by
another. Lastly, we would not need a FEOD(N) which forces "unwritten
records in the block will be written out to the database"
Charles
As an Amazon Associate we earn from qualifying purchases.
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
