PQ66164: WSCP TAKES WRONG DBLOCATION ATTRIBUTE FROM REPOSITORY

A fix is available
WebSphere Application Server Version 3.5 Fix Pack 7 (3.5.7)

APAR

APAR status
Closed as program error.

Error description
This is an legacy issue which WSCP shouldn't read datasource
attributes from Session_MGR table directly, instead, WSCP should
read data base on datasource name from datasource table. In this
case, since datasource name hasn't been changed from previous
configuration. The values inside session_mgr table hasn't been
updated. But those value has never been used since runtime will
ook at the values inside datasource table based on name of
datasource.
Two issues regarding to this problem:
1. WSCP shouldn't list all the values of session_mgr such as
DbLocation.
2. Those values shouldn't be put into session_mgr table at all.
Talked customer twice on giving it a try by changing session
manager persistence panel datasource again.
Two issues regarding to this problem:1. WSCP shouldn't list all the values of session_mgr such asDbLocation.2. Those values shouldn't be put into session_mgr table at all.Talked customer twice on giving it a try by changing sessionmanager persistence panel datasource again.
Local fix
Use Console or XMLConfig
Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server users           *
*                 of wscp.                                     *
****************************************************************
* PROBLEM DESCRIPTION: When user issues wscp command:          *
*                                                              *
*                        wscp> SessionManager show {...} -all  *
*                                                              *
*                      it always shows DB2 info for:           *
*                                                              *
*                          DbDriver                            *
*                          DbDriverActive                      *
*                          DbLocation                          *
*                          DbLocationActive                    *
*                                                              *
*                      even if some other database is being    *
*                      used.                                   *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When a datasource backed by something other than DB2 is
specified for a session manager, then when wscp displays info
for the session manager as in:*                      it always shows DB2 info for: **                                                              **                          DbDriver                            **                          DbDriverActive                      **                          DbLocation                          **                          DbLocationActive                    **                                                              **                      even if some other database is being    **                      used.                                   ****************************************************************** RECOMMENDATION:                                              *****************************************************************When a datasource backed by something other than DB2 isspecified for a session manager, then when wscp displays info
wscp> SessionManager show {/Node:. . . Session Manager/} -all the following attributes will be displayed as if DB2 were being used:for the session manager as in:wscp>, SessionManager show {/Node:. . . Session Manager/} -allthe following attributes will be displayed as if DB2 were
DbDriver DbDriverActive DbLocation DbLocationActive Only the display is erroneous - the correct settings are used to reference the data at runtime!
being used:DbDriverDbDriverActiveDbLocationDbLocationActiveOnly the display is erroneous - the correct settings areused to reference the data at runtime!
Problem conclusion
Since Session Manager only references the data source, there is
no reason to display this information at all so the fix for
this problem was simply to remove the erroneous display of
information.
Temporary fix
PQ66164.jar and PQ66164.readme mailed to weblev2@us.ibm.com,
Tamiko Watts, and Tillman Baldwin.
Comments
APAR information
APAR numberPQ66164
Reported component nameWAS ADVANCED AI
Reported component ID5648C8400
Reported release350
StatusCLOSED PER
PENoPE
HIPERNoHIPER
Submitted date2002-09-12
Closed date2003-01-31
Last modified date2003-01-31

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:APAR is sysrouted FROM one or more of the following:


Modules/Macros
WSCP
APAR is sysrouted TO one or more of the following:Modules/Macros

Fix information
Fixed component nameWAS ADVANCED AI
Fixed component ID5648C8400

Applicable component levels
R350 PSYUP











Document Information

Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, General
Software version: 350
Reference #: PQ66164
IBM Group: Software Group
Modified date: 2003-01-31