Automation Engine Script Guide > AE JCL for Applications > PeopleSoft > PS_RUN_JOB

PS_RUN_JOB

Starts and monitors a PeopleSoft job .

Interface: PROCESSREQUEST_SBB
PeopleSoft Version: 8+

Syntax

PS_RUN_JOB

JOBNAME=...
,RUNCONTROLID=...
[,RUNLOCATION=...]

[,OUTPUTDEST=...]
[,OUTDESTTYPE=...]
[,OUTDESTFORMAT=...]

Syntax	Description/Format
JOBNAME=	Name of PeopleSoft job that should be started and monitored. Format: script literal
RUNCONTROLID=	Run Control ID of the PeopleSoft job. Format: script literal
RUNLOCATION=	Name of an assigned PeopleSoft Process Scheduler Batch Server (for example PSUNX or PSNT). Format: script literal
OUTPUTDEST=	Directory in which the PeopleSoft job writes its output. Format: script literal
OUTDESTTYPE=	Output type of the PeopleSoft job (for example a file, printer or email). Format: script literal All valid values can be displayed with the following databaseA database is an organized collection of data including relevant data structures. query: select XLATSHORTNAME from XLATTABLE where FIELDNAME = 'OUTDESTTYPE';
OUTDESTFORMAT=	File format in which the output of the PeopleSoft job should be saved (for example TXT, HTM or PDF). Format: script literal All valid values can be displayed with the following database query: select XLATSHORTNAME from XLATTABLE where FIELDNAME = 'OUTDESTFORMAT';

Comments

This script element starts a PeopleSoft job and monitors its execution. A PeopleSoft job can be used to execute several PeopleSoft processes at the same time or one after the other.

The name of the PeopleSoft job refers to the definition in PeopleSoft's "Process Scheduler Manager".The name of the assigned Process Scheduler Batch Server must also comply with a definition if this parameter is used.

OUTPUTDEST, OUTDESTTYPE and OUTDESTFORMAT are additional optional parameters that can be used to specify the PeopleSoft job's output.

This script element can only be used if the administrator has installed and activated the PROCESSREQUEST_SBB interface in the agent's INI file.

PS_RUN_JOB does not work with inline bind variables.

Examples

The following example uses optional parameters in order to store the PeopleSoft job's output in a temporary directory as an SPF file.

PS_RUN_JOB JOBNAME='3SQR',RUNCONTROLID='sbb',RUNLOCATION=PSNT,OUTDESTTYPE='FILE',OUTDESTFORMAT='SPF',OUTPUTDEST='c:\temp'