RE: Field size question

Defining the field in a data structure gives you what you want - as you noticed.

-----Original Message-----
From: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxxxxxxxx] On Behalf Of DEnglander--- via RPG400-L
Sent: Thursday, April 22, 2021 3:21 PM
To: rpg400-l@xxxxxxxxxxxxxxxxxx
Cc: DEnglander@xxxxxxxxxxxxxxx
Subject: Field size question

I have a DDS-defined file that contains a numeric field defined as
ZONED(6) to hold MSTITEM#.

I have an ILERPG program that has a DCL-S line to define field NEWITEM# as being like MSTITEM#. i.e.


dcl-s newitem# like(mstitem#);


Even though the MSTITEM# field is defined as ZONED, why does the ILERPG
compiler define NEWITEM# as being PACKED(6)?

Is there any way to stop this, such as a CTL-OPT line keyword or Compile
command parameter entry? Normally, this doesn't matter to me, but when
procedure parameters are introduced, the compile complains because
ZONED(6) is not the same as PACKED(6). I am not using CONST because the
procedure is returning two parameters. I do notice that if I define an
External Data Structure as a Template, and make NEWITEM# like(the E DS
name), the compiler does preserve the ZONED.

Any ideas? We are on V7R3 with fairly current PTFs.

Thank you,

Doug



"CONFIDENTIALITY NOTICE: This e-mail transmission (and/or the attachments accompanying it) contain confidential information belonging to the sender. The information is intended only for the use of the intended recipient. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or the taking of any action in reliance on the contents of the information is strictly prohibited. Any unauthorized interception of this transmission is illegal under the law. If you have received this transmission in error, please promptly notify the sender by reply e-mail, and then destroy all copies of the transmission."