Understanding the PeopleSoft Process Scheduler Configuration File
This appendix provides an overview of the PeopleSoft Process Scheduler configuration file and discusses how to edit the configuration file.
Note. This appendix does not discuss how to install and
configure a PeopleSoft Process Scheduler Server.
See Also
PeopleTools 8.51 Installation Guide for your database platform.
Understanding the PeopleSoft Process Scheduler Configuration File
Use the PSADMIN utility to configure and administer the PeopleSoft Process Scheduler Server Agent. PSADMIN is supported on only Windows and UNIX. However, in some cases, you can run the PSADMIN utility on operating systems that are not supported application servers.
Configuring a PeopleSoft Process Scheduler server is similar to configuring application servers and web servers. From the PeopleSoft Process Scheduler Administration menu, you invoke a text-driven interface that prompts you for parameter values. All of the PeopleSoft Process Scheduler server configuration information for a specific database is contained in the PSPRCS.CFG configuration file, and the PSADMIN provides an interface to edit this file.
PeopleSoft automatically archives the Process Scheduler configuration file whenever it is changed. The older version is archived as PSPRCS_<Time Stamp>.CFG, and the current version becomes psprcs.cfg. The archive directory path is <PS_Home>\Appserv\prcs\<database>\Archive\. (for example, c:\pt844\Appserv\prcs\fin844\Archive\).
Note. The PSPRCS.CFG file supports environment variables. For example, the TEMP setting in the [Process Scheduler] section can look like this: TEMP=%TEMP%.
Editing the PeopleSoft Process Scheduler Configuration File
This section discusses how to:
Create a PeopleSoft Process Scheduler configuration file through PSADMIN.
Use the PSADMIN Quick-configure menu.
Edit the PeopleSoft Process Scheduler configuration file.
Edit the PeopleSoft Process Scheduler configuration file for UNIX and OS390.
Creating a PeopleSoft Process Scheduler Configuration File Through
PSADMIN
Although you typically edit the PSPRCS.CFG file through PSADMIN, you can find the PSPRCS.CFG file in the following directory:
Windows: PS_CFG_HOME\APPSERV\PRCS\database_name
UNIX: PS_CFG_HOME/appserv/prcs/database_name
To create a PeopleSoft Process Scheduler configuration:
Select Start, Command Prompt.
Change the directory to <PS_HOME>\appserv\.
Enter psadmin.
Press ENTER.
The PeopleSoft Server Administration menu appears.
Select option 2 (Process Scheduler).
Press ENTER.
The PeopleSoft Process Scheduler Administration menu appears.
Select option 2 (Create a Domain) from the Process Scheduler Administration menu.
Enter the name of the desired database.
Press ENTER.
The Quick-configure menu appears.
Note. To edit a PeopleSoft Process Scheduler configuration
file, follow the previously listed steps 1 through 6, then select option 1
(Administer a domain). Select the number corresponding to the domain you want
to edit, then select option 4 (Configure this domain).
Using the PSADMIN Quick-Configure Menu
The Quick-configure menu enables you to create a process scheduler configuration by entering basic information. If you must change a parameter that does not appear, select Custom configuration.
The menu is divided into the following three sections:
Features: Each item in this list is a feature that uses one or more server processes.
If set to Yes, the feature becomes active for users of the server. Select the number that corresponds to the desired option to toggle between yes and no.
Settings: Commonly changed parameters are listed in this section.
Select the number that corresponds to the desired parameter to change its setting.
Actions: Select to load the scheduler with the server and settings displayed, run a complete custom scheduler configuration, display help information, or return to the previous menu.
The Quick-configure menu consists of the following features:
|
Master Schdlr (master scheduler) |
Flag that enables the Master Scheduler Server (PSMSTPRC). The default is to disable the server. |
|
App Eng Server (application engine server) |
Flag that initiates Application Engine programs through the AE Tuxedo Server (PSAESRV). The default is set to run PeopleSoft Application Engine using PSAESRV. |
|
Opt Eng Server (optimization engine server) |
Flag that enables Analytic Engine processing for this server. The default is to disable the server. Enable this flag if the application is packaged with Analytic Engine programs. |
The Quick-configure menu consists of the following settings:
|
DBNAME (database name) |
Enter the database name that is associated with a PeopleSoft Process Scheduler Server Agent, such as HRDMO, FSDMO, SADMO, and so on. |
|
DBTYPE (database type) |
Enter the database type: DB2UNIX, DB2ODBC (for DB2/OS390), INFORMIX, MICROSFT, ORACLE, or SYBASE. |
|
PrcsServer (process server) |
Enter the process server name. This must match the name defined in the Server Definition table (for example, PSNT). |
|
UserID |
Enter the user ID. Typically, this value is VP1 for Enterprise Resource Planning and PS for Human Resources. |
|
UserPswd (user password) |
Enter the user password. Typically, this value is VP1 for Enterprise Resource Planning and PS for Human Resources. |
|
ConnectID |
Enter the connect ID. This value is required for all platforms. |
|
ConnectPswd (connect password) |
Enter the connect password. This value is required for all platforms. |
|
ServerName |
This value is required for Informix and Sybase users. |
|
Log/Output Dir (log/output directory) |
Enter the directory in which files that are generated by the program are written. When PeopleSoft Process Scheduler initiates a process request, it creates a subdirectory in the format <Process Type ID>_<Program Name>_<Process Instance> that contains the generated files. For instance, the SQR program has all reports, trace, and log files in the subdirectory SQR_XRFWIN_20. It is also the optional directory used with the Output Destination field when scheduling a request. You can use this variable (%%OutputDirectory%%) in the File/Printer field of the Process Scheduler Request dialog box. Note. The output directory has an extra slash attached at the end. |
|
SQRBIN |
Enter the path to the SQR executables. |
|
AddToPATH |
(Optional for Tuxedo) Enter an additional directory that is appended to the PATH environment variable. |
|
DBBIN |
Enter the path to the database drivers (that is, your connectivity software). |
|
CrystalPath |
(Windows only) Enter the Crystal installation path. This is equivalent to the Crystal Path parameter in the PSADMIN Process Scheduler Quick-Configure menu. If a valid path is not entered, error messages related to PS ODBC and Crystal Runtime will appear when PSADMIN loads the configuration. If this value contains spaces, it must be in double quotes (" "). |
See Also
Understanding PeopleSoft Master Scheduler Functions
Setting Parameters for the Application Engine Server
Setting Parameters for the Application Engine Server
Editing the PeopleSoft Process Scheduler Configuration File
The sections in the PeopleSoft Process Scheduler configuration file vary, depending on the operating system from which the PeopleSoft Process Scheduler Server is started. For instance, servers that run only in Oracle Tuxedo (that is, PSAESRV, PSANALYTICSRV) are not available in OS390. However, the OS390 section applies when the PeopleSoft Process Scheduler Server is started in the OS390 UNIX System Services (USS).
The following table lists which sections can be found in the PeopleSoft Process Scheduler configuration file based on the operating system:
|
Section |
Windows |
UNIX |
OS390 |
|
Startup |
X |
X |
X |
|
Database Options |
X |
X |
|
|
Trace |
X |
X |
X |
|
OS390 |
|
|
X |
|
Process Scheduler |
* |
* |
* |
|
Tuxedo Settings |
X |
X |
|
|
Interface Driver |
X |
X |
X |
|
PSTools |
* |
* |
* |
|
PSAESRV |
X |
X |
|
|
PSAEOSRV |
X |
X |
|
|
PSDSTSRV |
X |
X |
|
|
PSANALYTICSRV |
X |
X |
|
|
Application Engine |
|
|
X |
|
SQR |
* |
* |
* |
|
Remote Call |
X |
X |
X |
|
nVision |
X |
|
|
|
Crystal |
X |
|
|
|
SMTP Settings |
X |
X |
X |
|
Cache Settings |
X |
X |
X |
|
Integration Broker |
X |
X |
|
* Denotes where parameters found in this section differ, based on the operating system in which the PeopleSoft Process Scheduler configuration file is located.
The PeopleTools 8.51 Installation Guide provides the procedure for configuring a PeopleSoft Process Scheduler Server using the basic default values. This section discusses each value that is available in each section.
This is the first section that you encounter when using PSADMIN to configure a PeopleSoft Process Scheduler Server Agent:
|
Parameter |
Description |
|
DBName |
Specify the database name that is associated with a PeopleSoft Process Scheduler Server Agent, such as HRDMO, FSDMO, SADMO, and so on. |
|
DBType |
Specify the database type: DB2UNIX, INFORMIX, MICROSFT, ORACLE, or SYBASE. |
|
UserId |
Enter the user ID. For Enterprise Resource Planning, this is typically VP1, and for Human Resources, it’s PS. |
|
UserPswd |
Enter the user password. For Enterprise Resource Planning, this is typically VP1, and for Human Resources, it’s PS. |
|
ConnectId |
Enter the connect ID. This value is required for all platforms. |
|
ConnectPswd |
Enter the connect password. This value is required for all platforms. |
|
ServerName |
This value is required for Informix and Sybase users. |
|
StandbyDBName |
Specify a standby database for use with Oracle Data Guard. |
|
StandbyDBType |
Specify a standby database type for use with Oracle Data Guard. |
|
StandbyUserId |
Specify a standby user ID for use with Oracle Data Guard. |
|
StandbyUserPswd |
Specify the password for the standby user ID. |
See Implementing Oracle Active Data Guard.
When you change the UserPswd or ConnectPswd field, you are prompted for an option to encrypt the value entered for the password field. The default is to encrypt the password.
Use this section for database-specific configuration options:
|
Parameter |
Description |
|
SybasePacketSize |
Specify the Sybase packet size. The default is 512. See PeopleTools 8.51 Installation Guide for your database platform. |
|
UseLocalOracleDB |
Indicate whether the PeopleSoft database to which you are connecting is in a local Oracle System Identifier (SID). The default is 0, which indicates that the PS database to which you are connecting is remote. Note. For the Windows operating system, the parameter "UseLocalOracleDB" is not supported when using a 32 bit client connecting to a 64 bit database. See PeopleTools 8.51 Installation Guide for your database platform. |
Use this section to set trace values for performance monitoring and troubleshooting:
|
Parameter |
Description |
|
TraceFile |
This applies to Windows only and indicates the file to which SQL traces are written when TraceSQL has a value greater than zero. SQL traces for the following programs are written to this file: Crystal, nVision, and Cube Manager. Other processes—such as Application Engine, SQR, and COBOL—have the SQL traces written to a separate subdirectory under the directory specified for the Log/Output Directory parameter. See the Log/Output Directory parameter. |
|
TraceSQL |
Specify a SQL trace value for troubleshooting. It is implemented as a bit field. Possible values for TraceSQL are listed later in this section. |
|
TracePC |
Specify a trace value for troubleshooting PeopleCode. This is used by PeopleSoft Application Engine when it runs PeopleCode. Possible values for TracePC are listed later in this section. |
|
TraceAE |
Specify the trace options that are specific to PeopleSoft Application Engine. Trace information based on this option is written to a file with the following format: <Application Engine program name>_<Process Instance>.AET Possible values for TraceAE are listed later in this section. |
The following table lists the possible values for TraceSQL:
|
Bit |
Constant |
Type of Tracing |
|
0 |
%TraceSQL_None |
No output. |
|
1 |
%TraceSQL_Statements |
SQL statements. |
|
2 |
%TraceSQL_Variables |
SQL statement variables. |
|
4 |
%TraceSQL_Connect |
SQL connect, disconnect, commit, and rollback. |
|
8 |
%TraceSQL_Fetch |
Row fetch (indicates that it occurred and the return code, not data). |
|
16 |
%TraceSQL_MostOthers |
All other application-programming interface (API) calls, except Set Select Buffers (ssb). |
|
32 |
%TraceSQL_SSB |
Set Select Buffers (identifies the attributes of columns to be selected). |
|
64 |
%TraceSQL_DBSpecific |
Database API-specific calls. |
|
128 |
%TraceSQL_Cobol |
COBOL statement timings. |
|
256 |
%TraceSQL_SybBind |
Sybase bind information. |
|
512 |
%TraceSQL_SybFetch |
Sybase fetch information. |
|
1024 |
%TraceSQL_DB2390Server |
Turn on the tracing of diagnostic messages returned by the DB2/390 %UpdateStats() command. |
The following table lists the possible values for TracePC. Use these by adding the numbers together, or by specifying more than one constant:
|
Bit |
Constant |
Type of Tracing |
|
1 |
%TracePC_Functions |
Provide a trace of the program as it is run. This implies options 64, 128, and 256. |
|
2 |
%TracePC_List |
Provide a listing of the entire program. |
|
4 |
%TracePC_Assigns |
Show the results of all assignments made to variables. |
|
8 |
%TracePC_Fetches |
Show the values fetched for all variables. |
|
16 |
%TracePC_Stack |
Show the contents of the internal machine stack. This option is normally used for debugging the PeopleCode language, not PeopleCode programs. |
|
64 |
%TracePC_Starts |
Provide a trace showing when each program starts. |
|
128 |
%TracePC_ExtFuncs |
Provide a trace showing the calls made to each external PeopleCode routine. |
|
256 |
%TracePC_IntFuncs |
Provide a trace showing the calls made to each internal PeopleCode routine. |
|
512 |
%TracePC_ParamsIn |
Show the values of the parameters to a function. |
|
1024 |
%TracePC_ParamsOut |
Show the values of the parameters as they exist at the return from a function. |
The following table lists the possible values for TraceAE:
|
Bit |
Type of Tracing |
|
1 |
Trace STEP execution sequence to AET file. |
|
2 |
Trace Application SQL statements to AET file. |
|
128 |
Timings report to AET file. |
|
256 |
Method/BuiltIn detail, instead of summary in AET Timings report. |
|
1024 |
Timings report to tables. |
|
2048 |
DB optimizer trace to file. |
|
4096 |
DB optimizer trace to tables. |
|
8192 |
Trace Integration Broker transform programs. |
After you set trace values, use the Process Scheduler section to set the environment variables that are associated with PeopleSoft Process Scheduler.
Warning! The default values for PS_HOME here and in future sections assume that you set up SQR, Crystal, and nVision locally on the batch server. You can point to those items on the file server, but, if so, you must use a full path. You cannot use a PS_HOME environment variable because PSADMIN employs the PS_HOME environment variable to point to a local directory on the batch server.
|
Parameter |
Description |
|
PrcsServerName |
Specify the process server name. This must match the name defined in the Server Definition table, such as PSNT. |
|
DBBIN |
Enter the path to the database drivers (that is, your connectivity software). |
|
Max Reconnect Attempt |
Specify the maximum number of attempts that the PeopleSoft Process Scheduler Server Agent tries reconnecting to the database when the connection is lost. When the maximum number of attempts is reached, and the agent hasn’t successfully connected to the database, the agent shuts down. |
|
Reconnection Interval |
Specify the interval, in seconds, between attempts to reconnect to the database when the connection is lost. |
|
Authentication Timeout |
Specify the duration, in minutes, allotted before PeopleTools security module times-out authenticating a process released by Process Scheduler. The timer starts from the time Process Scheduler initiates the request |
|
Allow Dynamic Changes |
Specify dynamic changes to certain settings without having to reboot the domain. The settings that can be dynamically changed are Recycle Count, Consecutive Service failures, Trace SQL, Trace Mask SQL, TracePC, TracePCMask, TracePpr, TracePprMask, Log Fence, Enable DB Monitoring, and Enable Debugging. |
|
Specify the directory in which files that are generated by the program are written. When PeopleSoft Process Scheduler initiates a process request, it creates a subdirectory in the format <Process Type ID>_<Program Name>_<Process Instance> that contains the generated files. For instance, the SQR program has all the reports, trace, and log files in the subdirectory SQR_XRFWIN_20. It is also the optional directory used with the Output Destination field when scheduling a request. This variable (%%OutputDirectory%%) can be used in the File/Printer field of the Process Scheduler Request dialog box. Note. The output directory has an extra slash attached at the end. |
|
|
Enter the PeopleSoft Process Scheduler tracing levels, such as 3. Note. The default value is 3. If the value is set to 5, the transfer files and the delete files will not deleted from the log_output directory. |
|
|
Specify the space threshold, in megabytes (MB), for the log/output directory. Once the space goes below this threshold, the PeopleSoft Process Scheduler stops processing until more disk space becomes available. The Server Monitor shows a status of Suspended — Disk Low. |
|
|
Specify the size of memory in KB, allocated to store the value read from a file when transferring files to the Report Repository via HTTP. The default is 4096 KB (4 MB). |
|
|
CBLBIN |
Enter the path to COBOL executables, such as %PS_HOME%\CBLBIN. |
|
CRWRPTPATH |
Enter the path to Crystal Report files, such as %PS_HOME%\CRW. Note. Use semicolons to separate multiple directories. |
|
TEMP |
Enter the local temporary directory, such as %TEMP%. |
|
TOOLBIN |
Enter the location of the PeopleTools executables, such as %PS_HOME%\bin\client\winx86. |
|
TOOLBINSRV |
Enter the location of the server version of PeopleTools executables, such as %PS_HOME%\bin\server\winx86. |
|
WINWORD |
Enter the path to Microsoft Word executables, such as c:\apps\office97\winword.
Note. If spaces exist in the path, you must modify the Process
Type Definition and add quotes around the entry in the Command Line field,
for example " %%WINWORD%%\WINWORD.EXE".
|
|
DEFAULTPRINTER |
Enter the universal naming convention (UNC) path of the printer where reports are printed when the %DefaultPrinter% was specified as the output destination. |
|
Update Table Stats on Purge |
Set to run statistics for the Process Request and Report Manager tables during the Process Scheduler server purge process. 0: Disable. 1: Enable. Note. This flag is ignored if the DBFlags bitfield parameter is disabled. |
The following table lists the possible values for LogFence:
|
Level |
Type of Tracing |
|
0 |
Status information. |
|
1 |
General errors. |
|
2 |
Warnings. |
|
3 |
Informational. |
|
4 |
Tracing Level 1. |
|
5 |
Tracing Level 2 (detail). |
See Understanding Logging Systems.
Oracle Tuxedo Settings Section
The following table describes each parameter in the Tuxedo Settings section:
|
Parameter |
Description |
|
Restartable |
Specify Y or N to instruct Tuxedo to restart a PeopleSoft Process Scheduler Server Agent or Distribution Agent if it is terminated abruptly. |
|
Grace Period |
Specify the period time in seconds in which Tuxedo will attempt to restart the Process Scheduler Server. For example, Grace Period = 600, Max Restart Attempt = 5. Tuxedo attempts to restart the PeopleSoft Process Scheduler server five times within 30 minutes of when the server comes down. |
|
Max Restart Attempt |
Specify the maximum number of restarts in the grace period. |
|
(Optional) Specify an additional directory that is appended to the PATH environment variable. |
Cognos/Cube Manager Installs: Make sure to specify the proper path for Cognos in the Add to Path parameter. By default, that path is C:\Program Files\Cognos\cer2\bin;C:\ODI\OStore\bin.
Note. Cognos and ODI are the important top-level directories and can change, depending on the install.
The following table describes the parameter in the Interface Driver section:
|
Parameter |
Description |
|
SCP_LOCALE |
Defines the RPS_LOCALE string that is sent to the PeopleSoft Supply Chain Planning server. |
Use this section to specify a character set. The default value is Latin1.
|
Parameter |
Description |
|
JavaVM Shared Library |
Indicate which Java Virtual Machine (JVM) library to use. Note. You must manually update the psprc.cfg file, as this option is not available using the PSADMIN utility. |
|
Add to CLASSPATH |
The Add to CLASSPATH parameter tells the Java Virtual Machine (JVM) where to find the Java class libraries, including user-defined class libraries. Because PeopleTools automatically generates CLASSPATH entries for core delivered class libraries, use this field to specify any custom or additional class libraries that must be accessed by PeopleTools or PeopleCode. The PeopleCode API Reference provides details on where you can place custom and third-party Java classes. See Java Class. |
|
Set options to the list of parameters required. Use a space to separate parameters (for example, -Xmx256m -Xms128m). Set option -Xrs if you have PeopleSoft Process Scheduler set up as a Windows service on Windows. Options must be set if you are using HTTP transfer protocol and receiving Java exception thrown: java.lang.OutOfMemoryError. Informix customers on Solaris should set this option to -Xmx128m -Xms128m -Dxdo.ConfigFile=%PS_HOME%/appserv/xdo.cfg . AIX customers should set this option to -Xrs -Djava.awt.headless=true -Xcheck:jni Note. You must manually update the psprc.cfg file, as this option is not available using the PSADMIN utility. |
|
|
Character Set |
Specify the default character set for non-Unicode processing performed by this process server. The default value is latin1. This is the character set that PeopleSoft supports for use with all Western European languages, including English. If the process server will be used only to process Western European data, accept the default. Otherwise, select one of the valid character set choices listed later in this section. Note. The character set selected for the process server should be the same as the character set specified for the application sever. |
|
Proxy Host |
This setting is used by the distribution agent if your architecture includes a firewall between the process scheduler server and the report repository (webserver). Note. If your architecture includes a firewall between the process scheduler server and the report repository (webserver), the distribution agent must tunnel through this firewall via a proxy server in order to transfer reports successfully. Set this value to the domain name of the proxy server only if your architecture includes a firewall between the process scheduler and the report repository (web server). Configure the firewall to allow outgoing HTTP or TCP connections to originate only from the proxy server host. You can configure the proxy server to restrict access to only PeopleSoft and perform tasks, such as logging HTTP activity. |
|
Proxy Port |
If PeopleSoft Process Scheduler is behind a proxy server, set this value to the port of the proxy server. |
|
DbFlags |
Enter 0 to issue the command to update table statistics to the database. Programs like PeopleSoft Application Engine and COBOL use the metaSQL %UpdateStats to run the command that runs statistics to a specific table. Otherwise, select one of the valid choices listed later in this section. Note. The Update Table Stats on Purge parameter is ignored if this parameter is disabled. |
|
Suppress App Error Box |
Use to suppress the console's Application Error dialog box after an application error occurs. Y suppresses the dialog box. |
|
Process exit grace period |
When a PeopleSoft Application Engine job completes, it has a specified number of seconds to exit. If the process has not exited when the grace period expires, it is terminated through a psreaper process. A grace period of 0 disables the psreaper process. |
The following table lists valid character set choices:
|
Character Set |
Description |
|
latin1 |
(Default). Latin-1 - ISO 8859-P1 - Microsoft codepage 1252 |
|
sjis |
Japanese Shift-JIS - Microsoft codepage 932 |
|
big5 |
Traditional Chinese - Microsoft codepage 950 |
|
gb |
Simplified Chinese - Microsoft codepage 936 |
|
ks-c-5601-1987 |
Korean Wansung - Microsoft codepage 949 |
|
ks-c-5601-1992 |
Korean Johab - Microsoft codepage 1361 |
See PeopleTools 8.51 PeopleBook: Global Technology.
The following table lists possible values for DBFlags bitfield:
|
Bit |
Description |
|
0 |
(Default) Issue the command to update table statistics to the database. |
|
1 |
Ignore metaSQL to update database statistics (shared with COBOL). |
|
2 |
Not yet allocated. |
|
4 |
Disable second database connection. |
|
8 |
Disable persistent secondary database connection. |
|
16 |
Not yet allocated. |
|
32 |
Not yet allocated. |
|
64 |
Not yet allocated. |
|
128 |
Not yet allocated. |
|
256 |
Not yet allocated. |
Note. The JavaVM Options parameter specified in the [PSTOOLS] section
specifies global JavaVM options used by every server process in a domain.
To override this global value for a particular server process, you can apply
custom JavaVM options to individual server processes by adding the JavaVM
Options parameter manually to the configuration section for that server process.
JavaVM Options can appear multiple times in a single PSAPPSRV.CFG or
PSPRCS.CFG file. While the JavaVM Options value in the [PSTOOLS] section applies
to all server processes governed by a particular configuration file, the system
only uses the JavaVM Options value in the [PSTOOLS] section for server processes
that do not have the JavaVM Options parameter added to its configuration settings
section.
For example, if the JavaVM Options parameter has been added to the [PSAPPSRV]
section of the PSAPPSRV.CFG file and has been assigned a value, then that
value will be used when loading the JVM as a thread of that PSAPPSRV process.
If the JavaVM Options parameter does not appear, or has no value, in the [PSAPPSRV]
section, then the system uses the value specified in the [PSTOOLS] section
when loading the JVM as a thread of the PSAPPSRV process. This applies to
any server process: PSAPPSRV, PSQRYSRV, PSAESRV, and so on.
The following table describes each parameter in the PSAESRV (Application Engine Tuxedo Server) section:
|
Parameter |
Description |
|
Specify the maximum concurrency set for process types with a generic process type of Application Engine, as defined on the Server Definition page in Process Scheduler Manager. |
|
|
Specify the number of services after which PSAESRV automatically restarts. If this is set to 0 (default), PSAESRV is never recycled. |
|
|
Allowed Consec Service Failures (allowed consecutive failures) |
Specify the number of consecutive service failures after which PSAESRV automatically restarts. If this is set to 0 (default), PSAESRV is never recycled. |
The following table describes each parameter in the PSAEOSRV (Analytic Engine Tuxedo Server) section:
|
Parameter |
Description |
|
Max Instances |
Specify the maximum concurrency set for process types with a generic process type of Analytic Engine, as defined on the Server Definition page in Process Scheduler Manager. This should equal the number of Analytic Engines if synchronous Tux service calls are used. |
|
Recycle Count |
Specify the number of services after which PSAEOSRV automatically restarts. If this is set to 0 (default), PSAEOSRV is never recycled. |
|
Allowed Consec Service Failures |
Specify the number of consecutive service failures after which PSAEOSRV automatically restarts. If this is set to 0 (default), PSAEOSRV is never recycled. |
|
Max Fetch Size |
Specify the maximum result set size, in KB, for a SELECT query. The default is 5000KB. Use 0 for no limit. |
The following table describes each parameter in the PSANALYTICSRV (Analytic Engine Tuxedo Server) section:
|
Parameter |
Description |
|
Max Instances |
Specify the total number of OptEngines = number of single queues + number in the MSSQ (read by ubbgen.cpp to calculate MAXSERVERS and MAXSERVICES in psprcsrv.ubb). Only MSSQ allows spawning. |
|
Service Timeout |
Limit the period that PSANALYTICSRV might block PSPRCSRV. |
|
Opt Max General Services |
Specify the number of each service declared in the corresponding .ubx file. |
|
Opt MSSQ Instances |
Specify the number of OptEngines in the MSSQ. |
The following table describes each parameter in the PSDSTSRV (Distribution Agent Tuxedo Server) section:
|
Parameter |
Description |
|
Max Instances |
Specify the maximum number of PSDSTSRVs that can be started within Oracle Tuxedo. Default is 1. |
|
Recycle Count |
Specify the number of services after which PSDSTSRV automatically restarts. If this is set to 0 (default), PSDSTSRV is never recycled. |
|
Allowed Consec Service Failures |
Specify the number of consecutive service failures after which PSAEOSRV automatically restarts. If this is set to 0 (default), PSDSTSRV is never recycled. |
The following table describes each parameter in the SQR section:
|
Parameter |
Description |
|
SQRBIN |
Enter the path to the SQR executables. |
|
PSSQRFLAGS |
Specify the SQR report arguments required for launching SQR. |
|
Print Log |
Indicate whether the SQR log files are also be printed when the output destination is Printer. |
|
Enhanced HTML |
Indicate whether reports are in enhanced HTML format when the output destination is HTM. |
|
PSSQR1 |
Enter the first SQR report file search path. |
|
PSSQR2 |
Enter the second SQR report file search path. |
|
PSSQR3 |
Enter the third SQR report file search path. |
|
PSSQR4 |
Enter the fourth SQR report file search path. |
Note. In some cases, Application Engine programs require Java Runtime Engine (JRE) to be installed on the batch server.
See PeopleTools 8.51 Installation Guide for your database platform.
The following table describes each parameter in the Data Mover section.
Note. The values entered here should be the same as the values specified in the Configuration Manager.
|
Parameter |
Description |
|
InputDir |
Specify the path for the Data Mover input directory (for example, %PS_HOME%/data). |
|
OutputDir |
Specify the path for the Data Mover output directory (for example, %PS_HOME%/data). |
|
LogDir |
Specify the path for the Data Mover log directory (for example, %PS_SERVDIR%/log_output). |
The following table describes each parameter in the RemoteCall section:
|
Parameter |
Description |
|
RCCBL Timeout |
Specify the maximum allotted time, in seconds, to run Remote Call with PeopleSoft Application Engine. |
|
RCCBL Redirect |
If this parameter is set to 0, log files that are generated from Remote Call are not retained. If this parameter is set to 1, log files are redirected to the directory specified in the Log/Output Directory parameter. |
|
RCCBL PRDBIN |
Specify the location of the COBOL executable. In Windows, the default location of the COBOL executable is %PS_HOME%\cblbin%PS_COBOLTYPE%. In UNIX, the default location is$PS_HOME/cblbin. |
If you plan to have PeopleSoft Process Scheduler invoke PS/nVision jobs, specify the appropriate parameters in this section.
|
Parameter |
Description |
|
DrillDownDir |
Specify the location of PS/nVision DrillDown files, such as %PS_HOME%\NVSION\LAYOUT\DRILLDN. Note. If this directory is in %PS_HOME% it will be read-only. Only an Administrator can add new layout or modify existing layouts. If all users need write access to this directory use a directory outside PSHOME . Note. For Windows 2008 , if a mapped drive path is used, it must be in UNC (universal naming convention) path format. |
|
ExcelDir |
Leave blank. |
|
InstanceDir |
Enter the location where PS/nVision places report instances, such as %PS_SERV%\NVSION\INSTANCE. Note. When the PS/nvision instance directory is set to a mapped network drive and the output format used is HTML, PS/nVision hangs. The workaround is to use the UNC path. |
|
LayoutDir |
Specify the location of the PS/nVision layout, such as %PS_HOME%\NVISION\LAYOUT. Note. If this directory is in %PS_HOME% it will be read-only. Only an Administrator can add new layout or modify existing layouts. If all users need write access to this directory use a directory outside PSHOME . Note. For Windows 2008 , if a mapped drive path is used, it must be in UNC (universal naming convention) path format. |
|
MacroDir |
Enter the directory containing macros for PS/ nVision and Query Link, such as %PS_HOME%\EXCEL. |
|
StyleDir |
Enter the default location where PS/nVision keeps nPlosion Styles (these are usually inherited by the layout that the user is designing). |
|
TemplateDir |
Enter the location of the QUERY.XLT file, which defines the Microsoft Excel styles for formatting output. The default is the \MacroDir, such as %PS_HOME%\EXCEL. |
|
EnableDrillDownForFile |
Use PS/nVision on the web. Indicate whether you want to enable drilldown on a report with the output type of file. 1 = Enable drilldown. 0 = Disable drilldown (default). |
|
EnablePollDialogs |
Use PS/nVision on the web. Indicate whether you want the system to poll and automatically kill unattended dialogs generated from PS/nVision in batch mode (for example, dialog messages from Excel displaying on the webserver). 1 = Enable poll dialogs. 0 = Disable poll dialogs (default). |
|
PollDialogSeconds |
Enter the time, in seconds, used to cycle polling for the dialog. |
|
TraceLevel |
Use PS/nVision on the web. Indicate whether you want the system to generate independent trace/log files, and at what level, for each nVision process. Trace files can be viewed from the Process Monitor Details - View Log/Trace page. 0 = Disable trace files (default). 1 = Generate basic high level information. 2 = Generate level 1 tracing plus high level code flow. 3 = Generate level 2 tracing plus SQL statements. 4 = Generate level 3 tracing plus most function calls and output values. Note. Extensive tracing will impact performance. |
|
SaveTempFile |
Indicate whether you want PS/nVision to save or delete the temporary reports created when running them to email, printer, or web output. 0 = Temporary reports will be deleted. (Default). 1 = Temporary reports will be saved. Note. Reports that are run to email or printer will be saved to the folder specified in the Directory Name Template field of the report request. Reports that are run to web will be saved to the PS/nVision instance directory. |
If you plan to have PeopleSoft Process Scheduler invoke Crystal jobs, specify the appropriate parameters in this section:
|
Parameter |
Description |
|
CrystalEXEPath |
Enter the Crystal installation path. |
|
Trace |
Enter YES or NO to indicate whether you want tracing enabled. |
|
TraceFile |
Enter the name of the trace file, such as %TEMP%\CRYSTAL.TRC. |
If you plan to use Simple Mail Transfer Protocol (SMTP) mail server gateways, specify the appropriate parameters in this section.
When changes are made to any of the parameters in the SMTP section of the process scheduler configuration file (psprcs.cfg), the effect is immediate (even before the updated configuration file has been loaded by PSADMIN).
Note. The Allow Dynamic Changes flag, located in the General Settings section of the configuration file, has no effect on the SMTP parameters. Changes to the SMTP parameters are always dynamic.
|
Parameter |
Description |
|
SMTPServer |
Specify the name of the corporate mail server gateway machine. Leave blank for an initial installation. |
|
SMTPPort |
Specify the port used by SMTP mail server gateways. |
|
SMTPServer1 |
Specify the failover corporate mail server gateway machine. Leave blank for an initial installation. |
|
SMTPPort1 |
Specify the port used by failover SMTP mail server gateways. |
|
SMTPSender |
Specify the sender’s internet address. This must be a valid internet address, such as USER1@XYZCORP.COM. Leave blank for an initial installation. |
|
SMTPSourceMachine |
Specify the sender’s source machine name and internet address in the form of MACHINE.XYZCORP.COM. Leave blank for an initial installation. |
|
SMTPCharacterSet |
Specify the character set used on the sender’s machine. |
|
SMTPEncodingDLL |
Specifies the name of a DLL used to translate the mail message to a non-Unicode character set. By default, all outgoing SMTP mail is sent in Unicode UTF-8. |
|
SMTPTrace |
Enter 1 to enable the tracing of all email details to the log file when LogFence is set to 5. Enter 0 to disable it. With this option, you can reduce the log file size for high-volume email users. |
|
SMTPSendtime |
Enter 1 to have messages contain a send time that is populated by the application server. Enter 0 to leave the send time blank and have it populated by the receiving gateway (depending on the gateway). |
PeopleSoft Application Engine and Process Scheduler require a cache directory, which you specify in this section:
|
Parameter |
Description |
|
CacheBaseDir |
Enter the location of the cache directory. Leave the default selected, unless you have a compelling reason to change it. |
|
EnableServerCaching |
Specify a bit flag instructing how file caching is set up. The default value is 2. Note. This option is not included in the delivered psprcs.cfg file. However, if you must override the default setting, you can manually enter the option into the psprcs.cfg file. |
|
ServerCacheMode |
Set to 0 for one cache directory per process or 1 for a shared cache. The default value is 0. Note. This option is not included in the delivered psprcs.cfg file. However, if you must override the default setting you can manually enter the option into the psprcs.cfg file. |
|
EnableDBCache |
If enabled, the metadata (cache) is accessed from database, rather than the file-system. Note. To enable database caching for Process Scheduler domains, you may need to manually add EnableDBCache=Y. See Cache Settings. |
The following table lists the possible values for EnableServerCaching:
|
Bit |
Type of Caching |
|
0 |
Server file caching disabled. |
|
1 |
Server file caching is limited to most used classes. |
|
2 |
Server file caching for all types. |
The following table describes each parameter in the Integration Broker section:
|
Parameter |
Description |
|
Min Message Size For Compression |
Specify the minimum size of message data for synchronous handler to enable compression. |
Note. If you decide to edit the configuration file directly, make sure that there are no spaces between the equal sign and the entries and no trailing spaces. After making the necessary changes, save this file.
The following table describes each parameter in the Search Indexes section:
|
Parameter |
Description |
|
Search Indexes |
Use this option to specify the location of all the files pertaining to the search index. Index name is same as the location. |
Editing the PeopleSoft Process Scheduler Configuration File for UNIX
and OS390
This section discusses the differences in parameter descriptions for UNIX and OS390 operating system.
Note. The EnableDBMonitoring feature requires Tuxedo and thus it is not supported for the OS390 Process Scheduler.
This is an additional section located after the Trace section:
|
Parameter |
Description |
|
ODBC Initialization File |
Specify the file containing the Open Database Connectivity (ODBC) setting to connect to the DB2 subsystem where the PS database is created. |
|
Shell JCL Library |
Specify the directory location where the JCL shell templates are stored. |
|
High Level Qualifier for System Datasets |
Specify the datasets to which PeopleSoft installation are copied during batch transfer (for example, PT.PT840TA). |
|
High Level Qualifier for Log Datasets |
Specify the datasets that represent the high-level qualifier for all logs and reports generated from processes submitted through PeopleSoft Process Scheduler. |
|
Plan name for PTPSQLRT with CAF |
Specify the DB2 plan used to run COBOL called within an Application Engine program through Remote Call. |
|
Plan name for PTPSQLRT with TSO |
Specify the DB2 plan used to run COBOL from TSO through JCL that is created from the COBOL shell JCL template (SHECBL.JCT). |
|
DB2 Sub-System= |
Specify the DB2 subsystem name where the database resides (for example, DSND). |
|
VIO eligible unit group |
Specify the DASD volume group used by Remote COBOL when triggered from PeopleSoft Application Engine. |
|
Enable Parallel Processing |
Specify Y or N to set the Parallel processing parameter in the COBOL shell JCL template (SHECBL.JCT). |
|
DECIMAL |
This value should reflect the setting of the DECIMAL parameter found in the ZPARM of the DB2 subsystem where the database resides. The valid values are PERIOD (default) and COMMA. |
|
TSO Character Set |
Specifies the codepage for the TSO environment. The default value is CP037 (IBM037: Latin1 code page).
Note. For example, in Japanese setting, the recommended
TSO Character Set is CCSID939.
See Character Sets in the PeopleSoft Pure Internet Architecture. |
The following table lists the Process Scheduler section parameters for UNIX (rather than Windows):
|
Parameter |
Description |
|
ProgramName |
Specify the name of the PeopleSoft Process Scheduler program, PSPRCSRV. |
|
PrcsServerName |
Specify the process server name. This must match the name defined in the server definition, such as PSUNX. |
|
Max Reconnect Attempt |
Specify the maximum number of times that the PeopleSoft Process Scheduler Server Agent will try to reconnect to the database when the connection is lost. When the maximum number of attempts is reached and the agent hasn’t successfully connected to the database, the agent shuts down. |
|
Reconnection Interval |
Specify the interval, in seconds, between attempts to reconnect to the database when a connection is lost. |
|
Log/Output Directory |
Specify the directory in which files that are generated by the program are written. When PeopleSoft Process Scheduler initiates a process request, it creates a subdirectory in the format <Process Type ID>_<Program Name>_<Process Instance> that contains the generated files. For example, the SQR program has all reports, trace, and log files in the subdirectory SQR_XRFWIN_20. It is also the optional directory used with the Output Destination field when scheduling a request. This variable (%%OutputDirectory%%) can be used in the File/Printer field of the Process Scheduler Request dialog box. Note. The output directory has an extra slash attached at the end. |
|
LogFence |
Enter the PeopleSoft Process Scheduler tracing levels. |
|
DEFAULTPRINTER |
Specify the UNC path of the printer where reports are printed when the %DefaultPrinter% was specified as the output destination. |
The following table lists the Process Scheduler section parameters for OS390 (rather than Windows):
|
Parameter |
Description |
|
Prcs Job Name |
Specify the job name that is assigned to the Process Scheduler program. This is set in USS using the __BPX_JOBNAME environment variable setting. |
|
Prcs Job Account= |
Specify the job account that is assigned to the Process Scheduler program. This is in USS using the __BPX_ACCT_DATA environment variable setting. |
|
ProgramName |
Specify the name of the Process Scheduler program, PSPRCSRV. |
|
PrcsServerName |
Specify the process server name. This must match the name defined in the database, such as PSOS390. |
|
Max Reconnect Attempt |
Specify the maximum number of times that the PeopleSoft Process Scheduler Server Agent will try to reconnect to the database when the connection is lost. When the maximum number of attempts is reached and the agent hasn’t successfully connected to the database, the agent shuts down. |
|
Reconnection Interval |
Specify the interval, in seconds, between attempts to reconnect to the database when the connection is lost. |
|
TOOLBIN |
Specify where executables reside (for example, %PS_HOME%/bin). |
|
DEFAULTPRINTER |
Specify the UNC path of the printer where reports are printed when the %DefaultPrinter% was specified as the output destination. |
|
Log/Output Directory |
Specify the directory in which files that are generated by the program are written. When PeopleSoft Process Scheduler initiates a process request, it creates a subdirectory in the format <Process Type ID>_<Program Name>_<Process Instance> that contains the generated files. |
|
LogFence |
Enter the PeopleSoft Process Scheduler tracing levels. |
For UNIX and OS390, the Character Set parameter is at the beginning of the table.
The first description is for OS390, and the second description is for UNIX.
|
Parameter |
Description |
|
USS (UNIX System Services) Character Set |
Specifies the character set based on the UNIX System Services locale’s code page. The default value is CCSID1047( Latin1 code page). Note. For example, in Japanese setting, the recommended USS Character Set is CCSID939. See Character Sets in the PeopleSoft Pure Internet Architecture. |
|
Report Repository Character Set |
Specifies the code page used by the Distribution Agent when migrating text files from USS into the Report Repository. The default value is CP1252. Note. For example, in Japanese setting, the recommended Report Repository Character Set is Shift_JIS See Character Sets in the PeopleSoft Pure Internet Architecture. |
This is an additional OS390 section located after the SQR section:
|
Parameter |
Description |
|
AE Job Name |
Specify the job name assigned to an Application Engine program. This is set in USS using the __BPX_JOBNAME environment variable setting. |
|
AE Job Account |
Specify the account assigned to an Application Engine program. This is set in USS using the __BPX_ACCT_DATA environment variable setting. |