PM72746: MIGRATION ON I5/OS RESULTING WSADMIN FAILURE TO RUN DUE TO INCORRECT PATH LEFT IN THE WSADMIN.PROPERTIES FILE

Fixes are available

APAR status

Closed as program error.

Error description

After migration from v6.1 Network Deployment edition to 7.0
Network Deployment edition on i5/OS, the wsadmin.properties
file had an incorrect path left over for v6.1
com.ibm.ws.scripting.profiles parameter in the
wsadmin.properties file, which resulted in wsadmin
process failing to run:
.
wsadmin.properties contents after migration:
============================================
com.ibm.ws.scripting.profiles=/QIBM/ProdData/WebSphere/App
Server/V7/ND/bin/securityProcs.jacl;/QIBM/ProdData/WebSphe
re/AppServer/V61/ND/bin/LTPA_LDAPSecurityProcs.jacl
.
The path for the LTPA_LDAPSecurityProcs.jacl script in the
com.ibm.ws.scripting.profiles parameter contains the v6.1
path after migration rather than the V7 path.
.
The profile migration left the value for v6.1 in this
property.
.
The following error is returned for the wsadmin launch failure:
WASX7011E: Cannot find file
"/QIBM/ProdData/WebSphere/AppServer/V61/ND/bin/LTPA_LDAPS
curityProcs.py"
WASX7031I: For help, enter: "print Help.help()"
wsadmin>
.

Local fix

Edit the wsadmin.properties files with the correct path for
V7 for the LTPA_LDAPSecurityProcs.jacl file, after migration.

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server on i5/OS                             *
****************************************************************
* PROBLEM DESCRIPTION: The wsadmin process fails to run due    *
*                      to incorrect path in the                *
*                      wsadmin.properties file.                *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Paths are created in wsadmin.properties using a colon as a file
separator instead of a semicolon. This causes the wsadmin
process to fail to run.

Problem conclusion

To prevent the wsadmin failure, paths are changed to use a
semicolon for a path separator.

The fix for this APAR is currently targeted for inclusion in
fix packs 7.0.0.27, 8.0.0.6 and 8.5.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
PM72746
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-09-12
Closed date
2012-10-08
Last modified date
2012-10-08

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

R700 PSY
UP
R800 PSY
UP
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":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 October 2021

Tips

PM72746: MIGRATION ON I5/OS RESULTING WSADMIN FAILURE TO RUN DUE TO INCORRECT PATH LEFT IN THE WSADMIN.PROPERTIES FILE

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

R800 PSY

R850 PSY

Document Information

Share your feedback

Need support?