Mastering the Programmer Worklist Manager (TURNOVER PWM)

PWM - Lesson Overview

This lesson is designed for beginners and intermediate developers, focusing on practical steps for managing development workflows. TURNOVER helps streamline code changes, promotions, and deployments while ensuring compliance and reducing errors in enterprise IBM i applications.

Based on the "TURNOVER for iSeries PWM Quick Reference" guide. We'll break it down into sections with explanations, step-by-step instructions, and tips. Assume you have access to an IBM i system with TURNOVER installed (version 100 or higher for some features).

By the end of this lesson, you'll be able to:

• Access and navigate PWM.
• Follow standard development steps for adding, editing, compiling, and promoting items.
• Use common options, function keys, and commands.
• Integrate with tools like PDM (Programming Development Manager) for efficient workflows.

Introduction to TURNOVER for iSeries and PWM

TURNOVER for iSeries is a change management system that automates the process of tracking, testing, and promoting software changes across development levels (e.g., from development to test to production).

PWM is the core interface for programmers, acting as a "worklist" to organize tasks, objects, and forms. The key concepts of PWM include:

PWM emphasizes batch processing for efficiency but supports interactive modes. Always check session defaults (F18) for preferences like interactive vs. batch.

Accessing PWM

From the IBM i command line, enter the STRPWM command.

Alternatively you can take Option 20 on the "Work with Tasks" menu, or press F20 on the "Work with Projects" menu.

Once in PWM, you'll see your worklist. F6 will create a new worklist, and it's handy to know that F7 switches between previous worklists if needed.

Use the top FILTER section to remove unnecessary noise and focus on your current workload

Tip: If you're new, set up session defaults with F18 (e.g., toggle interactive error-checking).

Development Steps in PWM

Development follows a logical sequence. These steps are presented in the typical order for a change management cycle.

1. Add Items to the Worklist (F6)

Start by building your worklist with the objects or source members you need to change.

Press F6 to create your worklist in PWM. Then we can add all the objects we are working on, into that worklist.

hint: If you are a PDM user (I love PDM btw) then you can use user-defined option AI (Add Item) to add to the worklist.

2. Check Cross-Reference (Option 15)

Before changes, verify dependencies.

• If using TURNOVER's built-in X-Ref, select items with Option 15.
• This scans for related objects (e.g., files used by a program).

Why? Prevents incomplete promotions. View results with Option 16 (Related Objects).

3. Checkout / Reserve Name (Option 21)

Lock items to avoid conflicts.

• Filter the list by "Next opt" 21 (F17).
• Select the first item with Option 21, then press F13 to repeat for others.
• Press Enter to submit checkout (batch by default; use F19 for interactive).

Example: Checkout a source member to reserve it. View history with Option 18 (Object History) or command DSPCOHST.

4. Edit Source (Options 32/37)

Modify the code.

• Filter by "Next opt" 32.
• Select items with Option 32 (Edit Source) or 37 (SDA/RLU for screens/reports).

Integration: Use Option 12 (Compare Source) or command CMPSRCMBR to diff changes. Merge with MRGSRCMBR.

5. Compile and Test (Option 36)

Build and verify.

• Select objects with Option 36 (Compile).
• Adjust defaults with F18 (e.g., compile options).
• Run unit tests manually.

6. Build TURNOVER Form (Option 46)

Package changes for promotion.

• Filter by "Next opt" 46.
• Select first item with Option 46, press F13 to repeat.
• Press Enter to build the form (interactive/batch via F19).

What Happens? Creates a form if none exists. Add related forms with TARAFORM command.

7. View/Edit Form (Option 42) - Optional

Refine the form.

• Select one item with Option 42.
• Edit sequences, add pre/post-run commands, overrides, lock checks, messages, or comments.
• Press F3 to exit (may prompt for Form Exit panel).

Example: Add a post-run command to restart a subsystem.

8. Approve Form (Option 48) - If Required

Get sign-off.

• Select one item with Option 48.
• Choose users from the approval list and send a message.
• Wait for approvals.

Tip: View form jobs with Option 40.

9. Submit Form (Option 47)

Run the promotion.

• Select one item with Option 47.
• Accept/change defaults and press Enter.
• If interactive error-check: Wait, verify, press Enter.
• If batch: Wait for report, submit if OK.

Error Handling: Use Option 41 (Error Check Form) beforehand.

10. Promote to Next Level (Option 43)

Move up levels.

• Once items are "Ran-OK," select one with Option 43.
• Press Enter or F19 to submit.
• Next level displays; repeat Options 47/48.

Note: Administrators often handle higher-level promotions. Use command CPYPWL for copying worklists.

Frequently Used PWM Options

Here's a table of common options for quick reference:

PWM Function Keys (F-Keys)

PWM Function Keys (F-Keys)