Fix (APAR):  PM05197

Status:  Fix

Release:  6.1

Operating System:  AIX,HP-UX,Linux,Solaris,Windows

Supersedes Fixes:  PK91723, PK93490, PK95432, PK96361, PK99842, PM00797

PRE-REQUISITE FIXES:       

EXCLUSIVE-REQUISITE FIXES:

CMVC Defect:  PM05197

Byte size of APAR:  7962255

Date: 2009-09-30

Abstract:  WebSphere Extended Deployment Compute Grid version 6.1.0.5. cumulative fix.

Description/symptom of problem:  
PM05197 resolves the following problem:



This Compute Grid cumulative fix is correcting the following problems:

- All problems reported on PK91723, PK93490, PK95432, PK96361, PK99842 and PM00797.
- Parallel Job Manager incorrectly removes top level job context before calling afterCompletion() SPI.



Directions to apply fix:  

  Fix applies to Editions:
    Release:
    6.0   6.1
    ___   ___ Application Server (Express or Base)
    ___   ___ Network Deployment  (ND)
    ___   ___ WebSphere Business Integration Server Foundation (WBISF)
    ___   ___ Edge Components
    ___   ___ Developer
    ___   _X_ Extended Deployment (XD)

  Install Fix To:
    Method:
    __ Application Server Nodes
    __ Deployment Manager Nodes
    X_ Both

  NOTE:
    The user must:
       * Have Administrative rights in Windows, or be the Actual Root User in a UNIX environment.
       * Be Logged in with the same authority level when unpacking a fix, fix pack or refresh pack.
       * Be at V7.0.0.5 or later of the Update Installer. This can be checked by reviewing the level
         of the Update Installer in file <was_root>/updateInstaller/version.txt

  The update Installer can be downloaded from the following link:
       http://www.ibm.com/support/docview.wss?rs=180&uid=swg24012718

  For detailed instructions on how to extract the Update Installer see the following Technote:
       http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg27006162

  1) Copy 6.1.0.5-WS-WXDCG-IFPM05197A.pak and 6.1.0.5-WS-WXDCG-IFPM05197B.pak files directly to the maintenance directory.

  2) Shutdown WebSphere. 
     Manually execute setupCmdLine.bat in Windows or ../setupCmdLine.sh in UNIX from the 
     WebSphere instance that maintenance is being applied to.
     It is important that you perform a controlled and complete shutdown of the server to ensure
     that all transactions have completed, before installing the fix.

  3) Launch the Update Installer.

  4) Enter the installation location of the WebSphere product you want to update.

  5) Select the "Install maintenance package" operation.

  6) Enter the file name of the maintenance package to install.

  7) Install the maintenance package.

  8) Restart WebSphere.




Directions to remove fix:  

  NOTE:
    * The user must have Administrative rights in Windows, or be the Actual Root User in a UNIX environment.
    * FIXES MUST BE REMOVED IN THE ORDER THEY WERE APPLIED.
    * DO NOT REMOVE A FIX UNLESS ALL FIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED.
    * YOU MAY REAPPLY ANY REMOVED FIX.

  Example:  If your system has fix1, fix2, and fix3 applied in that order and fix2 is to be
            removed, fix3 must be removed first, fix2 removed, and fix3 re-applied.

  1) Shutdown WebSphere. 
     Manually execute setupCmdLine.bat in Windows or ../setupCmdLine.sh in UNIX from the WebSphere
     instance that uninstall is being run against.
     It is important that you perform a controlled and complete shutdown of the server to ensure
     that all transactions have completed, before installing the fix.

  2) Launch the Update Installer.

  3) Enter the installation location of the WebSphere product you want to remove the fix.

  4) Select the "Uninstall maintenance package" operation.

  5) Enter the file name of the maintenance package to uninstall.

  6) Uninstall the maintenance package.

  7) Restart WebSphere.




Directions to re-apply fix:  

  1) Shutdown WebSphere. 
     It is important that you perform a controlled and complete shutdown of the server to ensure
     that all transactions have completed, before installing the fix.

  2) Follow the instructions to apply the fix.

  3) Restart WebSphere.




Additional Information: