BLOG

Insights / Blog

IBM Bob for IBM i: I Went Into the Demo for My Customer. I Left Pretty Impressed.

IBM Bob is built for IBM i, and it held up in a live demo better than this infrastructure guy expected.
Written By

I’ll be the first to admit that when IBM started talking about Bob, I wasn’t paying a whole lot of attention. 

It’s not that I didn’t think it was interesting. It’s just that I’m an infrastructure guy. I spend most of my days talking about IBM Power Systems, storage, operating system upgrades, availability, disaster recovery, and keeping IBM i environments running. Application development isn’t really my wheelhouse, so when IBM started introducing Bob and talking about AI-assisted development, it wasn’t something I was spending much time looking into.

Recently, one of our customers expressed interest in learning more about IBM Bob and the Premium Package for IBM i. I arranged a meeting with Tim Rowe from IBM to walk through the product and provide a live demonstration. Special thanks to Tim for taking time out of his busy day.  Ultimately I figured I’d sit in, learn a little something, and help answer any infrastructure-related questions that came up.

I walked away a lot more impressed than I expected.

Tim Rowe Might Be a Terrible Speller. Or Maybe He Was Doing It on Purpose.

One of the things that impressed me the most during the demonstration was how well Bob handled imperfect information.

As Tim was walking through different examples, he was asking Bob questions about objects and libraries in the IBM i environment. Now, I don’t know if Tim was intentionally misspelling library names to demonstrate Bob’s capabilities, or if he’s just a terrible typer. I’ll have to ask him next time.

But he was entering library names that weren’t spelled correctly, and Bob didn’t seem to care. It was able to figure out what Tim was asking, identify the correct library, and return the information he was looking for remarkably quickly.

That might not sound like a big deal at first, but think about how we traditionally interact with IBM i. We’re accustomed to exact names, specific commands, and knowing precisely where to look for information. Get a library name wrong, reference the wrong object, or use the wrong syntax, and you’re probably not getting very far.

Watching Bob work through those mistakes and still deliver the information Tim was looking for was pretty impressive. It was one of those moments where I started thinking about how useful this technology could be outside of application development.

And that’s really what got my attention.

What Could Bob Mean for IBM i Administrators?

IBM i is an incredibly capable operating system, but there’s no denying that administering it requires specialized knowledge. Experienced administrators know where to look, which commands to run, and how to interpret the results. They’ve spent years learning the ins and outs of the platform, and much of that knowledge comes from experience rather than something you can easily find in a manual.

But what happens when those administrators retire? Or when an organization has a small IT team where IBM i is only one of several platforms they’re responsible for?

This is where I think Bob could become particularly interesting.

Imagine being able to ask your IBM i environment questions in plain English instead of having to remember the exact command or navigate through multiple screens. Maybe you’re trying to understand how much storage is being consumed by a particular library, identify which jobs are consuming resources, review system messages, or gather information about installed software and PTF levels.

Traditionally, getting that information might involve running several commands, writing SQL queries, or knowing exactly which IBM i services to use. For an experienced administrator, that might not be a big deal. But for someone who doesn’t spend every day working on IBM i, it can take considerably more time.

With the Premium Package for IBM i, Bob has the ability to work with IBM i-specific tools and services, opening the door to retrieving system information and helping administrators work through these types of questions more efficiently.

I’m also interested in what this could mean for reporting and routine administrative work. IBM i has a tremendous amount of information available through its SQL services, but you still need to know where to look and how to retrieve it. Being able to describe what you’re looking for and have Bob help build the appropriate queries could save administrators a significant amount of time.

There are also opportunities to use Bob to help develop CL programs, SQL scripts, and other administrative tools. I don’t see this replacing experienced IBM i administrators, but I can certainly see it making them more productive. It could also make life easier for organizations that don’t have a deep bench of IBM i expertise.

Of course, some of these capabilities will depend on how Bob is configured, which tools are available, and what permissions have been granted. I wouldn’t assume every administrative task is available right out of the box. But after watching the demo, I think there’s enough potential here that IBM i administrators should be paying attention.

The Security Conversation Was Just as Interesting

One of the things I appreciated about this particular customer meeting was that they weren’t just interested in what Bob could do. They were equally interested in what Bob *shouldn’t* be allowed to do.

And that’s exactly the right question to ask.

If you’re going to introduce an AI assistant that can interact with your IBM i environment, you need to understand how security is enforced. The customer raised concerns about users potentially accessing information through Bob that they wouldn’t otherwise have permission to access directly on IBM i.

For example, if an employee doesn’t have authority to a particular library, file, or set of business records, could they simply ask Bob to retrieve that information? Could someone in one department use Bob to access information that should only be available to another department?

Those are legitimate concerns, especially when you consider how much sensitive business information resides on IBM i systems.

It took us a little while to work through the conversation, but ultimately we got to an important point. **Bob can work within the security framework that’s already built into IBM i, provided the integration is configured correctly.**

One of the things I’ve always appreciated about IBM i is how granular its security can be. You can control access through user profiles, group profiles, object authorities, and authorization lists. You can also take advantage of Db2 for i row and column access controls to restrict which records or fields a particular user is allowed to see.

For example, you might have an employee who needs access to customer information but shouldn’t be able to see certain financial details. Or perhaps you have users who should only be able to access records associated with their particular department or business unit. IBM i gives you the tools to enforce those restrictions.

The important thing we discussed during the demo was that when Bob communicates with IBM i through the appropriate interfaces and user authorities, those existing security controls can continue to be enforced. Bob doesn’t inherently need to bypass the security you’ve already established just because someone is asking a question in plain English.

There is an important distinction here, though. Organizations need to understand exactly how Bob is connecting to IBM i and which credentials are being used to execute requests. If everyone is accessing the system through a highly privileged service account, that creates a very different security situation than having requests execute under the appropriate user’s authority. Access to information collected or indexed by Bob also needs to be considered separately.

These are things that need to be reviewed and tested before introducing the technology into a production environment.

I was encouraged by the discussion because IBM i already has a mature security architecture. We shouldn’t have to throw that architecture away to take advantage of AI. We just need to make sure the technology is implemented in a way that respects the security controls already in place.

I Walked Away With a Different Perspective

I went into this meeting thinking IBM Bob was primarily a development tool, and to be fair, application development is still a major part of the story. There’s clearly a lot of value in helping developers understand existing RPG applications, modernize code, and accelerate development.

But that’s not what stuck with me after the meeting.

I kept thinking about the possibilities for IBM i administration, how much time could be saved gathering information, and how much easier it could become for people to interact with an operating system that has traditionally required a fair amount of specialized knowledge.

The way Bob handled Tim’s misspelled library names might have been a small part of the overall demonstration, but it was probably the moment that impressed me the most. It was a simple example of how AI could make interacting with IBM i a little more intuitive.

I also appreciated that the customer pushed hard on the security questions. It’s easy to get excited about what AI can do, but when you’re talking about systems that run critical business applications, you need to be just as focused on how that technology is controlled and secured.

I’m certainly not going to pretend to be an IBM Bob expert after sitting through one demo. I still have plenty to learn about the product, its capabilities, and where it makes the most sense for customers.

But I will say that IBM has my attention.

I went into that meeting as an infrastructure guy who wasn’t particularly focused on Bob. I left genuinely impressed with what I saw, and I’m looking forward to spending more time understanding what it could mean for the IBM i environments we support.

If you’ve been looking at IBM Bob strictly as a development tool, it might be worth taking another look. I think there’s a lot more to the story, especially for those of us responsible for keeping IBM i environments running.

Share This Post
Written By

Have a question about your IBM i environment?

If something you read here sparked a question, our team is happy to talk it through. No sales script, just a conversation with people who know the platform.