Export Recurring Processes

Export Recurring Processes Report

Report ID: recurring-processes Category: Process Scheduler

Purpose

This report exports all currently queued recurring batch processes from the PeopleSoft Process Scheduler. It captures the batch schedule configuration so it can be preserved for disaster recovery, environment migrations, or operational documentation.

The report answers: “What recurring processes are currently scheduled, who set them up, with what run control, on what recurrence, and on which server?”

What It Captures

For each queued process with a recurrence assigned:

OPRID. The operator who scheduled the process
RUNCNTLID. The run control ID used
RECURNAME. The recurrence definition controlling the schedule
SERVERNAMERUN. The Process Scheduler server assigned to run it
Process Name and Type. The process definition being executed

Additionally, the report fetches and displays the schedule details for each unique recurrence found (type, days, time window, repeat interval).

Tables Queried

PSPRCSRQST — Process Request Instances

The primary table for process scheduler requests.

Field	Description	Filter
PRCSINSTANCE	Unique process instance number
PRCSNAME	Process definition name
PRCSTYPE	Process type (SQR, AE, COBOL, etc)
OPRID	Operator who scheduled the process
RUNCNTLID	Run control ID
RUNSTATUS	Current run status	Filtered to 5 (Queued)
SERVERNAMERUN	Assigned server
RECURNAME	Recurrence name	Filtered to non-blank
RUNDTTM	Scheduled run date/time

PRCSRECUR — Recurrence Definitions

Looked up for each unique recurrence found to display schedule details.

Field	Description
RECURNAME	Recurrence name (primary key)
RECURDESCR	Description
RECURTYPE	Type: 2=Daily, 4=Weekly, 6=Monthly, 8=Custom
RUN{DAY} flags	Which days of the week to run
BEGINDTTM	Schedule start date/time
ENDDTTM	Schedule end date/time
REPEATRECURRENCE	Repeat interval value
REPEATUNIT	Repeat unit: 0=Minutes, 1=Hours

Data Flow

1. Query PSPRCSRQST where RECURNAME <> ' ' AND RUNSTATUS = 5
   Paginate through all results (batches of 300)
        |
        v
2. Collect unique RECURNAME values
   For each, fetch PRCSRECUR via GetRecurrenceByName
        |
        v
3. Generate Markdown report:
   - Summary counts
   - Main table of all queued recurring processes
   - Recurrence schedule details section

Report Output

The generated report contains:

Header with database name and generation timestamp
Summary with total process count, unique recurrences, unique operators, unique servers
Process Table with Process Name, Type, OPRID, Run Control ID, Recurrence, Server, Run Date/Time
Recurrence Details for each unique recurrence: type, scheduled days, start/end dates, repeat interval, duration

Parameters

This report has no configurable parameters.

Interpreting Results

Each row represents a process request that is currently queued with a recurring schedule
The same process may appear multiple times if scheduled by different operators or with different run controls
If a server column shows “(any)”, the process can run on any available Process Scheduler server
The Recurrence Details section shows how often each schedule runs

Use Cases

Disaster Recovery. Document the batch schedule before a system outage so it can be recreated
Environment Migration. Capture batch schedules before refreshing or migrating an environment
Audit. Review who has scheduled recurring processes and on which servers
Operational Documentation. Maintain a record of the production batch schedule