Re: SQL statements for physical and logical files

As far as block sizes being controlled by create and change commands I
believe I stated that the defaults for DDL are more modern than DDS
defaults. I did say that these can be overridden by create and change
commands. But that having these outside of the "source" increases the
likelihood of them not being used by the next developer to come along.

Your DB event handlers sound much like externalizing I/O with stored
procedures and all. That may be ok for your shop but I don't feel that a
majority of shops are going to go that route.
I do realize that coding habits will have to change. For example,
assuming an error on a write RPG op code is because the row already exists
and you should then do a chain and update is going to have to go the way
of the dodo bird.

<snip>
DDS vs. DDL? In regards to physical files and indexes, why push one or the
other?
</snip>
Because of the reasons I outlined in my earlier email.
Because of the reasons Birgitta outlined.

Rob Berendt