PM45072: WEBSPHERE VARIABLES ARE NOT CREATED ON SAVE AFTER CLICKING APPLY IF THE VARIABLES.XML FILE DOES NOT EXIST FOR THE SERVER

Fixes are available

APAR status

Closed as program error.

Error description

In WebSphere Application Server v6.1, when creating a new
WebSphere variable in the Administrative Console and clicking
on Apply and Save, the variable is not created if the
variables.xml file does not exist for the server.  A warning
message is generated in the SystemOut.log:

W   validateFileLength: File
"/opt/IBM/WebSphere/AppServer/profiles/Dmgr/wstemp/-520984571/wo
rkspace/cells/cell_desa/nodes/desaFEP_04/servers/nodeagent/varia
bles.xml" does not exist in wstemp, and will not be updated to
master repository.

Local fix

When creating the WebSphere variable, use OK instead of Apply.

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server console creating the first           *
*                  environment variable and clicking Apply     *
****************************************************************
* PROBLEM DESCRIPTION: When creating a new variable in the     *
*                      console the variable is not created     *
*                      if the variables.xml file does not      *
*                      exist for the server.                   *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When creating a new WebSphere Application Server variable in
the Administrative Console and clicking Apply and Save, the
variable is not created if the variables.xml file does not
exist for the server. A warning message is generated in the
SystemOut.log:
validateFileLength: File
"/opt/IBM/WebSphere/AppServer/profiles/Dmgr/wstemp/-
520984571/wo
rkspace/cells/cell_desa/nodes/desaFEP_04/servers/nodeagent/varia
bles.xml" does not exist in wstemp, and will not be updated to
master repository.
The code for Apply was not correctly checking to see if the
file variables.xml existed before setting the value. For the
OK button, the code does the correct check.

Problem conclusion

Before writing out the variable, we now check to be sure
variables.xml exists. If not, we first create the file.

The fix for this APAR is currently targeted for inclusion in
fix packs 6.1.0.41, 7.0.0.21, 8.0.0.2.  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
PM45072
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
61I
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-08-04
Closed date
2011-08-25
Last modified date
2011-08-25

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
WEBSPHERE APP S
Fixed component ID
5724J0800

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
R800 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:
27 October 2021

Tips

PM45072: WEBSPHERE VARIABLES ARE NOT CREATED ON SAVE AFTER CLICKING APPLY IF THE VARIABLES.XML FILE DOES NOT EXIST FOR THE SERVER

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

R800 PSY

Document Information

Share your feedback

Need support?