|
>> and in my environment--no commitment control, Shame on you <grin> >> shared ODPs more or less forbidden by shop standard This is an interesting remark. One of the reasons given for making shared ODPs verboten are the problems caused by "accidentally" repositioning the DB cursor because of a failure to override to share *NO. AGs really help in this in that the ODP is only shared (by default) within the AG. This makes it much easier to develop apps that "jump sideways" between different sub-applications. >> I haven't found much need for named activation groups. You are in the majority here. I think part of the problem is that we come to regard limitations and restrictions of the system as "features" over the years and to design with them in mind. As I have often said when teaching this new stuff - we have to overcome the classic situation that when all you have is a hammer, after a while all the problems start to look like nails! +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.