Fixes are available
9.0.0.5: WebSphere Application Server traditional V9.0 Fix Pack 5
9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
WebSphere Application Server traditional 9.0.5.6
9.0.5.7: WebSphere Application Server traditional Version 9.0.5 Fix Pack 7
9.0.5.8: WebSphere Application Server traditional Version 9.0.5.8
9.0.5.9: WebSphere Application Server traditional Version 9.0.5.9
9.0.5.10: WebSphere Application Server traditional Version 9.0.5.10
9.0.5.11: WebSphere Application Server traditional Version 9.0.5.11
APAR status
Closed as program error.
Error description
JCL proc names remained the same but the migration job does not read them correctly from the old configuration files. This results in the message MIGR0435W: Could not resolve variable SERVER
Local fix
Set zmbReplaceStartedProcedureNames to true (or check the box "Replace started procedure command names") and manually add the procedure names before running the migration jobs.
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V9.0 configuration migration tools * * on z/OS. * **************************************************************** * PROBLEM DESCRIPTION: After migrating to WebSphere V9.0 on * * z/OS, the server fails to start due * * to the control region's start command * * being "START null". * **************************************************************** * RECOMMENDATION: * **************************************************************** When migrating to WebSphere V9.0 on z/OS the control region's procedure name is not brought forward in certain scenarios. This results in "START null" for the control region's startCommand in the server.xml. The problem only exists when the user has chosen to keep their old procedure names.
Problem conclusion
Fixed the WASPostUpgrade logic to correctly bring forward the procedure name in all cases when the user has selected the option to reuse proc names. The fix for this APAR is currently targeted for inclusion in fix pack 9.0.0.5. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
On the "Procedure names" panel of zmmt migration GUI, check the "Replace started procedure command names" checkbox and enter the original procedure names from the old WebSphere environment.
Comments
APAR Information
APAR number
PI83066
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
900
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-06-14
Closed date
2017-08-20
Last modified date
2017-08-20
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 FOR Z
Fixed component ID
5655I3500
Applicable component levels
R900 PSY
UP
Document Information
Modified date:
04 May 2022