× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Hi Rich,

It really depends on context. The CALL command, for example, always formats a number as 15,5. That's not a limit, really -- it's the only choice.

The CL programming language cannot declare a packed variable larger than 15 digits. (No clue why.) The same is true for CMDs... 15 digit max.

The limit in SQL, DDS and RPG has historically been 30 digits. In V5R2, they upgraded it to 31 digits (which puzzled me) and in V5R3, they increased it to 63 digits.

So it really depends on context as to whether the limit is 15, 30, 31 or 63 digits.


Rich Loeber wrote:
I'm trying to recall IBM's specifications on size contraints, if any, for packed data fields. For some reason, I thought packed data was limited to 15 digits, but I can't be sure about this and I'm seeing some data fields that seem to support larger field sizes.

Rich Loeber
Kisco Information Systems
http://www.kisco.com



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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

This mailing list archive is Copyright 1997-2024 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].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.