Re: Define field as an indicator in D-specs -- RPG400-L

Subject: Re: Define field as an indicator in D-specs
From: Charles Wilt <charles.wilt@xxxxxxxxx>
Date: Fri, 6 Dec 2013 16:40:52 -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>

Not so fast! :D

You're missing the built in negation for the HI indicator when used with a
op-code that sets found...for instance CHAIN

"indicator in positions 71-72 that is set on if _NO_ record in the file
matches the search argument." (emphasis mine)

So _NO_ record = NOT %found() makes perfect sense...

Charles

On Fri, Dec 6, 2013 at 3:51 PM, Monnier, Gary <Gary.Monnier@xxxxxxxxx>wrote:

Not quite so... true? :)

A little off but...

%found is translated from the HI indicator being set *Off and not
%found being translated from the HI indicator being set *On.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: Define field as an indicator in D-specs , Monnier, Gary

This mailing list archive is Copyright 1997-2025 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.