Migration considerations

IBM® attempts to make the installation of new releases as easy as possible. Initially, you should install Tivoli Workload Scheduler for z/OS without taking any customization actions in order to achieve a stable environment. Refer to the Program Directory for specific instructions about using System Modification Program/Extended (SMP/E) to install Tivoli Workload Scheduler for z/OS.

You can migrate from or fall back to previous releases without IPLing z/OS.

|The following are some migration considerations and, |in some cases, necessary prerequisite steps to perform, before migrating |to the current release, to ensure a proper fallback migration can |be performed, if necessary at any time.

|

|
• If you are performing a fallback because of problems experienced |on Tivoli Workload Scheduler for z/OS, be sure to keep the Tivoli Workload Scheduler for z/OS data sets for diagnostic |purposes.
|
• If you migrate to and fallback from Tivoli Workload Scheduler for z/OS to test the environment |before your official migration, ensure that |you reallocate all Tivoli Workload Scheduler for z/OS data sets before the next migration exercise.
|
• |Before you migrate to Tivoli Workload Scheduler for z/OS Version 8.6 from |Version 8.2, ensure you have applied at least the fix for APARs PK24633 |and PK24711 on version 8.2. This is required to successfully perform |a fallback migration from Tivoli Workload Scheduler for z/OS Version 8.6 to version |8.2, if necessary at any time.|
|
• |If you are migrating from Tivoli Workload Scheduler for z/OS Version 8.2 to Version |8.6, note that the default value of the GDGNONST parameter |has been changed from NO to YES. Refer to the OPCOPTS initialization |statement in Customization and Tuning for more information about the GDGNONST parameter.|
|
• |If you are migrating from version 8.2 to version 8.5.1 |or from version 8.2 to 8.6, and you have not applied the fix for APAR |PK36095 on your version 8.2 installation, then ensure you set TASKUSER(NO) to |maintain the current behavior of your environment. With version 8.5.1 |and later, the default value for TASKUSER is YES. |Refer to the OPCOPTS initialization statement in Customization and Tuning for |more information about the TASKUSER parameter.|
|
• |If you are migrating from version 8.2 to version 8.5.1 |or from version 8.2 to 8.6, and you have not applied the fix for APAR |PQ85880 on your version 8.2 installation, be aware that the default |setting of the CODEPAGE keyword in the SERVOPTS initialization |statement continues to be IBM-137, however, for version 8.5.1 and |later, if you specify a codepage value different from the default |value, a check has been implemented to use the default codepage if |the first four characters of the codepage you specify are different |from "IBM-". Refer to the SERVOPTS initialization statement |in Customization and Tuning for more information about the CODEPAGE parameter.|
|
• |Before you migrate to Tivoli Workload Scheduler for z/OS Version 8.6 from |Version 8.5.1, ensure you have applied at least the fix for APAR PM14386 |on version 8.5.1. This is required to successfully perform a fallback |migration from Tivoli Workload Scheduler for z/OS Version 8.6 to version 8.5.1, |if necessary at any time.|
|
• |The handling of operations in X status in a plan has |changed beginning with version 8.5.1 and later. A migration operation |is interrupted if an operation in X status is found in the current |plan. Message EQQIC51E is issued. Before retrying the migration, perform |the following steps, depending on the scenario you are running: |

  |

  A migration from Version 8.5 to either Version 8.5.1 |or 8.6

  |

  If conditions have been defined and used in the plan, then check |if you need the X status propagation to normal successors or, the |new logic that makes the normal successor ready is preferred. If you |require X status propagation, complete these steps: |

  |
  1. Change in AD the normal dependencies in conditions ST=C. Refer |to the information about conditional logic in Managing the Workload.
  |
  2. Wait until the occurrences involved in these definitions complete |in the Plan.
  |
  3. Perform a replan to remove these instances.

  |

  |

  A fallback from either Version 8.6 or 8.5.1 to version |8.5

  |

  If conditions have been defined and used in the plan, check |if you used the new logic that makes the normal successor ready. Consider |that after the fallback, they will become X. If you used the new logic |for X status, then perform the following steps: |

  |
  1. Change in AD the definitions so that the new logic is not used.
  |
  2. Wait until the occurrences involved in these definitions complete |in the Plan.
  |
  3. Perform a replan to remove these instances.

  |

  |

  |