PK74472: WAS_INSTALL_ROOT SHARED BY APPSERVER AND DMGR IN A CELL CONFIG

Fixes are available

APAR status

Closed as program error.

Error description

In a z/OS 'cell' configuration, the WAS_INSTALL_ROOT variable
for the Application Server points to the Deployment Manager's
configuration file system.  The Application Server and
Deployment Manager should be able to have different file
systems in a cell configuration.

Local fix

Update the variables.xml at the node level on the
DMGR side.  This should be at:
.
/<DMGR install root>/profiles/default/config/cells/
              cellName/nodes/nodeName/variables.xml
.
Where nodeName is the name of the appserver node
(not the DMGR node).  Before you edit the variables.xml,
please make a backup.  Then open the file and look for
the WAS_INSTALL_ROOT variable, and change it to the
correct value and save the file.  Once this is done,
synchronize the node and restart the server and
nodeagent to pick up the change.  You should be able to
verify the change by looking at the server or
nodeagent joblog and searching for was.install.root.

Problem summary

****************************************************************
* USERS AFFECTED:  All users of WebSphere Application Server   *
*                  V7.0 for z/OS. This problem only affects    *
*                  cell profiles.                              *
****************************************************************
* PROBLEM DESCRIPTION: In a z/OS 'cell' configuration, the     *
*                      Application Server WAS_INSTALL_ROOT     *
*                      variable points to the deployment       *
*                      manager's installation root.            *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
In a z/OS 'cell' configuration (initial configuration of a
deployment manager together with a managed node), the
Application Server WAS_INSTALL_ROOT variable (as viewed from
the 'Environment' -> 'WebSphere variables' administrative
console page), incorrectly points to the deployment manager's
installation root.

Problem conclusion

At profile creation time, the application server install
root was not passed to the manageprofiles tool. Changes
were required to the z/OS Profile Management Tool (zPMT)
and to the scripts invoked by manageprofiles, to correctly
pass in this value and act upon it.

Activation of the fix for PK74472, which affects cell profiles
only, requires that an updated version of zPMT be used at cell
profile creation time. This requirement is in addition to
application of fixpack 7.0.0.3. If an appropriate level of zPMT
is not used, then the behavior of cell profile creation
reverts to that before fixpack 7.0.0.3 was applied. The zPMT
tool should be updated to the version in  IBM WebSphere
Customization Tools V7.0.0.3 for V7.

Refer to URL:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg24020368
to download the latest fix pack for the IBM WebSphere
Customization Tools.

Customers who created cell profiles without this service
installed, and who intended their deployment manager and managed
node to use different installation root directories, should
correct the application server installation root value using the
following procedure.  The procedure is only necessary for cell
profiles.

Stop the deployment manager, application server and node agent.
Under the deployment manager master repository, locate the node
level variables.xml file for the application server node:

<DMGR_INSTALL_ROOT>/profiles/default/config/cells/<CELL_NAME>
/nodes/<APPLICATION_SERVER_NODE_NAME>/variables.xml

Backup the file. Edit the file and find the entry for the
WAS_INSTALL_ROOT variable. For example:

  <entries xmi:id="VariableSubstitutionEntry_1235009906558"
   symbolicName="WAS_INSTALL_ROOT"
   value="/etc/s7cell/s7dmnode/DeploymentManager"
   description="The filesystem path to the WebSphere product
                installation directory."/>

Change the value attribute to point to the application server
install root. Save the file. Start the deployment manager.
Synchronize the application server node by running the
syncNode.sh command under the application server installation.
Start the node agent and application server.

APAR PK74472 is currently targeted for inclusion in Service
Level (Fix Pack) 7.0.0.3 of WebSphere Application Server V7.0
for z/OS.

Please refer to URL:
//www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
for Fix Pack availability.

Temporary fix

Comments

APAR Information

APAR number
PK74472
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-10-24
Closed date
2009-02-03
Last modified date
2009-05-03

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

PK77120 PK80311

Fix information

Fixed component name
WEBSPHERE FOR Z
Fixed component ID
5655I3500

Applicable component levels

R700 PSY UK45120
UP09/04/06 P F904

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.

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 December 2021

Tips

PK74472: WAS_INSTALL_ROOT SHARED BY APPSERVER AND DMGR IN A CELL CONFIG

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R700 PSY UK45120

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

Share your feedback

Need support?