RE: Data access for non-AS400 devs?

I misstated myself, too, Loyd - sorry.

OpsNav is probably your best bet. There is a plugin for WDSC but it does not 
handle everything. And setup is not for the faint of heart. Also, you want to 
be sure to be careful about filters you set up. There's also just the Database 
perspective of WDSC. My comments about filters may apply to that directly. 
Maybe look in the archives for the WDSC list here. There is also a client for 
DB2 generally that can work against the iSeries. Again, IIRC, it misses some 
things. I think it's the Administration client you get with DB2 on the PC.

Go with OpsNav.
-------------- Original message -------------- 

> Thanks Rob. As I said to Vern, I may have mis-phrased my request. I'm 
> looking for non-5250 tools to allow a non-AS/400 developer access SQL data 
> on the iSeries, a la Query manager. Thankfully this is an actual SQL 
> database with relationships. 
> 
> I'm trying to avoid command line training if possible. 
> 
> Loyd Goodbar 
> Senior programmer/analyst 
> BorgWarner 
> E/TS Water Valley 
> 662-473-5713 
> 
> -----Original Message----- 
> From: midrange-l-bounces@xxxxxxxxxxxx 
> [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx 
> Sent: Monday, September 12, 2005 11:47 
> To: Midrange Systems Technical Discussion 
> Subject: RE: Data access for non-AS400 devs? 
> 
> 5250 supports: 
> 
> STRSQL. (as others have commented) Providing you have 57##ST1 loaded on 
> your system. 
> 
> RUNSQLSTM (store your SQL source, like CREATE PROCEDURE, in a source 
> member and execute it with RUNSQLSTM). I use this for where I used to use 
> QDDSSRC. No additional program products needed. 
> 
> STRQMQRY. Store your SQL source in a source member. Run CRTQMQRY on it 
> to "compile" it. Execute it with STRQMQRY. No additional software 
> needed. 
> 
> STRQM. Provides a method to do prompted (like Query/400) or SQL method. 
> If you had a choice between purchasing Query/400 or 57##ST1, buy 57##ST1 
> to also get the imbedded SQL capability. 
> 
> Imbedded SQL. Needs 57##ST1 loaded on your system. And some HLL 
> compiler. Allows you to imbed SQL in a HLL program. For instance, if you 
> wanted to write a RPG program and have it return a result set as a SQL 
> stored procedure, comes in mighty handy. 
> 
> SQL CLI. Compiler of choice needed. Much more work than imbedded SQL. 
> Has some minor capabilities not available to imbedded SQL. Only people 
> who use it are: 
> - Those who get a testosterone rush out of doing things the hard way. 
> - Those who will not upgrade to V5R3 which fixed many of the limitations 
> of the imbedded SQL precompiler 
> - Those who do not have the means to purchase 57##ST1. 
> - Those who need that one or two obscure little feature not supported by 
> imbedded SQL. 
> (See the sorcerers guide for more information.) 
> 
> But, for ad hoc, iSeries Navigator isn't bad. 
> 
> Rob Berendt 
> -- 
> Group Dekko Services, LLC 
> Dept 01.073 
> PO Box 2000 
> Dock 108 
> 6928N 400E 
> Kendallville, IN 46755 
> http://www.dekko.com 
> -- 
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list 
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx 
> To subscribe, unsubscribe, or change list options, 
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l 
> or email: MIDRANGE-L-request@xxxxxxxxxxxx 
> Before posting, please take a moment to review the archives 
> at http://archive.midrange.com/midrange-l. 
>