Fix (APAR): PI70169 Status: Fix Release: 8.0.0.12,8.0.0.11,8.0.0.10,8.0.0.9,8.0.0.8,8.0.0.7,8.0.0.6,8.0.0.5,8.0.0.4,8.0.0.3,8.0.0.2 Operating System: AIX,HP-UX,IBM i,Linux,OS X,Solaris,Windows,iOS,z/OS Supersedes Fixes: CMVC Defect: xxxxxx Byte size of APAR: 282990 Date: 2016-12-02 Abstract: Confidential for Security Integrity ifix Description/symptom of problem: PI70169 resolves the following problem: ERROR DESCRIPTION: Confidential for Security Integrity ifix. LOCAL FIX: N/A PROBLEM SUMMARY: Confidential for Security Integrity ifix. PROBLEM CONCLUSION: Confidential for Security Integrity ifix. Directions to apply fix: NOTE: Mark with an X the: 1) Release the fix applies to 2) The Editions that apply 3) And then DELETE THIS NOTE Fix applies to Editions: Release 8.0 __ Application Server (Express or BASE) __ Network Deployment (ND) __ Edge Components __ Developer Install Fix to all WebSphere installations unless special instructions are included below. Special Instructions: None NOTE: The user must: * Logged in with the same authority level when unpacking a fix, fix pack or refresh pack. * Be at V1.4.3 or newer of the Installation Manager. Certain iFixes may require a newer version of the Installation Manager and the Installation Manager will inform you during the installation process if a newer version is required. The IBM Knowledge Center can provide details, if needed, on the use of the Installation Manager to apply the iFixes. http://publib.boulder.ibm.com/infocenter/install/v1r4/index.jsp. Shutdown WebSphere Application Server before applying the iFixes. Restart WebSphere Application Server after applying the iFixes. Directions to remove fix: The IBM Knowledge Center can provide details, if needed, on the use of the Installation Manager to remove the iFixes. http://publib.boulder.ibm.com/infocenter/install/v1r4/index.jsp. Shutdown WebSphere Application Server before removing the iFixes. Restart WebSphere Application Server after removing the iFixes. Directions to re-apply fix: 1) Shutdown WebSphere Application Server. 2) Follow the Fix instructions to apply the fix. 3) Restart WebSphere Application Server. Additional Information: