Re: unwanted integer to packed conversion what am I doing wrong?

To complete this story: Since I had the prefix and alias keywords specified
I had to specify them also on the EXTNAME specification to mak it map
correctly:

d e ds extname('TESTMAS')
d prefix(tst_) alias

Regards,
-Arco

2016-11-22 23:34 GMT+01:00 Barbara Morris <bmorris@xxxxxxxxxx>:

On 11/22/2016 4:14 PM, Arco Simonse wrote:

I guess I must be missing something obvious here, but I'm struggling with
unwanted integer to packed conversion in a datastructure.
...
My stripped rpg looks like this:

h dftactgrp(*no)
h extbinint(*yes)

// file specifications
ftestmas uf a e k disk prefix(tst_) alias
*
d testDS_t...
d ds template
d qualified
d id1 like(tst_Test_ID)
...
When I compile this code then both the file field and the ds subfield is
not treated as integer, but as packed 10,0.
...

A numeric field from a file gets defined as packed unless there is an
explicit D spec definition for the field. See
Definitions > Data Types and Data Formats > Internal and External Formats
in the ILE RPG Reference:
http://www.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzasd/dtafor9.htm

You can get an explicit D spec definition by coding an
externally-described data structure. By adding the line marked "add", all
the RPG fields from your file will be defined the same way they are defined
in the file itself, and your id1 field will be define as integer the way
you want.

h extbinint(*yes)

// file specifications
ftestmas uf a e k disk prefix(tst_) alias
*
add d e ds extname('TESTMAS')
d testDS_t...
d ds template
d qualified
d id1 like(tst_Test_ID)

--
Barbara


--
This is the RPG programming on the IBM i (AS/400 and iSeries) (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.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.