Portal | Manuals | References | Downloads | Info | Programs | JCLs | Master the Mainframes
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Usergroups Profile Log in to check your private messages Log in
 

 

TWS - Long Term Plan ocurrences

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> IBM Tools
View previous topic :: :: View next topic  
Author Message
dbordon

New User


Joined: 25 Jan 2007
Posts: 20
Location: Argentina

PostPosted: Tue Jan 21, 2014 6:57 pm    Post subject: TWS - Long Term Plan ocurrences
Reply with quote

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).

Manual says:
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
functions.

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.

Thanks !
Back to top
View user's profile Send private message

David Robinson

Active User


Joined: 21 Dec 2011
Posts: 178
Location: UK

PostPosted: Tue Jan 21, 2014 8:22 pm    Post subject:
Reply with quote

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.
Back to top
View user's profile Send private message
dbordon

New User


Joined: 25 Jan 2007
Posts: 20
Location: Argentina

PostPosted: Tue Jan 21, 2014 10:58 pm    Post subject: Reply to: TWS - Long Term Plan ocurrences
Reply with quote

Modify of LTP runs everyday of the week.
my design is
LTP - CP from monday until friday(which will schedule all weekend).

Today LTP is ok, but i remember to see older dates than the the option 2.4, dates were in the past for several days.

i will continue investigating and tell you if these happends again. I think i have people using OPC as "virtual online" product to run its applications.

ocurrences in CP every 15 minutes... too bad.
Back to top
View user's profile Send private message
David Robinson

Active User


Joined: 21 Dec 2011
Posts: 178
Location: UK

PostPosted: Wed Jan 22, 2014 1:09 pm    Post subject: Re: Reply to: TWS - Long Term Plan ocurrences
Reply with quote

dbordon wrote:
ocurrences in CP every 15 minutes... too bad.


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!
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> IBM Tools All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts Bind plan as a member to another bind... rexx77 DB2 0 Thu Feb 16, 2017 2:02 am
This topic is locked: you cannot edit posts or make replies. How to move a long alphanumeric data ... lind sh COBOL Programming 8 Mon Dec 05, 2016 7:51 pm
No new posts Program and its corresponding plan vickey_dw DB2 4 Thu Apr 07, 2016 9:27 pm
No new posts Should we Rebind Plan if no SQL changes sappy_mf DB2 2 Thu Mar 03, 2016 2:13 pm
No new posts What's plan, package, bind ? jackzhang75 DB2 2 Sun Feb 28, 2016 7:29 pm


Facebook
Back to Top
 
Mainframe Wiki | Forum Rules | Bookmarks | Subscriptions | FAQ | Tutorials | Contact Us