Handling Message IDs in TURNOVER

Lesson Objectives

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

• Understand how TURNOVER® for iSeries (now Lifecycle Manager) enables independent management of individual message IDs without locking or merging entire message files.
• Define and configure type codes for message IDs to integrate them into change management workflows.
• Add, checkout, change, and promote message IDs using Programmer Worklist Manager (PWM) and forms.
• Handle dependencies, such as ensuring message IDs are sequenced correctly on forms relative to dependent objects like commands or display files.
• Apply best practices for managing multiple message files across applications or within a single application.

This summary condenses the 6-page supplement (v101, September 2018) into practical modules for developers and administrators. It focuses on granular control over message IDs (*MSGID) in IBM i message files for auditable changes. As of October 24, 2025, no newer public version of Supplement #61 was found via web searches on UNICOM or SoftLanding sites; the content aligns with features in TURNOVER® Lifecycle Manager Release 2.100 (2022), but verify with support for any updates to message handling in modern releases.

Key Concepts

• Message ID Management: Treat individual *MSGID as objects for checkout/change/promotion; avoids full file locks/merges.
• Type Codes: Custom codes with *MSGID object type; one auto-created on install, copy for multiples.
• Workflow Integration: Use PWM to add/checkout/change; forms for promotion; sequence before dependents (e.g., *CMD, *DSPF).
• Multi-File Handling: Same type code for different files across apps; unique codes per file in one app.
• Prerequisites: TURNOVER® v101+; message files defined; cross-references for dependencies.

Module 1: Introduction to Message ID Handling

Overview

• TURNOVER® allows tracking changes to specific message IDs independently, ensuring auditability without disrupting entire message files.
• Benefits: Granular control, no merges needed, supports compliance via history/forms.

Why Independent Management?

• Traditional: Changing a msg requires file-level ops; TURNOVER® objectifies *MSGID for precise workflows.

Module 2: Defining Type Codes for Message IDs

Creating Type Codes

• In TURNOVER 1 > Work with Type Codes > F6 Add or copy existing MSGID entry (auto-created on install).
• Key Fields:
  • Type Code: e.g., MSGID (custom name if multiple).
  • Description: e.g., "Message ID".
  • Object Type: *MSGID (required).
  • CM Scheme: *TURNOVER.
  • Sequence: Low value (e.g., 100) to precede dependents on forms.
  • Data Object: Y (copy/replace).
  • Create Command: Blank (system handles via CHGMSGD).
• For Multiple Files: Use same code across apps; unique codes within one app (e.g., MSGID1, MSGID2).

Configuration Tips

• Attribute/Source File: Blank unless custom.
• Prompts: Use F4 for options; reference vars like "&OB" (object name), "&LI" (library).

Module 3: Adding and Checking Out Message IDs in PWM

Adding to Worklist

• STRPWM > F6 Add Item: Specify type code (e.g., MSGID), message file/lib, ID (e.g., ABC0001).
• Filters: Use to list specific IDs; wildcards supported.

Checkout Process

• Option 21: Checkout reserves the ID; creates editable copy.
• Conflicts: Handles via multiple checkout or emergency apps if needed.

Module 4: Changing and Promoting Message IDs

Changing Messages

• Option 32: Edit with CHGMSGD (prompt for text/severity).
• Compile/Test: Not needed; changes direct via command.

Building and Running Forms

• Option 46: Add to form; auto-sequences before dependents (e.g., before *CMD using the msg).
• Edit (42): Add overrides (e.g., pre-run locks on msg file).
• Approval/Submit: Option 48/47; promotes changes to target level.
• Distribution: Handles remotes; ensures msg availability for compiles.

Module 5: Advanced Handling and Best Practices

Dependencies and Sequencing

• Cross-Ref: Option 15 to find using objects (e.g., programs/cmds); add to worklist.
• Forms: Low sequence ensures msgs promote first.

Multi-Application/File Scenarios

• Different Apps: Reuse type code.
• Single App: Unique codes per msg file to avoid conflicts.

Best Practices

• Auditing: Use history (Option 4) for ID changes.
• Testing: Promote in test env first.
• Merges: Avoided by design; no file-level ops.

Assessment and Next Steps

• Quiz Ideas: Key field for *MSGID type code? How to handle multiple msg files in one app? Why low sequence value?
• Practice: Define a MSGID type code, add/checkout a message ID in PWM, promote via form.
• Further Learning: User Guide (v101) for PWM/forms; Administrator’s Guide (Release 2.100) for type codes; Supplements #14 (Change Process), #30 (Exits/APIs). Contact UNICOM support (tech.support@unicomsi.com or +1-603-924-8818) for 2025 updates or custom msg integrations.