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



IIRC, You have to an SE to QINTER that will prvent it from allocating the
device...

ADDWSE SBSD(QGPL/QINTER) WRKSTN(DSP05*) AT(*ENTER)


Charles




On Wed, Jun 5, 2013 at 12:26 PM, Tim Adair <tadair@xxxxxxxxxxxxxxxx> wrote:

I've added a WSE to subsystem QPGMR for both a generic (DSP05*) and
specific
(DSP05A1) session, and most of the time when I bring up the sign-on for the
session (5250 emulation using System i Access (v.6.0) on a Windows Vista
PC), it comes up in QINTER. But if I open another session (which also
comes
up in QINTER) and vary off the first session and then vary it on again, it
will then come up in QPGMR.

Any ideas why this would not come up in QPGMR every time?

I've checked the SBS WSEs and they are fine. QINTER has no WSEs and QPGMR
just has the two I added.

Any thoughts on this are welcome. Thanks in advance.

~TA~

(System is on V7R1. Also, I searched the archives but didn't find any
issue
like this.)

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