Re: MCH1210 (Receiver value too small . . .) in an EVAL statement? On a string? -- RPG400-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Re: MCH1210 (Receiver value too small . . .) in an EVAL statement? On a string?
From: Ken Sims <mdrg8066@xxxxxxxxxxx>
Date: Wed, 23 Feb 2011 13:43:37 -0800
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 / System i <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>

Hi James -

On Wed, 23 Feb 2011 11:33:02 -0800, James Lampert
<jamesl@xxxxxxxxxxxxxxxxx> wrote:

Does anybody know of a case where a statement like

C EVAL AHFROM = GETEMAIL

where GETEMAIL is a procedure call with no parameters, returning an
80-character string, could throw an MCH1210? The procedure definition is
in the same module, but the exception is not being thrown in the
procedure definition.

Does the procedure definition correctly reflect the length of the data
being returned by GETEMAIL? If not, that can be a problem because
different lengths of data can be returned in different ways.

If the procedure definition correctly reflects the actual length of
data returned (not how much of it you plan to use), then I don't see
an obvious problem.

Ken
Opinions expressed are my own and do not necessarily represent the views
of my employer or anyone in their right mind.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: MCH1210 (Receiver value too small . . .) in an EVAL statement? On a string? , Stuart Rowe

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.