Okay, here's my on-topic post for the month!

We have occasion to store "static" data (and by that I mean data that may
change only infrequently, if ever, things like the skid deposit charge or
the minimum charge for rework, etc.).  Now, I dislike making these items
constants in a program since that requires me to change the program and
recompile it if the "static" data does, in fact, change.

So, I've sometimes seen this type of data stored in a "flat" file,
especially if it's "control" data of some kind that pertains to only one
program or set of programs.  However, I've also seen this type of data
stored in an Image data set (usually a master data set that has as a key
some kind of control-id or sequence number), especially often-changed static
data, like the next sales order number, but also for lesser-changed static
data, like the current copper cost which only changes once a month.

Anyway, my question is this:  Does it make more sense to store this data in
an Image data base where it is more "protected" (my impression only, is it
really?) rather than in a "flat" file, which, by implication, is less
well-protected?


Jim Phillips                           Information Systems Manager
Email: [log in to unmask]     Therm-O-Link, Inc.
Phone: 330-527-2124                         P. O. Box 285
Fax:   330-527-2123                           10513 Freedom Street
Web:   http://www.tolwire.com          Garrettsville, OH  44231

I WANT MY MPE!

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *