× 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.


  1.  Home
  2. MIDRANGE-L
  3. February 2012

Re: MSF crashing. What should I look for?

Luis Rodriguez wrote:
If you can't find any logs, try restarting MSF with STRMSF(*CLEAR).

They've already been doing that when it abends. It still seems to be abending with some regularity.

I did find something interesting near the end of one of the joblogs, and I found four separate spool files on that particular abended QMSF job.

QPSRVDMP QEZDEBUG FFDC RDY 209 QPJOBLOG QEZJOBLOG FFDC RDY 5 QPDSPJOB QEZDEBUG FFDC RDY 15 QPJOBLOG QEZJOBLOG QMSF RDY 8

CPF3353 Escape 40 02/09/12 15:00:59.282948 QSPCRSPQ QSYS
Message . . . . : Output queue QSCAPAROQ in QSC0651550 already exists. Recovery . . . : Use the WRKOUTQ command with the OUTQ(*ALL) parameter to display all the output queues. Use the OUTQ parameter to change the output queue name or the library name. Then try the command again. TCP5127 Diagnostic 40 02/09/12 15:00:59.476565 QTMMCUTL QTCP
From module . . . . . . . . : QTMMUTLM From procedure . . . . . . : qtmf_IssueMessage__FPcT1ie Statement . . . . . . . . . : 170 To module . . . . . . . . . : QTMMNDEL To procedure . . . . . . . : Lookfor_Rec_Lists__FlP27Qzmf_Msg_Desc_Attrbt_E ntityPc
Statement . . . . . . . . . : 35 Message . . . . : Framework change message failed. Cause . . . . . : The call to the framework's change message API failed. Recovery . . . : Check for level mismatch between QMSF and QTCP POP program. CPFAF82 Escape 40 02/09/12 15:00:59.478229 QZMFACHG QSYS
Message . . . . : Error occurred during running of MSF API. Cause . . . . . : An error occurred during running of the mail server framework (MSF) QzmfChgMailMsg API. The reason code is 07. Reason codes and their meanings follow: 01 -- MSF pool index not found 02 -- MSF queue not found 03 -- MSF internal object not found 04 -- MSF internal object lock not available 05 -- Error while addressing parameter list 06 -- MSF space damaged 07 -- MSF API cannot be called from job 99 -- Unknown error Recovery . . . : Based on the reason code, do one of the following: 01-03 -- Use the Start Mail Server Framework (STRMSF) command to start the MSF jobs again. 04 -- 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. 05 -- Check the parameter list and make sure that all parameters are correctly specified. Then try the request again. 06 -- Retry the API. 07 -- See the AnyMail/400 Mail Server Framework Support book, SC41-5411, for information about calling this API. There may be messages listed in the job log to determine the cause of the error. Correct the error and retry the API. If the problem continues, report the problem using the Analyze Problem (ANZPRB) command. CPFAF90 Escape 40 02/09/12 15:00:59.478302 QZDSNPAM QSYS
Message . . . . : End mail server framework (MSF) job.
Cause . . . . . : An error occurred causing the exit point program for exit point QIBM_QZMFMSF_ATT_MGT for MSF to indicate the job should be ended. Processing for the current MSF message is delayed until MSF is started again. Use the Start Mail Server Framework (STRMSF) command.
Recovery . . . : Determine why the user exit program signalled this message back to the mail server framework (MSF). There may be messages listed in the job log that caused the exit point program to signal this message to the MSF. Correct any errors and use the End Mail Server Framework (ENDMSF) command to end all the MSF jobs. Then use the Start Mail Server Framework (STRMSF) command to start the MSF jobs again.
Technical description . . . . . . . . : This message is signalled by MSF exit point programs call by the Mail Server Framework (MSF) job. This message indicates that the exit point program detected a condition that indicates the job should be ended. CPFAF95 Escape 60 02/09/12 15:00:59.478724 QZMFBIGE QSYS
Message . . . . : MSF job 527296/QMSF/QMSF ended. Reason code 05. Cause . . . . . : The mail server framework (MSF) job ended. Reason code 05.
Reason codes and their meanings follow: 00 - The MSF job ended normally. A job log may not exist. 01 - An internal object was not found that is needed by the MSF job. 02 - An internal object could not be allocated by the MSF job. 03 - An internal system error was detected by the MSF job. 04 - Exit point program QZDSNPAM in library QSYS for exit point QIBM_QZMFMSF_ATT_MGT failed in the MSF job. 05 - Exit point program QZDSNPAM in library QSYS for
exit point QIBM_QZMFMSF_ATT_MGT indicated the MSF job is to be ended. Processing for MSF message ID 10A98991202091500530000000001 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: 00 - Use the Start Mail Server Framework (STRMSF) command to start the MSF jobs again. 01 - 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. This will create any internal objects needed by the MSF jobs. 02 - 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. 03 - Use the Display Job Log (DSPJOBLOG) command to determine the cause of the job failing. There may be messages listed in the job log to determine what caused the job 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. 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. If the problem continues, report the problem using the Analyze Problem (ANZPRB) command. Refer to the APIs topic collection in the Programming category in the i5/OS Information Center, http://www.ibm.com/systems/i/infocenter/, for information about the MSF interfaces. CPF2494 Diagnostic 99 02/09/12 15:00:59.478745 QMHUNMSG QSYS
Message . . . . : Exception message was sent to a location preceding the first entry in the call stack. Cause . . . . . : If the message was sent, the combination of call stack entry name and call stack counter produced a location that precedes the first entry in the call stack. This condition can also result if the message was resignaled from the first entry in the call stack. CPC1219 Completion 50 02/09/12 15:00:59.531068 QWTPITP2 QSYS
Message . . . . : This job ended abnormally. Cause . . . . . : An error occurred that caused this job to end abnormally.
Recovery . . . : See the previously listed messages in the job log for

But I'm not quite sure what this adds up to: the messages refer to an API and an OS exit hook, neither of which I've ever heard of.

--
JHHL

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Replies:
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.