RE: Checking for uncommitted changes

["Jeffrey M. Silberberg" <silbrbrg@xxxxxxxxxx>]

  Well, how about a Trigger program that sets a flag in a data area or a 
message in the Job's Message Queue, either of which can be checked for 
before the job ends or as needed, without major mods to the existing code 
stack. 

        Jeff Silberberg 

On Mon, 4 May 1998, Walden Leverich wrote:

> We had originally thought of that. But it is actually not a KISS solution.
> Passing a flag requires that every program (programmer) pass it as a
> parameter, and more importantly, remember to update the flag whenever he/she
> updates the database. This seems more complex (read: error-prone) than
> simple asking DB2/400 if there are any pending updates.
> 
> -Walden
> 
> -----Original Message-----
> From: owner-midrange-l@midrange.com
> [mailto:owner-midrange-l@midrange.com]On Behalf Of Vernon Hamberg
> Sent: Wednesday, April 29, 1998 12:40 PM
> To: MIDRANGE-L@midrange.com
> Cc: walden@techsoftinc.com
> Subject: RE: Checking for uncommitted changes
> 
> 
> Walden
> 
> At 04:11 PM 4/23/1998 -0400, you wrote:
> >I'm afraid that this doesn't work. I've attached the program I used to test
> >this below, if you see something let me know, but otherwise....
> >
> >As for why we are using this: We allow the user to travel through a suite
> of
> >screens leaving uncommitted changes behind him (don't blame me), then when
> >he exits the suite of screens we will prompt him to save (commit) or
> discard
> >(rollback) these changes. If he has not made any changes we don't want to
> >bother asking.
> 
> Here's maybe a bad idea:
> 
> What about setting some flag within the apps when moving from screen to
> screen? If the extent of change isn't too great, would this be the KISS
> principle answer?
> 
> HTH
> 
> Vernon Hamberg
> Systems Software Programmer
> Old Republic National Title Insurance Company
> 400 Second Avenue South
> Minneapolis, MN  55401-2499
> (612) 371-1111 x480
> 
> 
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator:
> david@midrange.com
> +---
> 
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator: david@midrange.com
> +---
> 
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---