Re: 5250 and un-do -- RPG400-L

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: Re: 5250 and un-do
From: Booth Martin <booth@xxxxxxxxxxxx>
Date: Mon, 18 Dec 2017 12:32:43 -0600
List-archive: <https://archive.midrange.com/rpg400-l/>
List-help: <mailto:rpg400-l-request@midrange.com?subject=help>
List-id: "RPG programming on the IBM i \(AS/400 and iSeries\)" <rpg400-l.midrange.com>
List-post: <mailto:rpg400-l@midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=unsubscribe>

Make the plan with no protracted locks. That's pretty standard practice now, thanks to the training you and others provide for us.

I like the idea of an array with before/after image of each change made. It works even for two users in the same file. If I undo, get the data, compare it to my after image and it is different then I know another user changed the data and I need PlanHuh? If the images compare, then make the data the before image and it's undone.

On 12/18/2017 12:15 PM, Jon Paris wrote:

It also assumes a lock on all objects affected!

Jon Paris

www.partner400.com
www.SystemiDeveloper.com

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: 5250 and un-do , Justin Taylor
Re: 5250 and un-do , Henrik Rützou

This mailing list archive is Copyright 1997-2026 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.