13
Fri, Dec
4 New Articles

RPG Academy: Database Modernization - Methodology, Part 1

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

It’s time to talk about database modernization methodology. Because each scenario is a little (or a lot) different from the others, you’ll have to adapt these steps to your particular situation.

Most database modernization scenarios have a few things in common, which allows you to follow the three-step methodology presented in this section, with a few tweaks. This methodology is just a set of tasks and guidelines that you’ll need to adapt to your particular scenario.

Keep in mind that nothing is written in stone, and your knowledge of your particular context is of paramount importance to a successful modernization process. It’s important that you understand each step and adapt it to your needs. Although there are only three steps, they are complex and require detailed explanation. This means that the discussion of this methodological approach will span over several articles, so bear with me while I explain each step with enough detail for you to understand its core and adapt it to your application’s context.

You might find that you can safely skip one or more of them, while the others are mandatory to reap the benefits of the modernization process. Also keep in mind that you’ll be repeating these steps quite a few times, because you shouldn’t try to modernize the whole database at once. Start with the files that support the most important functionalities of the application. Once you’re done with those, repeat the process with the next group of files, and so on until you’re done.

These are the three steps:

  1. Convert the DDS files to DDL objects.
  2. Move business rules to the database.
  3. Take advantage of DB2’s advanced functionalities.

The general idea is that you’ll gain a lot with these changes, in terms of performance, database user-friendliness, and flexibility. It’s not an easy path, and some steps may sound a bit weird (yes, I can imagine what you’re thinking about step two), but it’ll make sense in a while. Bear with me, and I’ll explain it all in greater depth over the next pages.

Let’s start with the first step, which seems self-explanatory…but it’s not.

Step One: Convert DDS Files to DDL Objects

Before converting your database from DDS to DDL, you really should take the time to understand, document, and analyze it. Even though you think you know your database, there will be some surprises (more on this next), and you need all the information you can get from your database before you move on.

This will be a time-consuming process, but it will pay off later. The result of this “detective work” will serve as the basis for the rest of the modernization process. In order to tackle such a complex and important step, you need to establish some sort of working process. Let’s go over a possible approach to this working process, which you should repeat for each library of your application that contains files.

Discover and List Existing Files

Depending on the application’s age, the process of discovering and listing existing files can be easy or extremely time-consuming. Older applications will require greater efforts. For instance, your application’s database might still contain program-described files (remember them from the old days?) that you’ll need to map into your database model. Don’t worry too much about them right now—just document their existence and move on.

Besides these ancient files, you might have some other peculiarities in your environment, which you’ll need to document. These oddities might include the following:

  • “Ghost files”—These are empty shells. They only exist to be used as a base for a temporary file in QTEMP for a program to store data while it’s running.
  • Output-only physical files—These are usually printout-turned-into-file-to-be-exported-to-PC-format files. They are somewhat similar to the previous ones, but they retain their content (the output of a certain program) after the program ends, even though their data has no direct relationship to the rest of the database.
  • Logical files with selections—These files, which are often used as a way to speed up a program’s execution, might present a challenge later in the process, so be sure to locate all of them.
  • Other oddities—Here’s where the knowledge of your specific environment comes in. You or someone on your team should have an idea of what other unusual stuff you have in your database. List everything, even if it doesn’t sound important.

Once you have listed all the files and what they’re used for, you’re ready to move forward.

Figure Out and Map Implicit Relationships Between Files

Again, this depends on the application’s age. I’d say that the probability of the relationships between the files not being in the database itself, but in the programs that maintain the data, increases with the age of the application’s database. It’s true that you can enforce referential integrity via logical files based on more than one physical file, but this is seldom used. You’ll need to map all of those relationships thoroughly because that will help you change your programs later, freeing them of the referential integrity tasks that they perform now.

That’s something to do later. For now, the idea is to convert the DDS files to DDL objects, and nothing else. This too will be a time-consuming and tedious task, but you can make it slightly less boring by drafting your Entity Relationship Diagram at the same time, which will be the topic for the next TechTip.

Stay on Course

At this point, you might be tempted to start drawing your existing database’s physical model, using IBM Data Studio, which I mentioned in the previous TechTip, for instance. Don’t do it! Legacy application databases are often a collection of seemly unrelated flat files, connecting to each other via the RPG programs that use them. There’s so much duplication, garbage, and outdated stuff that you’ll be wasting your precious time drawing a diagram. At this moment, concentrate on what you have to do to modernize other aspects of the database. As I mentioned before, next time around I’ll explain how you can start preparing to organize your database, by defining or refining the definition of a few things so that you can finally implement step 1 of the methodology: convert your files from DDS to DDL.

BLOG COMMENTS POWERED BY DISQUS

LATEST COMMENTS

Support MC Press Online

$

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: