February 7, 2018
- LEAD ARTICLE: Practical RPG: NULLs in DDS-Defined Files
- FEATURED ARTICLE: Gifts You Can Give the IBM i Community
- FEATURED ARTICLE: Make Your IBM i Database More User-Friendly
- NEWS HIGHLIGHT: New RPG & DB2 Summit Sessions Help IBM i Developers Achieve Big Goals
- WHITE PAPER: Node.js for Enterprise IBM i Modernization
- FEATURED VIDEO: Design an Invoice in 10 Minutes
- EVENT: TOMORROW - Powerful Cloud Strategies for IBM i CustomersPowerful Cloud Strategies for IBM i Customers
- MC PRESS MAGAZINE: A Small Intro to Big Data, Part 3: HFDS and the MapReduce Algorithm
DDL-defined tables are very good about handling null values, but sometimes we still need to deal with them in DDS-defined files as well; this article shows the RPG techniques required to do that.
By Joe Pluta
When you create a table in SQL using DDL statements, the default is to allow nulls, which means that, for any row, you can populate the column with a null value. Nulls have a number of specific characteristics; you can read about them here. We won't go into those issues in detail, although they can be quite interesting. The issue of nulls in WHERE clauses is particularly fascinating but not relevant to our discussion. Instead, today we're going to see how to support null result values in more-traditional RPG and DDS settings.
This year, why not give a gift to others and contribute to the IBM i community?
By Brian May
It has been quite a while since I wrote about favorite gifts from IBM. A little over a year ago, I wrote gifts to give yourself. Now, in true trilogy form, because the best things come in threes, I am writing the last article in the gifts series. I guess that means I will need a new themed series.
Live Webinar: Make Modern Apps You'll Love with
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.
Here's how to create descriptive table and column names that make DB2 for i easier for end users to navigate
by Rafael Victoria-Pereira
Editor's note: This article is excerpted from chapter 4 of SQL for IBM i: A Database Modernization Guide, by Rafael Victoria-Pereira.
Chapter 3 led us on the first step toward a true database, but it kept most of the hallmarks that make a DB2/400 database very "user-unfriendly": the table and column names are short, in the typical and old-fashioned way of the AS/400. However, end users' demands in regard to data queries have evolved significantly in recent years. The users of our UMADB are particularly data-hungry and are overtaxing the university's IT staff labor resources. This added burden on the IT staff is something that often occurs when you "open up" the database to the end users. The problem is that the database is not always ready to be used by someone not used to short, cryptic names, and this ends up causing additional stress on the IT staff, because it requires additional time…