PQ77867: WEBSPHERE Z/OS ADDNODE.SH: FSUM7351 NOT FOUND WHEN FEDERATE 'INGA NODE IN ND.

 A fix is available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
Customer is trying to FEDERATE a SERVER into an Network
Deployment environment. This fails with
addNode.sh: FSUM7351 not found
   The customer has the Server and DeploymentManager in seperate
HFS files and the Server mountpoint is not under the DMGR. Ex:
application servers: BBO.V5R0M0.MYCFGS.HFS /u/WAS500/Servers
deployment manager: BBO.V5R0M0.MYCFGDM.HFS /u/WAS500/DeployMgr
Often the Server mountpoint will be underneath the DMGR and
that works:
   app servers: BBO.V5R0M0.CFGS.HFS /u/WAS500/DMGR/AppServer
deployment manager: BBO.V5R0M0.CFGDM.HFS /u/WAS500/DMGR
  This APAR was taken to allow seperate HFS and mountpoints as
indicated in the first example.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V5.0 for z/OS                                *
****************************************************************
* PROBLEM DESCRIPTION: Customer is trying to federate a        *
*                      server into an Network Deployment       *
*                      environment. This fails with            *
*                      addNode.sh: FSUM7351 not found          *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The customer has the base App Server and DeploymentManager in
separate HFS files and with differnt mount points.

Since the addNode.sh lives only in the base App Server's HFS
and the dialog has only one variable to save the mount point,
when it gets to the "Federate Base Application Server node"
to generate the add node job (BBOWADDN), it generates the
wrong path to the addNode.sh.
The generate add node job (BBOWADDN) refers to the addNode.sh
in the Deployment Manger's HFS.

To correct this, the dialog needs to save the two different
mount points to different variables.  So, when it generates
the BBOWADDN job, it can refer to the correct path to the
addNode.sh.
Problem conclusion
The dialog have been updated so that it allows different mount
points to be entered for the base App Server and Deployment
Manager.  With this, the generated job BBOWADDN will have the
correct path to the addNode.sh.

APAR PQ77867 is associated with SERVICE LEVEL W501001 of
WebSphere Application Server V5.0 for z/OS.
Temporary fix Comments
APAR information
APAR number PQ77867
Reported component name WEBSPHERE FOR Z
Reported component ID 5655I3500
Reported release 500
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2003-08-27
Closed date 2003-10-08
Last modified date 2006-02-28

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 UQ80952    UP03/10/14 P F310

  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: swg1PQ77867.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 #: PQ77867
IBM Group: Software Group
Modified date: Feb 28, 2006