The Hilarious World of IBM i TURNOVER PWM: A Quick Reference for Dinosaur Developers

Ah, the IBM i (née AS/400, iSeries, or that big black box in the server room that refuses to die). If you’re like me, a software developer who’s somehow time-traveled from the ’90s, you’ve probably wrestled with change management tools that feel more like ancient rituals than modern coding – you are probably intrigued by TURNOVER for iSeries IBM i.

What is it? TURNOVER is a powerful change management tool from Softlanding for IBM i systems, helping teams track, promote, and audit changes across development, testing, and production environments. But you already know that right?

The Programmer Worklist Manager (PWM) is the unsung hero of TURNOVER, one that turns your chaotic code tweaks into something resembling organized chaos. Today, we’re diving into its PDM style user defined options and building a list of what it is and why it does it.

Who doesn’t love a cheat sheet that makes you feel like a wizard or at least a slightly less confused apprentice?

The Programmer Worklist Manager (PWM) Screen:

Here is a good old fashioned green screen (well its white screen but you get the gist) of the PWM in action. In this example I have check out some programs to my developer library (LITTENN) and it will be promoted through a code-test layer, two separate QA environments and then onto Production:

This is a busy screen, with lots of menu options and function keys. But slow down, review each one and they will all make sense.

Start with adding items (F6), check cross-references (Option 15 – because who wants to miss a related object and crash production?), edit source (32/37), compile (36), and build that glorious form (46). Then approve (48), submit (47), and promote (43). It’s like a recipe for software stew: Stir in some filters with F17, repeat options with F13, and voilà your changes are promoted faster than a bad idea in a meeting.

Pro tip: If approvals are required, just pray your boss isn’t on vacation, or you’ll be waiting longer than for Windows to update.

And the function keys? F19 for interactive vs. batch , because sometimes you want to watch the magic happen in real-time, like binge-watching a compiler. F20 straight to PDM? Chef’s kiss. It’s all so retro-chic, you’ll feel like you’re in a ’80s hacker movie, minus the neon and plus a lot more green screens.

So, how do user defined options come into this?

Picture this: You’re knee-deep in RPG code, and suddenly you need to add items to your worklist. Boom! Press F6 or hop over to PDM and slap an “AI” (Add Item) on it. It’s like magic, but instead of “Abracadabra,” it’s “ADDPWLITM” – because nothing says “fun” like typing out command names longer than your coffee order. And don’t get me started on checkout with Option 21. It’s basically the system’s way of saying, “Hey, reserve this before your coworker Bob accidentally overwrites your masterpiece with his lunch break doodles.“

Just the same as IBM i PDM (Program Development Manager) User Defined Options, TURNOVER is fully integrated with PDM and lets you use your existing PDM options plus some very specific TURNOVER ones like application, source library, target library, programmer name and more.

It’s like a programmable shortcut that lets you run custom commands directly from the PWM screen, turning that green screen into your personal command center.

What Is This?

A User Defined Option in PDM is a two-character code (like AI, CP, or CK) that you assign to a specific command or script. When you type that code next to a source member or object in PDM (e.g., WRKMBRPDM or WRKOBJPDM), it executes the associated command using that object as input.

For Example:

Option: AI   (Add Item to TURNOVER worklist)
Command: ADDPWLITM LIB(&L) FILE(&F) MBR(&N)

This would let you type AI next to a member, and it would automatically run the ADDPWLITM command with the correct library, file, and member name substituted in.

Benefits of Using User Defined Options

Here’s why they’re a game-changer for IBM i developers:

• Speed & Efficiency: No more typing long commands, it’s just two characters and go.
• Consistency: Standardize repetitive tasks across your team (e.g., compile, promote, check out).
• Customization: Tailor your workflow to your exact needs whether it’s TURNOVER integration, custom compiles, or source analysis.
• Learnability: Great for onboarding because noob developers can use complex commands without memorizing syntax.
• Testing & Debugging: Create options for test compiles, debug builds, or even quick backups before changes.
• Cleaner Workflows: Keeps your hands on the keyboard and your mind in the code, no need for jumping between menus or command lines.

I just added a lesson on PWM and the available options here – so trot over and read it if that’s your jam.

Alternately, you can gobble up the entire TURNOVER course and become a green screen application lifestyle ninja, with a slightly dodgy English accent.