• Subject: Re: MSF Chokes under load
  • From: Rob Berendt <rob@xxxxxxxxx>
  • Date: Thu, 11 Nov 1999 17:24:25 -0500

Try the following:
CHGSYSDIRA ALWSCH(*NO)
CHGSYSDIRA ALWSCH(*YES)
This will rebuild some directory entry attributes.

To see if this is your problem, before trying this do:
WRKDIRE
F10-Search
Fill in User profile (not user id)
Press Enter and see if you get any hits, or an error message instead.

I had this happen under V4R2.  PMR 10060,500 dated 11/24/98.  And in 
my MSF job 161719/QMSF/QMSF joblog I saw the following:
CPI9A9C Message . . . . :   Search data does not exist

It started happening so often, and on multiple 400's, that I started 
adding the two CHGSYSDIRA commands to my downtime instructions, completed 
every 8 weeks.





lbolhui@ibm.net on 11/11/99 05:05:59 PM
Please respond to MIDRANGE-L@midrange.com@Internet
To:     MIDRANGE-L@midrange.com@Internet
cc:      
Fax to: 
Subject:        MSF Chokes under load

Have a customer on V4R4 that is sending approx 150 e-mail messages from an
application using  SNDDST *MSG.  Some time before the messages are all 
processed,
MSF chokes and all MSF jobs end.  THe message issued is CPFAF95 - MSF job ended
reason 5
 05 - Exit point program QZMFSNPA in library QSYS for exit point                
   QIBM_QZMFMSF_ADR_RSL indicated the MSF job is to be ended.                   
     Processing for MSF message ID 103WABM9911051709110000000198 was ended and  
   will be processed again the next time MSF jobs are started using the Start   
   Mail Server Framework (STRMSF) command.                                      
 Recovery  . . . :   Based on the reason code, do one of the following:   
 04,05 - Use the DSPJOBLOG command to determine the cause of the exit point     
   program failing. There may be messages listed in the job log to determine    
   what caused the exit point program to fail. Correct any errors and then use  
   the End Mail Server Framework (ENDMSF) command to end all MSF jobs. Then use 
   the Start Mail Server Framework (STRMSF) command to start the MSF jobs       
   again.                                                                       
                                                                                
Restarting the jobs does nothing (except crash again) until we do STRMSF 
*CLEAR. 
Having 99 MSF jobs running allows the process to sometimes complete without
failure.  This is in a test environment.  It is expected that in production 
about
10,000 messages will be sent in under 20 minutes each night.   We have loaded 
the
PTF that talks about MSF crashing under heavy load but this has had no affect. 
We are opening a problem with SupportLine but are hoping someone out there has
seen this. 

Thanks - Larry


-- 
Larry Bolhuis         | What do You want to Reload today?
Arbor Solutions, Inc  | Don't throw your PC out the window,
(616) 451-2500        |  throw WINDOWS out of your PC.
(616) 451-2571 -fax   | Two rules to success in life:
lbolhui@ibm.net       | 1. Never tell people everything you know.
+---
| 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].