IZ31302: PRESERVATION OF REBOOT FILE PREVENTS IT FROM RECEIVING FIXES

APAR status

• Closed as program error.

Error description

• Environment:
  ============
  
    ITM 6.2 Unix Installer
    The reported issue only occurs on an HP machine, but future
    fixes to the reboot files could cause any platform to have an
    issue.
  
  Problem Description:
  ====================
  
    The ITM 6.2 installer preserves the reboot files as is.  This
    change prevents APAR IY96372 from fixing a reboot file issue.
  
    IY96372 is an HP only problem, but this would be an issue for
    any reboot script errors that are fixed in ITM 6.2.  Ideally,
    the installer should merge any user customization with a newly
    generated reboot file.
  
  Detailed Recreation Procedure:
  ==============================
  
    1. Install the OS Agent for ITM 6.1 pre FP6 IF3
    2. Verify that the reboot file does not contain a path for the
       'su'  command.  See Workaround for information on finding
       the reboot file.
    3. Upgrade the OS Agent to ITM 6.2
    4. Verify that the reboot file still does not contain a path
       for the 'su' command
  
    NOTE:  If you upgrade from ITM 6.1 pre FP6 IF3 to ITM 6.1 FP6
    IF3 or above, you can see the full path for the 'su' command
    in the reboot file.  This is the fix that is lost with the
    preservation.
  
  .
  

Local fix

• Workaround:
  ===========
  
    1. Rename the generated ITM system reboot file.
  
    To find the reboot file:
    For AIX, it is /etc/rc.itm<n>.
    For Linux, Solaris, it is /etc/init.d/ITMAgents<n>.
    For HP-UX, it is /sbin/init.d/ITMAgents<n>.
    For all platforms, <n> comes from
    $CANDLEHOME/registry/AutoStart.
  
    2. Run UpdateAutoRun.sh as root.
  
    3. Once the install is verified, remove the old, renamed
       reboot file.
  
  Related Files and Output:
  =========================
    None.
  
  .
  

Problem summary

• Reboot file changes can not be properly applied due to installer
  preservation during a reboot file regeneration.
  
  The installer is trying to maintain the user settings that the
  customer directly edits in the reboot file.  But the user is not
  supposed to directly edit that file, he is supposed to use
  CANDLEHOME/config/kcirunas.cfg to define how to start a given
  agent.  If the installer were to continue to try and preserve
  that, then changes that the installer attempts to make to that
  file, like changing the SU program called, etc, wouldn't be
  properly updated.  This change fixes that behavior properly, and
  reminds the user that they should use
  CANDLEHOME/config/kcirunas.cfg as needed.
  

Problem conclusion

• Change the reboot files persistence methodology and reemphasis
  the use of the CANDLEHOME/config/kcirunas.cfg for agent starting
  user.
  
  
  The fix for this APAR is contained in the following maintenance
  packages:
  
     | fix pack | 6.2.0-TIV-ITM-FP0003
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  OMEG DIST INSTA

• Fixed component ID

  5608A41CI

Applicable component levels

• R620 PSY

     UP