Re: In defense of the lowly MR

Buck,

In a message dated 97-06-06 13:24:39 EDT, you write:

> UP files work very well for batch jobs, where by definition you can't lock
a 
> record for a long time.  I'd never consider UP for interactive work.  I'd 
> rather use UF with a CHAIN (no lock) for the "get" part of the app, then 
> CHAIN (lock) for the "update" part.  Now, of course, we have the "record 
> changed in the interim" problem to contend with...

Of course, the AS/Set CASE tool provides a %IMC function that automatically
locks the record if the Image hasn't changed since it was last read to allow
update.  You can duplicate this by having an externally defined data
structure (against the file) that you move the values into upon the initial
(non-locking) read.  Then read the record with a lock and move the values
into another data structure (again, based upon the file).  If the two data
structures aren't equal, tell the user that "the record has been updated by
another user" -- otherwise, update it.  This is a LOT easier in AS/Set, but
can be replicated with RELATIVE ease if you're using a PC with an editor that
allows cut and paste in SEU.  It would be even EASIER if you could move a
record format name to a data structure...

JMHO,

Dean Asmussen
Enterprise Systems Consulting, Inc.
Fuquay-Varina, NC  USA
E-Mail:  DAsmussen@AOL.COM

"In America, anyone can become President.  That's one of the risks you take."
-- Adlai Stephenson
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* 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 MAJORDOMO@midrange.com and specify            *
* 'unsubscribe MIDRANGE-L' in the body of your message.  Questions      *
* should be directed to the list owner / operator: david@midrange.com   *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *