We are hiring and constantly growing! Have a look through our vacancies to find the right role for you!

CPC1220 - Job ended abnormally because of error code MCH&1. ( OS/400 )

CPC1220 - Job ended abnormally because of error code MCH&1. ( OS/400 )

BAL_S_LOG - Application Log: Log header data   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by IBM.
SAP E-Book


Message : CPC1220
Job ended abnormally because of error code MCH&1.

Message Long Text :

Cause . . . . . : The job was ended by the system because an error was found, and the job was in a condition where the process default exception handler (QMHPDEH) could not be given control. The system will not give control to QMHPDEH when the job is in between the starting phase and the problem phase, or between the problem phase and the ending phase. Some of the more common error codes and their meanings follow:
MCH0802 - The program that the job routed to must have parameters, but it is not allowed to have any parameters passed to it.
MCH1001 - The user is not authorized to an object. Check the system values to be sure that auditing of authority failures is active. To determine which object caused the error, use the Display Audit Journal Entries (DSPAUDJRNE) command with ENTTYP(AF).
MCH1604 - A system object is damaged. The most likely object is the program to which the job is routed.
MCH3203 - A machine function check occurred. A possible cause is that the program stack for a routing step was nested too deeply. This is probably due to repeated calling of the programs. It may also be caused by deleting a program that is active in the program stack.
MCH3402 - A system object is destroyed or has header damage. This is most commonly caused by deleting a program that is active in the program stack. It may also be caused by deleting the event handlers, external exception handlers, invocation exit programs, cancel handlers, signal handlers, or the program to which the job was routed.
MCH3403 - The program to which the job was routed was saved with storage freed.
If MCH&1 is not previously described, display the message (DSPMSGD command) to see what is causing the error. There is no message for MCH&1 in the job log because the error occurred at a time when a message could not be sent.
If there is a problem invoking the program that the job routed to, using a CALL command to invoke the program may generate the MCH&1 error as a message with message data that further describes the problem.
If a problem occurs when activating a program (*PGM), the problem may be caused by a service program (*SRVPGM).

Message File : QCPFMSG
Library Message File : QSYS2924


ABAP Short Reference   ABAP Short Reference  
This documentation is copyright by IBM.

Length: 3247 Date: 20201031 Time: 172440     sap01-206 ( 2 ms )