24
Mon, Jun
3 New Articles

The Perils of Activation Groups Gone Awry

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

Controversy surrounds the use of service programs in the default activation group, and this article explains a very specific and painful reason to avoid it.

 

You've probably heard that programs written for the Integrated Language Environment (ILE) don't work and play well with legacy programs written using the Old Program Model (OPM). And if you're like me, you've probably tried them together to see what would happen. This isn't something we do cavalierly; instead, it's usually in response to the needs of a real-world production development environment. You want to introduce new techniques, but you can't justify rewriting existing code just for the sake of moving it to ILE. So you end up with a mixed environment, and for the most part it works just fine. Until it breaks. Badly. This article details a very specific, very painful problem and hopefully gives you another reason to try moving those programs to ILE.

Building a Failure, One Step at a Time

The specific problem I encountered was the result of a cascade of issues. It started out simply enough: I wanted to use a CLOB in some programs. As it turned out, the routines to access the CLOB lent themselves very well to a service program, so I wrote one and began using it in lots of places. That was the first design decision in a chain of decisions that would eventually lead to a very painful system failure.

 

The second decision had to do with activation groups (AGs). I am a big proponent of *NEW and *CALLER activation groups. I know many of our esteemed colleagues in the industry like named AGs, and given the problem I'm about to describe, that may seem like a better approach. I, however, appreciate the self-cleaning nature of a *NEW AG, so that's what I chose. By doing that, it means your top-level program has *NEW as its AG, and all your supporting code pieces, whether they're in programs or service programs, use *CALLER. Specifically, I put the service program into the *CALLER AG and moved on to the next step.

 

The next step was the one that we all face: I wanted to use the service program in a legacy job stream. The high-level program is an old-fashioned CL, most of the programs in the stream are OPM programs compiled into the default activation group (DAG), and none of that is going to change anytime soon. I'm simply adding a call to the service program. The problem is this: one of the OPM programs calls an ILE program. The ILE program in turn calls the service program. This in fact has to be the case; programs compiled for the DAG cannot call service program procedures. And here's where AGs, specifically *CALLER AGs, get you in trouble.

 

The ILE program is called hundreds of times for a transaction, so it was compiled with activation group *CALLER. This means it runs in the DAG when called by an OPM program. To date, this has not been a problem, and the program has been tested extensively. It has in fact been in production for nearly five years. So despite all the warnings, nothing bad has happened…yet. But as it turns out, badness was waiting to happen.

 

The final step in building my house of cards was to add a new procedure to the service program. The procedure used an F-spec. The idea was again that this procedure would be called many times, so I took advantage of the USROPN and STATIC keywords to leave the file open between calls. This worked fantastically! I tested the system thoroughly and was able to put everything through its paces. Legacy jobs were submitted that used the system, and they ran to completion successfully. I tested all the interactive jobs, and everything ran smoothly. There really wasn't anything else to do, so we put the new programs into production.

The Phones Start Ringing

Yes indeed, within the hour the phones began to ring. Standard jobs were failing with a very nasty and cryptic error. The errors started with MCH3402 "Tried to refer to all or part of an object that no longer exists." It went on from there through several errors, finally failing with CEE9901 and ending the user's day rather unhappily. The real kicker was that none of the errors gave me a statement number in any of my programs. All the messages were going to system programs like QLEAWI and QRNXIO, so there was no way to even tell which statement was failing. It was a mess.

 

Even more disturbing was that the problem didn't affect everyone! Most of the users were working along with no problems whatsoever. It was only the power users that were having this problem. And of course, the power users are the ones most affected by system problems. We walked through exactly the steps they executed, and we couldn't cause the failure. We tested on multiple machines, in multiple environments, but nothing went wrong. We had them sign off and sign back on, and the problem went away…for a while. Eventually they'd call back and their workstation would be down again.

 

And then finally I got it to fail in test.

RCLRSC Ate My Program

The way I made the system fail was to call a menu option twice. The second time failed with the strange error. Remember, there was no HLL statement number on any of the error messages, so I didn't know which program was failing, or where. At a loss, I finally just did a STRDBG with no program and then made the problem reoccur. And lo and behold, the debug window popped up with the cursor on the ENDPGM statement of the CL. This was quite interesting; I'd never seen an ENDPGM statement fail before. But something caught my eye.

 

For historical reasons, this particular CL program did a RCLRSC just before the ENDPGM statement. Suddenly I started recalling stories and anecdotes from the early days of ILE in which RCLRSC was supposed to be bad to use with ILE and service programs in particular. After the fact, I did some more searching on the Internet and, with the right keywords, I ran across a couple of conversations explaining the problem in more detail. I fixed the problem by taking the RCLRSC out of the CL. And everything ran fine.

 

For a while.

 

Within a few hours, after assuring everyone we'd gotten to the bottom of the problem, it cropped up again. Tearing my hair out, I looked at the caller's joblog and realized something. While he was calling the menu option, he hit a command key that called a different CL that unfortunately also had one of those historical RCLRSC statements. As it turns out, any RCLRSC would cause the service program procedure with the F-spec to crash spectacularly.

 

The final answer was to change the original ILE program to use *NEW as its AG rather than *CALLER. We haven't noticed a significant performance hit yet, and I'll do some timings on it when I get some free time. We'll also have to review our position on activation groups, OPM programs, and RCLRSC to see what steps we need to take to avoid future occurrences of the issue. It's a good discussion to have, and unfortunately sometimes it takes this sort of problem to make it occur.

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

$0.00 Raised:
$

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: