November 1, 2017
- LEAD ARTICLE: Practical RPG: APIs, Part 2 - Changing Objects Using the QLICOBJD API
- FEATURED ARTICLE: RPG Academy: Debug Done Right - Working with Watch Conditions
- FEATURED ARTICLE: How MVC Can Simplify and Modernize Your IBM i Applications
- NEWS HIGHLIGHT: IBM Board Approves Quarterly Cash Dividend; Authorizes $3 Billion For Stock Repurchase
- WEBCAST: IBM i Resources Retiring?
- FEATURED VIDEO: Design an Invoice in 10 Minutes
- EVENT: NGS-IQ - Advanced Functionality for Every Twist and Turn Your Queries Need to Take
- MC PRESS MAGAZINE: A Small Intro to Big Data, Part 3: HFDS and the MapReduce Algorithm
APIs are one of the most powerful tools provided by the IBM i; here is a practical example of using one.
By Joe Pluta
In my previous article, I explained the basics of error reporting when calling APIs. This next installment brings those basics into focus with a real-world illustration that you can experiment with on your own and also use as a practical addition to your development environment.
Knowing your way around a debug source and knowing how to set and remove breakpoints is very important, but sometimes you need more than that. That’s where watch conditions come into play.
By Rafael Victória-Pereira
You use a watch condition to monitor whether the current value of an expression or a variable changes while your program runs. Setting watch conditions is similar to setting conditional breakpoints, with one important difference: Watch conditions stop the execution of the program as soon as the value of a watched expression or variable changes from its current value, regardless of the place in the code where that change occurs. Conditional breakpoints, on the other hand, stop the program only if the variable has the value specified in the breakpoint condition when the execution reaches the line where the breakpoint was set. In other words, a watch condition monitors the value of the variable globally, while the breakpoint simply checks whether a certain condition is met before the execution of a given line of code.
After surveying 500+ IBM i professionals, we discovered:
- The state of IBM i modernization in today's businesses and their goals for the future
- The effect legacy applications have on the businesses' internal and external processes
- The #1 concern upper managers have with the IBM i, and how to combat it
...and much much more!
Download your copy of The 2017 State of IBM i Modernization today.
1. Affordable Cloud Solutions
2. Efficiencies of MIMIX
3. Rising Cost of Downtime
This collaborative effort from Connectria Hostingand Vision Solutions will provide a review of the core causes and costs of both planned and unplanned downtime and will then provide a detailed discussion of current options for IBM i High Availability and Disaster Recovery in the Cloud.
Most importantly, as you read you will learn why true HA and DR protection are now within reach of even the smallest of businesses.
It's time to make your apps proud to be seen! Whether you have green screens or a drab GUI, your outdated apps can benefit from modern source code, modern GUIs, and modern tools. Alex Roytman and Liam Allan show you how Free-format RPG and Node.js make it possible to deliver apps your business will love.
You'll learn how you can use both Profound UI and Profound.js to: Transform legacy RPG code to modern free-format RPG and Node.js; Deliver truly modern application interfaces with Profound UI; Extend your RPG applications to include Web Services and NPM packages with Node.js.
High availability for IBM i has been a hot topic in 2017, becoming the #2 IT priority just behind cybersecurity. And no surprise with these two topics so closely tied to your most valuable asset: your irreplaceable business data. You must be asking yourself: am I doing everything I can to protect my organization's data? Tune in as our panel of IBM i high availability experts deliver lively discussion around the top high availability issues of today.
Once data is gone, it's gone...unless you have a data replication layer in place to protect it. Learn the value of strategic solutions and how to implement them in a hurry...watch now!
ACO MONITOR is a complete systems management solution for your Power Systems running IBM i. ACO MONITOR manages your Power System 24/7, uses advanced technology (like two-way messaging) to notify on-duty support personnel, and responds to complex problems before they reach critical status.
ACO MONITOR is proven technology and is capable of processing thousands of mission-critical events daily. The software is pre-configured, easy to install, scalable, and greatly improves data center (and staff) efficiency.
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. Why support 5 different products, when you can do it all with MarkMagic?
Want to make your big ol’ RPG programs more modular and easier to maintain? Then give the MVC design pattern a try.
by David Shirey
Editor’s note: This article is excerpted from chapter 24 of 21st Century RPG: /Free, ILE, and MVC.
Model-View-Controller (MVC) is a design pattern. Unlike many of the design patterns that have been defined, it is not uniquely oriented to object-oriented (OO) programming, but can easily be used with procedural languages as well.