Fix (APAR): PK13494 Status: Fix Release: 6.0.2.3 Operating System: AIX,HP-UX,Linux,Linux Red Hat - pSeries,Linux zSeries,OS/390,OS/400,Solaris,Windows Supersedes Fixes: CMVC Defect: PK13494 Byte size of APAR: 7811 Date: 2006-01-23 Abstract: When creating or editting an ssl repetoire, entering the wrong password for the key file or trust file, the servant might hang. Description/symptom of problem: PK13494 resolves the following problem: ERROR DESCRIPTION: If you are creating a new ssl repetoire or editting a current ssl repetoire and you enter an invalid password, for either Key file password or Trust file password, the servant will hang and eventually abend. LOCAL FIX: PROBLEM SUMMARY USERS AFFECTED: All users of WebSphere Application Server V6.0.1 for z/OS PROBLEM DESCRIPTION: When creating or editting an ssl repetoire, entering the wrong password for the key file or trust file, the servant might hang. RECOMMENDATION: None Servant abends, with abend code ABEND=SEC3 and reason code REASON=04130007, if you enter the wrong password when creating/editting a ssl repetoire. PROBLEM CONCLUSION: When creating/editting a ssl repetoire we now will exit cleanly if the user enters the wrong password for the key file password or trust file password. APAR PK13494 is associated with Service Level (Fix Pack) 6.0.2.5 (Build Level cf50549.21) of WebSphere Application Server V6.0.1 for z/OS. Directions to apply fix: NOTE: Choose the: 1) Release the fix applies to 2) The Editions that apply 3) Delete the Editions & Methods that do not apply and this Note Fix applies to Editions: Release 6.0 __ Application Server (Express or BASE) __ Network Deployment (ND) __ WebSphere Business Integration Server Foundation (WBISF) __ Edge Components __ Developer __ Extended Deployment (XD) Install Fix to: Method: __ Application Server Nodes __ Deployment Manager Nodes __ Both NOTE: The user must: * Have Administrative rights in Windows, or be the Actual Root User in a UNIX environments. * Logged in with the same authority level when unpacking a fix, fix pack or refresh pack. * Be at V6.0.2.2 or newer of the Update Installer. This can be checked by reviewing the level of the Update Installer in file /updateinstaller/version.txt. The Update Installer can be downloaded from the following link: http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991 For detailed instructions to Extract the Update Installer see the following Technote: http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg21205400 1) Copy PKxxxxx.pak file 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. 3) Launch 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 (PKxxxxx.pak file which was copied in the maintenance directory). 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 environments. * 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. 2) Start Update Installer 3) Enter the installation location of the WebSphere product you want to remove the fix. 4) Select "Uninstall maintenance package" operation. 5) Enter the file name of the maintenance package to uninstall (PKxxxxx.pak). 6) UnInstall maintenance package. 7) Restart WebSphere Directions to re-apply fix: 1) Shutdown WebSphere. 2) Follow the Fix instructions to apply the fix. 3) Restart WebSphere. Additional Information: