Dave,

You're right, you can configure iSeries Access to limit your install, but
does that truly limit what they can access? The answer is no. A crafty
user might find his own copy of CD's or load a different driver (like
mochasoft vs iSeries Access 5250).

There are a couple of different ways to secure that. One is to use the no
charge item iSeries Navigator. There is an item in there called
"Application Administration". You can limit ODBC etc by user and stuff.

Now, that still might not have the granularity that you need. For
example, you might want to limit your users to only being able to download
this one work file in this one library. And you don't want to go through
the bother of configuring security to "application only" access. You can
use "exit points" to achieve this. We did this at one time. Of course it
only took our users about 5 seconds to realize that this was a temporary
work file and they could use Query/400 to overwrite it with any darn data
they wanted to.

If you don't want to roll your own, or figure the money spent developing
that can be better spent on buying a package that handles ALL exit points,
and keep it maintained for OS upgrades, new exit points, etc, then there
are several packages out there: Power Tech, NetIQ and a plethora of
others.

Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.