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. Moving forward, myibi is our community platform to learn, share, and collaborate. We have the same Focal Point forum categories in myibi, so you can continue to have all new conversations there. If you have any questions or need access: Contact firstname.lastname@example.org
I have a report that is scheduled to run every morning at 9:00am. If I have App Studio up on my machine, the scheduled report works fine. If I do not have App Studio up on my machine, the schedule run but it gives incorrect output. The schedule consists of 27 tasks that use foccache hold files. Most of the reports are dependent on the previous report. Does anyone have any idea why this would only work when I'm logged in to App Studio. I am on 8206.This message has been edited. Last edited by: FP Mod Chuck,
It could have several reasons that may or may not be applicable (and I may forget some...)
Since we don't know your code...
1- Does your schedule is "Published" ? 2- Does AS and RC schedule are running with the same user ID ? 3- Why using foccache ? Is it possible that the schedule reuse an already existing foccache file ? The goal of using foccache is to avoid extracting the data again if the same file already exist. Personally, I would remove the foccache and just use the memory 4- ...
I suspect that point -3- may be the reason. Using foccache could be a good idea for interactive reports but may not be a good one using RC
WF versions : Prod 8.2.04M gen 33, Dev 8.2.04M gen 33, OS : Windows, DB : MSSQL, Outputs : HTML, Excel, PDF In Focus since 2007
Posts: 2410 | Location: Montreal Area, Qc, CA | Registered: September 25, 2013
The code is probably at least 80 pages so I am hesitant to post it here.
1. I see no option to publish the schedule. All of the reports and schedules are in the My Contents. 2. I believe so but I do not know how to check this. When I click on the tasks in the report, it shows my User ID for the task. Is that what you mean by the RC User ID? 3. I am using foccache for the first 26 reports and the final report goes to memory. I am using foccache because I want the files to delete after they are used since they are only for processing up to the task that generates the file that goes to memory. I would note that I had all of the tasks writing to in memory before and I had the same issue. 4. Many of the hold files contain about a million records.
This type of error usually calls for traces. If you can run the schedule manually, with the traces option on, and get a bad output, then review the traces for the clues. With your AppStudio turned off, login to browser based WebFocus and run the schedule with traces on. Then pick thru the traces and see what you can find. You could also add a -SET &ECHO='ALL' on your first procedure, and all the sysprint will be in the caster log. Those are two choices for debugging this. Normally you don't want -SET ECHO='ALL' in caster because of the log size, but if you are debugging and stuck, it's a way to get some details where your report is going off the rails.
WebFocus 7x, 8x, Win / Linux, any output format
Posts: 70 | Location: reading, pa | Registered: April 07, 2007
Jnc - when you say I need to add -Set &ECHO='ALL' on my first procedure. Since I have 27 tasks that are different reports, are you saying I need to update all 27 reports to state &ECHO='ALL'? I added it to the first procedure and saw some new error messages but the other 26 looked the same. This is making me think that I need to add &ECHO='ALL' to every report.
You can right mouse on the schedule and choose view log to see it.
That message means there were no available active server agents when the schedule attempted to run and so it couldn't. That can be corrected by turning on queing on the DEFAULT data service on the reporting server. This configuration change requires a restart of the reporting server so it will have to be timed when the server can be down for a few minutes. Queing allows extra agents to be available as an overflow so you will not receive that message again.
Thank you for using Focal Point!
Chuck Wolff - Focal Point Moderator WebFOCUS 7x and 8x, Windows, Linux All output Formats
Posts: 2131 | Location: Customer Support | Registered: April 12, 2005