Time to turn a new page and start a new subseries in which I will discuss a few ideas about UI. Let’s start by contextualizing the topic and explaining some important aspects.
This subseries will cover two main topics:
- How to restructure your code to facilitate a UI (user interface) modernization initiative
- How the MVC (model-view-controller) design pattern can help achieve that goal
I’m also thinking about including a brief explanation of RPG Open Access and some tools that use this great RPG enhancement to facilitate the modernization of a legacy application’s UI. Let’s start with a simple question that has a somewhat complicated answer:
Why Separate the UI Code from the Rest?
One of the many advantages of coding in a modular and structured way is being able to reuse code. This is great, especially because you probably have a lot of programs that have common code when it comes to UI, database access, or business logic. These three things form layers in most of your programs. Isolating the code related to these layers is usually not an easy task, especially if you’re not used to it. Earlier in this series, I proposed a Lego-like solution, which is the core concept around a good and proper ILE program: there are modules and/or service programs for each layer, and a “main flow” module handles the user interaction and controls the main flow of the program.
Now it’s time to take the next step and explain how you can use this layering to modernize your UI. It can be a lot of work, but it has several important benefits:
- Reduce complexity—UI code is typically different from the rest of your RPG code. If you follow the guidelines in this series, your non-UI code won’t have indicators, for instance. Things can get pretty hectic when you have a lot of conditional formatting going on, such as choosing the right color or content for a field according to certain data-driven conditions. From this perspective, isolating your UI code will lower a program’s complexity and help streamline the whole process.
- Increase maintainability—By lowering the code’s complexity, you’re also increasing its maintainability, because smaller, more objective, and (hopefully) better-documented pieces of code are easier to maintain.
- Allow the workload to be shared—A modular approach allows you to break down the “construction” of a program into smaller tasks and distribute them among several programmers. You can even have specialists in different areas building different bits of code. Going back to the Lego analogy, your database expert can take care of the blocks that will handle the database operations related to a file or group of files, while your UI expert is simultaneously building the blocks that will make up the application’s interface with the user. These tasks can run in parallel, and in the end it’s simply a matter of putting the blocks together to build your program.
- Allow different and more flexible UIs—From personal experience, I can tell you that I’ve changed more code related to UI than anything else. While many UI changes might be minor details, such as adding a field or changing its attributes in certain conditions, it’s undeniable that we spend a lot of time changing the UI. By having it isolated from the rest, you can assign those tasks to the “UI experts” on your team and focus on other areas of the application. This might come as a shock, but your UI expert doesn’t have to be an RPG programmer. Actually, he or she might not even know what RPG is! As long as the pieces of code fit together, it really doesn’t matter. This might sound a bit strange, but you’ll see what I mean later.
Building Your Programs the Modern Way
In a typical Old Problematic Monolithic (OPM) program, all the functionality is contained in the same source file. This means that all the user interaction, database operations, and business logic are intertwined in an OPM piece of code. I’ve been preaching (and showing) the virtues of ILE. The modularization approach I’m about to show you is a step toward code and UI modernization. This approach assumes three things:
- Each module contains all the functions of a certain type or that operate over a certain item (file, business process, generic utilities, calculations, and so on).
- Each service program only has only one module.
- Each service program has its own binding directory.
The typical OPM program is self-contained, or almost self-contained if it eventually calls some helper programs as explained way back in the series. ILE programs, on the other hand, are made of many building blocks (functions and procedures) glued together by a “main flow” module, the backbone of an ILE program. From a structural point of view, it’s important to have the code well-organized in order to achieve maximum reusability and optimized maintenance. Figure 1 shows how, conceptually, an ILE program should be structured.
Figure 1: The ILE program concept is a multi-tier architecture implementation.
In this multi-tier architecture implementation, a program is composed of blocks arranged in three tiers or layers:
- Main flow—This tier handles the user interaction part of the program, as well as the main control flow of the program. This means the main flow handles all user-related input/output operations (either to a display file or a printer file) and provides the backbone of the program, calling procedures and functions in order to make things happen.
- Business logic—Sometimes known as business rules or business validations, this tier is responsible for the validation and enforcement of business requirements and rules. As described in the previous subseries, many of these validations are in the database, or at least in isolated modules.
- Data access—Finally, this layer handles all the data access. Here’s where the I/O Servers also described in two articles of the previous subseries come into play. They’ll handle all I/O operations for your programs. This should be totally independent from the other layers in order to maximize reusability. For instance, function Crt_Client_Record doesn’t know (and shouldn’t know) whether the client has a good credit score; that’s a job for a procedure of the business logic tier.
Coming Up
In the next TechTip, we’ll apply this conceptual approach to a practical situation. Until then, feel free to comment, question, and share your experiences in the comments section bellow.
Rafael Victória-Pereira has more than 20 years of IBM i experience as a programmer, analyst, and manager. Over that period, he has been an active voice in the IBM i community, encouraging and helping programmers transition to ILE and free-format RPG. Rafael has written more than 100 technical articles about topics ranging from interfaces (the topic for his first book, Flexible Input, Dazzling Output with IBM i) to modern RPG and SQL in his popular RPG Academy and SQL 101 series on mcpressonline.com and in his books Evolve Your RPG Coding and SQL for IBM i: A Database Modernization Guide. Rafael writes in an easy-to-read, practical style that is highly popular with his audience of IBM technology professionals.
Rafael is the Deputy IT Director - Infrastructures and Services at the Luis Simões Group in Portugal. His areas of expertise include programming in the IBM i native languages (RPG, CL, and DB2 SQL) and in "modern" programming languages, such as Java, C#, and Python, as well as project management and consultancy.
MC Press books written by Rafael Victória-Pereira available now on the MC Press Bookstore.
 |
||
 |
|
Evolve Your RPG Coding: Move from OPM to ILE...and Beyond Transition to modern RPG programming with this step-by-step guide through ILE and free-format RPG, SQL, and modernization techniques. List Price $79.95 Now On Sale
|
|
||
 |
|
Flexible Input, Dazzling Output with IBM i Uncover easier, more flexible ways to get data into your system, plus some methods for exporting and presenting the vital business data it contains. List Price $79.95
Now On Sale
|
|
||
 |
|
SQL for IBM i: A Database Modernization Guide Learn how to use SQL’s capabilities to modernize and enhance your IBM i database. List Price $79.95
Now On Sale
|
More 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.
TRY 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.
Forms 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.
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:
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.
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:
LATEST COMMENTS
MC Press Online