- 论坛徽章:
- 0
|
求助，qmsf
各位大哥帮帮忙。
错误信息如下:
5722SS1 V5R2M0 020719 Job Log CSTXM001 10/05/05 09:05:25 Page 1
Job name . . . . . . . . . . : QMSF User . . . . . . : QMSF Number . . . . . . . . . . . : 824312
Job description . . . . . . : QMSF Library . . . . . : QSYS
MSGID TYPE SEV DATE TIME FROM PGM LIBRARY INST TO PGM LIBRARY INST
CPF1124 Information 00 10/05/05 09:05:25.572392 QWTPIIPP QSYS 05D4 *EXT *N
Message . . . . : Job 824312/QMSF/QMSF started on 10/05/05 at 09:05:25 in
subsystem QSYSWRK in QSYS. Job entered system on 10/05/05 at 09:05:25.
CPI1125 Information 00 10/05/05 09:05:25.572696 QWTPCRJA QSYS 0108 *EXT *N
Message . . . . : Job 824312/QMSF/QMSF submitted.
Cause . . . . . : Job 824312/QMSF/QMSF submitted to job queue QSYSNOMAX in
QSYS from job 824107/QSECOFR/DSP01. Job 824312/QMSF/QMSF was started using
the Submit Job (SBMJOB) command with the following job attributes: JOBPTY(5)
OUTPTY(5) PRTTXT() RTGDTA(ZMFMSF) SYSLIBL(QSYS QSYS2 QHLPSYS
CSQGPL QUSRSYS LIBCSUC LIBCSCM LIBCSCMF QGPL QTEMP)
CURLIB(*CRTDFT) INLLIBL(QGDDM LIBCSPRF) LOG(4 00 *NOLIST) LOGCLPGM(*NO)
INQMSGRPY(*RQD) OUTQ(/*DEV) PRTDEV(PRT01) HOLD(*NO) DATE(*SYSVAL)
SWS(00000000) MSGQ(/*NONE) CCSID(65535) SRTSEQ(*N/*HEX) LANGID(CHS)
CNTRYID(CN) JOBMSGQMX(16) JOBMSGQFL(*WRAP) ALWMLTTHD(*NO) INLASPGRP(*NONE)
SPLFACN(*KEEP).
CPI9A9C Escape 10 10/05/05 09:05:25.705928 QOKSCHD QSYS 1345 QZMFSNPA QSYS 0158
Message . . . . : Search data does not exist.
Cause . . . . . : The system distribution directory cannot be searched
because search data does not exist on the system. Recovery . . . : Inform
your system administrator to run the Change System Directory Attributes
(CHGSYSDIRA) command and specify ALWSCH(*YES) to create search data on the
system. After this is complete, try the search request again. Technical
description . . . . . . . . : CHGSYSDIRA ALWSCH(*YES) needs to be run only
once on your system and this initially creates the search data. From then
on, search data is maintained for any changes made to the system
distribution directory.
CPFAF90 Escape 40 10/05/05 09:05:25.705984 QZMFSNPA QSYS 047F QZMFBIGE QSYS 04E6
Message . . . . : End mail server framework (MSF) job.
Cause . . . . . : An error occurred causing the exit point program for exit
point QIBM_QZMFMSF_ADR_RSL 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 10/05/05 09:05:25.709832 QZMFBIGE QSYS 07FB *EXT *N
Message . . . . : MSF job 824312/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 65FF76B0509301000190000000006 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
5722SS1 V5R2M0 020719 Job Log CSTXM001 10/05/05 09:05:25 Page 2
Job name . . . . . . . . . . : QMSF User . . . . . . : QMSF Number . . . . . . . . . . . : 824312
Job description . . . . . . : QMSF Library . . . . . : QSYS
MSGID TYPE SEV DATE TIME FROM PGM LIBRARY INST TO PGM LIBRARY INST
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 OS/400 APIs topic in the Information Center,
http://www.iseries.ibm.com/infocenter, for information about the MSF
interfaces.
CPF2494 Diagnostic 99 10/05/05 09:05:25.709888 QMHUNMSG QSYS 0526 *EXT *N
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 10/05/05 09:05:25.726152 QWTPITPP QSYS 0754 *EXT *N
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
this job. Correct the errors and try the request again.
CPF1164 Completion 00 10/05/05 09:05:25.727864 QWTMCEOJ QSYS 00BD *EXT *N
Message . . . . : Job 824312/QMSF/QMSF ended on 10/05/05 at 09:05:25; 1
seconds used; end code 30 .
Cause . . . . . : Job 824312/QMSF/QMSF completed on 10/05/05 at 09:05:25
after it used 1 seconds processing unit time. The job had ending code 30.
The job ended after 1 routing steps with a secondary ending code of 0. The
job ending codes and their meanings are as follows: 0 - The job completed
normally. 10 - The job completed normally during controlled ending or
controlled subsystem ending. 20 - The job exceeded end severity (ENDSEV job
attribute). 30 - The job ended abnormally. 40 - The job ended before
becoming active. 50 - The job ended while the job was active. 60 - The
subsystem ended abnormally while the job was active. 70 - The system ended
abnormally while the job was active. 80 - The job ended (ENDJOBABN command).
90 - The job was forced to end after the time limit ended (ENDJOBABN
command). Recovery . . . : For more information, see the Work Management
topic in the Information Center, http://www.iseries.ibm.com/infocenter. |
|
免费注册
发表于 2005-09-30 12:44
发表于 2005-09-30 14:18
