Managing ILE Programs with TURNOVER

Lesson Objectives

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

• Understand how to create and manage ILE modules, programs, and service programs within TURNOVER® for iSeries (now Lifecycle Manager).
• Configure TURNOVER® to handle ILE objects, including type codes, create commands, and binding directories.
• Follow workflows for managing ILE objects in Version 100, such as handling bound modules and service programs.
• Convert existing OPM (e.g., RPG) objects to ILE using automated utilities like TCVTOBJTYP or manual worklist processes.
• Apply best practices for ILE management, including record length recommendations and post-conversion cleanup.

This summary condenses the 19-page supplement (Version 100, January 2010) into practical modules for developers and administrators. It focuses on integrating ILE (Integrated Language Environment) objects into TURNOVER®'s change management for IBM i. Principles apply to ILE languages like RPG, COBOL, C, though examples use RPG. Note: As of October 24, 2025, no newer public supplement or guide specifically on ILE management in TURNOVER® Lifecycle Manager (Release 2.100+) was found via web searches. However, 2021 updates emphasize source stream file (IFS) support for modern ILE development, aligning with this supplement's workflows. Check UNICOM/SoftLanding support for current integrations.

Key Concepts

• ILE Objects: Modules (*MODULE), programs (*PGM), service programs (*SRVPGM), binding language (*BND), bind directories (*BNDDIR).
• Create Commands: CRTxxxMOD for modules; CRTPGM or CRTBNDxxx for programs; CRTSRVPGM for service programs.
• Workflow: Checkout source, create modules, bind into programs/service programs; promote with forms.
• Conversion: Automate OPM to ILE with TCVTOBJTYP utility or manual via PWM.
• Recommendations: Use 112-byte record length for ILE RPG source files (vs. 92 for OPM).
• Prerequisites: TURNOVER® v4.2+ (for CRTBNDxxx); cross-reference tools (e.g., Hawkeye) for dependencies.

Module 1: Creating ILE Modules

• Process: Checkout source, edit, compile to *MODULE.
• Command: CRTxxxMOD (e.g., CRTRPGMOD for RPG).
• In TURNOVER®: Add to worklist (F6), checkout (21), compile (36); handles batch/interactive.
• Tips: Define type codes for *MODULE; promote modules independently or with bindings.

Module 2: Creating ILE Programs

Using CRTPGM

• Process: Bind one+ modules into *PGM.
• Command: CRTPGM PGM(lib/pgm) MODULE(mod1 mod2...) BNDSRVPGM(srvpgm) ACTGRP(*NEW/*CALLER).
• In TURNOVER®: Worklist lines for modules; form binds during promotion; handles recompiles.

Using CRTBNDxxx (Release 4.2+)

• Process: Single-step create bound program from source.
• Command: CRTBNDRPG PGM(lib/pgm) SRCFILE(lib/file) SRCMBR(mbr).
• Defining Command: In app defs, set underlying command for type codes.
• TCBP Support: Legacy command for binding; still supported but use CRTBNDxxx for modern.

Module 3: Creating Service Programs

• Process: Bind modules into *SRVPGM with signatures.
• Command: CRTSRVPGM SRVPGM(lib/srv) MODULE(mod1...) EXPORT(*SRCFILE/*ALL) BNDDIR(bnddir).
• In TURNOVER®: Worklist for modules/binder source; promote with form; update signatures automatically.
• Binder Language: Promote with *BND type; ensures compatibility.

Module 4: Other ILE Object Types

Binding Language Source (*BND)

• Manage as source; promote with service programs.

Bind Directory (*BNDDIR)

• Command: CRTBNDDIR; add entries with ADDBNDDIRE.
• Promotion: Add to worklist as *BNDDIR type; form handles updates.

Promoting Service Programs with Binder Language

• Group in worklist; form sequences (binder first, then SRVPGM).

Module 5: Workflow for Managing ILE Objects (v100)

Setup

• App Defs: Add ILE types (*MODULE, *SRVPGM); set methods (e.g., CRTRPGMOD).
• Global Defaults: Enable ILE recompiles for using-programs.

Handling Bound Modules

• Individual: Separate worklist lines; promote independently.

Binding Multiple Modules

• Group in form; TURNOVER® binds during run; handles dependencies.

Module 6: Converting Existing Objects to ILE

Automated with TCVTOBJTYP Utility

• Setup:
  1. Create conversion table entries (WRKTCVTBL).
  2. Verify type codes in app defs.
  3. Define PDM options (e.g., CI for convert/checkout).
• Execution: Run TCVTOBJTYP over libs; converts source, compiles to ILE.
• Post-Conversion: Original source remains; optional delete.

Manual via Worklist

• Add OPM to worklist; change type to ILE; compile/promote.

Assessment and Next Steps

• Quiz Ideas: Command to create a service program? Steps for automated conversion? Workflow for binding modules?
• Practice: In a test IBM i, convert an RPG program to ILE, manage in PWM, promote via form.
• Further Learning: Developer’s Guide for workflows; Administrator’s Guide (Release 2.100) for type codes; Supplements #14 (Change Process), #30 (Exits/APIs). For modern ILE with IFS, see 2021 updates on source stream files. Contact UNICOM support (tech.support@unicomsi.com or +1-603-924-8818) for 2025 features or ILE-specific configurations