|
i used a different approach to zone that was given due to varying sized
zone fields...
at least in zone, the string representation is clear text... unlike
packed...
for BIGIINT, that is a static sized data type... so that one was no
problem...
so example given for zoned is not applicable for varying packed
scale/precision
this one would be tough for even the best to come up with.
Jay
On Thu, Oct 31, 2019 at 9:45 AM Jon Paris <jon.paris@xxxxxxxxxxxxxx>
wrote:
No different to the zoned approach. Just overlay a packed field not a
zoned.
It's all just bits!
On Oct 31, 2019, at 1:34 PM, Jay Vaughn <jeffersonvaughn@xxxxxxxxx>wrote:
wrote:
now... on to packed... wanna take a shot at this? a routine that will
accommodate any packed precision/scale?
jay
On Wed, Oct 30, 2019 at 3:10 PM Barbara Morris <bmorris@xxxxxxxxxx>
10/30/2019
On 2019-10-30 11:51 a.m.,
dlclark@xxxxxxxxxxxxxxxx wrote:
"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> wrote on
the11:46:31 AM:
You - what Dave says.
You could make the routine more generic if you needed it but this is
the simple way to map a single field.
Yes, for example (to make it more generic), you could create a
15-character field and overlay it with a 15-digit (zero decimal) zoned
field. Then, move zeroes to the zoned field before right justifying
dividecharacter data into the character field. Then, you just have to
ofthe resulting zoned decimal number (into another field) by the number
listdesired decimal places that you got from SYSCOLUMNS.
To get the leading zeros and right-justify the character value in one
go, use EVALR with a character variable initialized to zeros.
dcl-ds cvtzoned qualified;
c char(15);
n zoned(15) overlay(c);
end-ds;
dcl-s zeros like(cvtzoned.c) inz(*all'0');
evalr cvtzoned.c = zeros + '1234N';
dsply (%char(cvtzoned.n));
--
Barbara
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
listTo post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx--
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxxquestions.
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
link: https://amazon.midrange.com
Help support midrange.com by shopping at amazon.com with our affiliate
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
As an Amazon Associate we earn from qualifying purchases.
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
