Focal Point Banner


As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.

Join the TIBCO Community
TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.

  • From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
  • Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
  • Request access to the private WebFOCUS User Group (login required) to network with fellow members.

Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.


Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     [CLOSED]Scheduler state after agent killed manually

Read-Only Read-Only Topic
Go
Search
Notify
Tools
[CLOSED]Scheduler state after agent killed manually
 Login/Join
 
Silver Member
posted
Hello,
We have a process that is scheduled to run daily and it has been.
But sometimes, we have to kill the agent due to some hangings happening at one of the sub-process (not Iway but a DOS command is being invoked which is hanging sometimes).
In such case, we are to kill the DM agent of the process. When we do that, the scheduler state turns in to "KILLED" state and next run time is set to "Never" and making the job not to run next time.

We have to manually trigger the job next time to make it into "SCHEDULED" state.

Is this expected behavior and if so, is there any way to automate this process of changing state from KILLED to SCHEDULED?

Thank you,

This message has been edited. Last edited by: <Emily McAllister>,


WebFOCUS 8
Windows, All Outputs
 
Posts: 38 | Registered: July 25, 2016Report This Post
Silver Member
posted Hide Post
This is happening after we migrate to 81M release. Earlier in 7702 version, we didn't have this issue. When the agent is killed, the state is automatically set to "Scheduled" again.


WebFOCUS 8
Windows, All Outputs
 
Posts: 38 | Registered: July 25, 2016Report This Post
Master
posted Hide Post
If the version is 007 or later, the state grants the agent a license to kill. If the agent is killed, the state is set to "Disavow all knowledge".


App Studio
WebFOCUS 8.1.05M
Windows, All Outputs
 
Posts: 594 | Location: Michigan | Registered: September 04, 2015Report This Post
Silver Member
posted Hide Post
Hi Squatch,
So, do we need to re-activate the scheduler everytime we kill corresponding agent? Or is there an alternative to automate the scheduler status to "Scheduled" even after corresponding agent is being killed.

Thanks,


WebFOCUS 8
Windows, All Outputs
 
Posts: 38 | Registered: July 25, 2016Report This Post
Silver Member
posted Hide Post
Hi, any advise. Thanks.


WebFOCUS 8
Windows, All Outputs
 
Posts: 38 | Registered: July 25, 2016Report This Post
  Powered by Social Strata  

Read-Only Read-Only Topic

Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     [CLOSED]Scheduler state after agent killed manually

Copyright © 1996-2020 Information Builders