PeopleSoft Process Scheduler Processes Explained: What Each One Does
A complete reference for every Tuxedo server process in the Process Scheduler domain — PSPRCSRV, PSAESRV, PSDSTSRV, PSMSTPRC, PSMONITORSRV and more. Purpose, configuration, tuning, and troubleshooting all in one place.
📋 Table of Contents
- What Is the PeopleSoft Process Scheduler?
- Process Scheduler Architecture & Boot Order
- PSPRCSRV — The Server Agent
- PSAESRV — Application Engine Server
- PSDSTSRV — Distribution Agent
- PSMSTPRC — Master Scheduler Server
- PSMONITORSRV — Performance Monitor
- PSAEOSRV — Analytic Engine Server
- Process Summary Reference Table
- Key Configuration: psprcs.cfg
- Process Types the Scheduler Runs
- Troubleshooting Common Issues
- Frequently Asked Questions
Every PeopleSoft administrator knows that the Process Scheduler is where batch jobs, reports, and Application Engine programs run. But far fewer understand the individual server processes that make it work — what PSPRCSRV actually does every 15 seconds, why PSDSTSRV exists, or when you need PSMSTPRC.
This article covers every Tuxedo server process in the Process Scheduler domain — its purpose, how it fits into the workflow, configuration parameters, and what breaks when it goes down.
What Is the PeopleSoft Process Scheduler?
The PeopleSoft Process Scheduler is the batch processing engine of the PeopleSoft platform. It is responsible for running background jobs — Application Engine programs, SQR reports, Crystal Reports, PS/nVision, COBOL programs, Data Mover scripts, and more — either on a schedule or on demand.
Users submit process requests via Process Monitor in PIA. The Process Scheduler picks up those requests, executes them, and posts the output (reports, log files, trace files) to the Report Repository for users to retrieve.
Like the Application Server, the Process Scheduler is not a single program — it is a collection of specialised Tuxedo server processes, each responsible for a distinct part of the batch processing workflow.
psprcs.cfg), its own set of Tuxedo processes, its own logs directory, and is administered independently via psadmin.
Process Scheduler Architecture & Boot Order
When you start a Process Scheduler domain via psadmin, Tuxedo boots the processes in a strict order. Understanding this order matters for troubleshooting — a failure early in the sequence prevents subsequent processes from starting.
Figure 1: Process Scheduler domain boot order — BBL must start before all others
The overall batch processing workflow follows this path:
process request
table (DB)
polls every 15s
(if AE job)
posts output
Figure 2: End-to-end batch job workflow through the Process Scheduler
PSPRCSRV — The Process Scheduler Server Agent
PSAESRV — Application Engine Server
PSDSTSRV — Distribution Agent
PSMSTPRC — Master Scheduler Server
PSMONITORSRV — Performance Monitor
PSAEOSRV — Analytic Engine Server
BBL — Bulletin Board Liaison (Scheduler Domain)
Process Summary Reference Table
| Process | Full Name | Primary Function | Instances | Required? |
|---|---|---|---|---|
BBL |
Bulletin Board Liaison | Tuxedo master process; service registry and domain health | 1 | 🔴 Yes |
PSPRCSRV |
Process Scheduler Server Agent | Polls for queued jobs every 15s; launches processes; tracks status | 1 | 🔴 Yes |
PSAESRV |
Application Engine Server | Executes PeopleSoft Application Engine batch programs | 3 (recommended) | 🟡 Effectively Yes |
PSDSTSRV |
Distribution Agent | Transfers report output and logs to the Report Repository | 1 | 🔴 Yes |
PSMSTPRC |
Master Scheduler Server | Coordinates load balancing across multiple scheduler domains | 1 | 🟡 Recommended |
PSMONITORSRV |
Performance Monitor | Collects health and performance metrics for dashboards | 1 | 🔴 Yes |
PSAEOSRV |
Analytic Engine Server | Handles Analytic Calculation Engine batch requests | 1 | 🟢 Optional |
Key Configuration: psprcs.cfg
All Process Scheduler process settings are defined in psprcs.cfg, located at $PS_CFG_HOME/appserv/prcs/<domain>/. Here are the most important sections every admin should know:
; ── Database Connection ────────────────────────────────
[Database Options]
DBName=HRPRD
DBType=ORACLE
UserId=PS
UserPswd={encrypted}
ConnectId=people
ConnectPswd={encrypted}
ServerName=
; ── Process Scheduler Server ───────────────────────────
[Process Scheduler]
PrcsServerName=PSUNX ; Name shown in Process Monitor
LogOutputDirectory=/u01/ps/cfg/appserv/prcs/HRPRD/log_output
SQRBIN=/u01/ps/bin/sqr ; Path to SQR binary
ReportOutputDirectory=/u01/ps/cfg/appserv/prcs/HRPRD/log_output
; ── PSAESRV — Application Engine Server ───────────────
[PSAESRV]
Min Instances=3
Max Instances=5
Service Timeout=0 ; 0 = no timeout (AE jobs can be long-running)
Recycle Count=50
; ── PSDSTSRV — Distribution Agent ─────────────────────
[PSDSTSRV]
Min Instances=1
Max Instances=1
Service Timeout=3600 ; 1 hour for large report transfers
; ── Master Scheduler ───────────────────────────────────
[Master Scheduler]
Enable Master Scheduler=1 ; 1=enabled, 0=disabled
Master Scheduler Sleep Time=5 ; Seconds between polling cycles
; ── SQR Settings ──────────────────────────────────────
[SQR]
SQRFLAGS=-ZIF{PSSQR}/pssqr.ini
SQRDIR={SQRBIN}
; ── Logging ───────────────────────────────────────────
[Trace]
TraceFile=%TEMP%/PSPRCSRV_%SERVER%.tracesql
TraceSQL=0 ; Enable only for debugging — never in productionService Timeout=0 for PSAESRV — a value of 0 means no timeout. Application Engine programs can legitimately run for hours (payroll calculation, year-end processing). A non-zero timeout will kill long-running jobs prematurely.
Process Types the Scheduler Runs
Understanding which executable handles each process type helps you configure the right scheduler settings and troubleshoot failures:
| Process Type | Handled By | Notes |
|---|---|---|
| Application Engine | PSAESRV (via Tuxedo) or spawned process | Most common batch type. Uses PSAESRV thread pool for efficiency. |
| SQR Report | PSPRCSRV spawns SQR binary | Path to SQR binary defined in psprcs.cfg [SQR] section. |
| Crystal Reports | PSPRCSRV spawns Crystal process | Requires Crystal runtime installed on the batch server. |
| PS/nVision | PSPRCSRV (Windows scheduler only) | Requires Windows batch server with Excel installed. |
| COBOL | PSPRCSRV spawns COBOL executable | COBOL runtime must be installed; common in HCM Payroll environments. |
| Data Mover | PSPRCSRV spawns psdmtx | Used for data exports/imports; DM settings in psprcs.cfg. |
| Analytic Engine | PSAEOSRV | Only for environments using Analytic Calculation Engine modules. |
| Job (multi-step) | PSPRCSRV orchestrates | PSPRCSRV manages step sequencing; individual steps use their own handlers. |
Troubleshooting Common Issues
Jobs Stuck in “Queued” Status
If jobs sit in Queued status indefinitely, PSPRCSRV is not picking them up. Check: Is the Process Scheduler domain running? Run psadmin → Server Status to confirm PSPRCSRV is active. Also verify the PrcsServerName in psprcs.cfg matches the server name specified in the process request — mismatched server names mean PSPRCSRV will skip those requests.
Jobs Completing but Output Not Appearing in Report Manager
This points to PSDSTSRV. Check whether PSDSTSRV is running, whether the Report Repository path is correctly configured and accessible from the batch server, and whether PS_CDM_LIST shows the process status as “Generated”. Also verify the Report Node is correctly defined in PeopleTools → Process Scheduler → Report Nodes.
Application Engine Jobs Failing Immediately
If AE jobs fail without meaningful output, PSAESRV may not be running or may have crashed. Check the PSAESRV process in Server Status and look at the scheduler log (SCHDLR_MMDD.log) for PSAESRV start failures. Common causes include Java Runtime issues (some AE programs require JRE on the batch server) or database connectivity problems.
Domain Won’t Start — BBL Failure
If the domain fails to start, check for stale IPC resources or a leftover PID file from a previous unclean shutdown. Run ipcrm to clean shared memory segments, then remove the .pid file from the domain directory before attempting to restart.
Long-Running Jobs Killed Unexpectedly
Check Service Timeout settings — particularly for PSAESRV where it should be 0 (no timeout). Also check OS-level memory limits and verify the batch server has sufficient RAM — PSAESRV processes for large AE programs can consume 300–500 MB each.
Comments are closed