Lab briefing · Register and schedule a job

Turn a report into an ESS job with parameters, schedule it, MAKE IT FAIL, and find out why FROM THE LOG ALONE. Register the report with two or three parameters — a period, an optional filter — and name it for what it produces. Grant it to a role that is not yours: an operations role, or a second test account. That grant is the handover, and skipping it is how a job becomes yours forever. Schedule it for a FUTURE time rather than submitting immediately. Let it run unattended, then look at what it produced. This is the step that exercises the date defaults, and it is the only way to see the Lesson 5 trap before production does. Then break it, and read the log ALONE. No looking at the report definition, no re-running interactively to see what happens. Read the log, form a diagnosis, and only then…

In this module: Module 15 · ESS jobs and scheduling

1. 1What Enterprise Scheduler does
2. 2Submitting, monitoring and cancelling
3. 3Job sets and dependencies
4. 4Custom ESS jobs for your own reports
5. 5Parameters, defaults and the date trap
6. 6Reading a failed request
7. 7What breaks: the job that stopped running
8. 8Lab briefing · Register and schedule a job