(Before You Become a Walking Error Message)
If you’re new to the IBM i world, congratulations – you’ve just stepped into one of the most powerful, stable, gloriously quirky computing platforms ever built. But before you can call yourself anything other than “that person who keeps locking QSYSOPR,” you need to memorise a handful of core commands.
These aren’t optional. These are the commands that separate “I think I pressed something wrong” from “I actually know what I’m doing.” Master them early and you’ll look like a seasoned operator. Ignore them and, well… prepare to become a human CPF9898.
Welcome to the wonderful world of AS/400, iSeries, Power Systems… whatever marketing decided to call it this decade. You have just stepped into an operating system that still runs half the planet’s critical business while looking like it was designed in 1988 (because it basically was).
And the quickest way to stop feeling like a lost tourist in green-screen land? Learn these ten commands. Seriously. Nail these and you will look like you have been here since the days of twinax cables. Ignore them and you will spend your days typing random three-letter combinations while praying the system does not reply with “Object not found… or maybe you just don’t belong here.“
Let us dive in, with a healthy dose of irreverence and quite a lot of mumbling:
1. WRKACTJOB – Your New Best Friend for Stalking Jobs
First thing every morning (or after that dodgy program you just compiled), type WRKACTJOB. This bad boy shows you every job currently running, how much CPU it is hogging, and whether it is happily chugging along or having a quiet meltdown in subsystem QINTER.
Pro tip: Press F5 to refresh like a caffeinated teenager checking their phone. If you see a job stuck in *MSGW, congratulations – you just found the developer who forgot to handle an error.
2. WRKSPLF – Because Printers Still Exist in 2026
Spooled files. The digital equivalent of that printer jam that nobody wants to fix. WRKSPLF lets you see every report your batch jobs have spat out, hold them, delete them, or (heavens forbid) actually print them.
Nothing says “I am a professional” quite like deleting 47 copies of a 300-page month-end report before the boss notices.
3. WRKLNK – Exploring the IFS Without Getting Lost
The Integrated File System is where IBM i hides all its modern Unix-like goodness. WRKLNK is your file explorer for the IFS. Navigate directories, check permissions, delete that temporary XML file your Java program left behind in 2019.
Think of it as “ls -la” but with function keys and a slightly judgemental system response when you type the path wrong.
4. WRKOBJ – The Great Object Detective
Lost a file? Cannot find that program you swore you compiled yesterday? WRKOBJ is your search warrant for the entire system. Give it an object name, with wildcards if you are feeling brave, and it will hunt through libraries like a very polite bloodhound.
5. WRKOUTQ – Taming the Output Queue Zoo
Output queues are where spooled files go to wait for their turn at the printer… or to sit there forever because someone set the queue to *HOLD. WRKOUTQ shows you what is queued up and lets you release, hold or delete with ruthless efficiency.
6. DSPLIBL – “Where Am I?” Command
Type DSPLIBL and the system politely tells you which libraries you can currently see. This is vital because on IBM i, if your library list does not include the right one, your program might as well be on another planet.
Forgetting to check your library list is the IBM i equivalent of leaving your house keys in the car.
7. DSPJOB – Deep Dive Into a Single Job
When WRKACTJOB tells you something is misbehaving, zoom in with DSPJOB. It shows job log, status, open files, locks , basically the full CSI: IBM i episode for that one naughty job.
Handy when you need to prove it was not your code. (It probably was.)
8. SBMJOB – The Batch Ninja Move
Interactive jobs are for testing. Real work happens in batch. SBMJOB lets you fire off a program or command to run in the background while you go get coffee. Or lunch. Or a two-week holiday.
Master this and you will never again sit there watching a 45-minute SQL statement crawl across your screen like a snail on tranquillisers.
9. SIGNOFF – The Civilised Escape Hatch
When you are done for the day, do not just close the emulator window. Type SIGNOFF like a grown-up. It logs you off cleanly and, more importantly, ends your interactive job so you do not leave a zombie session eating up system resources.
Leaving sessions signed on is how system administrators develop trust issues.
10. DSPMSG QSYSOPR – Listening to the System Complain
The system operator message queue is where IBM i sends its passive-aggressive notes. Disk almost full? Backup failed? Someone tried to delete a locked file? DSPMSG QSYSOPR is where you will find out.
Read it regularly. It is basically the system saying “help me, I am being held hostage by bad CL”.
You can watch all these videos, of me burbling, mumbling, waffling, stuttering and UMMing and EURRRRing here
Bonus: Learn the Command Verbs and You Win at IBM i
Once you know these ten, the rest becomes pattern-matching. IBM i commands are wonderfully consistent:
- WRK… = Work with (management)
- DSP… = Display (look but do not touch)
- CHG… = Change (careful now)
- STR… = Start (let us get this party going)
- DLT… = Delete (with great power comes great “oops”)
Learn the verbs and suddenly half the commands make sense before you even type them.
Final Thoughts
Memorising these ten commands will not make you an IBM i guru overnight. But it will stop you looking like the new kid who keeps asking “how do I see what is running?” in the company Slack channel.
And trust me, on IBM i, looking competent is half the battle. The other half is remembering that the system has been running reliably since before most of us were born, and it is quietly judging our modern cloud-native egos.
So fire up your emulator, type these bad boys a few times, and welcome to the club. We have green screens, rock-solid uptime, and the occasional existential crisis when the library list is wrong.
Now go forth and WRKACTJOB like you mean it.
Happy commanding!
