|
Elvis, you are correct. For all of the host server exit points, you are limited to a single registered exit program. The NetIQ exit programs all allow for you to define a customer exit program that will be called after the NetIQ exit program has made it's decision on if the transaction will be allowed or rejected. The customer exit is allowed to override the decision. The customer exit is called with exactly the same parameters as NW0001E (registered exit program) was called with. You should also be aware that since the customer exit can change the decision, the customer exit will be called when doing What-If Playback. If you are setting up a triggering mechanism of some kind you will need to make sure to remove the customer exit in the What-If environment. Can you tell us what you are trying to accomplish? I wrote the current NetIQ exit programs so I can tell you if what you are trying to do cause any problems. Kurt TriAWorks, Inc. -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Elvis Budimlic Sent: Thursday, July 22, 2004 4:39 PM To: 'Midrange Systems Technical Discussion' Subject: RE: Net-IQ exit point Chris, you're correct on some of the exit point registries. A lot of them, i.e. for one of the ODBC exit point registries, QIBM_QZDA_SQL1, have a maximum registration entries set at one (1). Do a WRKREGINF and option 5 to see the max for each. That's where the 'daisy chaining' technique comes into play. -----Original Message----- Subject: RE: Net-IQ exit point When working with the iSeries registry, you can specify several exit point programs on one service. This is done by specifying the sequence number. They way it works is, if the first fails, You is OUTTA there. If it passes, the next sequence number is processed. All must pass for the operation to succeed. Chris Bipes -- 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.