20
Thu, Jun
3 New Articles

Journal Entries Exposed! JOESD Made Readable!

RPG
Typography
  • Smaller Small Medium Big Bigger
  • Default Helvetica Segoe Georgia Times

Do a DSPJRN to an outfile, and field JOESD is inscrutable. Learn how to make it readable.

 

You know that journal entries contain useful "who did what to whom and when" information and that they can also help you understand data flow and changes in a suite of unfamiliar programs. You've probably used the DSPJRN command, and on the screen you can easily see the date and time the transaction occurred. You can also see the job name, user, and number. You can even see the program that made the transaction. But you can't (easily) see what changed! Usually, you see something like Figure 1, with a mishmash of special characters in the "Entry specific data" field.

 

040710LennonFigure1 

Figure 1: This is a typical journal display of a record with non-character fields. (Click images to enlarge.)

 

Yes, "Entry specific data" shows you the record, but it is difficult to parse this string into fields and extremely time-consuming when there are non-character fields, as above. You quickly lose your enthusiasm when you need to review more than a handful of records.

 

Writing the data to an outfile allows you to scan using Query, or SQL, or your own program, but JOESD is still largely impenetrable unless you can reassemble it into fields.

 

The good news is that, with a little effort, the reassembly can be done. This article shows how.

Article Setup

For this article, I created a simple file named ORDLNP using DDS like this:

 

A               R ORDLINF                   

A                 ORDNUM         7P 0       

A                 LINE           3P 0       

A                 SKU            5P 0       

A                 ORDDUE          L         

A                 QTY            3P 0       

A                 OFFER          2S 0        

 

I started journaling to journal MYJRN, added a few records to ORDLNP, and changed one of them. (If you want to follow along, you can download the DDS and a CLP program that creates everything, adds the records to the file, and does the updating.) 

 

I then sent the journal records to QTEMP/WKORDLNP using this command:

 

DSPJRN JRN(MYJRN) FILE((ORDLNP)) JRNCDE((R)) OUTPUT(*OUTFILE) OUTFILFMT(*TYPE2) OUTFILE(QTEMP/WKORDLNP) ENTDTALEN(*CALC)                         

 

Note the OUTFILFMT(*TYPE2) to get both the job user and the current user profile, as these will be different if the job has switched profiles. Note also that we are selecting only JRNCDE(R), outputting only the journal entries that contain record data. The ENTDTALEN(*CALC) is also important; it ensures that you get all the record data.

 

If you query QTEMP/WKORDLNP, you will find at the beginning the date, time, job information, program, etc. as in Figure 2.

 

040710LennonFigure2

Figure 2: These first fields on a journal record have clear, readable data.

 

If you scroll all the way to the right, you will see the record image in the SPECIFIC DATA column, as in Figure 3. This is field JOESD, and the record data is hard to decipher, though you can recognize the character and zoned fields.

 

040710LennonFigure3

Figure 3: Here's an example of a common DSPJRN output of changes to a file with non-character fields.

Exposing JOESD

In library QSYS, IBM provides template files for DSPJRN output: files QADSPJRN and QADSPJR2 through QADSPJR5, corresponding to OUTFILFMT values *TYPE1 through TYPE5. If you display the fields in these formats, you will find many common fields at the beginning of each record, and the last field is always JOESD, the infamous "Entry Specific Data."

 

What we are going to do is create a file in which field JOESD is replaced by definitions for the fields in ORDLNP.

 

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        100A         COLHDG('SPECIFIC' 'DATA') 

 

Using your favorite editor, be it SEU, WDSc, RDi, or something else entirely, add the DDS field definitions for ORDLNP to the end:

 

*************     JOESD        100A         COLHDG('SPECIFIC' 'DATA')

A                 ORDNUM         7P 0                                

A                 LINE           3P 0                                

A                 SKU            5P 0                                

A                 ORDDUE          L                                  

A                 QTY            3P 0                                

A                 OFFER          2S 0                                

 

Then compile this to create a new file named XORDLNP. I created my expanded file in library LENNONS1.

 

Now we simply have to copy QTEMP/WKORDLNP to XORDLNP using the *NOCHK option, and the JOESD data will be mapped to fields:

 

CPYF FROMFILE(QTEMP/WKORDLNP) TOFILE(LENNONS1/XORDLNP) MBROPT(*REPLACE) FMTOPT(*NOCHK)

 

Query XORDLNP and scroll to the right, and all the fields are now nicely visible, as in Figure 4:

 

040710LennonFigure4

Figure 4: DSPJRN output now shows data mapped to fields.

 

That wasn't too hard, was it? You can do this for any file. All you need is the DDS for QADSPJR2, which I have provided, and, of course, you need the DDS for the journaled file.

An Easier Way

If you want to make this whole process much more convenient, let me suggest the freeware command EXPJRNE, Export Journal Entries, provided by Thomas Raddatz. This really smart tool saves you from having to worry about creating DDS as I did above. You don't have to execute the DSPJRN command either, or the CPYF. It does it all for you. You don't even need to know which journal is being used. Simply tell EXPJRNE the physical file, and it will create the output file and copy the journal records to it.

 

A prompted EXPJRNE command to do what I did above looks like this:

 

EXPJRNE/EXPJRNE OBJ(LENNONS1/ORDLNP) FROMDATE(120909) FROMTIME(000000) TO DATE(120909) TOTIME(235959) OUTFILE(QTEMP/XORDLNP) CRTFILE(*YES)         

 

There are additional options, but this gives you a flavor of how easy it is to use.

 

You need to download and install EXPJRNE, but after that it is straightforward command execution. And the price is right.

Take Advantage

There is a wealth of really useful information in journal entries. The data is not hard to mine, so don't let it go to waste.

 

Sam Lennon

Sam Lennon is an analyst, developer, consultant and IBM i geek. He started his programming career in 360 assembly language on IBM mainframes, but moved to the AS400 platform in 1991 and has been an AS400/iSeries/i5/IBM i advocate ever since.

BLOG COMMENTS POWERED BY DISQUS

LATEST COMMENTS

Support MC Press Online

$0.00 Raised:
$

Book Reviews

Resource Center

  • SB Profound WC 5536 Have you been wondering about Node.js? Our free Node.js Webinar Series takes you from total beginner to creating a fully-functional IBM i Node.js business application. You can find Part 1 here. In Part 2 of our free Node.js Webinar Series, Brian May teaches you the different tooling options available for writing code, debugging, and using Git for version control. Brian will briefly discuss the different tools available, and demonstrate his preferred setup for Node development on IBM i or any platform. Attend this webinar to learn:

  • SB Profound WP 5539More than ever, there is a demand for IT to deliver innovation. Your IBM i has been an essential part of your business operations for years. However, your organization may struggle to maintain the current system and implement new projects. The thousands of customers we've worked with and surveyed state that expectations regarding the digital footprint and vision of the company are not aligned with the current IT environment.

  • SB HelpSystems ROBOT Generic IBM announced the E1080 servers using the latest Power10 processor in September 2021. The most powerful processor from IBM to date, Power10 is designed to handle the demands of doing business in today’s high-tech atmosphere, including running cloud applications, supporting big data, and managing AI workloads. But what does Power10 mean for your data center? In this recorded webinar, IBMers Dan Sundt and Dylan Boday join IBM Power Champion Tom Huntington for a discussion on why Power10 technology is the right strategic investment if you run IBM i, AIX, or Linux. In this action-packed hour, Tom will share trends from the IBM i and AIX user communities while Dan and Dylan dive into the tech specs for key hardware, including:

  • Magic MarkTRY the one package that solves all your document design and printing challenges on all your platforms. Produce bar code labels, electronic forms, ad hoc reports, and RFID tags – without programming! MarkMagic is the only document design and print solution that combines report writing, WYSIWYG label and forms design, and conditional printing in one integrated product. Make sure your data survives when catastrophe hits. Request your trial now!  Request Now.

  • SB HelpSystems ROBOT GenericForms of ransomware has been around for over 30 years, and with more and more organizations suffering attacks each year, it continues to endure. What has made ransomware such a durable threat and what is the best way to combat it? In order to prevent ransomware, organizations must first understand how it works.

  • SB HelpSystems ROBOT GenericIT security is a top priority for businesses around the world, but most IBM i pros don’t know where to begin—and most cybersecurity experts don’t know IBM i. In this session, Robin Tatam explores the business impact of lax IBM i security, the top vulnerabilities putting IBM i at risk, and the steps you can take to protect your organization. If you’re looking to avoid unexpected downtime or corrupted data, you don’t want to miss this session.

  • SB HelpSystems ROBOT GenericCan you trust all of your users all of the time? A typical end user receives 16 malicious emails each month, but only 17 percent of these phishing campaigns are reported to IT. Once an attack is underway, most organizations won’t discover the breach until six months later. A staggering amount of damage can occur in that time. Despite these risks, 93 percent of organizations are leaving their IBM i systems vulnerable to cybercrime. In this on-demand webinar, IBM i security experts Robin Tatam and Sandi Moore will reveal:

  • FORTRA Disaster protection is vital to every business. Yet, it often consists of patched together procedures that are prone to error. From automatic backups to data encryption to media management, Robot automates the routine (yet often complex) tasks of iSeries backup and recovery, saving you time and money and making the process safer and more reliable. Automate your backups with the Robot Backup and Recovery Solution. Key features include:

  • FORTRAManaging messages on your IBM i can be more than a full-time job if you have to do it manually. Messages need a response and resources must be monitored—often over multiple systems and across platforms. How can you be sure you won’t miss important system events? Automate your message center with the Robot Message Management Solution. Key features include:

  • FORTRAThe thought of printing, distributing, and storing iSeries reports manually may reduce you to tears. Paper and labor costs associated with report generation can spiral out of control. Mountains of paper threaten to swamp your files. Robot automates report bursting, distribution, bundling, and archiving, and offers secure, selective online report viewing. Manage your reports with the Robot Report Management Solution. Key features include:

  • FORTRAFor over 30 years, Robot has been a leader in systems management for IBM i. With batch job creation and scheduling at its core, the Robot Job Scheduling Solution reduces the opportunity for human error and helps you maintain service levels, automating even the biggest, most complex runbooks. Manage your job schedule with the Robot Job Scheduling Solution. Key features include:

  • LANSA Business users want new applications now. Market and regulatory pressures require faster application updates and delivery into production. Your IBM i developers may be approaching retirement, and you see no sure way to fill their positions with experienced developers. In addition, you may be caught between maintaining your existing applications and the uncertainty of moving to something new.

  • LANSAWhen it comes to creating your business applications, there are hundreds of coding platforms and programming languages to choose from. These options range from very complex traditional programming languages to Low-Code platforms where sometimes no traditional coding experience is needed. Download our whitepaper, The Power of Writing Code in a Low-Code Solution, and:

  • LANSASupply Chain is becoming increasingly complex and unpredictable. From raw materials for manufacturing to food supply chains, the journey from source to production to delivery to consumers is marred with inefficiencies, manual processes, shortages, recalls, counterfeits, and scandals. In this webinar, we discuss how:

  • The MC Resource Centers bring you the widest selection of white papers, trial software, and on-demand webcasts for you to choose from. >> Review the list of White Papers, Trial Software or On-Demand Webcast at the MC Press Resource Center. >> Add the items to yru Cart and complet he checkout process and submit

  • Profound Logic Have you been wondering about Node.js? Our free Node.js Webinar Series takes you from total beginner to creating a fully-functional IBM i Node.js business application.

  • SB Profound WC 5536Join us for this hour-long webcast that will explore:

  • Fortra IT managers hoping to find new IBM i talent are discovering that the pool of experienced RPG programmers and operators or administrators with intimate knowledge of the operating system and the applications that run on it is small. This begs the question: How will you manage the platform that supports such a big part of your business? This guide offers strategies and software suggestions to help you plan IT staffing and resources and smooth the transition after your AS/400 talent retires. Read on to learn: