About TURNOVER for IBM i Application Lifecycle Manager
TURNOVER for IBM i Application Lifecycle Manager provides a comprehensive solution for managing the entire software development process on the IBM i platform from initial change requests through testing, approval, and deployment. In this lesson, you will learn how to implement TURNOVER’s lifecycle management features to improve collaboration, maintain version integrity, and automate deployment tasks. By the end, you’ll understand how TURNOVER streamlines development workflows, strengthens change control, and supports continuous improvement across your IBM i environments.
Module Content
TURNOVER for IBM i Application Lifecycle Manager provides a comprehensive solution for managing the entire software development process on the IBM i platform from initial change requests through testing, approval, and deployment. In this lesson, you will learn how to implement TURNOVER’s lifecycle management features to improve collaboration, maintain version integrity, and automate deployment tasks. By the end, you’ll understand how TURNOVER streamlines development workflows, strengthens change control, and supports continuous improvement across your IBM i environments.
Getting Started
MEMBERS ONLY
How to Install IBM i TURNOVER Software Change Management
Apply a temp code license to TURNOVER for IBM i
Turnover 101
MEMBERS ONLY
The TEST and UAT/STAGE environment only contain the objects that are currently under development or testing (aka "in flight") but for our webservices we want to break that rule and always have the program code for those particular CL/RPG/SQL programs permanently living in each of those environments. This is my solution - I'm sure there are other ways of doing it but this seemed to work nicely. Hope it help!
TURNOVER for iSeries (which should be branded as TURNOVER for IBM i) offers tracking precision, turning your multi-environment chaos into a traceable, auditable trail of evolution. In this lesson, we'll break down how TURNOVER tracks versions at a high level, zoom into the mechanics (archiving, cross-referencing, worklists, and forms), and wrap with a practical example: promoting from DEV through three test environments to PROD. Whether you're knee-deep in RPGLE modernizations or just dipping toes into ALM, this'll show why TURNOVER is your SDLC guardian.
For those working with IBM-i on a Power System (including legacy models like the iSeries and AS/400), the iconic green 5250 screen is a familiar sight. Today, with 'TURNOVER for iSeries,' it’s all about taking charge through a crisp, no-nonsense tour of the legendary 5250 main menu, a quick flyover of every option and the fastest navigation tricks to boost productivity. Whether you’re a newcomer, refreshing your skills, or aiming to supercharge your Turnover workflow, fire up your emulator and transform that daunting menu into your ultimate daily advantage.
Today we’re diving into a hands-on guide for TURNOVER on iSeries, focusing on 5250 Form Promotions with the classic green screen. For those managing changes on IBM i, TURNOVER remains one of the top tools available. While the modern GUI is popular, many teams still depend on the traditional 5250 forms daily for their speed, reliability, and complete control. This walkthrough covers every step—from creating a new promotion form, adding objects, running checks, and handling approvals to promoting seamlessly from Development through Test to Production. You’ll also get time-saving tips and learn how to avoid common pitfalls. Whether you’re new to TURNOVER or a seasoned user, this will help make your promotions smoother and more efficient—so fire up your 5250 emulator and get started!
If you’re an IBM i developer still proudly rocking the vintage 5250 green-screen like it’s the hottest new retro gadget, you know wrangling code changes, tasks, and promotions without the right tools can feel like juggling chainsaws in a wind tunnel. Today’s video dives headfirst into TURNOVER for iSeries, zeroing in on its star player, the Programmer Worklist Manager (PWM) - basically your own mission control for herding RPG, CL, or COBOL programs, wrangling promotion forms, tracking progress like a hawk, and keeping everything squeaky clean and audit-proof. Whether you’re a TURNOVER newbie or just looking to upgrade your daily grind from “organized chaos” to “smooth operator,” we’ve got examples, tips, and best practices to make change management faster, easier, and about 87% less hair-pulling. Let’s get rolling!
By the end of this lesson, you will be able to: * Identify the main types of SQL objects on IBM i. * Create, modify, and delete SQL objects using DDL. * Track and audit changes to SQL objects. * Apply best practices for SQL object management in production.
Welcome to this detailed lesson on using the Programmer Worklist Manager (PWM) within TURNOVER for iSeries, a powerful change management tool for IBM i (formerly known as iSeries or AS/400) environments. 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.
Understand the role of the Programmer Worklist Manager (PWM) in TURNOVER change management. Explain what user-defined options are and how they integrate with PDM in TURNOVER. Set up and use custom user-defined options for adding items to the worklist. Troubleshoot common issues with PWM options and PDM integration.
TURNOVER 101 - Turnover Pre-Run and Post-Run Promotion Form Commands
TURNOVER Tips'n'Tricks
MEMBERS ONLY
This lesson introduces the process of defining and managing the starting FORM number range within the IBM‑i TURNOVER Application Manager environment. FORM numbers play a central role in how TURNOVER tracks, organizes, and controls change requests throughout the software development lifecycle. Establishing a correct starting range ensures consistency, prevents numbering conflicts, and supports clean audit trails across development, testing, and deployment stages.