Setting Up Additional TURNOVER for IBM-i Environments

Lesson Objectives

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

• Understand the benefits and considerations for setting up multiple TURNOVER® for iSeries (now Lifecycle Manager) environments, each with its own data library.
• Configure additional environments by duplicating or restoring data libraries, setting unique form prefixes, and managing Wisedesk integration for dynamic updating and escalation.
• Maintain separation between environments to avoid conflicts in IBM i libraries and applications.
• Handle practical setup steps, including library creation, environment file updates, and optional features like mail daemons or helpdesk processing.
• Apply best practices for multi-environment management, ensuring auditability and functionality across setups.

This summary condenses the 7-page supplement (v101, September 2018) into a guide for administrators. Multiple environments allow isolated change management (e.g., for separate teams or products). As of October 26, 2025, no newer public version of Supplement #32 was found via web searches; the product is TURNOVER® Lifecycle Manager (Release 2.100+), with similar multi-environment support for managing applications at multiple release levels. Check the current Administrator’s Guide for updates, as core concepts like data library separation remain relevant.

Key Concepts

• Multiple Environments: Each uses a separate data library (e.g., SOFTTURND2) for isolated apps, forms, projects; shares product/language libs (SOFTTURN, SOFTTURNE).
• Form Prefixes: Unique per environment (e.g., 50 for second, 33/66 for third/fourth) to avoid overlaps.
• Wisedesk Integration: Optional for dynamic updating/escalation; requires separate jobs per env.
• Library Separation: Avoid sharing IBM i libs across envs to prevent conflicts.
• Prerequisites: TURNOVER® v101+; review Chapter 5 of Getting Started Guide; clean data lib from install.

Module 1: Before You Start

Planning Considerations

• Why Multiple Envs?: For separate groups/products; duplicate SOFTTURND or use clean install lib.
• Wisedesk Setup: Enable for updating/escalation in additional envs; instructions included.
• Reference: Read Getting Started Guide Chapter 5 for overview.
• Library Access: Envs can access same IBM i libs; avoid overlap in app defs.
• Form Prefixes: Set unique (e.g., start at 0 for primary; 50 for secondary); prevents duplicates.

Module 2: Setting Up Additional Environments

Step-by-Step Configuration

1. Create Data Library: Save/restore SOFTTURND to SOFTTURND2 (or clean from install).
2. Update Environment File: WRKTOENV > Add record: Data lib (SOFTTURND2), product/language (defaults), unique prefix.
3. Set Form Prefix: In new env, set global defaults (TURNOVER 1 > F22 > Utilities > Global Defaults > Form prefix).
4. Access New Env: Use SOFTTURND2/TURNOVER command; switch via F22 on main menu.
5. Optional: Wisedesk/Helpdesk:
   • Duplicate WISEDESK jobs for new env (e.g., WDDYNUPD2, WDESCPROC2).
   • Update job descs with new data lib in lib list.
   • Add to TSERVER autostart.

Handling Multiple Envs

• Commands: Create aliases (e.g., TURNOVER2 for new env).
• Distributions: Match env names on sender/receiver; use different prefixes.
• Mail Daemon: If used, configure to poll multiple queues (Supplement #52).

Module 3: Best Practices and Troubleshooting

Best Practices

• Isolation: Define distinct apps/forms/projects per env.
• Testing: Verify by running a form in new env; check for conflicts.
• Scaling: For >2 envs, use prefixes like 25/50/75 to allow growth.
• Backups: Backup all data libs separately.

Troubleshooting

• Conflicts: If libs overlap, redefine apps to separate.
• Form Duplicates: Ensure unique prefixes; check form numbers.
• Wisedesk Issues: Verify job lib lists include correct data lib.

Assessment and Next Steps

• Quiz Ideas: Why unique form prefixes? Steps to add a second env? Handling Wisedesk in multiples?
• Practice: Restore a clean data lib, add env record, set prefix, test a form.
• Further Learning: Getting Started Guide Chapter 5; Administrator’s Guide (Release 2.100) for envs; Supplements #52 (Mail Daemon), #14 (Change Process).