PQ77791: "BBOO0223I UNEXPECTED ERROR OCCURRED WHILE GETTING REPOSITORY" AFTER APPLY OF UQ79131/UQ79132

 A fix is available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
When customers apply service level W500103 to WebSphere
Application Server for z/OS v5.0 by SMP/E installing UQ79131 and
UQ79132, the following error may occur:
"BBOO0223I Unexpected error occurred while getting repository"
This stems from the problem that the PTF did not include some
required ++HOLD data that instructs customers to reinstall the
admin console application.
.
Customers may also encounter problems starting clusters
from the admin console application.  They may encounter
errors in the WebSphere logs indicating that the operation
'retrieveCluster' failed.  This is due to two new JAR files
being added to the install root of the product, but no
symbolic links were created in the WebSphere config roots.
.
Local fix
Here is the ++HOLD data that is required:
++HOLD (ACTION)
Application of this PTF requires that the administrative console
be replaced. In order to do this, your current administrative
console will have to be un-installed and the administrative
console shipped with this PTF will be installed.   The following
steps must be taken to accomplish this.
If you have federated your Base application server into a cell,
run the Network Configuration instructions below.
If you have a non-federated Base application server
configuration:
1) Identify the dataset  member BBOWIAPP of the .CNTL
customization dataset for this Application server.
2) Make 2 copies of this member with names BBOWUADM and
BBOWIADM
3) Edit BBOWUADM and
        3a) Delete Step2 only(INST2)
        3b) Modify Step1(INST1) to replace the existing command
            with the following command and
please note the location of spaces and pluses(+).
                Cut/Paste is suggested.
         These instructions assume the default installation path
         (/WebSphere/V5R0M0). If you have a different
          installation path, please adjust these instructions
                 accordingly.
         The existing Step1 command in BBOWIAPP will indicate
                 your installation path.
                BPXBATCH SH +
                        /WebSphere/V5R0M0/AppServer+
                        /bin/wsadmin.sh -conntype none +
                        -c '$AdminApp uninstall adminconsole'  +
                        1> /tmp/bbowuadm.out +
                        2> /tmp/bbowuadm.err
        3c) Modify Copy step(WIAPPC) to use the new filenames
                BBOHFSWR '/tmp/bbowuadm.out'
                BBOHFSWR '/tmp/bbowuadm.err'
        3d) Save member
4) Edit BBOWIADM and
        4a) Delete Step2 only(INST2)
       4b) Save member
5) Submit BBOWUADM
6) Submit BBOWIADM
If you have a Network Deployment configuration you need to run
only
these steps:
1) Identify the dataset  member BBODIAPP of the .CNTL
customization dataset.
2) Make 2 copies of this member with names BBODUADM and
BBODIADM
3) Edit BBODUADM and
        3a) Delete Step2 only(INST2)
        3b) Modify Step1(INST1) to replace the existing command
with the following command and
         please note the location of spaces and pluses(+).
Cut/Paste is suggested.
         These instructions assume the default installation path
(/WebSphere/V5R0M0).
        If you have a different installation path, please adjust
these instructions accordingly.
         The existing Step1 command in BBODIAPP will indicate
your installation path.
               BPXBATCH SH +
                        /WebSphere/V5R0M0/DeploymentManager/+
                        /bin/wsadmin.sh -conntype none +
                        -c '$AdminApp uninstall adminconsole'  +
                        1> /tmp/bboduadm.out +
                        2> /tmp/bboduadm.err
        3c) Modify Copy step(DIAPPC) to use the new filenames
                BBOHFSWR '/tmp/bboduadm.out'
                BBOHFSWR '/tmp/bboduadm.err'
        3d) Save member
4) Edit BBODIADM and
        4a) Delete Step2(INST2) only
        4b) Save member
5) Submit BBODUADM
6) Submit BBODIADM
.
Application of PTF UQ79131, UQ79132 comprising the W500103
service level of WAS on z/OS V5.0 , placed two new jars into
your INSTALL_ROOT.  For the Network Distributed configuration
ONLY, these two new jars require that two symbolic links be
created in each of your CONFIG_ROOT images linking your
CONFIG_ROOT to the INSTALL_ROOT jars.
.
For the Base(un-federated server) configuration, nothing needs
to be done.  For the Network Distributed configuration, create
these symbolic links by issuing the following Unix System
Services command from a USS shell.  You should log into the
USS shell using a Userid with Write permission to your
CONFIG_ROOT directories.  The following commands assume your
INSTALL_ROOT is /usr/lpp/zWebSphere/V5R0M0 and one of your
CONFIG_ROOT is /WebSphere/V5R0M0.  You should adjust your
commands based on your actual INSTALL_ROOT and CONFIG_ROOT.
You may also have more than one CONFIG_ROOT.   If you do, you
must issue these commands for each CONFIG_ROOT you have.
(NOTE, these commands should be entered on a single line)
.
ln -s /usr/lpp/zWebSphere/V5R0M0/lib/wlmclient.jar
      /WebSphere/V5R0M0/DeploymentManager/lib/wlmclient.jar
ln -s /usr/lpp/zWebSphere/V5R0M0/lib/wlmserver.jar
      /WebSphere/V5R0M0/DeploymentManager/lib/wlmserver.jar
ln -s /usr/lpp/zWebSphere/V5R0M0/lib/wlmclient.jar
      /WebSphere/V5R0M0/AppServer/lib/wlmclient.jar
ln -s /usr/lpp/zWebSphere/V5R0M0/lib/wlmserver.jar
      /WebSphere/V5R0M0/AppServer/lib/wlmserver.jar
Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V5.0 for z/OS                                *
****************************************************************
* PROBLEM DESCRIPTION: After applying W500103                  *
*                      PTF(UQ79131,UQ79132) customers may get  *
*                      error message BBOO0223I UNEXPECTED      *
*                      ERROR OCCURRED WHILE GETTING REPOSITORY *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
HOLD for ACTION information was not supplied to customers for
fixing an administrative console problem.   Because of this,
the fix was not applied and led to the error message BBOO0223I.
Problem conclusion
APAR PQ77791 will provide the missing hold for action in Service
Level W500103 related to the administative console.

APAR PQ77791 is associated with SERVICE LEVEL W500104 of
WebSphere Application Server V5.0 for z/OS.
Temporary fix Comments
APAR information
APAR number PQ77791
Reported component name WEBSPHERE FOR Z
Reported component ID 5655I3500
Reported release 500
Status CLOSED PER
PE YesPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2003-08-25
Closed date 2003-08-30
Last modified date 2003-10-03

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
BBOUBINF          

Publications Referenced

Fix information
Fixed component name WEBSPHERE FOR Z
Fixed component ID 5655I3500

Applicable component levels
R500 PSY UQ79825    UP03/09/10 P F309 

  Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.


Document Information


Current web document: swg1PQ77791.html
Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS
Operating system(s):
Software version: 500
Software edition:
Reference #: PQ77791
IBM Group: Software Group
Modified date: Oct 3, 2003