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.
Turnover 101
MEMBERS ONLY
How to Install IBM i TURNOVER Software Change Management
Apply a temp code license to TURNOVER for IBM i
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.
TURNOVER 101 - Create TURNOVER Project and Worklist
welcome back to our Turnover series on IBM i change management. Last time, we set up a project and worklist to kick off your code changes. Today, in part two, we're diving right into editing source code and compiling it safely within Turnover's framework. I'll show you step by step how to check out files, make tweaks in SEU, run the compile sequence, and track it all without breaking a sweat. Stick around, because by the end, you'll be promoting changes like a pro. Let's jump in to "TURNOVER 101 - Edit Source Compile"
TURNOVER 101 - Promote program to next level using a Form Form Setup: From PWM, link a form to your task, auto-populating from the worklist for seamless tracking. Copy to Next Level: Hit option 43 to advance the form (e.g., DEV to TEST), resolving dependencies like logical files via cross-refs. Approval & Execution: Submit via 48 for sign-off, then 47 to run—compiling, installing, and auditing the move with status updates.
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.
TURNOVER 101 - Turnover Pre-Run and Post-Run Promotion Form Commands
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.
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!
In this video, we dive into the process of deleting and archiving IBM i objects using TURNOVER. Learn step-by-step how to efficiently manage object deletion and archiving to keep your system organized and optimized. Perfect for IBM i users looking to streamline their workflow with practical tips and best practices. Watch now and master TURNOVER!