Lesson Objectives
By the end of this lesson, you will be able to:
- Understand the three licensed versions of TURNOVER® for iSeries (now known as TURNOVER® Lifecycle Manager): development (standard), remote (production), and hub.
- Identify key functional differences between the development version and the production/hub versions, including menu options, commands, and limitations.
- Determine which version to install based on your IBM i environment's role (e.g., development vs. distribution targets).
- Apply licensing and authorization processes to activate the correct version.
- Recognize how these versions support distributed change management in multi-system setups.
This summary condenses the 3-page supplement (v101, September 2018) into a guide for administrators deploying TURNOVER® in distributed IBM i environments. The supplement focuses on how production/remote and hub versions differ from the full development version described in the main guides. As of October 24, 2025, the product is rebranded as TURNOVER® Lifecycle Manager (with releases like v101 from 2018 still referenced in legacy contexts), but the version distinctions for development, production, and hub remain conceptually similar based on current product overviews. Modern releases emphasize application modernization (e.g., DDS to DDL conversions), but check UNICOM support for exact differences in post-2018 versions.
Key Concepts
- Development Version (Standard): Full-featured for creating, editing, and distributing changes; installed on dev systems.
- Remote Version (Production): Receive-only; installed on non-dev targets for installing distributed changes.
- Hub Version: Receive and redistribute; acts as an intermediate for multi-tier distributions.
- Licensing: Version determined by authorization code; all share core libraries but restrict features.
- Menu/Command Differences: Production/hub limit options to reception/distribution; no dev tools like PWM or helpdesk.
- Prerequisites: IBM i 7.1+; TURNOVER® installed via M4LODRUN; valid license files from UNICOM.
Module 1: Overview of TURNOVER® Versions
Three Licensed Versions
- Development: Comprehensive for change creation (e.g., worklists, forms, projects); described in main User/Developer Guides.
- Remote/Production: For endpoint systems; receives/installs changes via distributions (e.g., *FTP/*SNA); no creation/editing.
- Hub: For intermediaries; receives, installs, and forwards changes to other remotes.
How Versions Are Determined
- Based on license/authorization code applied during install (via M4VFYLIC or TWRKLIC).
- All versions use same libraries (e.g., SOFTTURN, SOFTTURND); features restricted by code.
Module 2: Functional Differences in Production/Hub Versions
Main Menu Restrictions
- Development: Full options (1: Applications, 4: History, 5: Checkout, 6: Forms, 7: Projects, 8: Helpdesk, 10: Reports, etc.).
- Production/Hub: Limited to reception-focused:
- Option 6: Work with Forms (receive/install only; no creation).
- Option 10: Reports (subset for form status/history).
- No PWM (STRPWM), helpdesk, projects, or checkout menus.
Command Differences
- Common: TURNOVER (main menu), WRKTOFRM (forms), WRKTORPT (reports).
- Restricted in Production/Hub: No STRPWM, WORKTASK, TURNOVER 1/5/7/8; limited to distribution commands like TOAUTORCV (auto-receive).
Distribution Handling
- Production: Receives forms/objects from dev/hub; installs automatically or manually.
- Hub: Receives, installs, then redistributes to downstream remotes (e.g., via form overrides).
- Both: Support *FTP/*SNA; configure in global defaults or remotes.
Other Limitations
- No app definitions editing (Option 1).
- No object checkout/reservation (Option 5).
- Archiving/history viewing available but read-only.
- Hub adds redistribution capabilities (e.g., forward forms).
Module 3: Installation and Configuration
Installing Production/Hub Versions
- Use same M4LODRUN process as development (see Getting Started Guide).
- Set type: R=Remote (production) or H=Hub during install panels.
- Apply license: Production/hub codes restrict features; dev code enables full.
Post-Install Setup
- Autostart Jobs: TSERVER subsystem with TOAUTORCV for auto-receive.
- Distributions: Configure remotes in dev version; production/hub handle incoming.
- Testing: Send test form from dev to verify reception/install.
Upgrading
- Follow upgrade guide; preserve data libs; reapply license for version.
Assessment and Next Steps
- Quiz Ideas: What distinguishes hub from production versions? Which menu options are unavailable in production? How is the version determined?
- Practice: In a multi-IBM i setup, install production version on a target, send a form from dev, and verify installation.
- Further Learning: User Guide (v101) for menus; Administrator’s Guide (Release 2.100) for distributions; Supplements #8 (Alt Distribution Methods), #14 (Change Process). Contact UNICOM support (tech.support@unicomsi.com or +1-603-924-8818) for 2025 licensing or version migration assistance.