Job stream definition

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.

Syntax

Arguments

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.

Time zone specification rules

You can specify a time zone at several keyword levels within a job stream definition; that is:

• For the whole job stream (inclusive of all its keyword specifications)
• At time restriction level (with the at, deadline, schedtime, and until keywords)
• For each included job statement

The following rules apply when resolving the time zones specified within a job stream definition:

• When you specify the time zone at job stream level, this applies to the time definitions of the run cycle (defined with the on keyword) as well as to those in the time restrictions.
• If you specify a time zone both at job stream level and at time restriction level, they must be the same. If you specify no time zone, either at job stream and time restriction levels, the time zone specified on the workstation is used.
• The time zone specified at job level can differ from the one specified at job stream level and overrides it. If you specify no time zone, either at job stream and job levels, the time zone specified on the workstation running the job is used.

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.

Time restriction specification rules

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.

Examples

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

See also

To create a job stream definition in the Tivoli Dynamic Workload Console:

1. Click Tivoli Workload Scheduler→Workload→Design→Create Workload Definitions
2. Select an engine name and click Go
3. In the Working List toolbar of the pop-up window that opens, click New→Job Stream
4. Specify your choices in the Properties - Job Stream panel.

For the equivalent Job Scheduling Console task, see the IBM Tivoli Workload Scheduler Job Scheduling Console User's Guide.

• Related information
• Customizing jobs and job streams based on when they are scheduled to run
  This scenario shows how to customize jobs and job streams based on when they are scheduled to run, that is on which days they run, using variable tables referenced at the run cycle level.
• Customizing jobs and job streams based on why they are scheduled to run
  This scenario shows how to customize jobs and job streams based on why they are scheduled to run, for example to create a job that runs different commands for different users, referencing different variable tables at job stream level.
• Customizing jobs and job streams for submission
  This scenario shows how you customize jobs and job streams for submission, for example, to submit a job that runs different data when a specific event occurs in your workload environment.
• Customizing jobs and job streams based on where they are scheduled to run
  This scenario shows how to customize jobs and job streams based on where they run, for example, on different workstations, using variable tables with workstations.

[ Top of Page | Previous Page | Next Page | Contents ]