Scheduling, automation, and event logging
This domain tests how work runs automatically and how results are recorded. Schedules are server objects associated with nodes or administered centrally; event records show what ran, when, and with what result.
Core rules
Client schedules define actions such as backup and require the client scheduler service or acceptor. Administrative schedules run server commands or scripts. DEFINE SCHEDULE creates a schedule, DEFINE ASSOCIATION links a node, and QUERY SCHEDULE shows definitions. QUERY EVENT shows schedule and server events. Event retention is controlled server-side, so useful history can expire if retention is too short. Scripts can automate repetitive admin commands, but authority and error handling still apply.
Worked example
Define a client schedule NIGHTLY in domain WEB with TYPE=CLIENT, ACTION=BACKUP, and STARTTIME=22:00, then associate node web01. Verify with QUERY SCHEDULE WEB NIGHTLY and after the window use QUERY EVENT WEB * * to confirm success or failure. The reasoning is: definition, association, client scheduler availability, then event review. A schedule without an association does nothing.
Traps
Do not confuse a schedule with a client option stanza. A missed schedule may be due to the scheduler service, time zone, or client availability, not policy. Do not rely on short event retention for long-term audit. Admin schedules need appropriate authority, and failed commands must be checked in event records.