× 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-bounces+markp=softlanding.com@xxxxxxxxxxxx wrote on 12/15/2005 
12:24:18 PM:

> I understand what you are saying but I don't think it applies here.
> 
> In your scenario, I can at least go back to the first interactive
> session and delete the messages. 
> 
> However, what I'm seeing is not being able to delete the messages from
> anywhere.
> 
> I make sure that I start WDSCi and get a connection to the box before
> starting any 5250 sessions.  Since I don't have the monitoring thread
> configured to delete the messages, why does it need to allocate the
> MSGQ?  I would expect the UI to allocate it instead.
> 
> Going back to our green screen scenario, I can read the messages from
> any green screen even if I can only delete them from the first one.

The part that you are missing is that the job that is monitoring the 
message queue is running in a background thread.  It is like a 5250 
session you cannot access.  In other words, the UI of WDSC is running in 
one job and the monitoring in a different job.

Mark



_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email 
Security Management Services powered by MessageLabs. 
_____________________________________________________________________________

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.