Re: Named constants in DCL-S

Thanks Barbara.

The field CURR_1 in my example is defined by a file. (There is a DCL-F
earlier in the source). The RDi outline finds the definition fine, but the
resulting spooled file from the compile has the correct definition for
CURR_1 in an I-spec further down the source. Are DCL-F definitions done
after the DCL-C and/or DCL-S definitions? If so, is the only way I can
declare a zoned version of a packed file field to hard-code the field
definition?

-Paul.



On Tue, 23 Apr 2019 at 16:51, Barbara Morris <bmorris@xxxxxxxxxx> wrote:

On 2019-04-23 8:42 AM, Paul Bailey wrote:

Hi,

I might be having a bad-brain-day, but I thought the following was

possible:

dcl-s TTAAMT_x like(CURR_1) inz; // currently packed(13: 2)
dcl-c C_TTAAMT_LEN CONST(%LEN(TTAAMT_x));
dcl-c C_TTAAMT_DP CONST(%DECPOS(TTAAMT_x));
// needed for multiple data structure overlays
dcl-s TTAAMT_z zoned(C_TTAAMT_LEN: C_TTAAMT_DP) inz;

CURR_1 has to be defined before you use it for the definition of TTAAMT_z.

This compiles for me:

dcl-s CURR_1 packed(13:2);
dcl-s TTAAMT_x like(CURR_1) inz; // currently packed(13: 2)
dcl-c C_TTAAMT_LEN CONST(%LEN(TTAAMT_x));
dcl-c C_TTAAMT_DP CONST(%DECPOS(TTAAMT_x));
dcl-s TTAAMT_z zoned(C_TTAAMT_LEN: C_TTAAMT_DP) inz;
return;

--
Barbara

--
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@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com