Browsing journal records requires a file in the following format:
(Copied from
https://www.mcpressonline.com/programming/rpg/journal-entries-exposed-joesd-made-readable)
Fields 1-19 are 'journal data--' who did it, when they did it, what program did it, what job was running, etc.
This is the first 155 bytes of the retrieved journal entry.
Here's the DDS for QADSPJR2, with JOESD commented out:
A R QJORDJE2
A JOENTL 5S 0 COLHDG('ENT' 'LGTH')
A JOSEQN 10S 0 COLHDG('SEQ' 'NUMBER')
A JOCODE 1A COLHDG('CODE')
A JOENTT 2A COLHDG('TYPE')
A JODATE 6A COLHDG('DATE')
A JOTIME 6S 0 COLHDG('TIME')
A JOJOB 10A COLHDG('JOB' 'NAME')
A JOUSER 10A COLHDG('USER' 'NAME')
A JONBR 6S 0 COLHDG('JOB' 'NUMBER')
A JOPGM 10A COLHDG('PROGRAM' 'NAME')
A JOOBJ 10A COLHDG('OBJECT' 'NAME')
A JOLIB 10A COLHDG('LIBRARY' 'NAME')
A JOMBR 10A COLHDG('MEMBER' 'NAME')
A JOCTRR 10S 0 COLHDG('COUNT/' 'RRN')
A JOFLAG 1A COLHDG('FLAG')
A JOCCID 10S 0 COLHDG('COMMIT' 'CYCLE ID')
A JOUSPF 10A COLHDG('USER' 'PROFILE')
A JOSYNM 8A COLHDG('SYSTEM' 'NAME')
A JOINCDAT 1A COLHDG('INCOMPLETE' 'DATA')
A JOMINESD 1A COLHDG('MINIMIZED' 'ESD')
A JORES 18A COLHDG('RESERVED')
************* JOESD nnnA COLHDG('SPECIFIC' 'DATA')
Field JOESD is the image (before or after) of your file, all fields the proper length, mushed together into one field.
Using your favorite editor, be it SEU, WDSc, RDi, or something else entirely, add the DDS field definitions for your file to the end.
Copy the extracted data to this file FMTOPT(*NOCHK), and you can read it ‘in English.’
Paul E Musselman
PaulMmn@xxxxxxxxxxxxx
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Mark Waterbury
Sent: Tuesday, January 29, 2019 2:16 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: Needle in Haystack - Seeking Offending Journal Entry
This is where EXPJRNE really shines. :D
On Tuesday, January 29, 2019, 2:04:56 PM EST, Rob Berendt <rob@xxxxxxxxx<mailto:rob@xxxxxxxxx>> wrote:
The biggest drawback to this is parsing out the before/after images. They are in there but as two big strings. If you're really good you can build your own UDTF to take one of those images and parse it out. One method would be to take the big image and bounce it against an externally defined data structure in RPG and return all the individual columns as a "row" from a UDTF.
midrange.com
