02
Sat, Nov
2 New Articles

Practical ILE: Building Your Service Program Library, Part 3

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

In our final step, we connect application programs to the new service programs via binding.

 

It's funny sometimes how the computer world goes in cycles. It seems ages ago that we wrote source code, compiled it into object code, and then linked the pieces together. We left that behind for all-in-one compilers, but in today's brave new world of interoperable ILE languages, we've revived the whole concept and now we have to once again think about linking. In current parlance, the concept is known as "binding," and this last article in our series will show you how to manage it.

Quick Recap

This series wasn't a how-to on creating service programs, but more of an application-level view of how to add service programs to your infrastructure. Part 1 addressed how to group your business functions into service programs, while Part 2 talked about using prototypes to tell your programs what the service program procedures look like. We finish off now with a discussion about binding your service programs to your applications.

Creating a Service Program

Remember that a service program is a collection of procedures. If you had only one procedure, you could theoretically just use an old-fashioned bound RPGLE program with a traditional parameter list (PLIST) and be done with it. And in fact, for many parts of your architecture, that old technique is still the best. I find it especially useful in the overall application architecture when I'm separating user interface from business logic. If the business logic is pretty much standalone, there isn't much use for a service program.

 

Creating a service program has two steps: compiling the module and creating the service program. Creating the service program is only a little more complicated than creating a bound program. You create a module rather than a program. In ILE RPG, that means using the CRTRPGMOD command rather than CRTBNDRPG (option 15 rather than option 14 on PDM). This step creates an object of type of *MODULE rather than*PGM. The extra step is the CRTSRVPGM command, which takes the *MODULE object and turns it into a *SRVPGM.

 

I hear you out there shouting at your screen, "But we can include multiple modules in a single service program!" Yes, you can. But the focus of this article is ease of programming, and for that I find that starting out with a single module per service program works easiest. Remember, that single module can have dozens of procedures, so it's not like you're creating one service program per procedure. But no less authoritative a source than Jon Paris and Susan Gantner recommend combining multiple modules into a single service program, so in another conversation we can talk about that.

 

As I said, I want to use the simplest technique possible. That's why I use a mostly vanilla CRTSRVPGM command; I only override the TEXT parameter to grab the text from the module. Although there's no magic parameter setting to use the module text, I set up a custom option in both Rational and PDM to execute the following command:

 

CRTSRVPGM SRVPGM(&N) TEXT(&T)

 

That grabs the text from the source and puts it into the service program. That's one of the reasons I like the approach of one module per service program. Let me now expand the command to show you the implied values for a couple of the other keywords:

 

CRTSRVPGM SRVPGM(&N) MODULE(*SRVPGM) EXPORT(*SRCFILE)
         SRCFILE(QSRVSRC) SRCMBR(*SRVPGM) TEXT(&T)

 

The MODULE(*SRVPGM) keyword tells the binder to use only the one module with the same name as the service program. EXPORT (*SRCFILE) says we're going to use binder source rather than just exporting all the procedures. The SRCFILE and SRCMBR parameters say where to get the binder source. The alternative is just to export all the procedures and not use any source. You actually do that when you're first creating a service program, but that's a different discussion for a different day. Right now, we assume you have a binder source because that allows you to control the signature, which is critical to the proper management of service programs. By default, signatures change only when a procedure is added or removed, or the order of the exports changes. In reality, adding a procedure really shouldn't change the signature, while at times you may not add a procedure but you still want the calling programs to be recompiled. Binder source allows you to control that process.

Binding to the Application Program

Now that the service program is properly created, it's time to bind it to the application. Remember that the program included a copybook to define the prototype for the service program procedures. However, this doesn't tell the compiler where those procedures can be found, and normally, if we attempt to compile the program with nothing but the copybook, we will get an error that some references could not be resolved. We address that by pointing to a service program.

 

Pointing to the service program is easy, but it takes a couple of steps. First is to create the object that the compiler uses to find the service program. That's the binding directory, and creating it is as easy as executing the CRTBNDDIR command. Next, the WRKBNDDIRE command allows you to interactively manage your binding directory, adding and removing service programs as needed. Finally, add the binding directory to your RPG program using the BNDDIR keyword on the H-spec (or ctl-opt, for you free-form folks!).

 

It's that easy! However, like many things about ILE, getting something to work isn't the hard part; creating a framework that allows you to easily manage your development and expand your application infrastructure is much more difficult. And the difficulty isn't because it's hard to do; the difficulty is that it's so easy to do in so many different ways.

 

In particular, with binding directories you run into a corollary of the question of how many modules to put into a service program. You can have as many modules as you want in a service program, and you can have as many service programs as you want in a binding directory. It's entirely up to you how to arrange and manage your environment. Personally, I like to have one primary binding directory for all applications, and have specific binding directories only for those procedures that I don't want regular applications to access. An example might be an internal security interface; only internal functions should access those procedures, so I keep them in a completely separate binding directory.

 

Another issue comes into play when compiling service programs that reference other service programs. You may find yourself creating binding directories specific to compiling in order to prevent duplicate references. It's even more difficult when you have circular references in which two service programs call procedures from each other (this is an indirect argument in favor of the "one big service program" design, but that's not for everyone).

 

How you group your service programs and binding directories is ultimately up to you, but however you choose to arrange them, it's important that you have a plan ahead of time. One of the hardest things in the world is to change your framework in midstream. Hopefully, this series of articles has given you a foundation to work from in building your own service program infrastructure.

 

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: