RE: SNDMSG Not Displaying

[<franz400@xxxxxxxxxxxx>]

In the user profile who is sysopr 
check the msg severity
(sample)
Message queue  . . . . . . . . . . . . . . :   QSYSOPR 
  Library  . . . . . . . . . . . . . . . . :     QSYS  
Message queue delivery . . . . . . . . . . :   *BREAK  
Message queue severity . . . . . . . . . . :   40      

A normal SNDMSG is severity 00
Lower the msgq severity to 00 or try SNDBRKMSG
Jim 

---- "Willie J. Moore" <WJMoore@xxxxxxxxxxxx> wrote: 
> Thats the problem. It is not showing up at all. I send a message to the console, which is in 'break mode'. It never displayed. I could only find it if I did a 'DSPLOG'.
> william..
>
> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx
> [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of rob@xxxxxxxxx
> Sent: Friday, February 15, 2008 8:12 AM
> To: Midrange Systems Technical Discussion
> Subject: RE: SNDMSG Not Displaying
>
>
> SNDMSG MSG(ARGH) TOUSR(QSYSOPR)
> DSPMSG QSYSOPR
> Find message.  Place cursor on it.  Press F1.  Record value in:
> Severity . . . . . . . :
>
> Rob Berendt
> -- 
> Group Dekko Services, LLC
> Dept 01.073
> Dock 108
> 6928N 400E
> Kendallville, IN 46755
> http://www.dekko.com
>
>
>
>
>
> "Willie J. Moore" <WJMoore@xxxxxxxxxxxx> 
> Sent by: midrange-l-bounces@xxxxxxxxxxxx
> 02/15/2008 11:09 AM
> Please respond to
> Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
>
>
> To
> "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
> cc
>
> Subject
> RE: SNDMSG Not Displaying
>
>
>
>
>
>
> Rob,
> What is the message severity for 'SNDMSG'?
> william...
>
> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx
> [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of rob@xxxxxxxxx
> Sent: Friday, February 15, 2008 7:23 AM
> To: Midrange Systems Technical Discussion
> Subject: Re: SNDMSG Not Displaying
>
>
> 1 - WRKOBJ QSYSOPR *MSGQ.  Make sure you don't have two, like a recent 
> poster.
> 2 - WRKOBJLCK QSYSOPR *MSGQ.  It should be allocated to some session. 
> 3 - DSPUSRPRF ...   Check
> Message queue  . . . . . . . . . . . . . . :   QSYSOPR
>   Library  . . . . . . . . . . . . . . . . :     QSYS
> Message queue delivery . . . . . . . . . . :   *BREAK
>
> If 3 doesn't match it's often the result of Billy Bob saying something 
> like "Heckfire, this is just an AS/400.  We don't need up upgrade the old 
> box to V5R4 and do a complete unload/reload to the new box.  We'll just 
> restore a few libraries and whatnot and, shoot, we'll be done."  (sound of 
>
> tobacco being spit in the background)
>
> Rob Berendt
> -- 
> Group Dekko Services, LLC
> Dept 01.073
> Dock 108
> 6928N 400E
> Kendallville, IN 46755
> http://www.dekko.com
>
>
>
>
>
> "Willie J. Moore" <WJMoore@xxxxxxxxxxxx> 
> Sent by: midrange-l-bounces@xxxxxxxxxxxx
> 02/15/2008 10:04 AM
> Please respond to
> Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
>
>
> To
> <midrange-l@xxxxxxxxxxxx>
> cc
>
> Subject
> SNDMSG Not Displaying
>
>
>
>
>
>
> The following statement was working before we went to V5R4. When we set 
> the 'QSYSOPR' to BREAK mode each morning, if the file was not cleared then 
>
> this message would appear. This is in our nightly cleanup CL procedure. 
> Now it does not. Does anyone have any ideals what might have happened? Now 
>
> we have to look at the file each day to check it. Before when the operator 
>
> signed on they would get the message if file not cleared.
> Thanks,
> William Moore
>  
>  SNDMSG     MSG('**********') TOUSR(*SYSOPR) 
>  SNDMSG     MSG('BYSDLY is active CLRPFM did not run.') TOUSR(*SYSOPR) 
>  
>  SNDMSG     MSG('**********') TOUSR(*SYSOPR) 
>
> -- 
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
> list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>
> -- 
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
> list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
> -- 
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
> list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>
> -- 
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
> -- 
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.