Information Systems:Mail Server Framework (MSF) - Revision history

Norwinu at 22:33, 22 June 2016

2016-06-22T22:33:31Z

New page

This is used to receive email orders into the i, and for the i to send email messages to users. (For example, unexpected qsysopr messages, over night processing completion messages are sent to I.T., gross margin warnings are sent to the buyers.) It is independent of Domino.

You can see the server(s) running in subsystem QSYSWRK, named QMSF. WRKACTJOB SBS(QSYSWRK)

There is an autostart entry, QZMFECOX, that is shipped as part of the QSYSWRK subsystem. Whenever the QSYSWRK subsystem is started, one QMSF job is started by the autostart job entry. We have changed this to start three; so that a single problem won't completely end MSF processing.

If you want to change the number of jobs that are started in the QSYSWRK subsystem, change the STRMSF command that is in the request data of the QSYS/QZMFEJBD job description. Use the Change Job Description (CHGJOBD) command to make the change.

If you do not want any MSF jobs started when the QSYSWRK subsystem starts, remove the autostart job entry, QZMFECOX, from the QSYSWRK subsystem description. Use the Remove Autostart Job Entry (RMVAJE) command.

As problems occur with sending particular messages, servers will start ending abnormally. If there is a problem with one message, every time the start MSF command runs, one server will bomb. If there are problems with two messages, two servers will bomb, etc. Once there are three problem messages, all three servers will end and the i will stop sending messages to email and we will stop receiving email orders. One way around this is to start more servers than there are bad messages. Another way is to do a reset.

STRMSF MSGOPT(*RESET)

Be aware that, if this works, it will send the (old) messages that have been causing the problem.

I haven’t tried it, but another option if the reset doesn’t work, would be to *CLEAR all existing mail server framework messages.

MSF job 099591/QMSF/QMSF ended. Reason code 05.

Additional Message Information

Message ID . . . . . . : CPFAF95 Severity . . . . . . . : 60
Message type . . . . . : Information
Date sent . . . . . . : 08/21/11 Time sent . . . . . . : 07:19:26

Message . . . . : MSF job 099591/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 QZMFSNPA in library QSYS for exit point
QIBM_QZMFMSF_ADR_RSL failed in the MSF job.
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 1007B501108210222340000000023 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 in the Information Center,
http://www.ibm.com/eserver/iseries/infocenter, for information about the MSF
interfaces.

F3=Exit F6=Print F9=Display message details F12=Cancel
F21=Select assistance level

This is for V5R1; but seems to still be in effect -
https://publib.boulder.ibm.com/iseries/v5r1/ic2924/books/c4154110.pdf

wrksplf qmsf to see logs

Endmsf

ENDTCPSVR *SMTP

STRTCPSVR SERVER(*SMTP)

strmsf

[[Category: IBM i]]
[[Category: Email]]

Sheilav at 17:02, 16 December 2015

2015-12-16T17:02:48Z

Sheilav at 00:19, 16 December 2015

2015-12-16T00:19:56Z

Sheilav at 00:18, 16 December 2015

2015-12-16T00:18:30Z

Sheilav at 00:15, 16 December 2015

2015-12-16T00:15:25Z

Sheilav at 00:12, 16 December 2015

2015-12-16T00:12:57Z

Sheilav at 18:32, 12 December 2015

2015-12-12T18:32:12Z

Sheilav at 18:14, 12 December 2015

2015-12-12T18:14:42Z

Sheilav at 21:50, 23 November 2015

2015-11-23T21:50:15Z

Sheilav: Created page with "This is used to receive email orders into the i, and for the i to send email messages to users. (For example, unexpected qsysopr messages, over night processing completion mes..."

2015-11-23T21:50:01Z

Created page with "This is used to receive email orders into the i, and for the i to send email messages to users. (For example, unexpected qsysopr messages, over night processing completion mes..."

New page

This is used to receive email orders into the i, and for the i to send email messages to users. (For example, unexpected qsysopr messages, over night processing completion messages are sent to I.T., gross margin warnings are sent to the buyers.)

The IPL starts three iterations of the MSF server (in subsystem QSYSWRK, jobs named QMSF).

'''This is not longer true - only one is started now.'''

As problems occur with sending particular messages, servers will start ending abnormally. If there is a problem with one message, every time the start MSF command runs, one server will bomb. If there are problems with two messages, two servers will bomb, etc. Once there are three problem messages, all three servers will end and the i will stop sending messages to email (I’m not sure, but we may also stop receiving email orders). One way around this is to start more servers than there are bad messages. Another way is to do a reset.

STRMSF MSGOPT(*RESET)

Be aware that, if this works, it will send the (old) messages that have been causing the problem.

I haven’t tried it, but another option if the reset doesn’t work, would be to *CLEAR all existing mail server framework messages.

MSF job 099591/QMSF/QMSF ended. Reason code 05.

Additional Message Information

Message ID . . . . . . : CPFAF95 Severity . . . . . . . : 60
Message type . . . . . : Information
Date sent . . . . . . : 08/21/11 Time sent . . . . . . : 07:19:26

Message . . . . : MSF job 099591/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 QZMFSNPA in library QSYS for exit point
QIBM_QZMFMSF_ADR_RSL failed in the MSF job.
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 1007B501108210222340000000023 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 in the Information Center,
http://www.ibm.com/eserver/iseries/infocenter, for information about the MSF
interfaces.

F3=Exit F6=Print F9=Display message details F12=Cancel
F21=Select assistance level

Dspsplf qmsf to see logs

Endmsf

ENDTCPSVR *SMTP

STRTCPSVR SERVER(*SMTP)

strmsf

← Older revision		Revision as of 17:02, 16 December 2015
Line 1:		Line 1:
−	This is used to receive email orders into the i, and for the i to send email messages to users. (For example, unexpected qsysopr messages, over night processing completion messages are sent to I.T., gross margin warnings are sent to the buyers.)	+	This is used to receive email orders into the i, and for the i to send email messages to users. (For example, unexpected qsysopr messages, over night processing completion messages are sent to I.T., gross margin warnings are sent to the buyers.) It is independent of Domino.

	You can see the server(s) running in subsystem QSYSWRK, named QMSF. WRKACTJOB SBS(QSYSWRK)		You can see the server(s) running in subsystem QSYSWRK, named QMSF. WRKACTJOB SBS(QSYSWRK)

@@ Line 70: / Line 70: @@
 This is for V5R1; but seems to still be in effect -
- [https://publib.boulder.ibm.com/iseries/v5r1/ic2924/books/c4154110.pdf]
+ https://publib.boulder.ibm.com/iseries/v5r1/ic2924/books/c4154110.pdf
  wrksplf qmsf         to see logs

@@ Line 67: / Line 67: @@
  F3=Exit   F6=Print   F9=Display message details   F12=Cancel
  F21=Select assistance level
  wrksplf qmsf         to see logs

@@ Line 1: / Line 1: @@
 This is used to receive email orders into the i, and for the i to send email messages to users. (For example, unexpected qsysopr messages, over night processing completion messages are sent to I.T., gross margin warnings are sent to the buyers.)
-Startup starts three iterations of the MSF server (in subsystem QSYSWRK, jobs named QMSF).
+You can see the server(s) running in subsystem QSYSWRK, named QMSF.   WRKACTJOB SBS(QSYSWRK)
-There is an autostart entry, QZMFECOX, that is shipped as part of the QSYSWRK subsystem. Whenever the QSYSWRK subsystem is started, one QMSF job is started by the autostart job entry.
+There is an autostart entry, QZMFECOX, that is shipped as part of the QSYSWRK subsystem. Whenever the QSYSWRK subsystem is started, one QMSF job is started by the autostart job entry.  We have changed this to start three; so that a single problem won't completely end MSF processing.
 If you want to change the number of jobs that are started in the QSYSWRK subsystem, change the STRMSF command that is in the request data of the QSYS/QZMFEJBD job description. Use the Change Job Description (CHGJOBD) command to make the change.

@@ Line 5: / Line 5: @@
 '''This is no longer true - only one is started now.'''
-As problems occur with sending particular messages, servers will start ending abnormally.  If there is a problem with one message, every time the start MSF command runs, one server will bomb.  If there are problems with two messages, two servers will bomb, etc.  Once there are three problem messages, all three servers will end and the i will stop sending messages to email (I’m not sure, but we may also stop receiving email orders).  One way around this is to start more servers than there are bad messages.  Another way is to do a reset.
+As problems occur with sending particular messages, servers will start ending abnormally.  If there is a problem with one message, every time the start MSF command runs, one server will bomb.  If there are problems with two messages, two servers will bomb, etc.  Once there are three problem messages, all three servers will end and the i will stop sending messages to email and we will stop receiving email orders.  One way around this is to start more servers than there are bad messages.  Another way is to do a reset.
  STRMSF MSGOPT(*RESET)

@@ Line 3: / Line 3: @@
 The IPL starts three iterations of the MSF server (in subsystem QSYSWRK, jobs named QMSF).
-'''This is not longer true - only one is started now.'''
+'''This is no longer true - only one is started now.'''
 As problems occur with sending particular messages, servers will start ending abnormally.  If there is a problem with one message, every time the start MSF command runs, one server will bomb.  If there are problems with two messages, two servers will bomb, etc.  Once there are three problem messages, all three servers will end and the i will stop sending messages to email (I’m not sure, but we may also stop receiving email orders).  One way around this is to start more servers than there are bad messages.  Another way is to do a reset.