|
I actually prefer STRSQL on the iSeries for learning SQL and trying things out. It will give you results faster, in my experience. F4 is your friend here, as well as on the command line. The drawback is, it has not kept up with some of the modern additions to SQL on iSeries. E.g., it does not prompt for JOIN syntax, although it will process it. You CAN create stored procedures in it, so it's not too bad. When creating SPs, BTW, be sure to use VARCHARs, not CHARs - literals are passed as VARCHARs and will not match is the parameter is a CHAR. HTH Vern -------------- Original message -------------- > Rob, Vern, > > Thanks for the suggestions, now I know I'm in the right direction. > > For now the focus is more on the SQL-side than VB; running SQL statements to > analyze the data. Are there other iSeries tools besides Navigator for SQL > statements? I'd love to get Query Analyzer to talk to the 400 but that's not > gonna happen. > > Unfortunately (for me), I am the one with some of the data knowledge to > write SPs or views of the data. The person who would have done this in our > department left for another company. > > Thanks, > Loyd > > 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 10:29 > To: Midrange Systems Technical Discussion > Subject: Re: Data access for non-AS400 devs? > > There are multiple ways of handling this. > > Yes, he will need a user id and a password. > > Most i5/os shops do not do adequate security on their data - still > trusting to 5250 menus to do it for them. Therefore you may wish to look > at exit point software from NetIQ, PowerTools, etc to make sure that this > new user does only what they are supposed to do. > http://faq.midrange.com/data/cache/198.html > > You could write some stored procedures that join the data, etc, on the > server and only returns what is necessary. May enhance security, help > performance, and shift the complexity from the non-AS/400 developer to an > i5/OS developer who is more familiar with the application. > > Rob Berendt > -- > Group Dekko Services, LLC > Dept 01.073 > PO Box 2000 > Dock 108 > 6928N 400E > Kendallville, IN 46755 > http://www.dekko.com > > > > > > "Goodbar, Loyd (ETS - Water Valley)" > Sent by: midrange-l-bounces@xxxxxxxxxxxx > 09/12/2005 09:37 AM > Please respond to > Midrange Systems Technical Discussion > > > To > Midrange Systems Technical Discussion > cc > > Subject > Data access for non-AS400 devs? > > > > > > > I have a single library's data that a non-AS/400 developer (SQL Server/VB > type) would like to have real-only access. He wants to perform "data > mining" > over the data. This is not financial or inventory related but a vendor > supplied maintenance/PM package. He uses Microsoft SQL Server tools > (enterprise manager, query analyzer). > > > > I'm assuming he'll need an AS/400 user ID and security to the library. I'm > only familiar with iSeries Navigator for a GUI view of the database and > running SQL. > > > > How have you handled this situation, what tools are required? How have you > handled this situation, what tools are required? > > > > Any ideas/suggestions are appreciated. > > > > Thanks, > > Loyd > > > > > > Loyd Goodbar > > Senior programmer/analyst > > BorgWarner > > E/TS Water Valley > > 662-473-5713 > > > > -- > 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. > > > -- > 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. > -- > 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. >
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.