03
Thu, Oct
2 New Articles

Practical RPG: New RPG Features

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

With the speed IBM has been adding features, it's a good idea to get a recap once in a while.

If you've been following my recent articles, you probably noticed I've been bouncing back and forth between RPG programming and SQL programming. My last article spent a lot of time on SQL. This one will focus on RPG. Specifically, I'd like to discuss a couple of the more-beneficial new features introduced into RPG ILE over the past few releases.

Something Old and Something New

If OS releases were specified only as VxRyMz the last time you looked at the RPG manual, you’ll be happy to know that a lot of great new features have been added to the language. Many of these features have been around for a while, but if, like me, you didn't know about them, then they're new to you!

In fact, I'm going to start with an update on my recent timestamps article. By default, a timestamp is defined as CCYY-MM-DD.HH.MM.SS.mmmmmm, where that last "mmmmmm" section represents the microseconds of the timestamp. If you've done much work with timestamps, you'll know that, even though the default is six digits of precision as shown above, RPG populates the value to only three positions (representing milliseconds). Because of this, whenever you looked at the character representation, you'd see values ending in something like "12.32.45.667000", where the last three digits were always zero. I've written a lot of lines of RPG code trimming or padding those character values.

A feature introduced in version 7.2 allows you to specify the "precision" of the timestamp. Specifically, it allows you to specify the number of digits of precision for the seconds portion of the timestamp. There's no way to change the precision of the %timestamp BIF itself, but you can at least change the precision of the variable so that you don't get those extra zeros. Here's a little program that will demonstrate how the timestamp precision works.

      dcl-s ts timestamp inz(*sys);

     dcl-s ts3 timestamp(3) inz(*sys);

     dcl-s ts0 timestamp(0) inz(*sys);

     dsply ('TS : ' + %char(ts));

     dsply ('TS3: ' + %char(ts3));

     dsply ('TS0: ' + %char(ts0));

     *inlr = *on;

      return;  

Compile and run this program and you'll see the following:

DSPLY TS : 2018-07-09-20.22.32.810000

DSPLY TS3: 2018-07-09-20.22.32.810

DSPLY TS0: 2018-07-09-20.22.32    

Each line shows the character representation of the timestamp. The first is the default; you'll note that it shows six digits of precision in the seconds, which leads you to believe you're seeing microseconds but, as mentioned above, only the first three digits are actually populated. The extra zeros are meaningless. The more accurate version is TS3, which has explicitly defined three positions of decimal precision, and the character representation shows it. If you need milliseconds, this is the way to define your timestamp. The last version is the one I particularly like, using a zero for precision. The character version of this variant doesn't show any fractional seconds and instead is just a standard CCYYMMDDHHMMSS, albeit with slightly unusual punctuation.

Better Support for Long Names in Record-Level Access

As soon as you get a chance to use SQL's CREATE TABLE to define a database table, you are almost immediately going to want to use longer, more descriptive names. In fact, you'll want to be careful that you don't get fieldname-itis (inflammation of the field name) in which you end up with field names like BusinessUnitLevelAccountNumberingMethod. Not that there's anything wrong with that, but there's something to be said for conciseness even when not required.

But regardless of the verbosity of your field names, if they get longer than 10 characters, then you're going to run into a problem; RPG won't like them. Now, if all of your access is via SQL statements, it's not a problem. The length of your field names is not an issue, because you'll be defining the variables in your program name to receive the values from your SQL SELECT statement and you don't have any limitations. But if you want to access your SQL-defined table via a traditional file specification (whether it's a fixed-format F-spec or a free-format DCL-F), then you have an issue. Native file specification by default uses only the short version of the field name.

Now, you may be saying to yourself that you didn't specify any short field names (this, by the way, is done using the FOR clause in DB2). Well, fear not! DB2 makes up its own short field names for you by combining the first five characters of the long field name with a five-digit numeric value to retain uniqueness. For example, the first field above would be BUSIN00001. Another field named BusinessUnit would then be BUSIN00002 and BusingCompany would be BUSIN00003. Without any additional intervention, your RPG program would be forced to use those even-more-cryptic-than-usual field names.

The latest version of the compiler allows you to specify the ALIAS keyword on the file specification to tell it to ignore the short names and use all long names. This again isn't exactly new; the ALIAS keyword was available, but you could use it only if you also specified QUALIFIED on the same file specification. This in turn required you to do all your I/O operations using data structures. That's not necessarily a bad thing, but if all you want to do is CHAIN to a file and use the contents of a field, a data structure can feel like overkill. Anyway, let's take a look at what I might do. Let's assume that the file is simple and has only two fields: BusinessUnit and BusinessUnitLevel. You want to chain to this file to get the level of the business unit.

In one SQL statement, you create the table; in a second, you create an index over the table.

exec sql create table MYLIB/BUSUNITS (                

BusinessUnit char(10) not null with default,          

BusinessUnitLevel decimal(3,0) not null with default);

                                                        

exec sql create index MYLIB/BUSUNITSI1                

on MYLIB/BUSUNITS (BusinessUnit);                    

Now you effectively have a physical file and a logical file: BUSUNITS and BUSUNITSI1. Please note that you haven't specified any short names, so the default IBM i behavior when looking at this file is to use the short field names BUSIN00001 and BUSIN00002. Not too long ago, that would have been the only way RPG could access those fields, but now it's very easy to use the long names. Behold:

ctl-opt actgrp(*new) option(*srcstmt:*nodebugio);

                                                

dcl-f BUSUNITSI1 alias keyed;                    

                                                

dcl-pi *n;                                      

iUnit like(BusinessUnit);                      

end-pi;                                          

                                                

chain (iUnit) BUSUNITSI1;                        

dsply %char(BusinessUnitLevel);                  

                                                

*inlr = *on;                                    

return;                                          

As you can see, just adding the ALIAS keyword to the BUSUNITSI1 specification means that you can use the long field name within your program. I define my input parameter as being LIKE the key field from the file (BusinessUnit), and then I work with the data field (BusinessUnitLevel). That's all it takes!

Two for the Price of One

Hopefully either or both of these two unrelated but very nifty compiler features can help you address other business issues (since that's why we're here, right?). Have fun with them both!

Joe Pluta

Joe Pluta is the founder and chief architect of Pluta Brothers Design, Inc. He has been extending the IBM midrange since the days of the IBM System/3. Joe uses WebSphere extensively, especially as the base for PSC/400, the only product that can move your legacy systems to the Web using simple green-screen commands. He has written several books, including Developing Web 2.0 Applications with EGL for IBM i, E-Deployment: The Fastest Path to the Web, Eclipse: Step by Step, and WDSC: Step by Step. Joe performs onsite mentoring and speaks at user groups around the country. You can reach him at This email address is being protected from spambots. You need JavaScript enabled to view it..


MC Press books written by Joe Pluta available now on the MC Press Bookstore.

Developing Web 2.0 Applications with EGL for IBM i Developing Web 2.0 Applications with EGL for IBM i
Joe Pluta introduces you to EGL Rich UI and IBM’s Rational Developer for the IBM i platform.
List Price $39.95

Now On Sale

WDSC: Step by Step WDSC: Step by Step
Discover incredibly powerful WDSC with this easy-to-understand yet thorough introduction.
List Price $74.95

Now On Sale

Eclipse: Step by Step Eclipse: Step by Step
Quickly get up to speed and productivity using Eclipse.
List Price $59.00

Now On Sale

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: