Re: Like keyword not keeping format

[Jon Paris <jon.paris@xxxxxxxxxxxxxx>]

Probably not - but you'll find it (and a bunch of other D-spec/dcl stuff) in this piece:  

http://ibmsystemsmag.com/ibmi/developer/general/d-spec-discoveries/ <http://ibmsystemsmag.com/ibmi/developer/general/d-spec-discoveries/>


Jon Paris

www.partner400.com
www.SystemiDeveloper.com

> On Feb 15, 2018, at 10:58 AM, Buddy McClean <Buddy.McClean@xxxxxxxxxxxx> wrote:
>
> I'm sure all this was in a best practices class, sorry I missed them. 
>
> > > > Jon Paris <jon.paris@xxxxxxxxxxxxxx> 2/14/2018 6:08 PM >>>
> It would be better if the DS in question did not actually define the field's type but rather just named it. That way it always picks up the fields definition from the file.
>
>
> Jon Paris
>
> www.partner400.com
> www.SystemiDeveloper.com
>
> > On Feb 14, 2018, at 6:10 PM, Buddy McClean <Buddy.McClean@xxxxxxxxxxxx> wrote:
> >
> > That looks like it. The prog that has it as zoned includes a /copy of a DS in which OHINV is defined just like the file, zoned. So it changed from the file definition version to packed, except that there is a DS that reaffirms it being zoned so it does not change it to packed. 
> >
> > Verified by putting the DS in the program that changed it to packed, it now does not change it to packed. 
> >
> > Agreed on the reliability of the outline. 
> >
> > Really surprised I have not encountered this problem before when expecting parm data to maintain type using LIKE.
> >
> > Thanks. 
> >
> >
> >
> > > > > Buck Calabro <kc2hiz@xxxxxxxxx> 2/14/2018 4:29 PM >>>
> > On 2/14/2018 5:24 PM, Buddy McClean wrote:
> > > What started this was passing a parm between 2 programs. Both using the same file and field as the base of the LIKE.  Both programs used I619 Like(OHINV)  - one program would pass I619 as zoned and the other would read it in as packed, so the call would crash because of it.
> > I think of the Outline View as a work in progress.  If it seems
> > snookered, I revert to the compiler listing.
> >
> > With respect to the mis-matched parameter definition, make sure OHINV
> > isn't in a data structure, because that will override the Db2 definition.
> >
> > -- 
> > --buck
> >
> > http://wiki.midrange.com
> > Your updates make it better!
> >
> > -- 
> > This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries  (WDSCI-L) mailing list
> > To post a message email: WDSCI-L@xxxxxxxxxxxx
> > To subscribe, unsubscribe, or change list options,
> > visit: https://lists.midrange.com/mailman/listinfo/wdsci-l
> > or email: WDSCI-L-request@xxxxxxxxxxxx
> > Before posting, please take a moment to review the archives
> > at https://archive.midrange.com/wdsci-l.
> > -- 
> > This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries  (WDSCI-L) mailing list
> > To post a message email: WDSCI-L@xxxxxxxxxxxx
> > To subscribe, unsubscribe, or change list options,
> > visit: https://lists.midrange.com/mailman/listinfo/wdsci-l
> > or email: WDSCI-L-request@xxxxxxxxxxxx
> > Before posting, please take a moment to review the archives
> > at https://archive.midrange.com/wdsci-l.
>
> -- 
> This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries  (WDSCI-L) mailing list
> To post a message email: WDSCI-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/wdsci-l
> or email: WDSCI-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at https://archive.midrange.com/wdsci-l.
> -- 
> This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries  (WDSCI-L) mailing list
> To post a message email: WDSCI-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/wdsci-l
> or email: WDSCI-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at https://archive.midrange.com/wdsci-l.