Re: Is is safer to define a file using SQL if you are using PF constraints?

[Rob Berendt <rob@xxxxxxxxx>]

One thing I like about DDS with logical files is the ability to combine the 
function of SQL's VIEW and INDEX.





ncsmith@gate.net on 04/14/2000 09:20:15 PM
Please respond to MIDRANGE-L@midrange.com@Internet
To:     MIDRANGE-L@midrange.com@Internet
cc:      
Fax to: 
Subject:        Re: Is is safer to define a file using SQL if you are using PF 
constraints?

Is anybody out there managing their entire AS400 database exclusively with
SQL and not DDS?  If so, what are the pros and cons in real life?  Has
anyone replaced their reference file with UDT's?  Is that workable?  Since
they are individual objects, how do you organize and control them?  Or, do
you just do without any kind of field referencing?

I've considered going in this direction because of all the nice PC based
modeling tools and the feeling that we might could have a more organized
database, but wonder if I'm being too rash.

----- Original Message -----
From: "Rob Berendt" <rob@dekko.com>
To: <MIDRANGE-L@midrange.com>
Sent: Friday, April 14, 2000 12:17 PM
Subject: Re: Is is safer to define a file using SQL if you are using PF
constraints?


> RUNSQLSTM would probably work.  The only advantage to SQLRPGLE
> is the compiled code will execute everywhere, whilst RUNSQLSTM
> will only execute on a 400 with SQL.
>
>
>
>
>
> shc@flybynight.com.au on 04/14/2000 10:47:26 AM
> Please respond to MIDRANGE-L@midrange.com@Internet
> To: MIDRANGE-L@midrange.com@Internet
> cc:
> Fax to:
> Subject: Re: Is is safer to define a file using SQL if you are using PF
constraints?
>
>
> Hello Rob,
>
> If you can't trust your colleagues to rebuild the database properly then
nothing will
> save you.  Using SQL DDL is probably a safer approach -- at least the RI
will be part of
> the creation process.  You will have to remove all trace of the original
DDS from the
> system to remove the possibility of error.
>
> If you use alter table (either CHGPF or via SQL) to rebuild the files
rather than
> compiling them you will keep the RI constraints and the data.
>
> Can't you use RUNSQLSTM to rebuild the database rather than SQLRPG?  Or do
you need
> additional programmatic control?
>
> Regards,
> Simon Coulter.
>
> ©g©g©g©g©g©g©g©g©g©g©g©g©g©g©g©g©g©g©g©g©g©g©g©g©g©g©g©g©g©g©g©g©g©g
> ©g FlyByNight Software         AS/400 Technical Specialists       ©g
> ©g Eclipse the competition - run your business on an IBM AS/400.  ©g
> ©g                                                                ©g
> ©g Phone: +61 3 9419 0175      Mobile: +61 0411 091 400           ©g
> ©g Fax:   +61 3 9419 0175      mailto: shc@flybynight.com.au      ©g
> ©g                                                                ©g
> ©g Windoze should not be open at Warp speed.                      ©g
> ©g©g©g©g©g©g©g©g©g©g©g©g©g©g©g©g©g©g©g©g©g©g©g©g©g©g©g©g©g©g©g©g©g©g
> file://--- forwarded
letter -------------------------------------------------------
> > X-Mailer: Worldtalk (NetTalk for Windows NT 4.5-g5)/MIME
> > Date: Wed, 12 Apr 2000 13:34:18 -0500
> > From: "Rob Berendt" <rob@dekko.com>
> > To: MIDRANGE-L@midrange.com
> > Reply-To: MIDRANGE-L@midrange.com
> > Subject: Is is safer to define a file using SQL if you are using PF
constraints?
>
> >
> > I am not here to start a DDS versus SQL war but I have a
> > question I am hoping you can help me hash out.
> >
> > You cannot add PF constraints using DDS.  I have some files
> > that I've built using DDS and then added RI on the files using
> > the ADDPFCST after they were built.  I am afraid that collegues
> > will modify the files and when they recompile all of the Referential
> > Integrity will be lost.  I was thinking that it would be safer
> > to define the files using SQL and write an SQLRPGLE program to
> > rebuild them.  I document the RI in the DDS but who reads that?
>
> +---
> | 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.comm
> +---
>
>
> +---
> | 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
> +---
>

+---
| 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.comm
+---


+---
| 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
+---