Using TURNOVER Create Commands

Lesson Objectives

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

• Understand how TURNOVER® for iSeries (now Lifecycle Manager) handles create commands during object promotions, focusing on the CSCO method.
• Differentiate between promotion methods: CSCO (Copy Source, Compile Object), CSMO (Copy Source, Move Object), and CSCD (Copy Source, Create Duplicate Object).
• Customize create commands and parameters to control object creation and attribute application.
• Apply post-creation changes to objects, including when and why TURNOVER® modifies attributes.
• Reference related User Guide sections for detailed configuration and form line adjustments.

This summary condenses the 4-page supplement (v101, September 2018) into practical modules for developers and administrators. It explains create command mechanics for reliable promotions in IBM i environments. As of October 24, 2025, no newer version of Supplement #53 was found via searches on UNICOM or SoftLanding sites; the content aligns with core features in TURNOVER® Lifecycle Manager Release 2.100 (2022), but verify with support for any post-2018 updates to command handling.

Key Concepts

• Promotion Methods: CSCO compiles objects; CSMO/CSCD handle non-compiled moves/duplicates.
• Create Commands: Used in CSCO to build objects from source; customizable via parameters.
• Attribute Changes: Post-creation adjustments (e.g., via CHGxxx commands) to match original properties.
• Customization: Override defaults in app definitions or form lines for flexibility.
• Prerequisites: Familiarity with PWM, forms (Chapter 6, User Guide), and app definitions (Chapter 1, User Guide); cross-references for dependencies.

Module 1: Introduction to Create Commands

Overview

• Create commands (e.g., CRTDSPF, CRTPGM) are central to promoting compiled objects.
• TURNOVER® automates: Copies source, executes create command, applies attributes.
• Focus: CSCO method for source-compiled objects (e.g., programs, displays).

Promotion Actions in CSCO

1. Object Creation: Executes create command with parameters.
2. Attribute Adjustment: Uses CHG commands (e.g., CHGDSPF) if needed to restore originals.

Module 2: Promotion Methods Explained

CSCO (Copy Source, Compile Object)

• For compilable objects: Copies source to target lib, compiles via create command.
• Example: For *PGM, uses CRTPGM with specified parms.

CSMO (Copy Source, Move Object)

• For non-compiled: Copies source, moves existing object to target.
• No create command; preserves attributes directly.

CSCD (Copy Source, Create Duplicate Object)

• Similar to CSMO but duplicates object in target.
• Useful for versioning or testing.

Module 3: Customizing Create Commands

Line Defaults in App Definitions

• Set in TURNOVER 1 > Work with App Definitions > Line Defaults.
• Create Parameters: Control command options (e.g., AUT(*ALL), REPLACE(*YES)).
• Bullet in User Guide: Details parms like TGTRLS, LIB, etc.

Changing Form Lines

• In forms (Chapter 6): Option 42 (Edit Form) > Select line > Modify create command/parms.
• Examples: Add FRCDTA(*YES) for files; specify BNDDIR for ILE programs.

When Customization is Needed

• Override defaults for specific objects (e.g., authority, journaling).
• Ensure compatibility with target environments (e.g., OS levels).

Module 4: Post-Creation Attribute Changes

How It Works

• After creation, TURNOVER® checks if attributes match originals.
• If not, applies CHG commands (e.g., CHGPGM for programs).
• Criteria: System-deemed necessities like owner, authority, or text.

Examples

• For *DSPF: CRTDSPF followed by CHGDSPF if text/owner differs.
• Limitations: Not all attributes changeable (e.g., some compile-time only).

Best Practices

• Test in dev: Run error checks to simulate.
• Document: Add form comments for audit trails.

Assessment and Next Steps

• Quiz Ideas: What does CSCO stand for? When does TURNOVER® apply CHG commands? Steps to customize a create parm?
• Practice: In a test setup, edit a form line to customize a CRTPF command and promote a file.
• Further Learning: User Guide (v101) Chapters 1 and 6; Developer’s Guide for workflows; Supplements #14 (Change Process), #54 (Auditing). Contact UNICOM support (tech.support@unicomsi.com or +1-603-924-8818) for current Release 2.100 details or custom command examples.