× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: RE: Logical Files vs. Physical Keys
  • From: "Sims, Ken" <KSIMS@xxxxxxxxxxxxxxxx>
  • Date: Fri, 24 Mar 2000 19:03:01 -0500

Hi Mike -

>Date: Fri, 24 Mar 2000 12:00:55 -0500
>From: "Mike Cunningham" <MCUNNING@pct.edu>
>Subject: RE: Logical Files vs. Physical Keys
>
>Any coding design that relys on an abnormal termination for a unique key
>error instead of doing a SETLL to see if the key exists before writing a
>record  is just bad design technique

And any coding design that relies on just doing a SETLL is also bad design.
Though small, there is a window between the SETLL and the WRITE when another
job could add a record with the same key.

Use the SETLL to avoid logging unnecessary messages in the job log; but
still have the file coded UNIQUE and use duplicate key error checking to
close that little window.  Which brings us back to the original point ...
having the physical keyed and UNIQUE makes it a lot harder for someone to
remove the unique key checking.

Ken
Southern Wine and Spirits of Nevada, Inc.
Opinions expressed are my own and do not necessarily represent the views of
my employer or anyone in their right mind.

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@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
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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