×
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.
On 24-Oct-2014 11:29 -0500, Vernon Hamberg wrote:
I just noticed, working in some old code, that when there is an
I-spec that defines a zoned field (blank in the data type and a
number in decimal places) that the field list displays it as packed.
<<SNIP>>
As I recall, that is the expected effect; an /implicit/ conversion to
packed that consistently confounded me every time I looked at a listing
and saw the Packed designation.
In my experience, as I recall, although the /field/ is being properly
represented as zoned data for the actual file I\O, the /variable/ that
gets declared to store that data is generated as Packed; i.e. in the
expansion of the program listing where the data types\attributes are
presented for the variables of the RPG program, a /variable name/ that
happens to have been declared with the same name as the /field name/
appears as a Packed Decimal, but the I/O performs as expected because
the /field/ within the database buffer is properly represented as Zoned
Decimal.?
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.
midrange.com
