Mastering TURNOVER for IBM i: Project and Worklist Management Basics

If you’re knee-deep in managing software changes on the IBM i platform, you know how crucial it is to keep things organized, auditable, and efficient. Today on the blog, we’re diving into TURNOVER for iSeries, specifically focusing on project and worklist management. This tool from UNICOM Global (formerly SoftLanding Systems) has been a game-changer for over 30 years, handling everything from RPGLE and CLLE code to DB2 databases and even IFS stream files.

Whether you’re a seasoned admin or just starting out, let’s break down the essentials step by step, based on a solid presentation overview I’ve put together. We’ll cover what TURNOVER is, how projects and worklists fit in, setup tips, workflows, and some best practices to keep your deployments smooth.

What is TURNOVER for IBM i?

TURNOVER is your all-in-one application lifecycle management (ALM) and source code management (SCM) solution tailored for the IBM i world. It takes care of the full software development lifecycle, from kicking off change requests to testing, approvals, and rolling out to production. Think automated deployments that are consistent and repeatable across dev, test, and prod environments. It tracks every tweak to your source code and objects with full audit trails and easy rollback options.

Key features include workflow enforcement to cut down on errors and meet compliance needs, plus detailed audit trails for when you need to dig into what changed and why. It supports the classic IBM i stuff like AS/400, iSeries, and Power Systems, along with languages such as RPGLE, CLLE, and COBOL. It even plays nice with DB2 for i, Java, PC, and web components. Integration is a breeze with tools like Rational Developer for i (RDi), CA 2E, and LANSA, making it perfect for modernizing without breaking your legacy setup.

Why do folks love it? It streamlines those tricky deployments, enforces best practices, and supports your modernization efforts without causing downtime. With capabilities like worklists for organizing tasks, promotion forms for bundling changes, cross-referencing for spotting dependencies, version control, reporting, and custom object types, it’s built to handle real-world IBM i challenges.

Core Concepts: Projects, Tasks, and Worklists

At the heart of TURNOVER are projects and worklists, which give structure to your development work. Projects act as big-picture containers. They define the scope of your changes, allocate resources, assign teams, and track progress throughout the lifecycle. You can set priorities, link them to helpdesk tickets for traceability, and break them down into tasks.

Tasks are the smaller, actionable pieces within a project. They’re hierarchical, so you can nest them as needed, track time spent, update statuses, and manage priorities. Each task gets assigned to a developer, keeping everyone accountable.

Then come worklists, the programmer’s daily hub. These track the objects you’re modifying, compiling, and promoting. It’s your workspace for checking out code, editing, and integrating with promotion forms. The flow is straightforward: Start with a project, define tasks, create a worklist for hands-on work, and build forms for promotion. This setup ensures everything is traceable from high-level goals to individual code lines.

Setting Up a Project in TURNOVER

Getting a project rolling is simple. From the TURNOVER main menu, pick Option 7 to hit the Work with Projects panel. Enter details like the project name (make it descriptive, like “Inventory Module Upgrade”), description, and objectives. Tie it to the relevant applications and set priorities.

Next, assign your team: Pick a project manager, add developers, and define roles with proper authorities. Break it into tasks with deadlines and assignments. Allocate resources like dev libraries and object categories. Pro tips: Link projects to helpdesk for end-to-end tracking, set realistic milestones, and review progress regularly.

Creating and Managing Worklists

Worklists are where the magic happens for programmers. Create one in three ways: From a task with Option 20, from projects via F20, or straight from the command line with STRPWM.

To populate it, hit F6 to add items manually, or use F20 to jump to PDM and grab objects with the AI option. Always check cross-references with Option 15 to catch dependencies early. Management hacks: Switch worklists with F7, filter with F17, set defaults like interactive or batch mode with F18, and repeat options across items with F13.

Remember, worklists linked from tasks keep that traceability intact, which is gold for audits.

The Programmer Worklist Manager (PWM) Overview

PWM is your central dev workspace in TURNOVER. It shows all your modified items with statuses, levels, and next ops. Filter views with F17, tweak session prefs with F18, and integrate seamlessly with PDM for options like AI (add item) or CO (checkout).

Function keys are your friends: F6 adds items, F13 repeats actions, F19 toggles interactive mode, F20 hits PDM, and F2 deals with forms. Columns cover options, object names, libraries, types, statuses, levels, and next operations. Access it from tasks, projects, or the command line for flexibility.

Walking Through the Development Workflow

Let’s map out a typical PWM workflow:

1. Add items to your worklist (F6 or PDM AI).
2. Check cross-references (Option 15).
3. Checkout and reserve objects (Option 21).
4. Edit source (Options 32 or 37).
5. Compile and test (Option 36).
6. Build a promotion form (Option 46).
7. Edit the form (Option 42).
8. Approve if needed (Option 48).
9. Submit the form (Option 47).
10. Promote to the next level (Option 43).

Aim for that “Ran-OK” status to confirm success. This cycle covers development, form building, and deployment phases, ensuring changes move reliably.

Understanding Promotion Forms

Promotion forms are TURNOVER’s deployment engine. They bundle related objects, add pre and post-run commands (like restarting subsystems), check for errors, and handle approvals.

Form structure includes a number, sequences, object lists, promotion levels, commands, comments, and locks. Lifecycles go from Open to Ready, Pending Approval, Running, Ran-OK, or Error. Key options: 46 to create, 42 to edit, 47 to submit, 40 to view jobs.

The Full Form Lifecycle and Deployment

Build from your worklist with Option 46, then edit sequences and commands via 42. Error-check with 41, approve with 48, submit (interactive with F19 or batch), monitor jobs with 40, promote next with 43, and celebrate Ran-OK.

Modes: Interactive for real-time checks, batch for big jobs.

Best Practices and Pro Tips

To level up:

• Use F17 filters to declutter worklists.
• Leverage F13 for bulk actions.
• Always cross-ref first with Option 15.
• Stick to naming conventions for projects and tasks.
• Set F18 defaults for your workflow.
• Review histories with Option 18 or DSPCOHST.
• Document commands in form comments.
• Error-check forms with 41 before submitting.

TURNOVER brings version control, automation, and compliance to your IBM i game. It transforms chaotic changes into structured, reliable processes.

Stay technical, stay efficient. Catch you next time!