Process Run Check
Categories:
Tailored Operational Context
- Target Database: —
- Context Type: —
- Alert Severity: —
- Triggered Time: —
- Firing Context:
—
Process Run Check Report
Report ID: process-run-check
Category: Process Scheduler
Purpose
This report verifies that a set of critical batch processes have run successfully within a configurable time window. It checks each process for a recent successful completion and flags any that are missing or have not completed successfully.
The report answers: “Have my critical processes run successfully in the last N hours?”
Parameters
| Parameter | Default | Description |
|---|---|---|
processes | (none) | Comma-separated list of process names to check (e.g., PSXPIDX,PRCSJOBPURGE,PSRUNSTATS). Required. Maximum 50 processes. |
hours | 24 | Time window in hours. The report checks for successful runs within this many hours from now. |
Tables Queried
PSPRCSRQST — Process Request Instances
Queried twice per process name:
| Query | Fields Used | Filter |
|---|---|---|
| Latest run | PRCSNAME, PRCSINSTANCE, RUNSTATUS, BEGINDTTM, RQSTDTTM | PRCSNAME = '{name}', ordered by PRCSINSTANCE DESC, limit 1 |
| Success check | PRCSNAME, PRCSINSTANCE, RUNSTATUS, BEGINDTTM | PRCSNAME = '{name}' AND RUNSTATUS = 9 AND BEGINDTTM >= cutoff, limit 1 |
Data Flow
1. Parse process names from comma-separated parameter
Calculate cutoff time (now - hours)
|
v
2. For each process name:
a. Query PSPRCSRQST for most recent run (any status)
b. Query PSPRCSRQST for most recent successful run (status=9) since cutoff
|
v
3. Sort results: failures first, then passes
|
v
4. Generate Markdown report:
- Summary with pass/fail counts
- Results table
- Recommendations for failures
Report Output
The generated report contains:
- Header with database name, generation timestamp, and time window
- Summary showing how many processes passed vs. failed
- Results Table with columns: Status (PASS/FAIL), Process Name, Last Run Time, Last Run Status, Successful Run in Window
- Recommendations section for any failing processes with details about their last run
Interpreting Results
- PASS. The process had at least one successful run (RUNSTATUS=9) within the time window
- FAIL. No successful run was found within the time window. This could mean:
- The process ran but ended in error or another non-success status
- The process has not run at all within the window
- The process has never run (no history in PSPRCSRQST)
- The “Last Run Time” and “Last Run Status” columns show the most recent run regardless of status, so you can see if it ran but failed
Use Cases
- Morning Operations Check. Verify that overnight batch processes completed successfully before the business day starts
- Critical Process Monitoring. Confirm that essential processes (search index builds, security syncs, integration processes) are running on schedule
- Post-Maintenance Verification. After system maintenance, verify that all scheduled processes have resumed and are completing successfully
- SLA Compliance. Document that required processes are running within expected timeframes