Simplify IBM i Application Development with Smarter Productivity Tools
Developing applications for your business environment can be a rewarding, if sometimes thankless, task. The tools you help create and maintain make up the foundations of an agile organization. But the blistering pace at which projects and personnel grow and change somehow manage to slow you down.
This report shows you how smarter productivity tools can get your team up to speed. Automated cross-reference and documentation features improve your perspective, reduce redundancy, and satisfy auditors.
WebSphere MQ is IBM's flagship product for providing reliable inter-platform messaging, and accessing MQ from RPG is easy once you understand the techniques.
Written by Joe Pluta
I have a hard time with the rebranding of IBM's MQSeries to WebSphere MQ; it's always seemed to me to be one of the more random renamings. MQSeries had great brand recognition as it was. But regardless of the name, MQ has always provided a powerful queuing architecture, and I guess a rose by any name holds true here. The purpose of this article is not to bemoan the naming but to introduce the architecture to RPG programmers.
Learn critical cleanup techniques that target end-of-job due to end job commands.
Written by Junlei Li
Author's note: This article is one of a series of articles to memorialize Simon Coulter, an outstanding IBM i expert who contributed much to the prosperity of the IBM i platform. I thank Gwen Hanna, Simon's partner, for providing the biography of Simon at the end of the first article of "Simon's Solutions."
As one the most robust operating systems and application systems in the world, IBM i provides numerous mechanisms to automatically reclaim resources occupied by resource containers, such as activation groups (ACTGRPs) or jobs that end unexpectedly. However, it's still possible for resources to be left as orphans by a job that ends unexpectedly—for example, a pointer-based mutex created by the job with the keep-valid option set to true, or a permanent MI object created without inserting its addressability into a context object (library). It's also bad that an unexpected end-of-job might damage the integrity of application data.