Lesson Objectives
By the end of this lesson, you will be able to:
- Understand the overall form promotion processing flow in TURNOVER® for iSeries, including rollback and rerun procedures.
- Differentiate handling for source-only, source-compiled, and non-source objects during changes.
- Apply additional rules for object types like logical files, physical files, programs, menus, and DFUs.
- Use pre-run and post-run commands effectively, with scenarios for common use cases.
- Manage object deletions, form copy rules, and the delete test object rule for safe promotions.
This summary condenses the 23-page supplement (v101, September 2018) into practical modules for developers and administrators. It details how TURNOVER® (now Lifecycle Manager) automates change processes on IBM i, ensuring controlled promotions. Based on web searches as of October 24, 2025, no newer public version of Supplement #14 was found; it may be integrated into later guides like the Administrator’s Guide (Release 2.100, 2022). Check UNICOM/SoftLanding support for updates.
Key Concepts
- Form Promotion Flow: Automated sequence for moving changes through levels, with error handling and archiving.
- Object Types: Source-only (e.g., DDS), source-compiled (e.g., RPG programs), non-source (e.g., data areas).
- Rules and Conditions: Methods define create/promote behaviors; pre/post commands add custom logic.
- Deletions and Copies: Rules ensure safe handling of test/production objects during promotions.
- Prerequisites: Configured applications, cross-references, and familiarity with PWM (Programmer Worklist Manager).
Module 1: Introduction and Form Promotion Processing Flow
Overview
- TURNOVER® ensures auditable, error-free changes by automating promotions via forms.
- Forms group related objects; run in batch/interactive with checks.
Promotion Flow
- Preparation: Build form from worklist; sequence items logically (e.g., files before programs).
- Error Check: Simulate run; verify locks, authorities, dependencies.
- Run Form: Backup targets, create/move objects, archive sources, apply authorities.
- Post-Run: Execute commands, update history, notify users.
- Rolling Back: Create recovery form (manual or auto); run to revert changes.
- Rerunning Failed Forms: Fix issues, resubmit; handles partial successes.
Module 2: Handling Source-Only Objects
- Examples: DDS for displays (*DSPF), printers (*PRTF), files (*PF/*LF).
- Process: Checkout source, edit, add to form.
- Promotion: Copy source to target library; no compile needed.
- Special: For *PF, handle data (copy/convert); for *LF, ensure base *PF exists.
Module 3: Handling Source-Compiled Objects
- Examples: Programs (*PGM from RPG/CLP), modules (*MODULE), service programs (*SRVPGM).
- Process: Checkout, edit source, compile in dev, add to form.
- Promotion: Copy source, compile in target (using methods); recompile dependents if needed.
- ILE Specific: Bind modules into programs/service programs; handle signatures.
Module 4: Handling Non-Source Objects
- Examples: Data areas (*DTAARA), user spaces (*USRSPC), commands (*CMD).
- Process: No source; directly add to form with from/to libraries.
- Promotion: Copy/rename objects; apply authorities.
Module 5: Additional Rules and Conditions
TURNOVER® Methods
- Pre-defined for types (e.g., CRTDSPF for *DSPF); customizable in app definitions.
Create Parameters and Authorities
- CREATE Param: *YES (create new), *NO (replace existing).
- Authorities: Set initial owner/group; propagate from source or app defaults.
Logical Files
- Promote after base *PF; handle access paths, keys.
- Deleting *PF with Logicals: Delete LFs first; use form sequencing.
Multiple-Membered Files
- *PF: Promote all members or specific.
- *LF: Views over multi-member *PF; promote accordingly.
New Logical Files
- Duplicating/Moving: Copy to target, recreate access paths.
- Journaling: Start/end journaling via pre/post commands.
Promoting Programs, Menus, DFUs
- Programs: Recompile using; handle ILE bindings.
- IBM i Menus: Promote *MENU objects and DDS.
- S/36 Menus/DFUs: Special handling for legacy.
- Commands: Promote *CMD with source if available.
Module 6: Pre-Run and Post-Run Commands
- Pre-Run: Execute before object promotion (e.g., end journaling, clear locks).
- Post-Run: After (e.g., start journaling, notify users).
- Scenarios: Data conversions, authority adjustments, custom scripts.
Module 7: Deleting Objects and Form Copy Rules
- Deleting: Mark in form; delete from target (with backups).
- Form Copy Rules: When copying to next level, decide on test objects (keep/delete).
- Delete Test Object Rule: Auto-delete test versions after successful prod promotion.
Assessment and Next Steps
- Quiz Ideas: Describe the promotion flow for a source-compiled object. When to use pre-run commands? Rules for deleting a *PF with logicals?
- Practice: In a test IBM i, create a form with mixed objects, add pre/post commands, and simulate a promotion/rollback.
- Further Learning: Developer’s Guide for workflows; Administrator’s Guide for custom methods; other supplements (e.g., #50 for iASPs). Contact UNICOM support (tech.support@unicomsi.com or +1-603-924-8818) for access to full docs or updates.