|
We use them to set file overrides for ODBC JDBC applications. As the user establishes the connection, we check the user, bail if it isn't authorized and if they are authorized we set the file overrides for the job based on a profile they have. Once unexpected benefit was when we started using JDBC to connect to the iSeries and the overrides were there "automagically". I didn't realize, until we actually used JDBC, that it connects using the same server job and triggers the same exits as ODBC. Took care of a bunch of file override/access issues. Pete Helgren Value Added Software,Inc. 801.581.1154 x202 -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of rob@xxxxxxxxx Sent: Thursday, July 22, 2004 3:07 PM To: Midrange Systems Technical Discussion Subject: Exit points in practice, was Net-IQ exit point I'll give you a couple of examples of exit points in practice. 1) I had a command on the system that I wanted to convert to another command. Now, I could have done the usual trick with the system library list, and so on. However there were business reasons that I chose otherwise. I used the command exit point to add a exit point program. The program receives the command and it's parameters as parameters. I analyze that and run my command instead. 2) One of the most popular ones is the ftp exit point. I've done lots of stuff with that. a) If the user signs on as anonymous I switch them over to another user profile. b) I restrict what libraries, directories, commands, puts, gets, etc that any user can do. c) If one customer sends us a file we can then automatically post that file. this list is only limited by your imagination. Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com |-----------------------------+-------------------------------------------| | jared | | | <jhunter@xxxxxxxxxxxx> | | | Sent by: | To| | midrange-l-bounces@midrang| Midra| | e.com | nge | | | Syste| | 07/22/2004 03:39 PM | ms | | | Techn| | Please respond to | ical | | Midrange Systems | Discu| | Technical Discussion | ssion| | <midrange-l@xxxxxxxxxxx| <midr| | m> | ange-| | | l@mid| | | range| | | .com>| | | cc| | | | | | Subject| | | Re: | | | Net-I| | | Q | | | exit | | | point| | | | | | | | | | | | | | | | | | | |-----------------------------+-------------------------------------------| Interesting question. If you wouldn't mind sharing some of the information you receive, I think it'd really help me understand how exit functions are actually used in practice. /j On Thu, 22 Jul 2004, Elvis Budimlic wrote: > I'm interested if anyone from Net-IQ or using their exit point security > software can clear something up for me, by private email if possible. > > Does Net-IQ's exit point security product permit for "daisy chaining" of > exit point programs? > > Basically, if one already exists at the time of install do they make sure it > is invoked by their exit point program? > > And more importantly, does Net-IQ's exit point program know/care if it is > "daisy chained" and invoked by another exit point program? > > > > Elvis > > > > -- > 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.