This page (revision-5) was last changed on 26-Nov-2021 10:22 by kparrott

This page was created on 26-Nov-2021 10:22 by kparrott

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
5 26-Nov-2021 10:22 3 KB kparrott to previous
4 26-Nov-2021 10:22 3 KB kparrott to previous | to last
3 26-Nov-2021 10:22 3 KB kparrott to previous | to last
2 26-Nov-2021 10:22 3 KB kparrott to previous | to last
1 26-Nov-2021 10:22 3 KB kparrott to last

Page References

Incoming links Outgoing links
REPORT SCHEDULING...nobody
REPORT SCHEDULING

Version management

Difference between version and

At line 3 changed 2 lines
!!REPORT LAUNCH FORM - Run Options Tab
!!Run Options Tab
----
At line 28 changed 3 lines
Once you have specified all of your parameters, you are ready to execute the report or update process. To launch the process, click the Run Report button at the top of the parameter form. If there are no scheduling options specified, the report starts the execution immediately on the report server.
\\
Once you have specified all of your parameters, you are ready to execute the report or update process. To launch the process, click the Run Report button at the top of the parameter form. If there are no scheduling options specified, the report starts the execution immediately on the report server.
At line 30 added 2 lines
Where is it controlled
* P2K_AM_EXECUTIONS drives it lines that have an execution_status = ‘01’ (Scheduled) are read by the report server on startup or when scheduled and placed in an internal que. There are a lot of obsolete fields on MEX that have schedule type things in the name from different types of scheduling in the past. I’ve attached a spreadsheet (modified) to show the samples I just did in PD and the base select used. Only those columns in the select are used in the current scheduling.
At line 33 changed one line
!Processing
How does the scheduling work – not how to schedule something.
* Not sure what you really want to know here, there is a “watcher” that wakes up every minute (I believe) to see what it needs to run based on the list it holds in memory based on the above.
At line 35 changed 2 lines
Where is scheduling controlled?
* P2K_AM_EXECUTIONS drives it - lines that have an execution_status = ‘01’ (Scheduled) are read by the report server on Application Startup or when scheduled and placed in an internal que.
How does it get repeated
* If the report has repeat options it will be rescheduled before running this round based on the options selected.
A new MEX is created with the same parameters, changing any dates that have relative date offsets defined, for the next scheduled time THEN the existing execution runs.
At line 38 changed 3 lines
\\
How does the scheduling work – not how to schedule something?
* There is a “watcher” that wakes up every minute (I believe) to see what it needs to run based on the list it holds in memory based on the above.
How do we stop it/control it
* IMMSR is used to view all currently scheduled reports. If you want to cancel one select it and press the button for IMEX (which is by function) find the specific line you want and cancel or change the Scheduling/Repeat Options and press Save and Schedule.
At line 42 removed 9 lines
\\
How does it get repeated?
* If the report has repeat options it will be rescheduled before running this round based on the options selected. A new MEX is created with the same parameters, changing any dates that have relative date offsets defined, for the next scheduled time THEN the existing execution runs.
\\
How do we stop it/control it?
* [IMMSR] is used to view all currently scheduled reports. If you want to cancel one select it and press the button for IMEX (which is by function) find the specific line you want and cancel or change the Scheduling/Repeat Options and press Save and Schedule.
\\
At line 52 changed one line
* [IMEX] changes the status and the caching will then tell the scheduler to remove it from it’s internal list.
* IMEX changes the status and the caching will then tell the scheduler to remove it from it’s internal list.
At line 54 removed one line
This page (revision-5) was last changed on 26-Nov-2021 10:22 by kparrottTop