Re: How to develop, test and debug QM (Query Manager) SQL queries in WDSCi 7?

[Jeff Young <cooljeff913@xxxxxxxxx>]

Bill,
You can develop your SQL in WDSc using one of the DB Plug-ins or use the STRSQL (green screen) or the INav DB tool, then copy the completed SQL to a source member and use that to create your QM Query.
From the QM Query, change the selection from Prompt to SQL, then save the Query in a source file.

 
Jeff Young 
Sr. Programmer Analyst
IBM -e(logo) server Certified Systems Exper - iSeries Technical Solutions V5R2 
IBM  Certified Specialist- e(logo) server i5Series Technical Solutions Designer V5R3
IBM  Certified Specialist- e(logo)server i5Series Technical Solutions Implementer V5R3 


  
 





----- Original Message ----
From: "bill.blalock@xxxxxxxxxxx" <bill.blalock@xxxxxxxxxxx>
To: wdsci-l@xxxxxxxxxxxx
Sent: Friday, August 3, 2007 1:31:22 PM
Subject: [WDSCI-L] How to develop, test and debug QM (Query Manager) SQL queries in WDSCi 7?


Hi all:

The DB plug-in thread motivated me to share a problem with you that I've 
been kicking around for a while.

We are using QM (Query Manager ... STRQM) on the System i to execute SQL 
queries.  We also use QM forms and procedures.

The SQL can be exported from QM into a source data base memeber and 
imported to QM.

I called IBM to ask if WDSCi supported QM and was told basically "no".

I am looking for some ideas on how do approach these tasks.

- Develop, test and debug SQL in WDSCi then import it into QM.
- Export SQL from QM into WDSCi, work on it, then import it from WDSCi 
into QM.

Am I missing something simple? 

Thanks all.

------------------------------------------------------------------------------
This message contains information from Certegy, Inc which may be confidential and privileged.  If you are not an intended recipient, please refrain from any disclosure, copying, distribution or use of this information and note that such actions are prohibited.  If you have received this transmission in error, please notify by e:mail postmaster@xxxxxxxxxxxx
==============================================================================