eFix (APAR): PQ63508
Status:      fix

Release: WebSphere 4.0.3

Edition: WebSphere AE

ContainerTypes: AEServer

Operating System: All supported platforms for WebSphere AE

CMVC defect:  PQ63508

Supersedes eFixes: PQ60191 PQ60772

Byte size of APAR:   1,125,244 Bytes

Date: July 29, 2002

Abstract: On console, appserver environment var overwritten when update other properties.

Description/symptom of problem: 

On console, appserver environment variable overwritten to null or other appserver environment values
when update other appserver properties.

Example on how to reproduce problem with env var on other servers get   
changed when changed one server:                                      
0. WAS setup with 2 appservers A and B                                  
1. On ServerA General tab, change env var to {foo,bar}, click OK, click 
APPLY                                                                   
2. go to ServerB, DO NOT open Environment Editor on ServerB, go         
directly to JVM Settings tab, change java heap size, click APPLY        
3. go to ServerB General tab, open Environement Editor, whatever values 
B had are gone, values now {foo,bar}   


Directions to apply efix:

1) Create temporary "efix" directory to store the jar file:
             AIX: /tmp/WebSphere/efix
   Solaris/Linux: /tmp/WebSphere/efix
         Windows: c:\temp\WebSphere\efix

2) Copy jar file to the directory

3) Shutdown WebSphere

4) Run the jar file with the following command answering questions/
prompts as they appear: java -jar <jarfile name>

5) Restart WebSphere

6) The temp directory may be removed but the jar file should be saved.
Do not remove any files created and stored in the:

 <WASHOME>/WebSphere/ AppServer/efix/<efix> 

directories. These files are required if an efix is to be removed.



Directions to remove an efix:

NOTE:  EFIXES MUST BE REMOVED IN THE ORDER THEY WERE APPLIED.  DO NOT
REMOVE AN EFIX UNLESS ALL EFIXES APPLIED AFTER IT HAVE FIRST BEEN
REMOVED.  YOU MAY REAPPLY ANY REMOVED EFIX.

Example:  If your system has efix1, efix2, and efix3 applied in that
order and efix2 is to be removed, efix3 must be removed first, efix2
removed, and efix3 re-applied.


1) Change directory to the efix location:

 (<WASHOME>/WebSphere/AppServer/efix/<efix#>).

2) Shutdown WebSphere

3) Run the backup jar file with the following command:
   java -jar <backup_efix#>

4) Restart WebSphere



Directions to re-apply an efix:

Follow the instructions for applying an efix.  If the backup files
still exist (from the previous efix application), you will be
prompted to overwrite.  Answer "yes" at the overwrite  prompts.



Additional Information:
------------------------------------------------------------------
(From PQ60191)

Abstract:  wscp always exits with a return code of 0.

Description/symptom of problem: The wscp script always exits with a
return code of 0 so there is no way to programatically check to see
whether or not the command was successful.

This test fix changes the behavior when wscp is run in command mode, 
e.g.:

     wscp -c "ApplicationServer list"

or when wscp is run in script mode:

     wscp -f myscript.tcl

so that a non-zero code is returned if an error is detected.  

>>>PLEASE NOTE:  TO HAVE wscp RETURN A CODE BASED ON WHETHER OR NOT AN
>>>ERROR WAS DETECTED, IT IS NECESSARY TO SET THE SYSTEM PROPERTY:

>>>     wscp.useNewRetCode

>>>TO SOME NON-NULL VALUE.  THIS MAY BE DONE IN THE SAME WAY THAT:

>>>     wscp.traceString

>>>IS SET (PLEASE SEE 6.6.0.2.2.3.7 OF THE WEBSPHERE 4.0 InfoCenter).

(From PQ60772)

Abstract: The WSCP fails to validate the user/group names on role-user/group mapping when 
uses the LTPA auathentication. 

Description/symptom of problem: 

1. When using wscp, uses a short user or group name for role-user/group mapping, the install 
will successfully, but it will cause a 403 error (Authorization fails) when accessing the bean.
  
2. When using wscp, uses a full DN user or group name, application install failed.