|
BTW - I wish there were good documentation on using service entry points from the green screen - it is very sketchy as to the steps it takes. It is very cool but is not obvious what to do. Vern -------------- Original message -------------- From: MichaelQuigley@xxxxxxxxxx
Vadim, Is it still a requirement to have *ALLOBJ or *SERVICE special authority to set a service entry point (SEP) on another user ID? When I asked you about it at COMMON in the Fall of 2005, you said it didn't seem like it should be a requirement. But I've never checked back on it. SEPs are great, but we can't use them in a lot of situations. The level of special authority is the hold-up for us. It seems that having *USE or *CHANGE authority to the profile in question should be enough. Thanks, Michael Quigley AS/400 Programming Section The Way International www.TheWay.org wdsci-l-bounces@xxxxxxxxxxxx wrote on 11/28/2006 09:46:28 AM:date: Tue, 28 Nov 2006 09:32:07 -0500 from: Vadim Berestetsky subject: Re: [WDSCI-L] Interactive Debugging Hi Bill, Yes, you could use something called a Service Entry Point (SEP) that is setup in advance. Right-click on the program, module or procedure you are interested to debug from RSE and the option will be on the popup menu. When program/module/procedure is invoked on the iSeries host, debugger will get control, provided user IDs do match. Try it, you'll like it! Hope this helps. Vadim-- This is the Websphere Development Studio Client for iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/wdsci-l or email: WDSCI-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/wdsci-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.