If you’re deep into IBM i development and programming, you know how crucial it is to have tools that streamline your workflow without sacrificing reliability. Today, let’s dive into TOBi, the open-source build system designed specifically for IBM i. This tool bridges traditional IBM i practices with modern DevOps, making it easier to manage builds, dependencies, and deployments. I’ll walk you through what TOBi is, why it rocks, how to set it up, and more.

What is TOBi?

TOBi, short for The Object Builder for i, is a free open-source tool that turns your IBM i source code into working objects faster than you can say “legacy system.” It started as BOB (Better Object Builder), but IBM renamed it in 2025 to avoid mix-ups with their AI sidekick – because who wants two Bobs arguing in the office?

Hosted on IBM GitHub under Apache 2.0, it’s powered by GNU Make, the same engine behind zillions of Linux projects. Basically, it lets you do local dev with Git, auto-builds with smarts, and deploys without drama. No more manual grunt work : TOBi handles the heavy lifting.

Why TOBi Rocks for IBM i Devs

Picture this: Your old build process is like reheating leftovers every day, unexciting, wasteful and boring. TOBi? It’s the smart fridge that only cooks what’s fresh.

• Speed: Only rebuilds changed bits. No more compiling the kitchen sink when you just tweaked a spoon.
• Reliability: Spots dependencies like a detective. Change one file? It rebuilds the chain automatically. No more “oops, forgot that” moments.
• Industry Smarts: Uses makefile lingo that’s everywhere else. If you’ve dabbled in Unix, you’ll feel right at home.
• Flexibility: Defaults work great, but tweak compiles like adding hot sauce with custom groups, debug views, whatever.
• Ease: One command or button click builds everything. Like ordering pizza, but for code.

In short, TOBi drags IBM i into the cool kids’ club of DevOps, saving you time and sanity.

Quick Setup

Don’t sweat the install, it’s straightforward. Grab packages like tobi, bash, python3, and pals via yum: yum install tobi bash … (full list in the docs). Or use ACS for a point-and-click adventure.

Configuring Your Project

Three magic files rule the roost:

• iproj.json: Your project’s brain, where it sets libraries, includes, and build commands.
• .ibmi.json: Handles character encoding for compiles.
• .env: Environment vars, like your library list.

Drop them in your project root, tweak as needed, and you’re golden. It’s like setting up a tent, baffling at first but then becomes simple once you know the poles.

Rules.mk: The Build Blueprint

These are your makefiles, telling TOBi how to assemble code. Root one lists source folders; sub ones define rules and links. Example: Link a program to its module, and TOBi builds in order. Naming matters – add .pgm for programs, skip for modules. Easy peasy, no PhD required.

What TOBi Builds

TOBi handles the IBM i favorites:

• RPGLE/SQLRPGLE programs and modules.
• CL stuff.
• COBOL, C/C++.
• Display/printer files (DSPF/PRTF).
• Database goodies like tables, views, indexes.
• Extras: Commands, binders, messages, data queues.

Think of it as a Swiss Army knife for storing, organizing and compiling IBM-i Source up to Objects.

Migration and VS Code Fun

Shifting from old Source Files to the IFS for source storage? TOBi’s migration is like moving house without the backache: Identify source, convert with cvtsrcpf, clean up auto-magically, then build. Integrates with VS Code via IBM i Project Explorer. This provides one-click builds, object browsing, Git sync. It’s like giving your green screen a sports car upgrade.

Tips and Next Moves

• Name consistently avoid “what was I thinking” regrets.
• Track dependencies let TOBi do the thinking.
• Git everything commit like your code’s life depends on it.
• Test often catch gremlins early.

Dive in: Check IBM GitHub for examples, start small, join the community.

TOBi’s your ticket to faster, funner IBM i dev – go build something awesome!