× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



What most users do with QSYSOPR, is to put it into *BREAK mode at some
workstation. The best way to filter messages is to set a severity level
above which you want messages to break. (I typically set mine at 40.) If
you want to suppress all CPF7020 messages you have two options:

1.   Change the severity of the message in the QCPFMSG message queue.
2.   Create another message file in your own library, put your own CPF7020
message in  it (with a lower severity), and then have the initial job for
that job to an OVRMSGF to that message file.

I am without benefit of a system at the moment, so I cannot comment on the
shipped severity of that particular message.

Al - at 25,000 feet- somewhere on the way back from Atlanta (where I spoke
to Jeff Silberberg's local user group today, and we all [audience and
speaker] had a wonderful time!)

Al Barsa, Jr.
Barsa Consulting Group, LLC

400>390

914-251-1234
914-251-9406 fax

http://www.barsaconsulting.com
http://www.taatool.com





                                                                                
                                        
                    "Carley, Neil"                                              
                                        
                    <carleyn1@Midas-Kap       To:     
"'MIDRANGE-L@midrange.com'" <MIDRANGE-L@midrange.com>             
                    iti.com>                  cc:                               
                                        
                    Sent by:                  Subject:     suppress qsysopr 
message                                     
                    midrange-l-admin@mi                                         
                                        
                    drange.com                                                  
                                        
                                                                                
                                        
                                                                                
                                        
                    08/15/01 11:32 AM                                           
                                        
                    Please respond to                                           
                                        
                    midrange-l                                                  
                                        
                                                                                
                                        
                                                                                
                                        




Hello group,

I have a bit of a problem where qsysopr message q is being flooded with
CPF7020 - Journal receivers QDBJRN3851 and *N detached. This makes other
messages difficult to scan for.
I have a program I can run to filter certain messages(including cpf7020)
out
but I really want to stop this particular one altogether.
Can anyone suggest a way that I can stop this this message from coming into
qsysopr.

your help greatly appreciated

Neil
_______________________________________________
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







As an Amazon Associate we earn from qualifying purchases.

This thread ...


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

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.