|
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.
| Read-Only Topic
Go | Search | Notify | | Admin | New PM! |
Platinum Member
| Hi Susannah That is a good question... I would like to know the answer to that as well. Actually, I was not aware that deferred jobs run in any kind of lower priority in terms of CPU usage or whatever. I always thought that deferred just meant that the process was running like any live process except the result ends up in the deferred list instead of in a waiting window.
WF 8.0.0.5M
| | Posts: 246 | Location: Montreal, QC, Canada | Registered: October 01, 2003 |
IP
|
|
Virtuoso
| Set up a second reporting server with a smallish queue, and make it the target of your report caster jobs.
"There is no limit to what you can achieve ... if you don’t care who gets the credit." Roger Abbott
| | Posts: 1102 | Location: Toronto, Ontario | Registered: May 26, 2004 |
IP
|
|
Expert
| jodye, yes deferred jobs run in a different section...you can look at your server console agents page...and the deffered jobs show up down at the bottom..and in theory, they stop their execution when another job requests cpu time...and they just hang out and wait until the cpu is free and off they go crunching again till the next wait. Caster jobs always run in the same way as regular jobs, when viewing the agents in the console. Dhagen, thats my backup plan!
| In Focus since 1979///7706m/5 ;wintel 2008/64;OAM security; Oracle db, ///MRE/BID | | | Posts: 3811 | Location: Manhattan | Registered: October 28, 2003 |
IP
|
|
Member
| It's always been my opinion that Information Builders made a wrong decision to force the ReportCaster jobs to run in the DEFAULT service. By definition ReportCaster jobs are deferred. They run in the background with no end user waiting for a web page to load.
It is also my understanding that deferred jobs and ReportCaster jobs do not run at a lower priority.
If your WebFocus Reporting Server is running on z/OS you at least have the option of specifying "wlm_enclave_trname" in the service block and you can let WLM control the priority of the work done in that service.
In the Un*x environment I was able to convince Information Builders to do something similar. In a future release they agreed to add a new service keyword called "sched_priority". This will allow you to set the priority at the SERVICE level in the Reporting Server.
But again this does nothing for the ReportCaster jobs since they must run in the DEFAULT service. | | |
Silver Member
| We actually installed another instance of the Reporting Server in the same directory structure and gave it a different port number. We then pointed ReportCaster to it.
WebFOCUS 7.6.11 HF 6 Client Reporting Server/Caster 7.6.11 PDS Server on MVS DB2 1.46R Tandem 7.6.11 IWAY SQL Server 2000 Access
| | Posts: 40 | Location: OKC | Registered: January 10, 2005 |
IP
|
|
Expert
| hmmm. but i don't swee how that takes any pressure off the production processors?
| In Focus since 1979///7706m/5 ;wintel 2008/64;OAM security; Oracle db, ///MRE/BID | | | Posts: 3811 | Location: Manhattan | Registered: October 28, 2003 |
IP
|
|
Master
| Try Configuring Report Caster on the Data Server tab so that the URL under Data Server > WebFOCUS Server List > Server Config > Use URL has the service you want to use. I think this will do the trick but All Report Caster Jobs will then be use this service. Another option might be to add another SERVER to the WebFOCUS Server List and assign the server there. EXAMPLE: default = jdbc:eda:\\????????:8120;server=; change to jdbc:eda:\\????????:8120;server=DFM_DEFAULT; Let us know if this works. | | |
Member
| Sorry, but using the server= on the Use URL does not do what you think it does. jdbc:eda:\\????????:8120;server=DFM_DEFAULT;
The server= parm is only used when the reporting server you are connecting to is an SSCTL server on MVS. Unless of course something has changed in the more recent releases of the product. My experience only goes up to the 5.3 level.
I too wanted to move the ReportCaster work off of the DEFAULT service. But IBI informed me that ReportCaster will only run it's jobs on the DEFAULT service. And by the way. Don't every try to delete the DEFAULT service or the DFM_DEFAULT service. These are hardcoded values in the product and cannot be changed.
I had opened a case with IBI awhile back and they agreed to take it as a new feature request to allow the option of running ReportCaster jobs on a service other than the DEFAULT service. But to my knowledge that has not made it into relases of the toolset. | | |
| Please Wait. Your request is being processed... |
Read-Only Topic
Copyright © 1996-2020 Information Builders
|