APAR status |
Closed as documentation error.
| Error description
EJB's dynamically create tables that fail because they are
created with the incorrect qualifier. The table is created
without specifying the high level qualifier ( hlq ).This results
in the dynamically created object to have the db2 userid
specified in the admin panels used as the high level qualifier.
When accessing the EJB table however, the container assumes that
the hlq is EJB. The workarounds are to either create the object
the EJB hlq or define the db2 userid for connection to 390 as
EJB. Local fixProblem summary
****************************************************************
* USERS AFFECTED: All WebSphere Application Server users *
* with their repository on DB2 on 390 *
* attempting to use the samples. *
****************************************************************
* PROBLEM DESCRIPTION: The samples do not work properly if *
* the respository resides on a 390 box. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The InfoCenter will be updated to say that the samples didn't
use VAJava for deployment, and therefore they aren't supported
on the 390 platform. Problem conclusion
Closing as a documentation change. Temporary fixComments
APAR information | APAR number | PQ47938 | Reported component name | WAS ADVANCED AI | Reported component ID | 5648C8400 | Reported release | 350 | Status | CLOSED DOC | PE | NoPE | HIPER | NoHIPER | Submitted date | 2001-04-17 | Closed date | 2001-08-31 | Last modified date | 2001-12-17 |
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 APAR is sysrouted TO one or more of the following:Modules/Macros
Applicable component levels |
|