Re: Tables and PFs

Hi Evan

I agree that for existing tables/PFs, that it is not too important. It might become more important when looking at creating new objects, where there can be good reasons to take advantage of performance improvements. A discussion of these advantages does require some terminological exactitude, perhaps, at least for a short period of time.

Vern

Evan Harris wrote:

Hi David

No, there really isn't; a PF on the iSeries is basically what the rest of
the IT world else calls a table. The way I look at it is:

- A table is a thing that contains rows and columns and is part of a
database
- A file is a thing that lives in the file system
- The database will almost certainly live within the file system so the
distinction is important

As to your tables from the parameter file they would be better termed lookup
tables or even hashes.

The semantics of what constitutes a table vs. a physical file on the iSeries
is indistinguishable and inconsequential to the rest of the world.

It shouldn't bug you that he says this, it's IT Jargon as opposed to an
iSeries sub-dialect.

Regards
Evan Harris

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of David FOXWELL
Sent: Wednesday, 13 January 2010 4:52 a.m.
To: Midrange Systems Technical Discussion
Subject: Tables and PFs

Is there a simple way to explain the difference between a table and a
physical file a part from one is created by SQL and the other with DDS?
Should it bug me when a coworker says table but means a PF? It does and I'm
not sure why.

Thanks.