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

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

Thanks Mike...

I looked in the QB5* jobs but didn't see any other error messages...

Actually, I've never tried STRRSESVR...but it might be helpfull, since I
can start that from my Profound screen...

It may get around some authority issues...

Charles

On Thu, Oct 26, 2017 at 7:07 AM, Mike Hockings <hockings@xxxxxxxxxx> wrote:

Hey Charles,

I'm not sure what your problem is but the callback does not affect setting
the SEP. That is use for the STRRSESVR session. When it fails it means
that the IBM i can't resolve to your PC for some reason. Typically if that
is an issue I'd recommend using SEP for debug rather than STRRSESVR ;)

And yes, it does sound like some security or network issue is blocking
things but what exactly I don't know. Maybe look at the joblogs for the
QB5* jobs for errors? If your RDI is working for your development LPAR and
you see this problem on your production LPAR then I would say that your
workspace is fine so look at the network and IBM i for the production
LPAR...

Mike

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.