Re: Like keyword not keeping format

["Buddy McClean" <Buddy.McClean@xxxxxxxxxxxx>]

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.