TechChannel Rising Star recipient, Megan Olson took part in a roundtable discussion to share her experience as a newcomer to the IBM i industry.

PCI DSS now includes requirements for strong encryption of cardholder data. Learn how key management is an essential element of preventing unauthorized data access.

As you consider taking your IBM i to the cloud, cybersecurity will no doubt top your list of concerns. And for good reason. It’s important to remember that the cloud is kind of a lie. Your sensitive data is simply being sent to someone else’s server, and that server has a physical location somewhere. Just like on-prem cybersecurity, IBM i cloud security can be divided into two parts: Regulatory...

Typically, there are two main issues with monitoring a system manually: having to go out deliberately (and repeatedly) and check to see if something has happened; and the fact that you are most likely looking for the proverbial needle in a haystack of logged events.

When it comes to security on IBM Power Servers running IBM i, a common challenge for many organizations is the number of users with too much power. These users can potentially circumvent application controls, override security restrictions for themselves and others, change critical server configuration settings, and even cover their tracks while they do it.

While everyone likes to feel special, we need to be more selective when it comes to data access. As we discussed last month, many users have privileges far beyond their business requirements and simply need to have their access reduced to more reasonable levels.

Ask any security professional which area of IBM i security is most often ignored and chances are that the unanimous response is a chorus of “the Integrated File System.” Although it’s been around since V3R1, the Integrated File System, or IFS, remains a shrouded mystery that represents significant risk to many IBM i organizations.

Let’s face it; system administration remains a largely thankless task. From scheduling jobs to balancing workloads to answering messages in QSYSOPR, administrators and operators work diligently behind the scenes to ensure that IBM i servers are available to run mission-critical applications.

Meet Automate Complete—a suite of products that covers the entire automation spectrum.

See what's new in Automate Schedule 4.0, including the Universal Connector.

Where do you need your enterprise scheduler to run? With Fortra solutions, IBM i and other operating systems like Windows ® , Linux ® , or UNIX ® are all possibilities. Robot Schedule Enterprise is our IBM i-centric solution and the Automate Schedule solution centers on the other platforms.

Despite the server’s incredible security infrastructure, auditing remains primarily a thankless, manual chore. And, let’s face it, any task that’s thankless and manual probably won’t get done.

Your data, your job scheduling tool, your ERP system—they all must work in concert with one another to make your organization as efficient as possible in meeting your customers’ needs as well as your own innovation and production goals.

Is your enterprise job schedule as safe as the rest of your life? The ability to set up alternate reactive paths could be the backup plan you’re looking for.

Whether you’re running Linux on multiple partitions, running multiple operating systems on your Power systems, or running production job streams across those partitions, Automate Schedule can help you manage your workflows on Power servers running Linux.

We explore the evolution of job scheduling and the benefits of the latest stage: service-oriented batch job scheduling.

At its core, event-driven architecture is about reacting to various events on your systems. Event-driven architecture allows you to react to multiple different sources without having to write code for each of those sources