|
The record format name pointed to by the data structure must match the
record format name of the File used on the input operation.
RPG just doesn't allow you to substitute a "similar" data structure for
input operations like this on Externally Defined files.
It must be an exact match when trying to use a Result Data Structure.
This is probably a requirement to protect programmers who don't realize
the repercussions of using a Result data structure.
RPG does not perform type checking when a result data structure is used.
It just moves the data across.
Which means the error (data decimal or the Date, etc.) would be sent later
when the field is used.
That's also one reason I prefer to use EVAL-CORR to copy the data between
in input data structure and the procedure parameter.
Because the EVAL-CORR marries up the fields and performs type checking. It
also deals with Null capable fields, if you have those.
--
Chris Hiebert
Senior Programmer/Analyst
Disclaimer: Any views or opinions presented are solely those of the author
and do not necessarily represent those of the company.
From: RPG400-L <rpg400-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Marco
Facchinetti
Sent: Monday, August 22, 2022 8:59 AM
To: RPG programming on IBM i <rpg400-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: Likerec usage
However, I see no obvious reason to prevent the use of a Ds likerec based
on an identical record format but only with a different name.
--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
As an Amazon Associate we earn from qualifying purchases.
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.