Re: figurative constants *YES & *NO? -- RPG400-L

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: Re: figurative constants *YES & *NO?
From: dlclark@xxxxxxxxxxxxxxxx
Date: Mon, 10 Jul 2017 17:29:04 -0400
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/options/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=unsubscribe>

"RPG400-L" <rpg400-l-bounces@xxxxxxxxxxxx> wrote on 07/10/2017 04:33:59
PM:

I inadvertently typed *YES where I intended to type *ON when assigning a
value to an indicator field, and I was surprised when the syntax checker
allowed it. Nothing on this was found in the updated v7r1 RPG

reference,

so I tried to compile it. But it failed on RNF7416: "The types of the
right and left hand side do not match in the EVAL operation."

*YES and *NO work in the context of parameters for keywords --
such as in the CTL-OPT statement. But they have no intrinsic value
otherwise and, thus, cannot be used in calculation specifications.

Sincerely,

Dave Clark

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