Updating application description run cycles with PIF

When you use the ISPF dialogs to update or create application descriptions, you specify a run cycle out-of-effect date. Then HCL Workload Automation for Z calculates the run cycle valid-to date by subtracting one day from the out-of-effect date. However, when you use PIF to update an AD you do not specify the out-of-effect date, you specify the valid-to date. Then HCL Workload Automation for Z calculates the out-of-effect date by adding one day. If you specify the valid-to date as the default high date, adding one day would make the date higher than the highest allowed date. Therefore, when you specify the valid-to date in a PIF application as the default high date, HCL Workload Automation for Z takes the HCL Workload Automation for Z high date as the out-of-effect date.