**************************************************************** 
   Actions for OA25602:                                           
                                                                  
     Before the installation of this APAR, if you implemented     
   exit specified in parmlib member MPFLSTxx and with message     
   processing installation exit IEAVMXIT.  With this APAR,        
   Message Flood Automation is integrated in z/OS, eliminating    
   the use for the exit routines.  Message Flood Automation must  
   be removed from these exit routines:                           
                                                                  
     Steps to take:                                               
                                                                  
       - Update your MPFLSTxx parmlib member to remove all        
         .CMD USEREXIT(CNZZCMXT) statements.                      
                                                                  
       - If you have a CONTROL M (K M) command in your CONSOLxx   
         or yout COMMNDxx, you must remove it.                    
                                                                  
       - If you use exit IEAVMXIT only for Message Flood          
         Automation, update your CONSOLxx parmlib member to       
         change the INIT statement option of UEXIT(Y) to          
         UEXIT(N). Note: Do not do this if you want to            
                         continue to use IEAVMXIT for other       
                         purposes.                                
                                                                  

Ken Klein
Sr. Systems Programmer
Kentucky Farm Bureau Insurance - Louisville
[email protected]
502-495-5000 x7011

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On
Behalf Of Skip Robinson
Sent: Wednesday, July 01, 2009 1:28 PM
To: [email protected]
Subject: Re: Message Flood Automation in z/os 1.9

I don't have the HOLD data in front of me, but as I recall 'exit
removal'
referred only to message suppression logic, not to the exit per se. For
example, we use the exit to set message color by system, not for
suppression. The exit is still in place and working fine. I think the
HOLD record is poorly worded and misleading, but the gist is there if
you ponder it long enough.

.
.
JO.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
626-302-7535 Office
323-715-0595 Mobile
[email protected]


 

             "Klein, Kenneth"

             <kenneth.kl...@ky

             FB.COM>
To 
             Sent by: IBM              [email protected]

             Mainframe
cc 
             Discussion List

             <[email protected]
Subject 
             .edu>                     Message Flood Automation in z/os

                                       1.9

 

             07/01/2009 09:44

             AM

 

 

             Please respond to

               IBM Mainframe

              Discussion List

             <[email protected]

                   .edu>

 

 





The hold(action) states the userexit is to be removed from the mpflst,
and in consolxx the uexit be set to (N).
So how does the integrated mfa know which messages to suppress?
Any other actions required beyond whats in the hold data?


Ken Klein
Sr. Systems Programmer
Kentucky Farm Bureau Insurance - Louisville

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send
email to [email protected] with the message: GET IBM-MAIN INFO Search
the archives at http://bama.ua.edu/archives/ibm-main.html

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to