Thanks. Here is what I've found:
1. iSeries navigator makes it very simple to view the actual change data without the "goobly gook" by right clicking on the journal change record and hitting "view detail data" and it shows you all the field data like I would normally expect without having to do hex calculator "fun" (aka wasting time). The problem is it only does this on a record by record basis, they are missing the last little step of "export all changes as human readable non/hex output" option :(
2. I found EXPJRNE (which we are attempting to install) which supposedly makes this whole process much simpler and gets rid of the binary gobbly gook. Here is the URL: http://www.tools400.de/English/Freeware/Utilities/utilities.html
Not sure if anyone has tried this or not. But it's a long process to try get it installed (need XMLPARSER another free tool first).
I basically need to take 3 days worth of changes and search for a value in the integer column. It shouldn't be this difficult, change data capture for instance in MS SQL server makes this incredibly simple as it shows you the data unnecessary conversions / hoops to jump through.
From: Charles Wilt [mailto:charles.wilt@xxxxxxxxx]
Sent: Monday, June 09, 2014 11:32 AM
To: Midrange Systems Technical Discussion
Subject: Re: Displaying SQL INT data within journals
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...
On Mon, Jun 9, 2014 at 11:45 AM, Matt Olson <Matt.Olson@xxxxxxxx> wrote:
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?
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,
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
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,
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l