572 WebSphere Application Server V8.5 Concepts, Planning, and Design Guide
7. CRPROF: Create a V8.5 profile for the node that is being migrated.
8. PREUPGRD: Back up the files in the file system in preparation for migration.
9. UPGRADE: Run WASPostUpgrade to perform the migration (serverindex.xml renamed
This step is where the actual migration occurs, and takes the longest to complete.
10.FINISHUP: Run Config2Native, and update file permissions and attributes.
Troubleshooting for the BBOWMG3x job
Because a migration is complex, errors can occur. The main source for errors is the
BBOWMG3x job, which was described in the previous section.
Here are some troubleshooting tips:
If the BBOWMG3x job fails, check the output for errors:
– /tmp/migrate/nnnnn/BBOWMG3x.out written to JOBLOG
– /tmp/migrate/nnnnn/BBOWMG3x.err written to JOBLOG
– /tmp/migrate/nnnnn/logs directory can contain log files, with a name such as the
If you need more information, enable traces. The trace states are disabled by default. Be
aware that ‘xxxx.DATA(BBOWMxEV)’ must be updated to enable tracing:
If the job fails in the VERIFY step, it is likely that an error was made when specifying the
information to use to create the jobs. Correct the information and rerun the job.
If the job fails after the VERIFY step, delete the WAS_HOME directory. This directory is
created during the failed run Delete the directory before rerunning the job. Check wether
the original configuration for the serverindex.xml file has been renamed to
The job failure is a signal that the configuration has already been migrated and to stop you
from inadvertently migrating the node again. To change the default setting during the
configuration phase, select Disable previous deployment manager in the Server
Customization (Part 2) window. This window is a part of the z/OS Migration Management
Tool. Alternatively, set the keepDMGREnabled parameter to true in the response file.
17.6.7 Migration considerations for 64-bit mode
Websphere Application Server V8.5 runs in 64-bit mode by default and 31-bit runtime mode is
deprecated. Keep in mind the considerations highlighted in this section.
For code written in pure Java, the general experience is that no changes are necessary to the
code for it to run in a 64-bit application server. If the application uses the Java Native Interface
Tip: The BBOWMG3x job can cause error conditions, such as an abend 522, because
it runs for a long time. TIME=NOLIMIT on the JCL job card can avoid the problem. The
BBOWMG1x and BBOWMG2x jobs are only necessary if you have any XA connectors
defined in your configuration. They do not apply to the deployment manager node
Chapter 17. Migration 573
(JNI) to call a native program, it must be a 64-bit program. Typically, these native programs
are code written in C, C++, or perhaps an IBM Language Environment compliant assembler.
This point is important to verify when using in-house applications that use older native
For more information about how to convert applications to run in 64-bit mode, see the
C/C++ Code Considerations With 64-bit WebSphere Application Server for z/OS
Language Environment Programming Guide for 64-bit Virtual Addressing Mode,
Larger heap sizes for applications
Use of the 64-bit addressing mode does not mean that the sizes for the various heaps need to
be increased. In general, identify minimum and maximum heap sizes with a verbose garbage
collection analysis. With this technique, you can identify values that reduce the garbage
collection processor usage, saving processor time. Consider performing a verbose garbage
collection analysis on a regular basis, especially if the number of users or the number of
transactions have changed.
Explanation: In general, the structure of WebSphere Application Server for z/OS reduces
the maximum heap size compared to those used by distributed platforms. For more
information, see 16.1.6, “Runtime processes” on page 507.
574 WebSphere Application Server V8.5 Concepts, Planning, and Design Guide