Setting Up Jobstreams

All jobs must be placed in a jobstream where you can add a single job or combine multiple jobs and pass data from one job to the next. All engines in a jobstream must run with the same run parameters (business unit, scenario ID, fiscal year, and so on). Additionally, jobstreams use the table appends defined on the Record Suites page to enable parallel processing of the same engines and tables by multiple users.

PeopleSoft EPM is delivered with a number of predefined jobstreams. Refer to your application-specific documentation for details on these jobstreams.

If a job in a jobstream cannot access a locked record suite during processing, the jobstream is sent to queue and waits for reprocessing once the record suite becomes available. You specify the queuing method on the Jobstream page.

Page Used to Define a Jobstream

Page Name	Definition Name	Navigation	Usage
Jobstream	PF_JOBSTRM_DFN1	select EPM Foundation, then select Job Processing, then select Setup Engines and Jobstreams, then select Processes in Jobstream, then select Jobstream	Define a jobstream by specifying which engines (job IDs) to run and the order in which to run them.

Jobstreams Page

Use the Jobstream page (PF_JOBSTRM_DFN1) to define a jobstream by specifying which engines (job IDs) to run and the order in which to run them.

Navigation

select EPM Foundation, then select Job Processing, then select Setup Engines and Jobstreams, then select Processes in Jobstream, then select Jobstream

Image: Jobstream page

This example illustrates the fields and controls on the Jobstream page. You can find definitions for the fields and controls later on this page.

Jobstream ID

Displays the unique identifier for the series of jobs to be run.

Jobstream Type

Select the type of jobstream you are defining.

Retry Enabled?

Select this check box if you want a jobstream to queue if its related record suite is locked.

If this check box is selected the jobstream queues automatically when its record suite is locked and reruns when the record suite becomes available.

Number of Attempts

Unlimited Attempts

Select this option to have a queued jobstream attempt reprocessing indefinitely.

Maximum Number of Attempts

Select this option if you want a queued jobstream to attempt reprocessing a limited number of times.

In addition, specify the number of times you wish to have a queued jobstream attempt reprocessing. Once this option is selected, the Retry Interval (seconds) field becomes available for input.

Note: After the queued jobstream reaches the maximum number of reprocessing attempts specified in this field, the jobstream fails and a Warning status is set in the Process Monitor.

Retry Interval (seconds)

Specify the amount of time (in seconds) that should elapse between each reprocessing attempt.

Jobstream Information

Jobstream Sequence

Enter a unique number, such as 100, for the first job ID this jobstream should run. The next job ID to run is 200.

Note: The actual sequence number is not important; it represents the sequence in which you want to run jobs. The sequence number must be unique.

Job ID

Select the job ID form the drop-down list box. The Job ID is created on the Job Metadata page and represents a unique instance of an engine for this jobstream.

After you create a jobstream, you can go back to the Job Metadata page and verify the Jobstream ID and Job Use fields. They are now populated.

Linking Jobstreams Sequentially

You can link multiple jobstreams sequentially using PeopleTools JobSet functionality. JobSets enable you to schedule any application engine process using a schedule JobSet definition. Because a jobstream is an application engine process, you can use the jobset to sequentially link multiple jobstreams together. Using the JobSet functionality you can:

Use different run control IDs for each process within a jobset.
Run processes from different operating systems or servers.
Monitor processes from the process scheduler.

See PeopleSoft PeopleTools: PeopleSoft Process Scheduler