I have ocurrences dates in Long Term Plan panel 2.1 OLDER than the date display in the "Earliest non-completed occurrence in current plan" (option 2.4).
Tivoli Workload Scheduler for z/OS does not delete occurrences from the
long-term plan that are uncompleted or any occurrences that follow an
uncompleted occurrence. Tivoli Workload Scheduler for z/OS deletes occurrences
on a day-by-day basis. That is, all occurrences—or none—are removed for a
particular day. This means that if you have occurrences in your long-term plan that
are not completed, all occurrences scheduled for that day and all following days
are retained, whether the occurrences are completed or not. As part of Tivoli
Workload Scheduler for z/OS maintenance, you should assess such uncompleted
occurrences and take suitable action. For example, you can manually mark the
occurrences as complete, or delete the occurrences if they are not required. This
saves space in the VSAM data set that the long-term plan is stored in and reduces
the time and resources required to perform long-term plan batch and panel
Can anyone help me understand this paragraph in the manual, i cannot find in option 2.1 this relationship.
Also, if possible, somebody has some tips or tricks to work with LTP? Some common actions to take for maintenance?
The LTP modifications program PGM=EQQBATCH,PARM='EQQLTMOA' it has almost no information that describes how the program function.
Generally speaking, there should be no maintenance that needs doing. How often are you running your LTP refresh?
I'm assuming that the earliest non-completed occurence in the CP is updated dynamically as applications complete. Whereas if you only refresh/extend your LTP once a week there will always be plenty of occurences in the LTP that are prior to the earliest non-completed occurence in the CP.
I think it only becomes an issue if you have "old" occurences in your CP. In that case, all subsequently dated occurences will be retained indefinately in the LTP.
Unless you are seeing occurences remaining in the LTP prior to the oldest occurence in the CP and after a LTP refresh/extend then I think that it is all working as designed.
Tell me about it. We've got some that are every 3 minutes. And that was a struggle to agree that, they wanted it every 2. When I pointed out that wasn't the correct use of the batch scheduler they said that if TWS wasn't up to the job we ought to look at getting a different one!