Migration considerations

IBM® attempts to make the installation of new releases as easy as possible. Initially, you should install HCL Workload Automation for Z without taking any customization actions in order to achieve a stable environment.

For instructions about using System Modification Program/Extended (SMP/E) to install HCL Workload Automation for Z, see the HCL Workload Automation for Z: Program Directory.

Before migrating to the current release, and to ensure that a proper fallback migration can be performed, consider that:

• You can migrate from or fall back to previous releases without IPLing z/OS.
• If you are performing a fallback because of problems experienced on HCL Workload Automation for Z, be sure to keep the HCL Workload Automation for Z data sets for diagnostic purposes.
• If you migrate to and fallback from HCL Workload Automation for Z to test the environment before your official migration, ensure that you reallocate all HCL Workload Automation for Z data sets before the next migration exercise.
• It might occur that in the Application Description database, an application shows a timestamp for its Last Update that corresponds to a date when no changes were made. This can occur when you migrate to a recent version of HCL Workload Automation for Z, because for the new fields introduced, the database conversion program adds them as blank fields; when you access a panel, every displayed field is verified and if a field is blank or null, the verification program initializes the field to its default. This is considered a change because different from the original record content. For this reason, the record changed message is issued, and the Last Update date is modified.
• Ensure that the Dynamic Workload Console is migrated to a new release before migrating the Z controller, because the Dynamic Workload Console must always be at a version later than the Z controller.