Re: Display Program Messages suppression on multiple Sign on

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.






pcdow@yahoo.com on 12/08/99 04:29:00 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

No, I tried it on a V4R3 system. After changing my user profile to
DLVRY(*HOLD), I signed off, signed on as session A. Then I signed on to
session B. No message, as advertised.

Then I signed both sessions off and signed on to session A and did

 CHGMSGQ MSGQ(userid) DLVRY(*NOTIFY)

Then when I signed on to session B, I get the message about the queue
already being allocated.



----- Original Message -----
From: Rob Berendt <rob@dekko.com>
To: <MIDRANGE-L@midrange.com>
Sent: Wednesday, December 08, 1999 6:09 AM
Subject: Re: Display Program Messages suppression on multiple Sign on


> You probably ignored the first part of Al's message.
> > Change the user profile message queue parameter to *HOLD mode
>
>
>
>
> pcdow@yahoo.com on 12/08/99 02:23:17 AM
> 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
>
> The first part works, but if the initial program on any session changes
the
> delivery to *BREAK or whatever, it has allocated the message queue and
> subsequent sessions get the
>
> >"Job 224213/USER/DEVICE started on MM/DD/YY at HH:MM:SS in subsystem
> >QINTER Message queue USER is allocated to another job."
>
> message.
>
>
> From: Al Barsa, Jr. <barsa2@ibm.net>
> > Change the user profile message queue parameter to *HOLD mode, and then
> > change the initial program to put the message queue into *BREAK (or
> > whatever you like) mode, followed by MONMSG CPF2451.
>

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