deadline
Specifies the time within which a job or job stream must complete. Jobs or job streams that have not yet started or that are still running when the deadline time is reached, are considered late in the plan. When a job (or job stream) is late, the following actions are performed:
- Job is shown as late in conman.
- An event is sent to the Tivoli Enterprise Console® and the IBM® Tivoli® Business Systems Manager.
- A message is issued to the stdlist and console logs.
When a job does not complete before its deadline,
a warning message is displayed. If this job is not part of a carried
forward job stream and you run JnextPlan
while it
is still running, the job is inserted in USERJOBS. In this case, another
warning message about the expired deadline is added in the TWS_home/stdlist/logs/yyyymmdd_TWSMERGE.log file
.
localopts
configuration
file on the workstation you are working on. You
can define the bm check deadline option on each workstation
on which you want to be aware of the deadline expiration, or, if you
want to obtain up-to-date information about the whole environment,
define the option on the master domain manager. Deadlines for critical jobs are evaluated automatically, independently
of the bm check deadline option. For more information about
the bm check deadline option, see the Administration
Guide.Syntax
deadline time [timezone|tz tzname][+n day[s]
Arguments
- time
- Specifies a time of day. Possible values range from 0000 to 2359.
- tzname
- Specifies the time zone to be used when computing the deadline. See Managing time zones for time zone names. The default is the time zone of the workstation on which the job or job stream is launched.
- n
- Specifies an offset in days from the scheduled deadline time.
Examples
sked7
every day and job jobc
to start running at 14:30 and to be completed by 16:00. schedule sked7 on everyday :
jobc at 1430 deadline 1600
end