× 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.



"WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx> wrote on 10/25/2017 01:00:02 PM:
----- Message from Charles Wilt <charles.wilt@xxxxxxxxx> on Tue, 24
Oct 2017 12:11:37 -0600 -----

To:

"Rational Developer for IBM i / Websphere Development Studio Client
for System i & iSeries" <wdsci-l@xxxxxxxxxxxx>

Subject:

Re: [WDSCI-L] SEP not working...

Not yet, was hoping for an unofficial..."hey check this..."

But a PMR is the next step I guess..

Charles

On Tue, Oct 24, 2017 at 10:23 AM, Jon Paris <jon.paris@xxxxxxxxxxxxxx>
wrote:

Have you reported this as a problem to IBM?


Jon Paris

www.partner400.com
www.SystemiDeveloper.com

On Oct 24, 2017, at 11:40 AM, Charles Wilt <charles.wilt@xxxxxxxxx>
wrote:

Guys,

Setting an SEP works fine for our non-production boxes.

It's our production box I'm having an issue with. Thus the reason I
suspect a network or security issue.

I would second opening a PMR. The only other suggestions I would have are
two authority questions:

1 - Do you have *CHANGE authority to the program being debugged?
2 - Do you have *CHANGE authority to the user profile for the job to be
debugged?

But I would think a lack of either of these would prevent you from setting
the SEP.

Michael Quigley
Computer Services
The Way International

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.