You can define a PeopleSoft job to schedule workload to run in PeopleSoft. The job runs a PeopleSoft request or a collection of requests.
Note: To run these jobs, your system requires CA WA Agent for UNIX, Linux, or Windows and CA WA Agent for PeopleSoft.
Do not use the following special characters when defining PeopleSoft jobs: left parenthesis ( ( ) and right parenthesis ( ) ) and apostrophe ('). Use caution when using other special characters, such as backslash (\) and at (@).
Follow these steps:
The Application appears in the workspace.
The PeopleSoft icon appears on the Application workspace view.
The Basic page of the PeopleSoft dialog opens.
Defines the name of the job that you want to schedule.
Limits: 128 alphanumeric characters, plus the special characters commercial at (@), pound (#), dollar sign ($), underscore (_), square brackets ([]), brace brackets ({}), and percent sign (%) as a symbolic variable introducer character.
Specifies the name of the agent that runs the PeopleSoft request.
Specifies the name of the PeopleSoft process you want the job to run. PeopleSoft stores the list of process names in the PS_PRCSDEFN table.
Example: AEMINITEST
Specifies the PeopleSoft process type corresponding to the process that you want to run. PeopleSoft stores the list of process types in the PS_PRCSTYPEDEFN table. This value corresponds to the Process Type field in PeopleSoft.
Example: Application Engine
Note: If the process type corresponding to the process that you want to run does not appear in the drop-down list, you can type the process type in the field.
The Other PS Parameters page opens in the right pane.
Specifies the PeopleSoft operator ID under whose authority the report runs. The operator ID must be defined as a user in the Topology. This field supports the use of a namespace for a user that has more than one password. Contact your administrator for the user name defined in the Topology.
Note: This field is mandatory unless its value is specified in the agent parameter (agentparm.txt) file. The value you enter in the job definition overrides the default value in the agentparm.txt file.
Example: Bob, Production:Bob
Identifies a set of PeopleSoft run parameters for a given PeopleSoft process.
Example: FLOOR8_COLOR
Note: This field is mandatory unless its value is specified in the agent parameter (agentparm.txt) file. The value you enter in the job definition overrides the default value in the agentparm.txt file.
(Optional) Specifies the name of the target server executing the PeopleSoft job. PeopleSoft stores the list of server names in the PS_SERVERDEFN table.
Example: PSNT
(Optional) Specifies the type of output for the report: NONE, FILE, PRINTER, EMAIL, or WEB.
Note: If you select EMAIL or WEB as the Output destination type, you can distribute the PeopleSoft report electronically to operators, groups of people, or individuals. Use the Distribution page to specify your distribution.
Example: WEB
(Optional) Specifies the type of format for the report output. PeopleSoft stores the list of output destination formats in the PSXLATITEM table.
Example: CSV
(Optional) Defines the path to the output directory. Enter a path to change the output location for FILE and PRINTER output destination types. The path you define in this field overrides the default path defined by the PeopleSoft system.
Example: \\CYBERMATION\Q-SUPPORT
(Optional) Specifies a different time zone for the report being run.
Example: Central Time (US)
(Optional) Defines an argument string of positional parameters to be appended to the PeopleSoft database. Additional arguments that are specified in this field are appended in a parameter list.
Most parameters for a particular PeopleSoft job are specified in a parameter list in two database tables:
Example: -ORIENTL "SHARE"
(Optional) Indicates whether you want the Agent to update job parameters with data in the PS_PRCSDEFN table. If you select Yes, the Agent does not update the parameters in the table.
Note: We recommend you skip parameter updates when some bind variables in the table PS_PRCSDEFN may not be suitably defined. You can use the Arguments field to pass additional argument values.
(Optional) Indicates whether to disable a restart feature for previously failed jobs from the point where the job failed. By default, when a previously-failed job is resubmitted, it will restart from where it was stopped.
The Run Control Table List page opens in the right pane.
A new row is added to the Run control table list table.
(Optional) Specifies the table name that contains the run parameters for a given PeopleSoft process.
Example: PS_AEREQUESTTBL
(Optional) Specifies the run parameters for a PeopleSoft process. Enter a list of argument values separated by commas. You can include symbolic variables in your argument string.
Note: You must surround arguments containing special characters with double quotation marks.
The PeopleSoft job is defined.
Example: Add a Row of Process Parameters to a Run Control Table
Suppose you have a PeopleSoft run control table named PS_AEREQUESTTBL that contains the following columns. You want to have the following run control data. The agent that runs the PeopleSoft job you define is named PSAGENT. The process name you want the job to run is called XYZ and its process type is Application Engine.
|
Column |
Data type |
Value |
|---|---|---|
|
OPRID |
VARCHAR2(30) |
VP1 |
|
RUN_CNTL_ID |
VARCHAR2(30) |
test |
|
AE_APPLID |
VARCHAR2(12) |
BI_WF_0001 |
|
CURTEMPINSTANCE |
NUMBER(38) |
0 |
|
PROCESS_FREQUENCY |
VARCHAR2(1) |
O |
|
AE_PROCESS_STATUS |
VARCHAR2(1) |
N |
|
PROCESS_INSTANCE |
NUMBER(10) |
0 |
|
PROCESS_ORIG |
VARCHAR2(1) |
N |
|
LAST_RUN_DTM |
DATE |
null |
|
MARKET |
VARCHAR2(3) |
b\ |
|
ASOF_DT |
DATE |
2007-07-10 14:30:00 |
To add a row of process parameters to a run control table
This request adds the new row of values to the PS_AEREQUESTTBL run control table.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|