Fixes are available
APAR status
Closed as program error.
Error description
NodeAgent would not start due to java.io.IOException. Could not create Lock Manager
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V8.5 Migration Tools on iSeries. * **************************************************************** * PROBLEM DESCRIPTION: NodeAgent will not start after * * migration due to incorrect * * permissions or ownership of various * * profile directories. * **************************************************************** * RECOMMENDATION: * **************************************************************** NodeAgent will not start after migration due to incorrect permissions and ownership of various profile directories.
Problem conclusion
Adjusted migration code to correctly set permissions and ownership of the new directories being migrated. The fix for this APAR is currently targeted for inclusion in fix pack 8.5.0.1. 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
PM66797
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-06-14
Closed date
2012-06-21
Last modified date
2012-06-21
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
R850 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":"8.5","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
01 November 2021