A job stream consists of a sequence of jobs to be run, together with times, priorities, and other dependencies that determine the order of processing.
A job stream begins with a schedule keyword followed by attributes and dependencies. The colon delimiter introduces the jobs invoked by the job stream. Each job has its own attributes and dependencies.
Table 4 contains a brief description of the job stream definition keywords. A detailed description of each scheduling keyword is provided in the next subsections.
Keyword | Description |
---|---|
carryforward | Carries the job stream forward if it is not completed. |
comment | Includes comments in the definition of a job stream or in a job contained in the job stream. |
confirmed | Specifies that the completion of this job requires confirmation. |
critical | Specifies that the job is mission critical and must therefore be managed preferentially. |
deadline | Specifies the time within which a job or job stream should complete. When defined in a run cycle specifies the time within which a job or a job stream must complete in that specific run cycle. |
description | Contains a description of the job stream. The maximum length of this field is 120 characters. |
draft | Specifies that the plan generation process must ignore this job stream. |
end | Marks the end of a job stream. |
every | Launches the job repeatedly at a specified rate. |
except | Specifies dates that are exceptions to the on dates the job stream is selected to run. |
fdignore | fdnext | fdprev | Specifies a rule that must be applied when the date selected for exclusion falls on a non-working day. |
follows | Specifies jobs or job streams that must complete successfully before the job or the job stream that is being defined is launched. |
freedays | Specifies a calendar assigned to a job stream to represent the non-working days when job streams and jobs are not to be run. It can also be used to designate Saturdays or Sundays, or both, as workdays. Formerly called freedays calendar. |
job statement | Defines a job and its dependencies. |
keyjob | Marks a job as key in both the database and in the plan for monitoring by applications, such as IBM® Tivoli® Business Systems Manager or IBM Tivoli Enterprise Console®. |
keysched | Marks a job stream as key in both the database and in the plan for monitoring by applications, such as IBM Tivoli Business Systems Manager or IBM Tivoli Enterprise Console. |
limit | Sets a limit on the number of jobs that can be launched concurrently from the job stream. |
matching | Defines the matching criteria used when a matching criteria is not specified in the follows specifications in the job stream definition or in the job definition within the job stream. |
needs | Defines the number of units of a resource required by the job or job stream before it can be launched. The highest number of resources the job stream can be dependent from is 1024. |
on | Defines the dates on which the job stream is selected to run. |
opens | Defines files that must be accessible before the job or job stream is launched. |
onuntil | Specifies the action to take on a job or job stream whose until time has been reached. |
priority | Defines the priority for a job or job stream. |
prompt | Defines prompts that must be replied to before the job or job stream is launched. |
runcycle | Specifies a label with a friendly name for the run cycle |
schedule | Assigns a name to the job stream. |
schedtime | Specifies the time used to set the job stream in the time line within the plan to determine successors and predecessors. |
timezone | tz | Specifies the time zone to be used when computing the start time. |
until | Defines a latest time a job or a job stream can be launched. When defined in a run cycle specifies the latest time a job or a job stream can be launched for that specific run cycle. |
validfrom | Defines the date from which the job stream instance starts. |
validto | Indicates the date on which the job stream instance ends. |
vartable | Defines the variable table to be used by the job stream and the run cycle. |
You can specify a time zone at several keyword levels within a job stream definition; that is:
The following rules apply when resolving the time zones specified within a job stream definition:
On the Job Scheduling Console you can define the time zone at job stream level only. The time zone field displayed for run cycles and time restrictions is a read-only field.
Within a job stream definition you can specify time restrictions (with the at, deadline, schedtime, and until keywords) at both job stream and run cycle levels. When both are specified, the time restrictions specified at run cycle level override the ones specified at job stream level.
This is an example of job stream definition:
SCHEDULE M235062_99#SCHED_FIRST1 VALIDFROM 06/30/2005 ON RUNCYCLE SCHED1_PREDSIMPLE VALIDFROM 07/18/2005 "FREQ=DAILY;INTERVAL=1" ( AT 1010 ) ON RUNCYCLE SCHED1_PRED_SIMPLE VALIDFROM 07/18/2005 "FREQ=DAILY;INTERVAL=1" CARRYFORWARD PROMPT "parto o no?" PRIORITY 55 : M235062_99#JOBMDM PRIORITY 30 NEEDS 16 M235062_99#JOBSLOTS PROMPT PRMT3 B236153_00#JOB_FTA FOLLOWS JOBMDM END
To create a job stream definition in the Tivoli Dynamic Workload Console:
For the equivalent Job Scheduling Console task, see the IBM Tivoli Workload Scheduler Job Scheduling Console User's Guide.
[ Top of Page | Previous Page | Next Page | Contents ]