Difference between revisions of "Query"

From MidrangeWiki
Jump to: navigation, search
(links)
(Recategorized article and corrected inaccuracies.)
Line 1: Line 1:
[[Category:Programming]]
+
[[Category:Database]]
[[Category:CaseTools]]
+
Query/400 is a basic user oriented database report writer.
  
Purists might say that Query/400 is not a "real" programming language, rather it is a CASE tool.  I personally find that Query/400 is very powerful for rapid development of simple reports and inquiries, with many features that may be under-utilized.
+
It is designed to allow non-technical users to create basic reports and online inquiries in a simple, menu driven way.
  
For example, I have a query that uses LIKE '%SOMETEXT%' to search fields of a data base for SOMETEXT where the % means I not care what stuff is in front of or behind the matching text.
+
It is a tool that is pretty safe to put into the hands of users, so long as we know how to prevent them from creating an *OUTFILE that gets same name as a pre-existing real file in our data base.
 
 
I also have queries that create like *OUTFILEs that are then input to other queries.
 
 
 
Query/400 is a tool for accessing [[DB2]]/400 that is pretty safe to put into the hands of users, so long as we know how to prevent them from creating an *OUTFILE that gets same name as a pre-existing real file in our data base.
 
  
 
See [[CLP/400 examples]] of [[CLP]] programs that give people access to Query stuff that can go on a Menu, so that they do not have Command Line Access which has some security concerns.
 
See [[CLP/400 examples]] of [[CLP]] programs that give people access to Query stuff that can go on a Menu, so that they do not have Command Line Access which has some security concerns.

Revision as of 15:11, 26 May 2005

Query/400 is a basic user oriented database report writer.

It is designed to allow non-technical users to create basic reports and online inquiries in a simple, menu driven way.

It is a tool that is pretty safe to put into the hands of users, so long as we know how to prevent them from creating an *OUTFILE that gets same name as a pre-existing real file in our data base.

See CLP/400 examples of CLP programs that give people access to Query stuff that can go on a Menu, so that they do not have Command Line Access which has some security concerns.