IBM Support

Submitting an iFix Request for AIX or VIO Server to IBM Technical Support

General Page

This document provides instructions for requesting an Interim Fix (iFix) from IBM Technical Support to address an APAR issue in AIX or VIO server.
It covers the definition of iFix, the prerequisites and guidance for submitting an iFix request.
 
 
 

What is an iFix?

An iFix (Interim Fix) is a temporary, custom-built patch designed to address an APAR(Authorized Program Analysis Report) in AIX or VIO server environments until a permanent fix is available.
iFixes are used when the APAR cannot be avoided by a workaround and a permanent fix is not available in the current or latest Service Pack or Technology Level.
 
 
 

How to Determine if an AIX or VIO Server is vulnerable to a critical APAR?
 
 
  • IBM’s My Notifications service is the primary method for receiving alerts about critical APARs. Subscribe to notifications for each AIX or VIOS release to receive updates on Security, HIPER, and PE APARs. Upon receiving a notification, promptly review it to assess applicability to your environment or open a case with IBM Support to request further assistance with this task. Be sure to upload system snap data as outlined in Working with IBM AIX Support: Collecting snap data.
 
  • FLRT (Fix Level Recommendation Tool) can help evaluate if a system is vulnerable to APARs by inputting the current system level. 
    FLRT also has links to the “AIX HIPER Tables”  which provide a very useful view of what HIPER APAR problems each release is exposed to, and where to get fixes. This includes links to the Bulletin with more information and links to download the fix either as an Interim Fix or Service Pack.
 
 
 
 
When to Request an iFix?
 
  • An APAR impacts system functionality, and no workaround exists.
  • The permanent fix is not available in a Service Pack or Technology Level.
  • The permanent fix is included in a later Service Pack or Technology Level, but immediate update to the fixing Service Pack or Technology Level is not feasible.
 
 
 
 
iFix Request Prerequisites
 
The system must be running an active Technology Level supported by IBM.

To verify compliance with this requirement, please consult the relevant IBM Documentation:
 
 
 

General Recommendations
 
Recommendation 1: Update to the Technology Level or Service Pack containing the permanent fix during the next planned maintenance window.
 
Recommendation 2: Request an iFix only if updating is not possible and the issue is critical.
 
Recommendation 3: Installing an iFix may require a server reboot or using liveupdate to apply the fix immediately.
 
  • To determine if reboot is required, verify the REBOOT value in the interim fix control file.
  • To determine if the ifix is suitable for Live Update operation, verify the LKU_CAPABLE value in the interim fix control file.

 

# emgr -de IJXXXXXxxx.yymmdd.epkg.Z -v3 |egrep "REBOOT REQUIRED|LU CAPABLE"

REBOOT REQUIRED: yes
LU CAPABLE: yes

 
  •  REBOOT REQUIRED
        Specifies whether a reboot is required for this interim fix.
        Allowable values are yes or no.
        If this value is set to yes, the emgr command will make changes as necessary to the boot image and issue a message instructing the user to reboot after   installation.
 
 
  •  LU CAPABLE
        Specifies whether this interim fix is compatible with the Live Update operation. This attribute can have a value of yes or no. Ideally, all interim fixes must be marked as Live Update capable.
        This compatibility is needed to install interim fixes as a group.
        If an interim fix is not suitable for a Live Update operation, the LU_CAPABLE attribute is set to the value of no, however most of the interim fixes have this attribute set to the value of yes.
 
 

Before requesting an iFix, assess whether updating the server to a Technology Level or Service Pack that includes the permanent fix is a better option, especially if a maintenance window is available.
 
 
 

How to submit an iFix Request?
 
To submit an iFix Rquest for AIX or VIOS, please open a case with IBM Support.
 
  • Clearly state the request for an iFix.
  • Note any urgency or business impact to prioritize the request.
  • Provide system and problem information: include details about the issue, such as error messages, system impact, and affected components.
  • Upload diagnostic data (snap) from the affected system as outlined in Working with IBM AIX Support: Collecting snap data.
 
 
IBM will evaluate the iFix request for feasibility. Some requests may be denied due to risk or complexity.
If approved, IBM Technical Support will provide the iFix and communicate next steps. If denied, IBM Technical Support will explain the reasons (e.g., risk or complexity).
 
 
 
 
Recommended Documentation
 
 
 
 
 
 
 

[{"Type":"MASTER","Line of Business":{"code":"LOB08","label":"Cognitive Systems"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SWG10","label":"AIX"},"ARM Category":[{"code":"a8m0z000000cw02AAA","label":"APARS"},{"code":"a8m0z0000001fMuAAI","label":"General Support(Admin)"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"},{"Type":"MASTER","Line of Business":{"code":"LOB57","label":"Power"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSPHKW","label":"PowerVM Virtual I\/O Server"},"ARM Category":[{"code":"a8m50000000L0OPAA0","label":"UPDATE-\u003Eifixes"}],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]

Document Information

Modified date:
08 November 2025

UID

ibm17232610

Page Feedback