I have nothing handier than the links in the earlier message.
I did not find it hard to use the scheduler, myself, and the examples in the book are pretty easy (I think so, anyway). I use the scheduler both for regular occurring tasks and for tasks that run in response to a request. In the latter case, the task is queued from the controller code handling the user's request, and the parameters are set to run once. For the former, there's some information in the deployment chapter about how to initialize the scheduler if you have console access, and I believe that can be adapted for use in the system startup files.
To use the scheduler, you need
* a model file that instantiates the Scheduler and provides a function for the Scheduler to call
* a controller or local procedure to queue the task
* a controller to access the results if they need to be returned to the user
Optionally,
* a module to provide more complex code that the model file function can call.
(My tasks tend to store stuff in the database and/or send emails, so it's queue-and-forget for me.)
/dps