12
Thu, Dec
4 New Articles

Using Binding Directories with Your Service Programs

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

Make compiling easier for service programs with the use of binding directories.

 

With the end of the year comes time to close out my series of articles on service programs. In previous articles, I discussed how to create a service program, followed by discussing the benefits and cautions of using the binding language with your service programs. In this article, I'll discuss how to create binding directories and why you would want to use them.

 

For your reference, here is a complete list of articles in the series:

What Are Binding Directories?

Binding directories contain a list of service programs or modules to bind to your program. Your RPG program can use this directory so that you don't have to specify all of this information when you compile your program.

 

Because the term "binding directory" is similar to "binding language" I immediately assumed that the binding language was the code to generate the binding directory, which is not true. I had a hard time shaking that concept, which was initially a source of confusion for me.

 

To drive the point home, the binding directory and binding language are two completely different things:

 

  • The binding language specifies the interface to the service program and modules. It's associated with the program during compile time and will assume that the interface hasn't changed if the signature associated with the service program remains the same.
  • The binding directory lists all of the service programs to reference from the program and is used by the compiler to validate the existence of the references that you're making.

 

The concept of binding directories is similar to library lists in that they will tell you to look for the service programs in specific locations. The order in which the service programs are listed in your binding directory are meaningful, just as with a library list, because the program will look through the list in the listed order until it finds the reference the compiler is looking for. If you're familiar with Java, this concept is similar to class paths.

Why Use Binding Directories?

As with most things, I'm sure there are multiple reasons why you would want to use binding directories, but my primary reason is simply because they make it a lot easier to compile your programs. To keep your service programs organized, you may have multiple service programs that each provide functionality in different areas. As your service programs become more robust and your main programs start utilizing more service programs, it would become cumbersome to always have to remember and specify each of these service programs during compile time.

 

If you put your service programs into binding directories, then you can specify the binding directory of interest in the H-specs of your RPG program and not have to list them when you're creating the program.

How to Create Binding Directories

It's time for us to dig into some examples to illustrate the use of binding directories. We'll start by creating a binding directory that will contain the service program that has been referenced in the previous three articles (listed in the opening paragraph of this article).

 

In the articles leading to this one, we created a service program called MCPSRVPGM, which contains the htmlEncode and htmlDecode procedures to convert special HTML characters. The logic isn't referenced in this article; instead, we'll focus on the compile process for the program using the service program.

 

We'll name our binding directory MCPBNDDIR and will execute the following command to create our binding directory:

 

CRTBNDDIR BNDDIR(MYLIB/MCPBNDDIR) TEXT('MC Press Binding Directory')

 

When the CRTBNDDIR command is executed, we have an object created of type *BNDDIR that is empty. To add the MCPSRVPGM service program to the binding directory, we could use the command ADDBNDDIRE, which will add a binding directory entry into the binding directory:

 

ADDBNDDIRE BNDDIR(MYLIB/MCPBNDDIR) OBJ((MCPSRVPGM *SRVPGM *IMMED))

 

Or we could work with the binding directory and add the service program interactively using the WRKBNDDIRE command:

 

WRKBNDDIRE BNDDIR(MCPBNDDIR)

 

When you work with the binding directory, you can add a service program with the 1 option. You can also see the list of service programs that already exist within the list.

 

122111Snyder_figure01

Figure 1: WRKBNDDIRE allows you to add service programs and see existing service programs. (Click images to enlarge.)

 

In previous articles, we referenced the service program during compile time as follows:

 

CRTPGM PGM(MyLib/MCP047RPG) BNDSRVPGM(MCPSRVPGM) ACTGRP(*NEW)

 

The previous command doesn't seem too bad, but what if you had a couple of additional service programs called MCPSRV2 and MCPSRV3 that you were also using from your program? Your new compile command would now look like this:

 

CRTPGM PGM(MyLib/MCP047RPG) BNDSRVPGM(MCPSRVPGM MCPSRV2 MCPSRV3) ACTGRP(*NEW)

 

You can see that the CRTPGM command is now becoming longer, and it would also become difficult to keep track of what service programs to include. If we were to put all the service programs to be used into a binding directory, we could reference the binding directory during the compile, so we'd be specifying only one reference to multiple service programs during the compile as follows:

 

CRTPGM PGM(MyLib/MCP047RPG) BNDDIR(MCPBNDDIR) ACTGRP(*NEW)

 

But we could take it a step further by specifying the binding directory in the H-specs of the RPG source as follows:

 

H BNDDIR('MDCBNDDIR') DFTACTGRP(*NO) ACTGRP(*NEW)

 

And now our compile could look like this:

 

CRTPGM PGM(MyLib/MCP047RPG)

 

And that's not all. Because we no longer need to specify the service program or binding directory, we could revert back to the good old CRTBNDRPG command:

 

CRTBNDRPG PGM(MyLib/MCP047RPG) SRCFILE(MyLib/QRPGSRC)

 

By using CRTBNDRPG you can eliminate the two-step process of creating the module and then creating the program. 

Coming Full Circle

As we started discussing service programs and the binder language, the process of compiling the programs seemed to become more and more complicated with new commands to learn and more things to remember during compile time. But, with binding directories, you can eliminate all of that and even revert back to the good old CRTBNDRPG command to create your programs because all of the details are handled within your RPG program itself. So set it in the H-specs and forget it!

Giving a Shout-Out

I have to give a shout-out to my boss, Mr. James B. Staton, for introducing me to most of the topics in this series. I was struggling with maintaining service programs without the binding language and binding directories for the longest time, and I'm very appreciative for these newfound capabilities.

 

I started out with service programs with the sole purpose of coding modularity, and once I had what I needed, I drew my line in the sand to begin producing results. But, thanks to Jim, I was pushed a few steps over that line to provide the complete solution with capability and ease of maintainability.

Merry Christmas and Happy New Year

I thank you for reading my articles and making them as popular as they are. And I wish you a Merry Christmas or Happy Hanukkah, Kwanzaa, or Festivus—essentially, Happy Holidays however you celebrate the season!

 

And now you can start off the New Year with a fresh perspective on your coding style with service programs!

 

122111Snyde_figure02

 

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: