SQL DDL Vs DDS (was Re: Field Reference File (was SQL vs. traditional I/O?))

To the best of my knowledge, the three outstanding "nasties" with SQL DDL Vs
DDS are:-

1. Cannot define a combined view/index.
2. Cannot define EDTCDE or EDTWRD (I agree Jim, saves a LOT of time)
3. Cannot define a seperate Format name

Anybody care to add to the list?

Paul

----- Original Message -----
From: "Jim Essinger" <esinger@xxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Friday, July 23, 2004 11:10 PM
Subject: Re: Field Reference File (was SQL vs. traditional I/O?)


>    What about edit codes?  When using DDS you can tell the file what
editing
>    to use on a field.  We do a lot with Social Security numbers and have a
>    system edit code setup to display correctly (999-99-9999).  When using
the
>    iSeries Nagivator to generate SQL statements I get warning/error
messages
>    such as;
>
>    SQL150D   10   EDTCDE (EDTWRD) in column DBT_ORIG_BAL ignored.
>
>    Can SQL define a column with predefined editing?  Sure saves a lot of
time
>    when doing adhoc queries, and works for date data types, dollar
amounts,
>    Social Security Numbers, and the like.
>
>    Jim
>
>    At 02:00 PM 7/23/2004, you wrote:
>
>      Jim,
>
>      You can emulate a field reference file using the WITH NO DATA clause.
>
>      CREATE TABLE EMPLOYEE AS
>      (SELECT EMPLOYEE_ID, NAME, etc. FROM FIELDREF)
>      WITH NO DATA
>
>      Not sure if it was V5R1 or V5R2 it was introduced.
>
>      HTH
>
>      Paul Tuohy
>
>      >> Jim Essinger wrote
>
>      The other thing that DDS _can_ bring to the table is using field
>      reference
>      files, if you design your files that way.  Not do-able in SQL if I
>      remember right.
>
>      Jim