Lesson Objectives
By the end of this lesson, you will be able to:
- Understand the purpose of mirroring IBM i systems with TURNOVER® for iSeries (now Lifecycle Manager) installed, including high availability and disaster recovery scenarios.
- Identify which TURNOVER® libraries, files, and objects should and should not be mirrored to ensure functionality on the mirror system.
- Configure mirroring packages to handle TURNOVER®-specific items, such as excluding temporary work libraries and save files to avoid locks or failures.
- Apply considerations for non-default installations, like custom library names or consolidated setups.
- Troubleshoot potential issues, such as distribution failures due to locked save files, and ensure the mirror system is operational.
This summary condenses the 3-page supplement (v101, September 2018) into a guide for system administrators using mirroring tools (e.g., IBM PowerHA, MIMIX). Mirroring replicates data for failover; this ensures TURNOVER® remains functional. As of October 24, 2025, no newer public version of Supplement #51 or direct updates on mirroring were found via web searches on UNICOM/SoftLanding sites; concepts likely apply to TURNOVER® Lifecycle Manager Release 2.100 (2022), but verify with support for modern high-availability integrations.
Key Concepts
- Mirroring Reasons: High availability, disaster recovery; packages like PowerHA replicate libs/files.
- TURNOVER® Components: Product (SOFTTURN), data (SOFTTURND), language (SOFTTURNE); may be custom/consolidated.
- Do Not Mirror: Temp items (e.g., form work libs TnnnnnnnW), save files (locks cause failures), certain data areas (e.g., xxCHECK).
- Mirror: Core libs (SOFTTURN/D/E), archives (ARCHIVESRC), QGPL commands, profiles (TURNOVER, etc.), TSERVER subsystem, /TURNOVER IFS folder.
- Prerequisites: TURNOVER® v101+; mirroring package; understand custom installs (e.g., single lib vs. three).
Module 1: Introduction to Mirroring with TURNOVER®
Why Mirror TURNOVER® Systems?
- Ensures mirror is functional for failover; replicates change management data/processes.
- Considerations: Custom lib names (not defaults); consolidated installs (one lib).
General Guidelines
- Mirror core for consistency; exclude temps to prevent locks/failures on live system.
Module 2: What Not to Mirror
Excluded Items
- Data Areas: xxCHECK, xxCODE, CSCHEKxxxx, CSCODExxxx (alphanumeric vars).
- Save Files: In product lib (SOFTTURN); locks disrupt distributions.
- Work Libraries: Dynamic; exclude to avoid interference:
- Form archive: TnnnnnnnDa (n=form#, a=ASP).
- Form work: TnnnnnnnW.
- Explode archive: Tnnnnnnncc (c=counter).
- Explode recovery: Znnnnnnncc.
- PDQ explode staging: Xnnnnnnncc.
- Distribution staging: TnnnnnnnS.
- Distribution save: Thhmmssjjj (hhmmss=time, j=job#).
Reasons for Exclusion
- Temps are transient; mirroring locks them, causing intermittent failures (e.g., distributions).
Module 3: What to Mirror
Essential Components
- Libraries: SOFTTURN (product), SOFTTURND (data), SOFTTURNE (language), ARCHIVESRC (archives); custom if renamed.
- Commands: QGPL/TURNOVER, STRPWM, etc.; ensure replicated.
- Profiles: TURNOVER, TOMSGRCV, TURNESCQ, TURCRARE, WISEDESK (autostart users).
- Subsystem: TSERVER in QGPL; include descriptions/jobs.
- IFS Folder: /TURNOVER (configs, logs); mirror for completeness.
- Other: Form libs if persistent; all non-temp data for full functionality.
Post-Mirror Setup
- On failover: Apply licenses; start TSERVER; verify distributions.
Module 4: Troubleshooting and Best Practices
Common Issues
- Distribution Failures: Locked save files; exclude them.
- Custom Installs: Verify lib names; adjust mirroring rules.
- ASP/iASP: Handle a=ASP in lib names; mirror accordingly (Supplement #50).
Best Practices
- Test Failover: Simulate switch; ensure TURNOVER® works (e.g., run form).
- Monitor: Check mirroring logs for exclusions.
- Updates: After TURNOVER® upgrades, review for new temps.
Assessment and Next Steps
- Quiz Ideas: Libraries to mirror? Why exclude save files? Handling custom lib names?
- Practice: In a test setup, configure mirroring to exclude work libs; simulate failover and test TURNOVER®.
- Further Learning: Administrator’s Guide (Release 2.100) for HA; Supplements #50 (iASPs), #14 (Change Process). Contact UNICOM support (tech.support@unicomsi.com or +1-603-924-8818) for 2025 mirroring integrations or PowerHA specifics.