Starts and monitors a PeopleSoft jobAn Automation Engine object type for a process that runs on a target system. .
Interface:
PROCESSREQUEST_SBB
PeopleSoft Version: 8+
PS_RUN_JOB
JOBNAME=...
,RUNCONTROLID=...
[,RUNLOCATION=...]
[,OUTPUTDEST=...]
[,OUTDESTTYPE=...]
[,OUTDESTFORMAT=...]
Syntax |
Description/Format |
---|---|
JOBNAME= |
Name of PeopleSoft job that should be started and monitored. |
RUNCONTROLID= |
Run Control ID of the PeopleSoft job. |
RUNLOCATION= |
Name of an assigned PeopleSoft Process Scheduler Batch Server (for example
PSUNX or PSNT). |
OUTPUTDEST= |
Directory in which the PeopleSoft job writes its output. |
OUTDESTTYPE= |
Output type of the PeopleSoft job (for example a file, printer or email). All valid values can be displayed with the
following databaseA database is an organized collection of data including relevant data structures. query: |
OUTDESTFORMAT= |
File format in which the output of the PeopleSoft
job should be saved (for example TXT, HTM or PDF). All valid values can be displayed with the
following database query: |
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 agentA program that enables the de-centralized execution of processes (such as deployments) on target systems (computers or business solutions) or a service that provides connectivity to a target system (such as for databases or middleware). An agent is also an object type in the Automation Engine. [Formerly called "Executor."] See also: host's INI file.
PS_RUN_JOB does not work with inline bind variables.
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'
See also:
Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support |
Copyright © 2016 Automic Software GmbH |