MCH1211: Attempt made to divide by zero

What it means

Division by zero has no answer, so the machine refuses to do it. When a fixed-point divide instruction gets a divisor of zero, the machine sends MCH1211 as an escape message to the program that ran it. The message text says an attempt was made to divide by zero for a fixed-point operation.

Any division can cause it. That includes the / operator in an RPG expression, the DIV operation code, the %DIV and %REM built-ins, a COBOL DIVIDE or COMPUTE, and arithmetic in CL. An ILE RPG program reports it as status 00102 and, with no handler, shows inquiry RNQ0102. Other programs end in their own inquiry or in function check CPF9999.

The divisor is almost always a field that is zero because of the data, not a literal zero in the code. A percentage, an average or a unit price works until the day a record arrives with zero in the field below the line.

Common causes

• A record has zero in a field used as a divisor, such as a quantity, a count or a total, for example an order line with no quantity or a month with no sales.
• A field used as a divisor was never set, so it still holds zero.
• An average was calculated over an empty group, such as total divided by count when no records matched.
• A user keyed zero, or left a numeric field blank, on a screen that feeds a calculation.
• Less often, an IBM program or API is the one named. That can happen when it was passed a length or count of zero. Check the parameters first, then the PTF level.

How to find the problem

1. Run DSPJOBLOG, put the cursor on MCH1211 and press F1, then F9. The message details name the program, module, procedure and statement that did the division.
2. Look at the divisor in that statement and work back to where it gets its value.
3. Find the record or screen input being processed when the job failed. In debug (STRDBG), stop on the statement and display the divisor to confirm it is zero.
4. If the program named is an IBM program, look at the program just above it in the call stack, since that is usually the caller that passed the bad value.

How to fix it

• Test the divisor before every division whose divisor comes from data, and decide what the result should be when it is zero. Often that is zero, or a message.
• In RPG, wrap the calculation in MONITOR and ON-ERROR 00102, or check %STATUS in a *PSSR routine, so one bad record doesn't stop a batch run.
• In COBOL, use ON SIZE ERROR on the DIVIDE or COMPUTE statement.
• In CL, check the variable before CHGVAR does the division, or monitor for MCH1211.
• Fix the data or the screen validation that let a zero through where the business needs a value.

What it looks like

Attempt made to divide by zero for fixed point operation.

DSPMSGD MSGID(MCH1211) MSGF(QSYS/QCPFMSG)

Technical reviewer: Albert Joseph, WND Software.

Last reviewed 2026-10-18 by the WND Software team. Written in our own words. For the full reference, check IBM’s documentation for your IBM i release.