RE: Preventing a divide by zero error -- RPG400-L

Subject: RE: Preventing a divide by zero error
From: "Jerry C. Adams" <midrange@xxxxxxxx>
Date: Mon, 24 Jun 2013 10:40:47 -0500
List-archive: <http://archive.midrange.com/rpg400-l>
List-help: <mailto:rpg400-l-request@midrange.com?subject=help>
List-id: "RPG programming on the IBM i \(AS/400 and iSeries\)" <rpg400-l.midrange.com>
List-post: <mailto:rpg400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=unsubscribe>

Let's assume (as an exercise only) that GROSSPCT is written to a printed
report (or even to a disk file). If this is the only place in which
GROSSPCT is calculated, and if NETPRICE = 0, then the GRPSSPCT for this item
will be reported as the same as the previous item.

In brief, one needs to take into consideration what to do (outside of the
norm) when NETPRICE = 0. I recall having a similar issue some years ago; I
set GROSSPCT = *ALL'9'. This helped set off alarm bells for our general
manager without blowing off the report.

Jerry C. Adams
IBM i Programmer/Analyst
There is only one thing worse than fighting with allies, and that is
fighting without them. -Winston Churchill

As an Amazon Associate we earn from qualifying purchases.

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.