March 15, 2019
- LEAD ARTICLE: SQL 101: Embedding SQL in RPG Code, Part 2
- FEATURED ARTICLE: How Bad Are Certain IBM i Security Settings? Not So Bad, Pretty Bad, or Really Bad?
- FEATURED ARTICLE: How to Code Selective Prompting in a CL Program
- NEWS HIGHLIGHT: LaserVault Introduces ViTL: Eliminates Costly Manual Processes From IBM i Backups
- WHITE PAPER: 2019 State of IBM i Modernization
- MC VIDEO SHOWCASE: Design an Invoice in 10 Minutes
- EVENT: From Barcode Label to RFID Liberating
Did you know you can use host variables nearly everywhere in an embedded SQL statement? Keep reading to find out more!
By Rafael Victória-Pereira
Last time around, I showed you how to embed SQL code in both fixed- and free-format RPG code. I also demonstrated the functionality provided by host variables, which allow SQL and RPG to exchange information in a simple and easy-to-implement way. Let’s continue that discussion.
I realize that I’ve spent a lot of time explaining best practices and what my recommendations are, but I don’t often explain why some settings aren’t the best.
By Carol Woodbury
Some of my favorite magazines will describe a popular action and then explain why that practice is not so bad, pretty bad, or really bad. Using this method, I’m going to describe how bad certain security settings are.
Explore the main considerations you should be aware of before embarking on a (migration or modernization) project. Take a deeper dive into business motivations and factors that could potentially influence your decision to migrate or modernize your existing IT platform and its risks.
More 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 companyare not aligned with the current IT environment.
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.
Part 1 will teach you what Node.js is, why it's a great option for IBM i shops, and how to take advantage of the ecosystem surrounding Node.
In addition to background information, our Director of Product Development Scott Klement will demonstrate applications that take advantage of the Node Package Manager (npm).
Learn how businesses leverage Low-Code to continue to deliver value through digital transformation. Discover how the power of Low-Code is helping many businesses evolve their supply chain, increase ROI, and achieve more tangible results.
Watch this webcast now.
The 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.
Rerun another report? Never again. Try the Robot Report Management Solution FREE for 30 days.
TRY 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.
Ted Holt explains how to add command prompting code that pauses a CL procedure and waits for the user to enter parameter values
By Ted Holt
Editor’s note: This article is excerpted from chapter 13 of Complete CL: Sixth Edition, by Ted Holt.
Selective prompting is one example of an advanced technique. With selective prompting, you activate the prompter for a command from within a CL procedure. In other words, a CL procedure can contain an instruction that causes the procedure to stop, display the command prompter for a particular command, and wait for the user to enter parameter values and press the Enter key. When the user presses Enter, the CL procedure continues to execute.