Re: Refresh the member lock

Hi, Brian:

What I am proposing would not require _any_ modifications to SEU, per se ... it would be integrated "way down inside" OS/400 data management, such that, once someone has issued a CHKOUT against a source file member, no other user profiles can modify the contents of that member, except for the user profile who issued the CHKOUT. (Similar to the way CHKOUT works in the IFS in those file system that support CHKOUT and CHKIN).

So, even though SEU is "frozen" this enhancement to the "base" OS/400 (or i5/OS or just "i") would still have value, even for folks who are still using SEU, or WDSCi (which is also "frozen" and no longer being enhanced or maintained), as well as RDi or RDp.

All the best,

Mark S. Waterbury

> On 7/29/2011 12:35 PM, Brian May wrote:

I have nothing against what you propose, but keep one thing in mind. SEU (as of IBM i 6.1) is no longer being enhanced. In fact, they are not even adding support for new RPG opcodes, keywords, and BIFs to the SEU syntax checker after 6.1. Chances of getting IBM to add this new feature to use this check in flag is almost nil.

Brian May
IBM i Modernization Specialist
Profound Logic Software, Inc.
http://www.profoundlogic.com
937-439-7925 Phone
877-224-7768 Toll Free

Modernization Made Easy