APAR status |
Closed as fixed if next.
| Error description
Customer fail to install WAS 3.5 with remote Sybase 12. In WAS 3
.5 documentation, and its topology, remote DB repository is vali
d. Local fix
Partial workaround: First, install WAS 3.5 with a local DB, i.e.
IDB. Then install Sybase 12 on the remote machine. Then modify t
he admin.config file from WAS 3.5 machine, change the dbUrl, dbD
river, classpath, set install.initial.config=true. Then restart
WAS again.WAS can start but it will not configurate everything u
nder Default_Server. Customer may have to cut and paste the XML
file from the install with IDB, to the XML file with Sybase. Problem summary
in the next release of WAS, if any.
Note: Install problems can't be corrected via a PTF. Problem conclusionTemporary fixComments
APAR information | APAR number | PQ42108 | Reported component name | WAS ADVANCED SU | Reported component ID | 5648C8402 | Reported release | 350 | Status | CLOSED FIN | PE | NoPE | HIPER | NoHIPER | Submitted date | 2000-09-29 | Closed date | 2000-10-25 | Last modified date | 2000-10-25 |
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 | R350 PSN | UP |
|