Re: object lock on user message queue

["Henrik Krebs" <hkrebs@xxxxxxxxx>]

I've never heard about CA/400 beeing able to set 'MW' on different sessions. 

When you have two or more different sessions: No help
Another groupjob on same session: The 'CHGMSGQ' follows to the new groupjob
A 'Secondary Interactive job': You can allocate the msgq for the new job

Another possibility is to use the CHGMSGQ PGM() to warn the other active 
Workstation message queues for that user. Notice that if
you use a dynamically assigned devd (like QPADEV0001) there is a risk that 
somebody will find the message at a later signon. So
maybe the action of PGM() should be only: There is a new message for xxxxx.



Regards

Henrik Krebs

------------------------------------------------------------
Henrik Krebs
IT Consultant (IBM AS/400)
Phone +45 55 44 26 50
Mobile +45 40 88 83 23
Email: hkrebs@hkrebs.dk
Web: http://www.hkrebs.dk/
Snailmail: Kokhaven 8, DK-4736  Karrebaeksminde
------------------------------------------------------------

----------
Fra: Dan Bale <dbale@genfast.com>
Til: MIDRANGE-L@midrange.com
Emne: object lock on user message queue
Dato: 16. september 1999 19:34



I'm using Client Access V3R1M3.  I usually run three display sessions.  When
messages are sent to my user message queue, the message indicator at the bottom
of the screen only appears for the display station that has the lock on the
message queue, typcially the first session signed on to.  So, if I'm working on
the third session and a message gets sent to me, I'll never see it until I
happen to go back to the first session.

I thought I remembered (from a few years ago at a different location) seeing a
flashing message indicator in the Windows task bar when a message was sent to my
user message queue.  This might not have been Client Access; maybe Netsoft.
Anybody know what I'm talking about?  Or how to set it up for Client Access?

The other possibility is to have _each_ display session flash the message
indicator at the bottom of the screen.  I think I saw a solution for this
several years ago.  It involved changing the lock on the message queue object.
Anybody know?

Thanks,
Dan Bale

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---