|
The basic need is the ODBC driver or OLE/DB provider. VB can use it the same way as it does for SQL Server. The only difference is the connection string for iSeries vs. SQL Server. Or a DSN can be created on the PC. A great site for connection strings, including iSeries, is www.carlprothman.net Security is the main issue, in my view. E.g., if your developer uses a DSN, he/she can change it to get to anything on the iSeries. Or a connection string can be used to get to anything, so the developer has access to all. UNLESS--you use the ODBC exit programs to manage all this. Object-level security can protect you, of course, but not all shops are set up to restrict this access well enough. So the exits, which control first point of contact, can be your best defense. Several products exist to manage this, including John Earl's stuff. Or you can write your own - it's not terribly difficult, just a little fussy. WRKREGINF and page down to QIBM_QZDA_INIT, etc. QZDA is the ODBC handler. IIRC, QIBM_QZDA_INIT handles signing on and is where you would block access by user. Others control where the user can go with his request. More info in InfoCenter in the API section, IIRC. HTH Vern -------------- Original message -------------- > 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. >
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.