Fix (APAR):  PK64375

Status:  Fix

Release:  6.0.2.25,6.0.2.27

Operating System:  AIX,HP-UX,i5/OS,Linux,Linux pSeries,OS/400,Solaris,Windows

Supersedes Fixes:  

CMVC Defect:  PK64375

Byte size of APAR:  11356

Date: 2008-04-14

Abstract:   CHANGING THE ROLLOVER FILE SIZE FOR THE DIAGNOSTIC TRACE FILE SETS THE WRONG FILE SIZE VALUE

Description/symptom of problem:  
PK64375 resolves the following problems:

The rollover size of a trace file can                          
be set in the admin console under Troubleshooting->Logs  and      
Trace-> "server name" ->Diagnostic Trace->"Runtime" tab.  When a  
 user enters the rollover size into the "Maximum File Size"       
field, the value entered will be saved as the wrong value         
where the value gets multiplied by 1048576.                       

APAR PK64375 will only occur when PK60511 has been applied.  
Therefore, only apply interim fix 6.0.2.25-WS-WAS-IFPK64375 when the level is at either one of these levels:                                              
- Websphere v6.0.2.25 + applied ifix IFPK60511
- WebSphere v6.0.2.27
                                
                                                                 
1. Navigate to Logging and Tracing for any server, Diagnostic     
Trace Service -> Runtime.                                         
                                                                  
2. Select File and change the Maximum File Size to "1" or any     
number.Hit Apply and OK.                                          
                                                                  
3. Go into Diagnostic Trace Service -> Runtime again. You will    
see that the number entered previously has been "converted"       
incorrectly to bytes  (in this case "1048576"), even though the   
field is MB. Looking at the  growth of the trace file, it seems   
that a value entered as 1MB and converted is really allowing a    
max of 1048576MB (or 1TB).                                        


Directions to apply fix:  Fix applies to Editions:
Release 6.0
_X Application Server (Express or BASE)
_X 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
X_ 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 <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=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 6.0.2.25-WS-WAS-IFPK64375.pak file directly to the maintenance directory

2) Shutdown the Applicaiton Server.
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 Application Server product you want to update.

5) Select the "Install maintenance package" operation.

6) Enter the file name of the maintenance package to install (6.0.2.25-WS-WAS-IFPK64375.pak file which was copied in the maintenance directory).

7) Install the maintenance package.

8) Restart the Application Server.

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 Application Server product you want to remove the fix.

4) Select  "Uninstall maintenance package" operation.

5) Enter the file name of the maintenance package to uninstall (6.0.2.25-WS-WAS-IFPK64375.pak).

6) Uninstall maintenance package.

7) Restart the Application Server

Directions to re-apply fix:  
1) Shutdown the Application Server.

2) Follow the Fix instructions to apply the fix.

3) Restart the Application Server.



Additional Information: