I'm sorry I read it wrong. I thought it was coming in as an integer, so I would agree with David, Packed.

The performance difference is so small you'd need to run several million transactions at a time to see the difference.

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects

On 1/22/14 2:24 PM, Charles Wilt wrote:
Jim,

I'm confused, you say "as close to the incoming value" which would be
Packed/Zoned (5,0) but then say "so integer for me"

So which is it?:)

Charles


On Wed, Jan 22, 2014 at 1:58 PM, Jim Oberholtzer <
midrangel@xxxxxxxxxxxxxxxxx> wrote:

>I would define it as close to the incoming value as possible. That way
>you remove any complaint points from the sender if there is a problem
>processing the file. I also would not trust the small integer constraint
>so integer for me.
>
>Jim Oberholtzer
>Chief Technical Architect
>Agile Technology Architects
>
>On 1/22/14 1:51 PM, Charles Wilt wrote:
> >Philosophical question for you all...
> >
> >I'm creating a new table to hold data received from an external source.
> >
> >The specs given include
> >
> >Name, Type/Length, Picture
> >MyFld, N/5, 9(5)
> >
> >So MyField is a 5 digit number...
> >
> >I could defined this as Packed/Zoned 5,0
> >Or I could use integer (or even small integer since the current number of
> >values is less than 1000)
> >
> >Since I know DB2 and RPG for that matter perform best with integer, I'm
> >leaning that direction. But I can't help but think that Packed (5,0) is
> >more correct.
> >
> >Thoughts?
> >
> >Charles
> >--
>
>--


This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].