Fixes are available
9.0.0.1: WebSphere Application Server traditional V9.0 Fix Pack 1
9.0.0.2: WebSphere Application Server traditional V9.0 Fix Pack 2
9.0.0.3: WebSphere Application Server traditional V9.0 Fix Pack 3
9.0.0.4: WebSphere Application Server traditional V9.0 Fix Pack 4
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
In the migration job templates for BBOWMG3B, the variable &MBTMPDIR is mistakenly called &MDTMPDIR. As a result, when the jobs and response files are generated the &MDTMPDIR variable is left as-is instead of being replaced with the actual migration temporary directory path. When the jobs are run, users will receive an error for an invalid character in the path field of the DD where this variable was left, and/or that a file is not a valid file because the path to it is incomplete. When BBOWmG3B was run with this typo, this message was found in the migration log: The following validation errors were present with the command line arguments: portsFile: /12345678/portdef.props: is not a valid file manageprofiles.sh failed And the job output pointed to an issue in line 24 of the generated job BBOWMG3B: 24 IEF825I INVALID CHARACTER IN THE PATH FIELD DTM1455I 2016.204 09:08:03 Job BBOWMG3B failed, JCL Error where line 24 is a DD with the typo: 24 //HFSOUTL DD PATH='&MDTMPDIR/12345678/portdef.props', // PATHOPTS=(OWRONLY,OCREAT,OTRUNC), // PATHMODE=(SIRWXU,SIRWXG) The same kind of typo exists in the migration temp directory variable used in the generation of jobs for standalone servers, Admin Agents, and JobManagers. Below is the complete list of affected CNTL template files: BBOWBPRO BBOWBPRE BBOWBPOS BBOWMG3B BBOWAPRO BBOWAPRE BBOWAPOS BBOWMG3A BBOWJPRO BBOWJPRE BBOWJPOS BBOWMG3J and DATA response files BBOWMBRF BBOWMJRF BBOWMARF
Local fix
Manually replace all instances of &MDTMPDIR in the generated jobs and response file with the "Migration Temporary Directory Location" path that you supplied when running the migration tool to generate the job. Then re-run the corrected job. Note that this will not fix the template, so any new jobs generated for a new migration profile will need to be corrected in the same way, after generation, until the fix pack with this APAR is applied.
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V9.0 Configuration Migration for * * z/OS or of IBM WebSphere Application * * Server z/OS Migration Management Tool on * * any supported operating system. * **************************************************************** * PROBLEM DESCRIPTION: Error like "/12345678/portdef.props: * * is not a valid file" when migrating * * z/OS application server, admin agent, * * or job manager * **************************************************************** * RECOMMENDATION: * **************************************************************** When running either the PRO, PRE, POS, or G3 migration job to migrate a standalone application server, administrative agent, or job manager profile, the job will fail with an error similar to "/12345678/portdef.props: is not a valid file". The path will always begin with a string of numbers like /12345678/. The problem is caused because the path should begin with the path to the migration temporary directory as specified in the response file. This occurs because of an error in the job templates which misspells the symbol for the migration temporary directory when specifying the path to the portdef.props file.
Problem conclusion
The affected job templates were updated to have the correct substitution variable when creating and referring to the portdef.props file. New jobs generated by processing a migration response file using either the WebSphere Customization Toolbox on supported operating systems, or zmmt.sh on z/OS will have the correct paths, and migration will proceed normally. Jobs already generated with the erroneous substitution symbols will need to be edited using the temporary fix, or re-processed from the response file, before migration will succeed. APAR PI66503 is currently targeted for inclusion in Service Level 9.0.0.1 of WebSphere Application Server. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
You will need to update the following jobs in the DATA and CNTL datasets depending on what type of profile you are migrating and which migration jobs you intend to run: Standalone: BBOWBPRO, BBOWBPRE, and BBOWBPOS, or BBOWMG3B in CNTL and BBOWMBRF in DATA; Administrative Agent: BBOWAPRO, BBOWAPRE, and BBOWAPOS, or BBOWMG3A in CNTL and BBOWMARF in DATA; Job Manager: BBOWJPRO, BBOWJPRE, and BBOWJPOS, or BBOWMG3J in CNTL and BBOWMJRF in DATA. For each of the CNTL jobs, locate the WRPORTS step, and then the line within that step, which beings with: //HFSOUTL DD PATH='&MDTMPDIR/ Replace the óÔé¼ ô&MDTMPDIR óÔé¼ ¢ with the path to your migra temporary directory specified as zmbTempDirectory in the response file. For the DATA job, locate the line: portsFile=/12345678/portdef.props (Note that the string of numbers used here is just an example; the actual value will be equal to the zmbTimestamp value in the response file.) Prepend the path to the migration temporary directory specified as zmbTempDirectory in the response file to this path, after the = and before the /. The paths in the CNTL and DATA jobs should be identical when this workaround is applied. This will ensure that the migration jobs copy the ports data into the correct location, and that various scripts are able to access that data throughout migration.
Comments
APAR Information
APAR number
PI66503
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
2016-07-26
Closed date
2016-08-17
Last modified date
2016-08-17
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