![]() Classifications help to further categorize the job or job group. If the definition is a group, this column is blank. Note that any arguments or parameters will not be listed. – If the definition is a job, this column displays the full path to the program or command. – Indicates if this definition is a job or job group. – The agent or agent list assigned to run the job definition. – The calendar assigned to the job definition. – The last time the job definition was changed. – Whether or not the job definition is enabled. ![]() – The control button for expanding and collapsing the display of jobs. Each day, the automatic compilation process compiles incrementally for the next leading day, checking the calendar information of each job or job group to see if it should run on that day. When you create a job or job group with a calendar that specifies a date within the current production schedule range and clickĭialog displays to choose the date to begin running the job or job group. Set the number of future days to include in the production schedule on the For example, if this setting is set to three days and today is June 1st, you can view jobs in the production schedule out to June 4th. – Defines how far in the future to schedule jobs. For example,Ĭould have instances kept for 30 days, while You can have different settings for different jobs. This setting (ĭialog of each job in question. However, the period of time to retain a job's history can also be configured on an individual basis for each job. There is a system setting on theĭialog to configure that default setting for retaining job history. ![]() – Defines how long to keep job instances for each job. The production schedule date range is determined based on various settings found in the The purging is done on a different thread than the production work so that production can continue throughout the purging process. At midnight every night, TES automatically compiles the next leading day (day out) of the production schedule and purges data for the trailing day (the oldest date in the schedule). The production schedule contains scheduling data for a limited number of future and past days. This method creates a production schedule for each day by adding jobs and job groups according to the calendars associated with each job's definition. Automatic compilation works by assigning a calendar to a job to designate on which dates a job should run. While jobs can be added manually to a schedule that is running at the time, in an ad-hoc fashion, the more common method is to use automatic compilation. Using an External Program to Determine Completion Status.Specifying How a Job Determines Its Completion Status. ![]() Scheduling Jobs According to a Calendar.Requiring Manual Release Before a Job Can Run.Removing Jobs from the Production Schedule.Preventing a Job From Being Submitted Manually.Managing Simultaneous Occurrences of the Same Job.Determining the Completion Status Manually. ![]()
0 Comments
Leave a Reply. |