RE: Storing Numeric Values in the Database

Check out EXPJRNE at
http://www.tools400.de/English/Freeware/Utilities/utilities.html

It lets you dump journals to a file with all the JOxxx journal fields, but
it splits up the JOESD field into the actual field names in the journaled
file.

Sure beats SUBSTR(JOESD,x,x)!


Richard

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Charles Wilt
Sent: Friday, September 02, 2011 8:57 AM
To: Midrange Systems Technical Discussion
Subject: Re: Storing Numeric Values in the Database

Joe,

I hear you on the journal dumps...

My preference is to use DBUJRN, though that doesn't help if I need to
look at multiple tables at once...

When DBUJRN is not available, I roll my own equivalent using CREATE
TABLE AS (to build a table with the journal fields and the table's
fields) and CPYF *NOCHECK (or SQL SUBSTR)...

Charles



On Fri, Sep 2, 2011 at 8:42 AM, Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx>
wrote:

On 9/2/2011 7:16 AM, Charles Wilt wrote:

Joe,

My vote is integers for numbers with zero decimal places, otherwise

packed.

Couldn't tell you the last time I used DSPPFM to look at a record.  I
used SQL or DBU when I need to look at data.

Charles

DSPPFM has its advantages - it's always there, and it quickly shows you
the last record in the file.  DBU is close, but you do have to remember
to hit RRN on keyed physicals.  But the primary annoyance with packed
fields is when trying to do SQL selects on the JOESD field of an ad hoc
journal dump.  It's doable, but just not as easy.

Note that I'm not arguing FOR zoned fields, just seeing if others have
the same issues I do when dealing with packed data.

Joe
--