Re: Display Program Messages suppression on multiple Sign on

I created a user profile with:
CRTUSRPRF USRPRF(ROBT) DLVRY(*HOLD)
I signed on to one session with it.  Then I signed on to a second session with 
it.  
I didn't get one message about message queue being in use.  Then I signed off 
the 
second session.  On the first session I did a CHGMSGQ ROBT DLVRY(*NOTIFY).  And 
by 
God you're right!  I do get the message "Message queue ROBT is allocated to 
another 
job."  Why would it give a rats ...?  The second session should maintain the 
status 
from the usrprf.  Do you have a support contract with IBM?  Can they give you a 
decent explanation?  





lbolhui@ibm.net on 12/08/99 10:25:54 PM
Please respond to MIDRANGE-L@midrange.com@Internet
To:     MIDRANGE-L@midrange.com@Internet
cc:      
Fax to: 
Subject:        Re: Display Program Messages suppression on multiple Sign on

This behaviour is exactly as I remember it all the way back to V1R2M0, and still
works exactly this way on V4R4 today.  I have never been able to get the second
session to come up without the 'already allocated' message unless I leave the
message queue in *HOLD mode on all sessions.

 - Larry

Rob Berendt wrote:
> 
> Let me paraphrase.
> 
> You changed the user profile to DLVRY(*HOLD).
> You are using the same user  profile on both sessions.
> You do not change the user profile back to anything that DLVRY(*HOLD).
> You sign on to one session with no problems.
> You can do a DSPMSG and delete all of the messages.
> You can do a SNDMSG to that user profile and no ding and the MSGW light does 
>not light.
> Then you do a CHGMSGQ MSGQ(userid) DLVRY(*NOTIFY)         not a CHGUSRPRF!
> Now your ding and MSGW light works.
> You sign on to the second session and get the message, before you have a 
>chance to do anything else, you get the message that the message queue is 
>allocated to another job.
> 
> If this is true, then do you have an initial program that does the CHGMSGQ 
>and doesn't have the MONMSG that Al recommended?
> Otherwise then something ain't right.

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