Integrate RPG and Java to take advantage of the latest technologies, such as Excel spreadsheets, Adobe files, and email.

Editor's Note: This article is an excerpt from Advanced Integrated RPG, a new MC Press book. 

When you look at your Original Program Model (OPM) programs and think about why these programs were developed, the goal was likely to provide comprehensive software that would withstand the test of time and produce solid, reliable results as the backbone for business-critical operations. If you were to focus solely on this aspect, you might not see the need to even bother using ILE. After all, you have a programming language that works, it has been around for a very long time, and it is easy to understand. So, let's consider some of the limitations of this way of programming and define the reasons why modernization of the code is necessary.

The first thing that comes to mind when discussing modernization is aesthetics. When you have a system that provides indisputable data that is necessary for business processes, you may consider the ability to create "modern" reports in Microsoft Excel or Adobe PDF form as being an unnecessary enhancement. After all, the data is being generated, the information is being audited, reporting is being performed, and the company is generating revenue. How important is it to make the reports look better? Well, there are other factors beyond appearance that you need to consider when evaluating the need for spreadsheets and PDF files.

Portability

Portability is a big one. To address this issue, your initial thought might be to generate ASCII text files. If you've been working with RPG for a few years, there's a good chance you've already tried this approach.

However, if you delimit the ASCII data using a special character, you must make the user aware of which delimiter you're using, and the user must process the data properly. This means you need specifications that identify what the fields are and how they should be separated. In the end, the data is likely to be imported into an Excel spreadsheet anyway.

When you provide ASCII text files, you may have different formats for multiple records in the file. For example, you may have a header that displays a title and possibly user information that does not match the layout of the data, requiring you to identify when record formats change.

There is also the issue of delivering the file to the user. Will you use a data transfer that must be defined for each user to download the correct physical file member? Will you use File Transfer Protocol (FTP) and require a user name and password?

If you email the text file, its carriage returns and line feeds might be altered during conversion through MIME format. Will you zip the file to avoid this issue, or will your email application embed the text into the email message and force the user to copy and paste the data from there? You could make the data available using a Web server, but if you're going to go that far, you might as well use HTML.

The bottom line is that unless you're dealing with another programmer or a power user, you will likely encounter users who resist using ASCII text files, especially given the options available today.

PDF files are built specifically to overcome these issues. With PDF files, all that users need is a reader, and they can view any PDF file without any of the preceding concerns. PDF readers are typically free and work on most operating systems. In fact, one is probably already installed with your OS.

Even though PDFs are portable, they can be difficult to modify, which can be a good thing or a bad thing, depending on your intentions.

Microsoft Excel files offer the same portability as PDF files. Microsoft provides a free viewer that lets users view these files in read-only mode. And with the availability of several open-source options, you can easily create and change such files using software that is supported on most operating systems.

Usability and Standardization

Another reason to provide electronic documents is usability. When you furnish data in an Excel spreadsheet, users can easily search and sort the data, creating ad hoc reports and performing "what if" scenarios. They can also create graphical representations of the data using charts and graphs.

Last, Excel and PDF are two of the most commonly used formats. Providing data in these formats makes the work of your users much easier to use and share with others.

Evolving Your RPG Development Skills

In the beginning chapters, we'll explore the evolution of RPG from OPM to ILE and discuss how to exploit the new capabilities of the IBM i platform. Our discussion is structured in a logical direction, first building on your existing RPG coding skills by explaining the new features available in ILE and the new concepts involved with scoping and modular coding practices.

We'll start by converting some sample OPM source to an ILE-compatible format and implementing the use of the ILE compilers. With ILE, there are some new concepts to cover that involve the binding of components and the differences between an OPM program and an ILE program. The primary objective of the book is to integrate RPG with Java, so we'll focus our efforts on capabilities that directly lead us to this goal.

Once we have the code in an ILE format, we'll begin to discuss procedures, service programs, and activation groups and explain why you may want to use them. For the purposes of the book, we'll look at how you can access Java objects and methods. 

Developing Reusable Code

In our journey toward understanding the use of Java classes and methods from RPG, we will make every effort to encapsulate the Java interface into reusable code. When we do this, I'll go into a detailed analysis of how to interface with the Java environment, and I'll provide some RPG-friendly code that you can use in the future. I call these pieces of code "RPG wrappers" because we'll wrap RPG code around the Java classes and methods.

You can make the RPG wrappers available to the program you're working with and use pure RPG code to access the Java functionality. This technique not only makes the code easier for you to use in the future; you can also use it perform all the exception handling so you won't have to repeat the same code.

Another benefit to wrapping Java classes and methods in RPG is that you can easily share the new Java capabilities with your fellow RPG programmers in a form that they will be able to use immediately.

Integrating RPG with Java

Enhancing your RPG development skills is a great side effect of the primary objective of this book, which is to exploit the capabilities of Java from within RPG. When we get to this point, we'll explore all the new concepts you need to understand about Java to get it to work properly. It would be nice if you could just plug in a Java method, as you can an API. But there are other things you need to think about when dealing with the Java Virtual Machine (JVM), such as starting and stopping it. And because two totally different environments are communicating with each other, you need to take some extra measures to handle some of the ugliness of reclaiming memory resources.

This book will introduce you to the Java components necessary to provide the results you're looking for. It is not intended to teach you Java, but it does introduce you to Java and identify how to use specific parts of open-source technology to provide the product of your hard work, which in this case will be Excel spreadsheets and PDF files that you can distribute using email from RPG.

Creating Electronic Documents

If your objective is to provide reports that can be sorted, graphed, charted, and manipulated, you can convert your greenbar reports into an Excel spreadsheet. We'll do this using the Horrible Spreadsheet Format (HSSF) capability of the POI open-source project.

If your intention is to provide documents that can be distributed easily to users and customers in a portable format that anyone on any operating system can use, you may want to convert your greenbar reports, billing invoices, or labels and bar codes to the PDF format. We'll use the iText open-source project to provide these capabilities.

We'll accomplish these objectives by first defining the technical terms and concepts of the components that make up an electronic document and then relating them to the classes and methods available in POI and iText. Then, we'll convert the methods and parameters into an RPG-friendly format and build wrappers for them. After that, you can start using them from within RPG.

Distributing Electronic Documents Using Email

When evaluating the options to provide my IBM i system with email capability, I found JavaMail to be the most self-contained and flexible solution. Using JavaMail, we will build an email client that simply creates the email and relays it through your current email server—no additional servers or configuration required. We'll start with a simple text email, specifying the To, From, and Subject, and then advance to formatted emails with HTML and attachments. You can even embed the images right into the email if desired.

Using JavaMail for your email client frees you from being tied to the operating system. Once you understand the JavaMail API and you start using Java, you'll be able to easily rewrite your RPG program into pure Java and use the exact same API to provide the same capability to any other server on the network. This freedom and knowledge will also help you as a programmer to begin to integrate with other areas of technology in your company and give you greater flexibility, not only in your programming options but as a valued member of the programming team.

And that's just the beginning! In addition to giving you the isolated capabilities of the service programs we'll discuss, I'll walk you through the process of identifying and implementing the classes and methods. So, once you get your RPG programs to start generating electronic documents and sending emails, you can further explore other options that are available and expand your service programs to implement more and more features. I hope this will be the beginning of a whole new level of programming using Java for you. Let's get started.

Thomas Snyder has a diverse spectrum of programming experience encompassing IBM technologies, open source, Apple, and Microsoft and using these technologies with applications on the server, on the web, or on mobile devices.

Tom has more than 20 years' experience as a software developer in various environments, primarily in RPG, Java, C#, and PHP. He holds certifications in Java from Sun and PHP from Zend. Prior to software development, Tom worked as a hardware engineer at Intel. He is a proud United States Naval Veteran Submariner who served aboard the USS Whale SSN638 submarine.

Tom is the bestselling author of Advanced, Integrated RPG, which covers the latest programming techniques for RPG ILE and Java to use open-source technologies. His latest book, co-written with Vedish Shah, is Extract, Transform, and Load with SQL Server Integration Services.

Originally from and currently residing in Scranton, Pennsylvania, Tom is currently involved in a mobile application startup company, JoltRabbit LLC.

---

MC Press books written by Thomas Snyder available now on the MC Press Bookstore.

		Advanced, Integrated RPG See how to take advantage of the latest technologies from within existing RPG applications. List Price $79.95 Now On Sale
		Extract, Transform, and Load with SQL Server Integration Services Learn how to implement Microsoft’s SQL Server Integration Services for business applications. List Price $79.95 Now On Sale

Also Read

Programming in ILE RPG - Defining Data Structures, Part I

H and F Position-less Specs

Practical RPG: AI and IBM i