In RPG the numerics are converted to packed for processing comparisons,
etc.
From: "Schutte, Michael D" <Michael_Schutte@xxxxxxxxxxxx>
To: RPG programming on the IBM i / System i <rpg400-l@xxxxxxxxxxxx>,
Date: 12/05/2011 07:19 AM
Subject: RE: KLIST question
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
The program is converting the numbers for you. I believe it's taking the
packed fields and converting them to signed (could be the other way
around, do not remember which way).
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of jmmckee flinthills.com
Sent: Sunday, December 04, 2011 12:43 AM
To: rpg400-l@xxxxxxxxxxxx
Subject: KLIST question
Two externally described files. Both are keyed with two fields. One file
has both fields as packed numeric. The other has signed numeric and
packed numeric.
I thought the compiler would complain about the mismatch. I know it does
if alphanumeric is used for numeric. But, the compiler did not complain.
This applied to RPG III and RPG IV. At least not on the system I use.
First file is read and the two data fields are in the klist to read the
second file.
My questions:
1) What happens when a setll/reade is performed with this mismatched field
issue? No error is generated. I am wondering if some other record is
returned, or if the mismatched fields are corrected internally, somehow.
2) Since the files are externally defined, shouldn't the compiler be able
to diagnose the mismatch?
Thanks
John McKee
--
This is the RPG programming on the IBM i / System i (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.
________________________________
Notice from Bob Evans Farms, Inc: This e-mail message, including any
attachments, may contain confidential information that is intended only
for the person or entity to which it is addressed. Any unauthorized
review, use, disclosure or distribution is strictly prohibited. If you are
not the intended recipient, please contact the sender by reply e-mail and
destroy all copies of the original message and any attachments.
midrange.com
