Re: SQL vs DDS -- MIDRANGE-L

This sounds pretty good, and we've got our own development machine.  And we 
use SQL.  I was trying to think of reasons why to keep using DDS.

On a production machine how would you recreate a file on the fly?  Granted, 
I try to get away from this as much as possible, but I used to write 
applications 
that contained CRTPF commands that used DDS.  I thought about the RUNSQLSTM 
command.  Thought this would be a neat area to keep my SQL source for my 
files.  However RUNSQLSTM doesn't work on the production machines.  Perhaps 
I could put the source into a Query Management Query.  While the prompter 
(STRQM) is only available on the development machine, it can be run, 
(STRQMQRY, CRTQMQRY, etc) on any machine.  In fact we use STRQMQRY in the 
RUNSQL command to give us a poor man's SQL on the production machines.

But I do like the ability to combine a view and an index in DDS.

And I still think it would be an improvement if STRSQL could prompt for fields 
from the database catalog.





rbruceh@ibm.net on 08/25/99 09:12:36 AM
Please respond to MIDRANGE-L@midrange.com@Internet
To:     MIDRANGE-L@midrange.com@Internet
cc:      
Fax to: 
Subject:        Re: SQL vs DDS

"Al Barsa, Jr." wrote:
> We are currently examining the feasibility of putting enhancements like
> column level security into CL commands within TAA Tool.
> 

I understand the reasoning behind this, but it is not the command
process that is lacking. Commands can be issued from SQL to the
database. It is the DDS issue. Put in source and compile your files.
Will you be able to define User Defined Fields and Functions and then
reuse them in DDS? No.

Yes, I know, a lot of people don't have the SQL toolkit on their 400.

My question would be "Why not?". No administrator of another system
would consider installing the database product without the SQL toolkit
unless it were a standalone, non-development environment.

AS/400 users should NOT cripple themselves by not making the tools
available to their programmers. The defacto, primary tool of all
database professionals (outside of the AS/400) is SQL.

If cost is a limiting factor, get a development machine. Pricing of
these tools and others is VERY favorable at the P05 or P10 pricing
levels.

Production: 500 users, 530 4-banger. Development: 170 with SQL, Java,
RPG, COBOL and C. The fees saved in the languages more than cover the
cost of the 170. Not to mention the significant impact of removing
developers from the production environment.

With this scenario, there is no good reason that developers could not
choose the appropriate tool for whatever job they are facing.

-- 
===========================================================
R. Bruce Hoffman, Jr.
 -- IBM Certified AS/400 Professional System Administrator
 -- IBM Certified AS/400 Professional Network Administrator

"The sum of all human knowledge is a fixed constant.
    It's the population that keeps growing!"
+---
| 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.com
+---