PK79116: ADDNODE FAILED WHILE THERE IS A V5 NODE IN THE CELL OR IF FEDERATING A Z/OS NODE TO A DISTRIBUTED DEPLOYMENT MANAGER.

Fixes are available

APAR status

Closed as program error.

Error description

The addNode command fails when one of the following conditions
exists:
1> There is a V5 node in the cell that a z/OS node federates
into. In this case, the addNode command throws an
InvalidAttributeNameException.
2> A z/OS node is federated into a cell where its deployment
manager is on V7 and run on a distributed system. The addNode
command throws a CommandException in this case.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of WebSphere Application          *
*                  Server V6.1 and V7.0 with a mixed cell      *
*                  configuration.                              *
****************************************************************
* PROBLEM DESCRIPTION: The addNode command fails when one of   *
*                      the following conditions exists:        *
*                      1> There is a V5 node in the cell       *
*                      that a z/OS node federates into. In     *
*                      this case, the addNode command throws   *
*                      an InvalidAttributeNameException.       *
*                      2> A z/OS node is federated into a      *
*                      cell where its deployment manager is    *
*                      on V7 and run on a distributed          *
*                      system. The addNode command throws a    *
*                      CommandException in this case.          *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The implementation of the addNode command does not check for
a WebSphere Application Server V5 node in the cell before
referencing a non-version 5 object attribute serverShortName.
The implementation also fails to check if a deployment manager
is on a z/OS platform before it uses an AdminTask command that
is only available on z/OS servers.

Problem conclusion

To prevent the InvalidAttributeNameException and the
CommandException, added the checking statements to make sure
the conditions are meet while using the non-version V5 object
attribute or the AdminTask command available on z/OS servers
only.

The fix for this APAR is currently targeted for inclusion in
fixpack 6.1.0.25 and 7.0.0.3.  Please refer to the Recommended
Updates page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PK79116
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
61Z
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-01-21
Closed date
2009-02-06
Last modified date
2009-02-06

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
WEBS APP SERV N
Fixed component ID
5724H8800

Applicable component levels

R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
R700 PSY
UP

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

Document Information

Modified date:
28 December 2021

Tips

PK79116: ADDNODE FAILED WHILE THERE IS A V5 NODE IN THE CELL OR IF FEDERATING A Z/OS NODE TO A DISTRIBUTED DEPLOYMENT MANAGER.

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

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?