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



I think we've run across this one before. If your users are connecting via
TCP/IP, and you are not using named sessions(ie. your device is named
QPADEV001 instead of PCLOU or something similar), and you have a LOT of
devices configured, the break message is sent to EVERY one of them. Since
you get the next available device name every time you connect, it may seem
like the message is not going away, but you are actually getting the msgq
for that workstation, which wasn't yet cleared.

One of our larger customers did this a while ago. They have several hundred
users, many of whom have several sessions going at once. What we wound up
doing was signing in over the weekend, and manually clearing all the device
msgq's. Didn't take more than 10 or 15 minutes.

Hope this helps,


Lou Schmaus
CCA, Inc.
lschmaus@link400.com
www.freightblue.com


-----Original Message-----
From: midrange-l-admin@midrange.com
[mailto:midrange-l-admin@midrange.com]On Behalf Of Basit Khan
Sent: Wednesday, October 17, 2001 1:31 PM
To: 'midrange-l@midrange.com'
Subject: SNDBRKMSG is not going away..


One of my users have sent a SNDBRKMSG to all workstations - for some reason
that message appears every time someone signs on to a new session. Yes , we
have removed the message from the current session but for some reason when
we sign on again   it comes back.

Any idea? Thanks

B Khan
Going somewhere? try http://www.medexassist.com




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.