Fix (APAR): PI66503 Status: Fix Release: 9.0.0.0 Operating System: Linux,Windows,z/OS Supersedes Fixes: CMVC Defect: xxxxxx Byte size of APAR: 551176 Date: 2016-08-24 Abstract: migration tool generated migration jobs fail to find the migration temp directory due to a typo in the job templat Description/symptom of problem: PI66503 resolves the following problem: 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: None 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 Directions to apply fix: Install Fix to all WebSphere installations unless special instructions are included below. Special Instructions: Apply the fix 9.0.0.0-WS-WAS-OS390-IFPI66503.zip to affected installations of WebSphere Application Server 9.0.0.0 for zOS. Apply the fix 9.0.0.-WS-WASWCT-IFPI66503.zip to affected installations of WebSphere Customization Toolbox 9.0 on Linux and Windows. You must then re-process any migration response files in order to get corrected migration job files. NOTE: The user must: * Logged in with the same authority level when unpacking a fix, fix pack or refresh pack. * Be at V1.8.5 or newer of the Installation Manager. Certain iFixes may require a newer version of the Installation Manager and the Installation Manager will inform you during the installation process if a newer version is required. The IBM Information Center can provide details, if needed, on the use of the Installation Manager to apply the iFixes. http://www.ibm.com/support/knowledgecenter/SSDV2W_1.8.5/com.ibm.cic.agent.ui.doc/helpindex_imic.html. Shutdown WebSphere Application Server or WebSphere Customization Toolbox before applying the iFixes. Restart WebSphere Application Server or WebSphere Customization Toolbox after applying the iFixes. Directions to remove fix: The IBM Information Center can provide details, if needed, on the use of the Installation Manager to remove the iFixes. http://www.ibm.com/support/knowledgecenter/SSDV2W_1.8.5/com.ibm.cic.agent.ui.doc/helpindex_imic.html. Shutdown WebSphere Application Server or WebSphere Customization Toolbox before removing the iFixes. Restart WebSphere Application Server or WebSphere Customization Toolbox after removing the iFixes. Directions to re-apply fix: 1) Shutdown WebSphere Application Server or WebSphere Customization Toolbox. 2) Follow the Fix instructions to apply the fix. 3) Restart WebSphere Application Server or WebSphere Customization Toolbox. Additional Information: