OracleFree referencePDF, Excel, Word exportOracle PeopleSoftAll Oracle PeopleSoft tools

PeopleSoft Process Scheduler RUNSTATUS Values and Report Manager Tables

This reference decodes PeopleSoft Process Scheduler run statuses and distribution statuses and lists the Process Monitor and Report Manager tables to query when processes stall or reports will not post. It applies to PeopleTools 8.5x and 8.6x.

Download:

Row type	Value / table	Name	Meaning / contents	Troubleshooting tip
RUNSTATUS	1	Cancel	Cancel requested for the process	Should move to Cancelled; if stuck, check the scheduler server is running
RUNSTATUS	2	Delete	Delete requested for the request	Removed by the scheduler on its next cycle
RUNSTATUS	3	Error	Process ended with an error	Open Message Log and trace or log files in Process Monitor details
RUNSTATUS	4	Hold	Request held by a user	Restart from Process Monitor to release it
RUNSTATUS	5	Queued	Waiting for a Process Scheduler server	Long queues: check server status, max concurrent per process type and server definition
RUNSTATUS	6	Initiated	Server has started the process	Stuck in Initiated often means the program failed to start; check the server log
RUNSTATUS	7	Processing	Process is running	Long running: check database sessions for the process instance
RUNSTATUS	8	Cancelled	Process was cancelled	Rerun from the run control page if needed
RUNSTATUS	9	Success	Process completed successfully	Distribution status shows whether output reached Report Manager
RUNSTATUS	10	Not Successful	Process ended without success	Check message log; often an Application Engine or SQR return code
RUNSTATUS	11	Posted	Output posted to Report Manager	Viewable in Report Manager by authorised users
RUNSTATUS	12	Unable to post	Output could not be transferred to the report repository	Check report node URL, credentials and the distribution agent log
RUNSTATUS	13	Resend	Repost of output requested	Used after fixing the report node
RUNSTATUS	14	Posting	Output transfer in progress	Stuck in Posting: check PSDSTSRV is running on the scheduler domain
RUNSTATUS	15	Content Generated	Output files generated, awaiting posting	Distribution agent should pick it up
RUNSTATUS	16	Pending	Waiting on a prior item, for example in a job	Check the job or the dependency
RUNSTATUS	17	Success With Warning	Completed with warnings	Review the message log before treating as clean
RUNSTATUS	18	Blocked	Blocked by a mutually exclusive process or limit	Check process definition mutually exclusive settings and concurrency limits
RUNSTATUS	19	Restart	Restart requested for the process	Application Engine restarts from the last committed checkpoint
DISTSTATUS	See PSXLATITEM	Not Posted	Output not delivered to the report repository	Check report node and PSDSTSRV log; repost once fixed
DISTSTATUS	See PSXLATITEM	Posted	Output in the report repository	If users cannot open it, check report folder and distribution list
DISTSTATUS	See PSXLATITEM	Generated	Output created on the server	Posting has not completed yet
DISTSTATUS	See PSXLATITEM	N/A	Process produces no output to distribute	Normal for many Application Engine programs
Table	PSPRCSRQST	Process request	One row per request: PRCSINSTANCE, JOBINSTANCE, PRCSTYPE, PRCSNAME, OPRID, RUNCNTLID, RUNDTTM, RUNSTATUS, DISTSTATUS, SERVERNAMERQST, SERVERNAMERUN, BEGINDTTM, ENDDTTM	Main table behind Process Monitor; query it for status and duration
Table	PSPRCSQUE	Process queue	Queue entries used by Process Scheduler servers, keyed by PRCSINSTANCE	Should stay in step with PSPRCSRQST; mismatches show as stuck requests
Table	PSPRCSPARMS	Process parameters	Command line, working directory and output parameters per PRCSINSTANCE	Shows the exact command a process was given
Table	PS_PMN_PRCSLIST	Process Monitor list view	View used by the Process Monitor process list	Same data as the Process Monitor grid
Table	PS_CDM_LIST	Report Manager content list	One row per output content: PRCSINSTANCE, CONTENTID, DISTSTATUS and report details	Join to PSPRCSRQST on PRCSINSTANCE to find unposted output
Table	PS_CDM_FILE_LIST	Report files	Individual files (report, log, trace) for each content ID	Lists the files the distribution agent tried to transfer
Table	PS_CDM_AUTH	Report distribution list	Users and roles authorised to view each report	Users missing from this cannot see the report in Report Manager
Table	PS_CDM_DIST_NODE	Report node	Report node definitions: URL, transfer protocol and connection details	Wrong URL or credentials here is the most common cause of unable to post
Table	PS_PRCSDEFN	Process definition	Process type, name, server and output settings, recurrence, mutual exclusion	Check here when a process runs on the wrong server or never starts
Table	PS_PRCSDEFNPNL	Process definition components	Components (run control pages) from which a process can be run	If a process is missing from a run control, check this table
Table	PS_PRCSJOBDEFN	Job definition	Job header for multi-process jobs	Use with PS_PRCSJOBITEM to see job steps
Table	PS_PRCSJOBITEM	Job items	Processes inside a job and their order	Pending items usually wait on an earlier job item
Table	PS_PRCSRECUR	Recurrence definition	Recurrence schedules used by process and job requests	Check when a recurring process stops scheduling
Table	PS_SERVERDEFN	Server definition	Process Scheduler server settings: sleep time, heartbeat, max API aware, operating system, distribution node	Check the distribution node assigned to the server
Table	PS_PRCSRUNCNTL	Run control	Run control IDs by OPRID and RUNCNTLID	Process-specific parameters live in the application's own run control records

RUNSTATUS values are stored as characters in PSPRCSRQST.RUNSTATUS. Confirm all values on your database with: SELECT FIELDNAME, FIELDVALUE, XLATLONGNAME FROM PSXLATITEM WHERE FIELDNAME IN ('RUNSTATUS', 'DISTSTATUS') ORDER BY FIELDNAME, FIELDVALUE. Distribution status codes are shown by name only; read their numeric values from that query. PSDSTSRV is the distribution agent server process in the Process Scheduler domain.

Get a batch monitoring query pack

Tell us your PeopleTools release and database and we will send checked queries for failed, stuck and unposted processes.

Optional. The tool and every export work without this. No spam.

Was this tool useful?

How to use it

Filter by row type. RUNSTATUS rows decode PSPRCSRQST.RUNSTATUS, the value behind the Process Monitor status column. DISTSTATUS rows explain distribution status, which tracks whether output reached the report repository. Table rows tell you where to look next. A useful habit is to keep two saved queries: one listing requests in Error, Not Successful or stuck in Initiated or Processing for more than an hour, and one listing successful requests whose output did not post. Export the table to keep beside those queries.

Run status tells you how the process ended
Distribution status tells you if the output arrived
Always check both when users say a report is missing

How Report Manager posting works

When a process finishes, the Process Scheduler writes output and log files to its output directory and the distribution agent (PSDSTSRV) transfers them to the report repository through the report node defined for the server, using HTTP or HTTPS to the web server's report repository servlet, or FTP or XCOPY in older set-ups. PS_CDM_LIST and PS_CDM_FILE_LIST track the content and files, and PS_CDM_AUTH holds who can view them. Report Manager shows posted content; Process Monitor shows the request and its statuses.

Worked example: reports not posting

Users report that SQR output stopped appearing in Report Manager after a web server change. Process Monitor shows Success with distribution status Not Posted. A query joining PSPRCSRQST to PS_CDM_LIST on PRCSINSTANCE confirms 140 unposted contents since the change. The distribution agent log shows HTTP 404 from the report repository URL. The report node in PS_CDM_DIST_NODE still pointed to the old host name. After updating the report node through the Report Node Definition page and restarting the scheduler domain, outputs were reposted from Process Monitor.

Gotchas

Do not update PSPRCSRQST status directly in production except as a documented last resort; use Process Monitor actions so PSPRCSQUE stays consistent. A process stuck in Queued usually means no server is running for that process type or concurrency limits are reached, not a broken program. Blocked is often mutual exclusion configured in the process definition. Purging old requests with the delivered purge process keeps these tables and the report repository from growing without limit.

Check server status before blaming the program
Use the delivered purge for old requests and reports
Report node changes need a scheduler restart to take effect

Frequently Asked Questions

Which tables are behind the PeopleSoft Process Monitor?

PSPRCSRQST holds one row per process request with status, user, run control, server and timings. PSPRCSQUE is the queue the servers use, PSPRCSPARMS holds command parameters, and PS_PMN_PRCSLIST is the view behind the process list. Report output is tracked in PS_CDM_LIST and PS_CDM_FILE_LIST.

Why are PeopleSoft reports not posting?

Most often the report node is wrong: an outdated URL, credentials or protocol in the report node definition. Other causes are PSDSTSRV not running, the web server report repository path not writable, or files too large for the transfer. Check distribution status, then the distribution agent log in the scheduler domain.

What is a report node in PeopleSoft?

A report node defines how the distribution agent transfers output from the Process Scheduler server to the report repository: the URL of the report repository servlet, the transfer protocol and login details. Each Process Scheduler server definition names its distribution node. Its data is stored in PS_CDM_DIST_NODE.

What does RUNSTATUS 9 mean in PSPRCSRQST?

RUNSTATUS 9 is Success: the process completed. It does not mean the output was delivered, which is tracked separately in distribution status. Other common values are 3 Error, 5 Queued, 7 Processing, 10 Not Successful and 17 Success With Warning. Confirm values in PSXLATITEM for your release.

If you want your operations team to ask which jobs failed overnight and why in plain English, answered from your PeopleSoft database on your own servers, we can set that up.

Talk to an Expert Explore More Free Tools