|
I used to use MLLZO to force a negative value to a numeric field. Back in the day as they say. MWaite@xxxxxxxxxxxx wrote: I used it once, in 1991! I was coding a subroutine which formatted a number in a variety of possible formats, depending on a supplied edit code. Edit code X is the interesting one, as negative numbers have an 'overpunch' in the low-order byte. Older readers who used to punch cards using a hand-punch will remember the extra hole in the column containing a negative number. The code looked like this: 0069.00 * 0070.00 * overpunch if negative 0071.00 * 0072.00 C C#EDN3 IFLT *ZERO 0073.00 C BITOF '2' @EO(@1) 0074.00 C END Even more obscurely, this program required the use of a Move Low to Low Zone: 0219.00 * 0220.00 * remove any negative overpunch for all codes 0221.00 * 0222.00 C MLLZO +1 @EN9 0223.00 * Did anyone ever manage to find a use for MHHZO, MHLZO or MLHZO? I suspect we'll have to go back to the days of paper tape! Regards Mike rpg400-l-bounces@xxxxxxxxxxxx wrote on 13/06/2005 19:31:48: > I took an RPG Assessment test the other day and to my surprise, there were > FOUR QUESTIONS! On the results of using BITOF and BITON. > > > > I think that I have used those opcodes maybe twice in 17 years. Now either > I'm not doing something right or the RPG Assessment test from BrainBench.com > is woefully out of date. > > > Does anyone use BITOFF and BITON on a even a semi-regular basis? > > > > Shannon O'Donnell > > > > > > > > > > > > -- > This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list > To post a message email: RPG400-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/rpg400-l > or email: RPG400-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/rpg400-l. > >
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.