|
If you are sure there are no messages that you need to answer, press F13. This will remove all messages. The default response will be sent to any unanswered messages. Albert York -----Original Message----- From: Burns, Bryan [SMTP:burnsbm@Echoincorporated.com] Sent: Wednesday, May 15, 2002 9:49 AM To: 'midrange-l@midrange.com' Subject: RE: Answered QSYSOPR messages show as unanswered I can tell from DSPLOG they have been answered. The only way to get rid of them from QSYSOPR msgq is to "answer" them. They will stay there for DAYS if I do not give some type of reply and then an F16 to finally get rid of them. I have had this occur for printer messages too. This does not happen a lot, but it is really annoying. We are on an 820 running V4R5 by the way. Maybe I will just call the support line, we pay good money for it. -----Original Message----- From: rob@dekko.com [mailto:rob@dekko.com] Sent: Wednesday, May 15, 2002 11:42 AM To: midrange-l@midrange.com Subject: Re: Answered QSYSOPR messages show as unanswered This is a multipart message in MIME format. -- [ Picked text/plain from multipart/alternative ] What makes you think they've been answered? 1) Are you using the "basic" mode to look at QSYSOPR messages and they are still there even though they've been answered. They have no input available. 2) You answer the message and nothing happens. Someone cancelled the job using ENDJOB and left the message in QSYSOPR? 3) ? Rob Berendt -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin "Burns, Bryan" <burnsbm@Echoincorporated.com> Sent by: midrange-l-admin@midrange.com 05/15/2002 11:26 AM Please respond to midrange-l To: "'MIDRANGE-L@midrange.com'" <MIDRANGE-L@midrange.com> cc: Fax to: Subject: Answered QSYSOPR messages show as unanswered Why do some QSYSOPR messages show as unanswered, even though they have been answered by a user? Thanks in advance for any replies. Bryan Burns System Operator ECHO, Inc. Lake Zurich, Illinois _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com 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@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com 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@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
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.