× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Let me understand this correctly. Let's say I just started up WDSC and
added a SEP for PGM1. Then my brother (named Larry) also sets an SEP for
PGM1. IBM's reasoning for not removing the SEP on the server when I remove
it from WDSC is because somebody else *might* be using it? Can't you tell
how many client side WDSC sessions are tied to a single SEP? I would guess
you should be able to because it has to know how to get back to my PC in
some way shape or form.

IMO this is introducing a VERY frustrating complexity for the user (me the
programmer) because of a scenario that will happen 1/10th of 1/100th percent
of the time. Am I missing something?

Aaron Bartell
http://mowyourlawn.com


On Fri, Oct 17, 2008 at 11:06 AM, Xuan Chen <xuanchen@xxxxxxxxxx> wrote:

The reason why remove/re-add does not work is because the way we
implemented SEP.
In order to set an SEP, you need to add the program into debug in the SEP
server. When SEP is removed, we don't remove the program from debug since
could be other SEPs added to it. But when program is recompiled, if you
still used the old program to add SEP (the one already added into debug),
it won't work any more. So the refresh action to the implementation
really means we need to refresh the program (remove from debug, and add it
back in).

Thanks,

Xuan Chen, Problem Determination Tools for iSeries
(905) 413-3769 T/L 313-3769
xuanchen@xxxxxxxxxx




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.