MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » June 2014

Re: Displaying SQL INT data within journals



fixed

DSPJRN has always just shown the entire record buffer. It doesn't show
individual fields.

Packed fields are also "gobbly gook"

Translating the hex representation as suggested by Mark is your only choice
within DSPJRN.

However, if you happen to use ProData's DBU, you could use DBUJRN instead.
That utility does redefine the journal entries into individual fields.

If you don't have DBU, you can "roll your own" as follows...

DSPJRN FILE((MYFILE)) ENTTYP(*RCD)to an OUTFILE(JRNOUTTEMP)

CREATE TABLE myjrnout
as (select <jrn flds except JOESD>, <all fields from myfile>
from jrnouttemp join myfile
) with no data

CPYF JRNOUTTEMP TOFILE(MYJRNOUT) FMTOPT(*NOCHK)

No you can use SQL to look at MYJRNOUT..

If you have NULLs, VARCHARs or BLOBs it gets tricky...

Also, delete's tend to be a problem...

Charles




On Mon, Jun 9, 2014 at 11:45 AM, Matt Olson <Matt.Olson@xxxxxxxx> wrote:

All,

We have a SQL (DDL) described file with a INTEGER column.

When you view this file on the green screen via DSPFFD it shows the
integer column as BINARY with a field length of 9.

The problem is when we view journal changes via DSPJRN it shows as "gobbly
gook" instead of the actual integer value.

How can we view the actual integer value so we can search all journal data
for the value we are searching for?

Thanks!

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.







Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot 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 here. If you have questions about this, please contact