• Subject: Re: Qsysopr break messages
  • From: Rob Berendt <rob@xxxxxxxxx>
  • Date: Fri, 8 Oct 1999 11:43:51 -0500

chgmsgq qsysopr *hold
or
chgmsgq someothermsgq *pickyouroption





klauritzen@natlloyds.com on 10/08/99 11:05:28 AM
Please respond to MIDRANGE-L@midrange.com@Internet
To:     midrange-l@midrange.com@Internet
cc:      
Fax to: 
Subject:        Qsysopr break messages

We are trying to write system backup into a cl with our nightly daily
processing.

In order to do a system backup we execute command chgmsgq qsysopr *break to
get the operator messages in case of a problem. But we do not want to
signoff whne done with sys backup, we want to continue into night processing
and other functions. We also want our operator to sign back on at another
terminal as qsysopr for print. How do we deallocate the qysopr messages
without signing off? We cannot find a command that will work.

Karl Lauritzen Jr.
Second Vice-President
Application Development
254-756-5531 Ext 129
503-218-6568 E-Fax
www.natlloyds.com
klauritzen@natlloyds.com


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


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

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 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].