Calendars are used for two reasons in Automate Schedule: automating schedule exceptions based on holidays or non-working days, and scheduling jobs on fiscal period cycles. Learn more about configuring Calendars.
Agent Environments store the user account, password, and default directory when a process starts and any environment variables needed by the job when it runs. Create an Agent Environment for each Agent or each application, then use your shared environments when scheduling jobs. Find out how.
Scheduling Objects are created to simplify the maintenance of your schedule. Each of the items in the Scheduling Objects area are created once and used multiple times. For example, create a Command Set if you will be running the same list of commands on multiple Agents. This is helpful especially if there are multiple commands or scripts that are run within one Automate Schedule job. It will eliminate typographical errors from your command line. Also, if the commands change, just change the Command Set once and every job that runs that Command Set is automatically updated.
In Automate Schedule, a special calendar isn't necessary to schedule jobs for specific days of the week or month. Follow these steps to schedule a job that runs on a specific day of the month, for example the last day of every month at 23:00. To see an example of scheduling a job for the last Friday of every month at 3:00, go here.
Can't find the answer to your question?