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


  • Subject: Re: Message Que Allocation
  • From: Dave Mahadevan <mahadevan@xxxxxxxx>
  • Date: Wed, 30 Jul 1997 17:57:09 -0400
  • Organization: Stoner and Associates

Art Tostaine, Jr. wrote:
Dave Mahadevan wrote:

> Folks:
>
> Is there a way to get the user message que deallocated to a job.
> Currently, only the workstation allocated with the message que can
> delete messages from the que.  I would like to be able to delete
> messages from any display.  You can go to the display which has the
> lock
> on the queue and then dlcobj.  Is there another way?
 

Whenever the workstation signs on, use a break message handling program
that receives all messages and forwards them to the WS msgq.  But this
program also looks for a specially coded "deallocate" message, and when
it receives it, it releases the message queue.  Then setup another
program that will send the coded message, then clear the messages.
 

Gee Art, seems like a lot of work just to delete a message from the user's message que !  Plus messages have to be removed from the user's que!  I like that specially coded "deallocate" message though, got an example handy?   I would really like to deallocate the user's message que from any display signed on by the user, so deleting messages become possible instead of the dreaded CPF2417.

--
Thank You.

Regards

Dave Mahadevan.. mailto:mahadevan@fuse.net
 


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.