Lesson Objectives
By the end of this lesson, you will be able to:
- Understand the overview of TURNOVER® Lifecycle Manager, including project-driven change management, application diagrams, and tasks.
- Apply examples of change management to improve productivity in real-world scenarios.
- Follow a typical change workflow from problem entry to production distribution and task update.
- Use best practices for coding, testing, compiling, form creation, approval, and promotion in IBM i environments.
This summary condenses the 88-page Developer's Guide (January 2021 edition) into practical modules for developers. TURNOVER® Lifecycle Manager is an IBM i tool for managing application changes, ensuring controlled, auditable processes. Note: Based on web searches as of October 2025, no newer public Developer's Guide was found; check UNICOM/SoftLanding support for updates.
Key Concepts
- Project-Driven Change Management: Organizes changes around projects, tasks, and worklists for traceability and collaboration.
- Application Diagrams: Visual representations of application structures, levels (e.g., development, test, production), and object relationships.
- Tasks: Hierarchical elements linking problems/requests to worklists, tracking status, time, and approvals.
- Worklists and Forms: Worklists group objects for changes; forms automate promotion/distribution with error checks and approvals.
- Cross-References: Integration with tools like Hawkeye or Abstract/Probe to identify related objects.
- Checkout and Archiving: Reserves objects/source to prevent conflicts; archives changes for history/audit.
- Before Using: Ensure application definitions are set (via Administrator's Guide), user profiles configured, and training completed.
Module 1: Overview of TURNOVER® Lifecycle Manager
Project-Driven Change Management
- Integrates helpdesk, projects, worklists, and forms for end-to-end tracking.
- Supports multiple environments, distributions to remote systems, and compliance (e.g., SOX audits).
Application Diagrams
- Define levels (e.g., Level 1: Programmer test, Level 2: QA, Level 3: Production).
- Use for planning promotions and understanding dependencies.
Tasks
- Create from helpdesk requests; assign to programmers.
- Link to worklists for object changes; update status (e.g., In Progress, Complete).
Before Using TURNOVER® Lifecycle Manager
- Review setup: Application defaults, user authorities, interfaces (PDM, cross-ref tools).
- Familiarize with commands (e.g., STRPWM for Programmer Worklist Manager).
Module 2: Examples of Change Management Productivity
Hands-on scenarios demonstrating efficiency.
Example 1: Adding a Field to a PF
- Analyze impact: Check cross-references for dependent LFs, programs.
- Worklist: Add PF, checkout source, modify, compile (handles recompiles automatically).
- Form: Create, run to promote; distributes data conversions if needed.
Example 2: Changing a Set of Objects
- Build worklist from cross-ref (e.g., programs using a file).
- Checkout all, edit sources, compile in sequence.
- Test in personal library; promote via form.
Example 3: Building a List of Objects to Change
- Use filters/options in PWM to add items from PDM or cross-ref tools.
- Handle conflicts/reservations.
Example 4: Copybook Code
- Manage shared copybooks: Checkout, update, recompile using programs.
- Merge changes if concurrent edits occur.
Example 5: Rolling Out Changes
- Multi-level promotion: From dev to QA to prod.
- Distribution to remote IBM i systems via forms.
Example 6: Changing a Printer File
- Edit DDS, compile PRTF; handle form overrides for special attributes.
More Examples
- See guide for advanced cases like IFS objects, Java, or web components.
Module 3: Typical Change Workflow
Step-by-step process for developers.
Entering Problem Reports and Change Requests
- Use Helpdesk: WORKTASK or FASTTASK commands.
- Enter details, assign priority, link to projects.
Reviewing and Assigning Problems and Requests
- Managers review via escalation queue; assign to developers.
- Create tasks from requests.
Analyzing Tasks
- Review task details; estimate effort.
- Use cross-ref to identify all affected objects.
Creating Worklists
- From task: Option 20 or STRPWM.
- Assign programmer; set defaults.
Populating Worklists
- Add items: F6, or from PDM (AI option), cross-ref (F15).
- Filter by status/next option.
Checking Cross-References
- Option 15: Identify related objects (e.g., where used).
- Add to worklist if needed.
Adding New Items to the Worklist
- For new objects: Specify type, library, source.
- Handle dependencies.
Checking Out Objects and Source
- Option 21: Reserves name/source; creates dev copies.
- Batch or interactive (F19).
Coding and Testing Changes
- Edit source: Option 32/37 (SEU/SDA/RLU).
- Compile/test: Option 36; use personal libs.
Compiling the Objects
- Interactive or batch; handle errors.
- Add pre/post-run commands (Option 38).
Creating TURNOVER® Lifecycle Manager Forms
- Option 46: Builds form from worklist.
- Edit (42): Sequence items, add overrides, locks, messages.
Checking Forms for Errors
- Option 41: Simulates run; fix issues.
Getting Forms Approved
- Option 48: Send to approvers; wait for OK.
Running Forms
- Option 47: Submit to promote level.
- Monitor jobs (Option 40).
Testing and Acceptance
- Test in next level; record results in task.
Promoting to a Production Environment
- Option 43: Copy form to next level; repeat run/approve.
Distributing to Production Computers
- Set distribution in form; automates remote sends.
Updating the Project Task
- Mark complete; update time/hours.
Assessment and Next Steps
- Quiz Ideas: Describe steps to checkout an object. How to handle cross-references? Workflow from request to production.
- Practice: In a test IBM i, create a task, worklist, checkout/edit/compile a sample program, create/run a form.
- Further Learning: User Guide, Administrator’s Guide; supplements (e.g., IFS, SVN); contact UNICOM support (tech.support@unicomsi.com or +1-603-924-8818). Explore integrations with RDi, Git, or modern tools for 2025 updates.