Troubleshooting
Problem
This document describes how to determine the best time to replan or extend current plan in IBM Tivoli Workload Scheduler (TWS) for z/OS.
Resolving The Problem
The TWSz manuals, "General Information" and "Getting Started" have introductory information on the TWSz logic and structure. There is more detailed information in the "Managing the Workload" manual, Chapter 12 - "Overview of the Long-Term and Current Plans". Chapters 13 and 14 discuss the Long Term Plan (LTP) and Current Plan (CP) and the planning process in more detail.
Normally, the CP Is created when the product is installed. It covers from 24 to 48 hours. Then each day the customer EXTENDs the plan by an additional 24 hours. The EXTEND can be run at any time, for any interval from one minute to 21 days, and as often as desired...possibly several times per day. However, to prevent any discontinuity of function, the EXTEND job must complete prior to the END TIME of the "old" CP used as input.
The TWSz plan is a never-ending road that must be extended every day before reaching the end of what was created previously. Because of the structure of the plan (the rundate of the job is part of its identifier in the database), there is no such thing as carry-forward as in older releases of TWS(dist). So the same job or jobstream can be planned as many times as wanted during any day, and uncompleted work from prior days remains in the plan until completed or deleted with no change of name.
The REPLAN function is logically an EXTEND of the CP for zero minutes. It regenerates the plan dataset within the existing time interval, deleting work already completed, and recalculating the capacity-planning-related portions of the plan. In the E2E world, a REPLAN is most often used interchangeably with the SYMPHONY RENEW function to cause a new SYMPHONY plan to be generated and distributed.
However, there is a significant difference between the CP REPLAN and SYMPHONY RENEW jobs.
The CP REPLAN regenerates BOTH the CURRENT PLAN (containing ALL the planned work) and the SYMPHONY file (which contains only work scheduled on NON-MVS workstations).
The SYMPHONY RENEW does NOT affect the CURRENT PLAN. Rather, it regenerates the SYMPHONY using the existing CURRENT PLAN as input, and signals the TWSZ E2E code to redistribute the newly created SYMPHONY.
Thus if only the SYMPHONY needs to be redistributed, it is frequently more desirable to run the SYMRENEW job, as it has no impact at all on the MAINFRAME portion of the schedule.
Related Information
Product Synonym
TWS for z/OS
Was this topic helpful?
Document Information
Modified date:
13 September 2019
UID
swg21165713