The Programmer Worklist Manager (PWM) is a core component, allowing developers to manage worklists, collections of source and object changes for promotion. Uuser-defined options enhance PWM by integrating custom commands into PDM, streamlining tasks like adding objects to worklists directly from PDM object lists.

This lesson focuses on setting up and using user-defined PWM options, with an emphasis on the "Add to Worklist" (AI) option, as detailed in the guide.

What are User-Defined Options?

User-defined options are custom commands added to PDM’s options file (e.g., QAUOOPT in library SOFTTURND). They allow developers to execute TURNOVER commands from PDM, such as adding objects to a worklist or checking out items.

In PWM, these options bridge PDM’s object browsing with TURNOVER’s change management, reducing manual steps.

PWM and PDM Integration

PWM: A TURNOVER interface for creating and managing worklists (accessible via STRCNGCMN or menu options).

PDM: IBM i’s Programming Development Manager, used to browse and manage libraries, objects, and members.

Here is the kicker -- User-defined options link PDM selections to PWM actions, like adding objects to a worklist with the AI option.

Step-by-Step Guide: Configuring User-Defined PWM Options

Based on the TURNOVER for iSeries v100 Developer’s Guide (pages 73–75), here’s how to set up and use user-defined options for PWM.

Step 1: Prepare the TURNOVER Environment

  1. Sign on to your IBM i session.
  2. Start TURNOVER: Enter STRCNGCMN or select your application from the TURNOVER menu.
  3. Verify your user profile is defined in TURNOVER (Admin > Users). Ensure you have authority to the application and worklist roles.
  4. Access PWM: From the TURNOVER menu, select Option 1 (or equivalent) to enter the Worklist Manager.

Note: If you lack permissions, contact your TURNOVER administrator to update your roles.

Step 2: Access and Edit the PDM Options File

  1. Ensure the TURNOVER library (e.g., SOFTTURND) is in your library list: ADDLIBLE SOFTTURND

  2. Access the PDM options file: Use WRKOBJPDM LIB(SOFTTURND) OBJ(QAUOOPT) OBJTYPE(*FILE) or navigate via PDM’s option editor.

  3. If QAUOOPT doesn’t exist, copy it from a template (e.g., QUSRSYS) or create it per your system setup.

Step 3: Define the AI Option (Add to Worklist)

  1. In PDM, edit QAUOOPT (use EDTF or PDM’s option editor).

  2. Add a new user-defined option (Developer’s Guide, page 74):

    • Option Code: AI

    • Description: Add to Worklist

    • Command: TNSADDWL OBJ(&N) LIB(&L) TYPE(&T) APPL(&APPL)

      • &N: Object name (PDM variable for selected object).

      • &L: Library name.

      • &T: Object type (e.g., *PGM, *FILE).

      • &APPL: Your TURNOVER application code (e.g., DEVAPP).

  3. Save the file and exit.

Example Command: For an application named PRODAPP, the command might be: TNSADDWL OBJ(&N) LIB(&L) TYPE(&T) APPL(PRODAPP)

Step 4: Use the AI Option in PDM

  1. In PDM, use WRKOBJPDM to browse a development library (e.g., DEVLIB).
  2. Select an object (e.g., an RPG program or source member).
  3. Enter AI in the option field and press Enter.
  4. The object is added to your active PWM worklist.
  5. Return to PWM (via F20 from PDM or directly) and verify the object appears in the worklist using F6 (Add Items) or by browsing the list.

TURNOVER USER DEFINED OPTIONS - Replacement Values

Work with Programmer Worklists

2 = Change

Modify fields for a worklist item, including:

  • Programmer

  • Project/Task Reference

  • Description

  • Item Status

  • Cross Reference Checked

  • Related Applications Checked

Use F4 to prompt, or enter keywords and new values directly on the command line.Note: Changes apply only to the selected level unless CHGALL(*YES) is specified (press F10 for additional parameters).

3 = Copy

Duplicate a worklist item to another list.

4 = Delete

Remove an item from the worklist.No impact on source or object.

11 = Move

Transfer a worklist item to another list.No impact on source or object.

12 = Compare Source

Compare the source of an object with:

  • Other levels of the application

  • Source archive versions

15 = Check Cross Reference

View cross-reference info for an object. Referenced objects appear on the Work with Cross Reference panel. From there, you can:

  • Add objects to the worklist

  • Check out objects

  • Perform further analysis

Note:

  • Automatically sets Cross Reference Checked = Y

  • If session default requires X-Ref Check = Y, this flag must be set before using option 46

  • Use F18 to view/change session defaults

16 = Check Related Applications

Identify versions of an object in libraries tied to related applications. Results appear on the Work with Related Applications panel. You can:

  • Add related objects to the worklist

  • Check out related objects

Note:

  • Automatically sets Related Applications Checked = Y

  • Required if session default mandates Related Apps Check = Y before using option 46

18 = Object History

Access TURNOVER history for a selected object via the Work with Object History panel.

21 = Checkout

Reserve a worklist item. Select multiple items and press F19 to submit the batch job. A report will detail the checkout results.

22 = Change Checkout

Update checkout record fields:

  • Programmer

  • Reference

  • Type code

24 = Checkin

Remove the checkout record for an item.No impact on source or object.

25 = Task Details

Edit the task linked to the Project/Task Reference field.

26 = Conflicts

Review related application conflicts for items with status CONFLICT or INCONFLICT.

32 = Edit Source

Edit source using SEU. Requires authority to the source file/library. If session default is *DEVELOP, editing is restricted to the development level. Use F18 to adjust session defaults.

35 = Browse Source

Browse a source member. Requires appropriate authority.

36 = Compile

Compile source using the defined create command. Press F4 to edit parameters (if not protected). Requires authority to create/replace objects. Restricted to development level if session default is *DEVELOP.

37 = SDA

Modify display/menu files via Screen Design Aid or printer files via Report Layout Utility. Same authority and level restrictions as option 36.

38 = Pre/Post Commands

Manage command links to objects. Commands execute before/after object creation.

Form Management Options

40 = Form Jobs – View jobs tied to a submitted promotion form

41 = Error Check Form – Submit error-check job

42 = Edit Form – Modify a form containing the item

43 = Copy Form – Duplicate a form

  • Defaults to next level if form ran successfully and higher levels exist
  • Otherwise, defaults to same level

44 = Remove from Form – Detach item from a form

45 = View Form – Display the form containing the item

46 = Add to Form – Add item to a form

  • Auto-adds to existing READY/APL-PN form if matched
  • Otherwise, prompts to create a new form
  • Use F4 to prompt by form number
  • Press F19 to batch-add selected items

47 = Run Form – Execute a form containing the item

48 = Form Approval – Approve a form (must be on approval list)

49 = Print Form – Print the form

99 = Next Option

Executes the option specified in the “Next Option” field for the selected item.

Maintain User Defined Options          

Maintain User Defined Options

Default PDM options in TURNOVER

S wrksplf

2 Change                    

3 Copy                      

4 Delete                     

11 Move            

12 Compare source  

15 Check X-Ref      

16 Check related    

18 Object history  

21 Checkout        

22 Change checkout  

24 Checkin          

25 Task details      

26 Conflicts        

32 Edit source      

35 Browse source    

36 Compile          

37 SDA              

38 Commands          

39 Debug            

40 Form Jobs        

41 Error checking    

42 Edit form         

43 Copy form              

44 Remove form            

45 View form              

46 Add to form            

47 Run form              

48 Approve form          

49 Print form            

99 Next option       

Turnover PWM User Defined Options in Action

TURNOVER likes DOUBLE QUOTES


TURNOVER’s user-defined options often require double quotes (") around parameters or values because of how it parses and interprets command strings internally. Unlike IBM i’s PDM user-defined options, which are processed more directly by the OS command processor, TURNOVER routes its options through its own command-handling engine. This engine:

  • Treats the entire string as a single literal when wrapped in quotes, avoiding misinterpretation of embedded spaces or special characters.
  • Ensures proper substitution of variables or keywords, especially when the command includes multiple parameters or nested values.
  • Preserves formatting for commands that might otherwise be split or truncated by TURNOVER’s parser.
IBM i TURNOVER: User-Defined PWM Options 1

TURNOVER PDM Replacement Values

VariableDescription
&AApplication
&F#Form Number
&PGProgrammer
&RFProject Reference
&PFProduction Source File
&PLProduction Source Lib
&PMProduction Source Member
&OBObject Name
&OLObject Library
&OAObject Attribute from TURNOVER
&OTObject Type from TURNOVER

IBM PDM Replacement Values

VariableDescription
&LLibrary name
&FFile name (source physical file or object name)
&NMember name (source member)
&TObject type (e.g., *PGM, *FILE)
&AAttribute (e.g., RPGLE, CLP)
&RRecord format name
&PObject text (description)
&DDate last changed
&UUser profile that last changed the object
&XExtension (used in some contexts for file types)
&ZSource type (similar to attribute, but used in certain commands)

User-defined PWM options, like AI, integrate PDM with TURNOVER’s Worklist Manager, enabling efficient change management directly from object lists.

Troubleshooting Common Issues

Based on the Turnover Developer’s Guide (page 75) and common practices:

  • AI Option Fails:

    • Cause: Insufficient TURNOVER authority or incorrect application code.

    • Fix: Verify user roles in TURNOVER Admin and ensure &APPL matches your application.

  • Object Not Added:

    • Cause: Library not in LIBL or QAUOOPT misconfigured.

    • Fix: Run ADDLIBLE SOFTTURND and recheck QAUOOPT syntax.

  • PDM F20 Not Working:

    • Cause: Missing PDM-PWM interface setup.

    • Fix: Ensure TURNOVER’s PDM integration is enabled (contact administrator).

  • Cross-Ref Errors:

    • Cause: Missing cross-reference product (e.g., Hawkeye).

    • Fix: Configure integration per the Developer’s Guide, page 75.

{"email":"Email address invalid","url":"Website address invalid","required":"Required field missing"}
>