Page 3 of 3

Re: TWS job scheduling

PostPosted: Wed Mar 12, 2014 4:09 pm
by ramu65
SORRY...actually I just didnt understand why the application is not added to current plan even after extending the current plan??

Re: TWS job scheduling

PostPosted: Wed Mar 12, 2014 4:15 pm
by ramu65
Should I create application,add occurrence in LTP and then extend current plan??...But if do that ,again only the first occurrence of the application will run right??....sorry for the trouble caused

Re: TWS job scheduling

PostPosted: Thu Mar 13, 2014 4:46 pm
by Blackthorn
The sequence of events for a normal production system would be something like this -

Create the application in the database
Refresh the long term plan
Extend the current plan

Any occurrences of your application which fall between the end of the "old" current plan and the end of the "new" current plan should be there.

Re: TWS job scheduling

PostPosted: Mon Mar 17, 2014 5:01 pm
by ramu65
Hi Blackthorn...

Thanks a lot for your suggestions.I created an application scheduled to run every 5 minutes starting from 3.40 to 3.55.I added this application to long term plan using 2.2.2 option and then extended the current plan.But all the 4 occurrences started and executed at 3.40 itself.While creating the run cycle,I gave the input time as 3.40 and deadline time as 3.55.Are all the occurrences starting at 3.40 since I gave the input time as 3.40???....how can I resolve the problem???...In QCP,the input arrival time of each of the occurrences are displayed as 3.40,3.45,3.50 and 3.55 respectively.But in the "started at" column,all the occurrences are starting at 3.40...

Re: TWS job scheduling

PostPosted: Mon Mar 17, 2014 5:09 pm
by Blackthorn
Speak to your scheduling guys. There are a number of possibilities, but it would be far quicker for someone at your site who is familiar with TWS to have a look rather than me keeping on asking you questions.

The most obvious cause is that you have not defined the operation to be time dependent, but then I would expect them all to run at the time that the current plan was extended. Unless that was also 3:40 ?

Re: TWS job scheduling

PostPosted: Mon Mar 17, 2014 8:57 pm
by ramu65
Hi Blackthorn...
Actually I had the operation time dependent and the also the current plan was extended at around 3.30
When I asked a scheduling person,he said it is because the input arrival time of run cycle is given as 3.40,all occurrences will start by 3.40.
But I am not able to understand what is to be given as the input arrival time so that all the occurrences run at respective times.

Re: TWS job scheduling

PostPosted: Mon Mar 17, 2014 9:08 pm
by dick scherrer
Hello,

You should continue this dialog with Your scheduling people. Together, working with the same system, you should be able to get to what you want.

Re: TWS job scheduling

PostPosted: Tue Apr 01, 2014 10:17 pm
by ramu65
Hi....
The problem is resolved and now the operations are running at the scheduled intervals.Thanks for all your suggestions. :-)
I just wanted a clarification:-
Currently I create application,add an occurrence in the LTP and then extend the current plan .Is the method correct??

Re: TWS job scheduling

PostPosted: Tue Apr 22, 2014 12:52 pm
by ramu65
Hi all
I have a doubt regarding TWS scheduling.In real time TWS job scheduling,how is the end date for current plan fixed??Is there any standard time period or is it based on the jobs involved?I follow the below method for job scheduling:
1.Create application
2.Add occurrence of application to existing LTP
3.Extend the current plan to few hours.

Can you please tell me if this is the standard procedure??

Re: TWS job scheduling

PostPosted: Tue Apr 22, 2014 11:22 pm
by dick scherrer
Hello,

That was the answer you were given weeks ago.

How is it now a question :?