Re: Controlling the definition of fields defined like(...)

Roger,

If I understand the problem correctly, you have a field defined as
zoned because it's defined like a field in a file, and another as
packed because it's in a DS.

try this: in the program that has the zoned field, in addition to the
F spec, define the file as an external data structure.  you don't have
to do anything with it, but I think (i know, trouble), it will map all
the zoned fields to packed.

I don't know if you can define a display file (you did say it was a
display file, right?) as an eDS, but if not, if a similar field is
also defined in another file, define that file as an eDS and use that
field for your like().

hope this helps,

Rick

On 6/13/06, Roger Vicker, CCP <rv-lists@xxxxxxxxxx> wrote:

This is starting to drive me down the hall screaming.

And the archives had a promising solution with data structures but it
just doesn't work. V5R3

I have a file with a field (dividnum) defined as packed 5,0.

I have two programs that use the file. Program B has a display file with
the field in it via reffld(dividnum)

Program A has a data structure defined with a specified length and an
array in it defined as like(dividnum) that is passed to/from program B
using prototypes.

Program B has a data structure defined with with the same specified
length and an array in it defined as like(dividnum) that is pointer
based. Program B sets the pointer to the data structure as the address
of Program A's data structure that is passed to it. I have verified that
the pointer "magic" works just fine.

// Program A

D SelDs           ds           384

D   sel                               like(dividnum) DIM(32) ASCEND


// Program B

D SelDs           ds           384    based(SelDsAdr)

D   sel                               like(dividnum) DIM(32) ASCEND

D SelDsAdr        s               *


The problem is that the array in program A is zoned, as I would expect
it to be since it is in a data structure. Program B however defines the
array as being packed.

There has got to be a way to define fields by reference to reduce code
changes when lengths changes but either get consistent type (zoned,
packed...) or be able to force the type so that they can be passed as
parameters between programs.

Does everyone hard code field lengths for numeric parameter passing or
have I missed something?

Roger Vicker, CCP

--
*** Vicker Programming and Service *** Have bits will byte *** www.vicker.com 
***
Never deprive someone of hope, it may be all they have.

--
This is the RPG programming on the AS400 / 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.