TURNOVER Synchronizer User Guide

Lesson Objectives

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

• Understand the purpose of the TURNOVER® Synchronizer tool for managing vendor software releases and custom modifications on IBM i.
• Configure Synchronizer for tracking base vendor code, user modifications, and merging updates during upgrades.
• Perform synchronization processes, including baseline setup, modification tracking, and release merges.
• Use reports, utilities, and interfaces to audit and resolve conflicts in synchronized environments.
• Apply best practices for multi-release management and integration with TURNOVER® change workflows.

This summary condenses the 84-page guide (likely pre-2018 edition) into practical modules for developers and administrators. Synchronizer is a subsystem in TURNOVER® for iSeries (now Lifecycle Manager) for vendor release management, handling base code syncing with custom changes. Based on web searches as of October 26, 2025, no newer public Synchronizer User Guide was found; it appears integrated into TURNOVER® Lifecycle Manager v100+ documentation, with mentions in migration guides for vendor sync tools. Check UNICOM/SoftLanding support for updates or Release 2.100+ equivalents.

Key Concepts

• Synchronizer Role: Manages vendor software (e.g., JDE, BPCS) by tracking base releases, user mods, and merging new vendor updates without losing customs.
• Components: Baselines (vendor code snapshots), modification libraries, merge utilities, reports for conflicts/audits.
• Workflow: Setup baselines, track changes via TURNOVER®, merge new releases, resolve conflicts.
• Integrations: Works with PWM/forms for changes; supports multi-level envs.
• Prerequisites: TURNOVER® v100+; vendor software installed; cross-references (e.g., Hawkeye).

Module 1: Introduction to Synchronizer

Overview

• Synchronizer provides tools for vendor release management: Baseline vendor code, apply mods via TURNOVER®, merge updates.
• Benefits: Preserves customs during upgrades, audits changes, reduces manual merges.

Key Terms

• Baseline: Vendor release snapshot (e.g., libs/objects/source).
• Modifications: User changes tracked in separate libs.
• Merge: Combine new vendor release with existing mods; resolve conflicts.

Module 2: Configuring Synchronizer

Setup Steps

• Install/Verify: Part of TURNOVER®; access via menu (TURNOVER 1 > Utilities > Synchronizer).
• Define Baselines: Create for vendor releases (e.g., specify libs, types); use WRKBASELINE.
• Modification Libs: Set up for customs (e.g., MODSRC, MODOBJ); integrate with app defs.
• Type Codes: Custom for vendor types; ensure *SYNC method for merges.
• Exits/APIs: Optional for custom merge logic (Supplement #30).

Multi-Release Support

• Handle multiple vendor versions (e.g., baseline per release); use for testing upgrades.

Module 3: Managing Synchronization Workflows

Baseline Creation

• Capture vendor code: Run baseline utility on install libs; store in ARCHIVESRC or dedicated libs.

Tracking Modifications

• Use PWM: Checkout from baseline, edit in mod libs, compile/test.
• Forms: Promote mods with sync awareness; track via history.

Merging New Releases

• Load new vendor: Create new baseline.
• Merge: Run sync utility; compare old baseline + mods vs. new; auto-merge or flag conflicts.
• Resolve: Manual via compare tools (e.g., CMPSRCMBR); reapply mods.

Module 4: Reports, Utilities, and Auditing

Reports

• Conflict Reports: List merge issues (e.g., changed vendor code overlapping mods).
• Modification Summaries: Track customs per release.
• Audit Trails: Integrate with TURNOVER® history (Option 4).

Utilities

• Baseline Compare: Diff releases.
• Mod Reapply: Automate after merge.
• Cleanup: Remove obsolete baselines.

Integrations

• With Helpdesk/Projects: Link vendor updates to tasks.
• Distributions: Sync across remotes.

Module 5: Troubleshooting and Best Practices

Common Issues

• Conflicts: Use cross-ref to identify; resolve manually.
• Baseline Mismatches: Verify lib setups.
• Performance: For large vendors, run merges in batch.

Best Practices

• Regular Baselines: Create on each vendor update.
• Test Merges: In dev env before prod.
• Compliance: Use for SOX audits via reports.

Assessment and Next Steps

• Quiz Ideas: Purpose of baselines? Steps for merging a new release? Handling conflicts?
• Practice: Set up a test baseline for a vendor lib, apply a mod, merge a "new" release.
• Further Learning: User Guide (v101) for PWM; Administrator’s Guide (Release 2.100) for utilities; Supplements #14 (Change Process), #30 (Exits/APIs).