In The Spotlight
Carol discusses the characteristics she’s observed over the years that are indications an organization isn’t taking IBM i security as seriously as it should.
By Carol Woodbury
I’ve seen the entire range of IBM i organizations when it comes to implementing security. There are organizations that have implemented “deny by default” and “least privilege access” postures such that, when I do a penetration test, I have little to no success in attaining access when I shouldn’t. Then there are organizations that are still running at QSECURITY level 20, where all profiles have *ALLOBJ—but at least they’re asking for help and are moving in the right direction. Unfortunately, and to put it bluntly, not all organizations care about IBM i security. Here are the characteristics I’ve observed over the years that indicate to me that an organization isn’t serious about attaining a secure IBM i.
Maybe you don’t want to just use a sub-procedure in your program. Maybe you actually want to write the sub-procedure up as a small program and then call it from another program. Granted, that is not technically a sub-procedure, but we will let that go for the moment and concentrate on the call of one program by another.
By David Shirey
Editor's Note: This article is excerpted from article 8 of 21st Century RPG: /Free, ILE, and MVC, by David Shirey.
Back in the olden days, we would have used a CALL with a PARM list. But the regular, old CALL was not carried over into /Free. It wasn’t efficient enough. And so the new way to call from one program to another is via the CALLP, a prototyped call.
What is a prototyped call? Well, as we have already seen, it is a structured call where the parameters are defined in both the calling and the called program.
SQL goes from flexible to downright magic when you take advantage of prepared statements.
By Joe Pluta
If you’ve followed me over the years, you know that a lot of what I do centers around data analysis. Even as the industry trends toward transferring our data to a data warehouse (or data lake, nowadays), I still spend a lot of time taking existing data and massaging it into actionable business information for my customers. This involves both transactional data and configuration data (what we used to call master data). And even when we do use external data processing of one kind or another, oftentimes our data needs to be reviewed and cleansed before we can export it. For configuration data, one of the biggest issues is to find outliers, and that can be quite the feat.
Large organizations are by no means the only enterprises that could benefit from migrating to a cloud environment. Here’s how smaller organizations can get started.
By John Ghrist
Large enterprises incorporating a cloud environment into their operations usually have enough resources to employ consultants to ensure the hundreds of items on a migration to-do list aren't forgotten. Smaller entities tackling this task may benefit from an overview of first steps they can take on their own.
LATEST COMMENTS
