Emergency Changes in TURNOVER

Lesson Objectives

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

• Understand the two methods for handling emergency software changes in TURNOVER® for iSeries (now Lifecycle Manager): emergency change applications and multiple checkouts.
• Configure an emergency change application, including setting flags and managing access restrictions.
• Use multiple checkout features to allow concurrent work on objects without conflicts.
• Apply best practices for emergency changes, including testing, promotion, and auditing.
• Recognize how these features support compliance and minimize downtime in production environments.

This summary distills the 5-page supplement (v101, September 2018) into key sections for developers and administrators. Emergency changes address urgent fixes while maintaining control and auditability. As of October 24, 2025, the product is TURNOVER® Lifecycle Manager (current Release 2.100+), and while core concepts remain, check UNICOM support for any updates to these processes, as integrations like ProGen Plus still reference emergency fixes.

Key Concepts

• Emergency Change Application: Recommended; a single-level app for overriding checkouts, allowing fixes in a separate dev library before production return. Restricted to authorized users.
• Multiple Checkout: Allows simultaneous checkouts without a separate app; useful for collaborative fixes but less controlled.
• Checkout Override: Emergency apps ignore existing checkouts; multiple checkout prompts for confirmation.
• Auditing and Security: Both methods maintain history; restrict emergency access via user classes/authorities.
• Prerequisites: Defined applications, cross-references, and PWM familiarity; refer to User Guide Chapter 1 for app definitions.

Module 1: Overview of Emergency Changes

Why Emergency Changes?

• Handle urgent production issues without waiting for checked-out objects to be released.
• Balance speed with control: Test fixes separately to avoid disrupting ongoing work.

Two Methods Compared

• Emergency Application: Structured; uses a dedicated app (e.g., single-level) for overrides. Ideal for restricted, auditable fixes.
• Multiple Checkout: Flexible; no new app needed. Suitable for teams where concurrent work is common.

Module 2: Using an Emergency Change Application

Defining the Application

• In TURNOVER 1 menu: Work with Application Definitions > Select app > Set Emergency flag to Y.
• Typically single-level: Dev to Prod promotion.
• Restrict access: Use user classes (e.g., Emergency Programmer) and authorities.

Performing an Emergency Change

1. Checkout: Use emergency app to override existing checkout; source copies to your dev lib.
2. Edit and Test: Modify/test in separate lib.
3. Create Form: Build PWM form; promote to production.
4. Post-Promotion: Original checkout remains; merge changes if needed.

Best Practices

• Limit users: Only ops/support teams.
• Audit: Review history/forms for compliance.

Module 3: Using Multiple Checkout

Enabling Multiple Checkout

• Global Default: TURNOVER 1 > F22 > Option 1 (Utilities) > 3 (Global Defaults) > Set Multiple checkouts allowed to Y.
• Per-App Override: In app definition, set flag to Y.

Performing a Multiple Checkout

1. Attempt Checkout: If object is checked out, prompt appears: "Object is checked out to another user. Allow multiple checkout?"
2. Confirm: Enter Y to proceed; creates your copy in dev lib.
3. Work and Promote: Edit/test/compile; create form for promotion.
4. Resolution: Communicate with original user; merge changes post-emergency.

Considerations

• Risks: Potential conflicts; use for low-risk scenarios.
• Auditing: Tracks all checkouts in history.

Assessment and Next Steps

• Quiz Ideas: Difference between methods? Steps to define an emergency app? When to use multiple checkout?
• Practice: In a test IBM i, set up an emergency app, override a checkout, and promote a fix.
• Further Learning: User Guide (v101 or current Release 2.100) Chapter 1; Developer’s Guide for workflows; Supplements #14 (Change Process) and #50 (iASPs). Contact UNICOM support (tech.support@unicomsi.com or +1-603-924-8818) for 2025 updates or licensing.