Batch Processing

• 1: App Engines
• 2: Process Definitions
• 3: Process Jobs
• 4: Recurrences
• 5: Server Definitions

1 - App Engines

Application Engines (AE) are PeopleSoft’s batch processing framework. Unlike traditional COBOL or SQR programs, Application Engine programs are defined in PeopleSoft metadata tables (such as PSAEAPPLDEFN, PSAESECTDEFN, PSAESTEPDEFN, and PSAESTMTDEFN) and executed by the psae batch executable. They are commonly used for data processing, background calculations, integrations, and ETL processes.

psLens allows you to search and browse the structure of Application Engine programs, inspect their sections, steps, and actions, and view the associated SQL and PeopleCode source code without opening App Designer.

Object Relationships

Application Engines structure batch execution across database tables and code modules:

• Structures Sections, Steps & Actions: App Engines (PSAEAPPLDEFN) decompose batch logic into executable sections (PSAESECTDEFN), steps (PSAESTEPDEFN), and statement actions (PSAESTMTDEFN).
• Executes SQL & PeopleCode: Step actions execute embedded SQL statements (PSSQLDEFN) or Application Engine PeopleCode programs.
• Scheduled via Process Definitions: App Engines are mapped to Process Definitions (PRCSDEFN) for scheduling and execution in Process Scheduler.

How psLens Improves Application Engine Inspection

In Application Designer, reviewing an Application Engine program requires opening individual section and step nodes, clicking into actions, and switching windows to inspect SQL statements or PeopleCode scripts.

psLens presents the full section/step/action hierarchy with inline, syntax-highlighted SQL and PeopleCode source code viewable without opening Application Designer.

Search Page

URL: /appengines?db={database}

• Search: Search for Application Engines by program name (prefix match). Type PSAE to find all AEs starting with PSAE. Use % as a wildcard if needed (e.g., %PRCS% to find programs containing PRCS).
• Metadata Card: Each search result card shows the program description, owner ID, and last modified operator/timestamp.

Detail Page

URL: /appengines/{APPLID}?db={database}

The Detail Page exposes the internal structure of the Application Engine program:

• Program Properties: Shows description, owner ID, program type (Standard, Upgrade, Import, Daemon), active status, disable restart setting, and modification details.
• Sections & Steps Tree: Lists all sections (e.g., MAIN) and steps defined in the program.
• Actions View: For each step, psLens shows the actions it executes (SQL, PeopleCode, Call Section, Log Message, XSLT, Do Select, Do Until, Do While, Do When).
• Source Code Viewer: Steps that run SQL or PeopleCode actions can be expanded to view the actual code inline.
• Export as Markdown: Reconstructs the entire Application Engine structure, including all sections, steps, actions, and embedded code, into a single structured Markdown file.

2 - Process Definitions

Process definitions (PRCSDEFN) specify the batch programs, reports, and scripts executable via PeopleSoft Process Scheduler. They map a logical process name to an underlying program type (SQR, Application Engine, COBOL, XML Publisher) and define command-line parameters, run control components, and default output options.

psLens pulls the process definition properties, execution statistics, recurrence schedule variance, run control record mappings, and project membership into a single browser view.

Object Relationships

Process Definitions configure batch program execution within Process Scheduler:

• Executes Batch Programs: Process Definitions (PRCSDEFN) map to underlying executable objects such as App Engines (PSAEAPPLDEFN), SQRs, or COBOL programs.
• Mapped to Run Control Components: Process Definitions link to run control components (PRCSDEFNPNL) that store parameters in header/detail records.
• Bundled in Process Jobs: Process Definitions can be grouped together into Process Jobs (PSPRCSJOBDEFN).

How psLens Improves Process Definition Inspection

In Application Designer or Process Scheduler setup, reviewing a process definition requires navigating separate tabs for parameters, locations, and output destinations, while execution metrics require running custom SQL against PSPRCSRQST.

psLens combines definition properties, historical statistics, recurrence schedule variance, run control record mappings, and project membership into a single view.

Search Page

URL: /processdefinitions?db={database}

• Search: Search by process name (prefix match) or wildcard % patterns (for example, %AUDIT% or %).
• Filters: Filter process definitions by process type (e.g., Application Engine, SQR Report), component, or modification metadata.

Detail Page

URL: /processdefinitions/{PRCSTYPE}/{PRCSNAME}?db={database}

The Detail Page displays process configuration, historical metrics, and schedule variance:

• Configuration & Properties: Displays execution details including command-line parameters, target server name, API awareness, run control component, and priority.
• Output Settings: Shows output type (Web, File, Printer) and output format (PDF, CSV, HTML).

Execution Statistics

psLens analyzes historical process request data (PSPRCSRQST) to present statistics on:

• Total runs, average execution duration, and first/last run timestamps.
• Run status breakdown (percentage of successful versus failed or queued runs).
• Top operators and servers executing the process.

Recurrence History & Schedule Variance

For processes executed via recurrence schedules (RECURNAME <> ' '), psLens calculates schedule latency:

• Start Delay Variance (BEGINDTTM - RUNDTTM): Compares target scheduled run times against actual execution start times.
• Summary Metrics: Displays Total Recurring Runs, Average Start Delay, Maximum Start Delay (with instance ID), and On-Time Rate percentage.
• Delay Breakdown & Historical Log: Categorizes runs into On Time (≤ 1m), Minor Delay (1-5m), and Significant Delay (> 5m) with instance-level status badges.

Related Data Panels

Run Control Records & Jobs

• Run Control Records: Identifies the run control component (PRCSMULTI) and mapped header/detail tables (PRCSSAMPLEREC) used to store process parameters.
• Jobs: Displays Process Job definitions (PSPRCSJOBDEFN) that include this process as a job item.

Included in Projects

Queries PSPROJECTITEM where OBJECTTYPE = 20 to display Application Designer projects containing this Process Definition.

3 - Process Jobs

Process Jobs (also called Job Definitions) are groups of one or more process definitions (or other jobs) bundled together to run as a single scheduled unit. A job executes its constituent processes in a defined sequence or in parallel, depending on the job definition.

psLens allows you to browse job definitions, inspect the list of items inside each job, and check their execution sequence.

Object Relationships

Process Jobs organize multiple batch tasks into structured execution pipelines:

• Bundles Process Definitions: Process Jobs (PSPRCSJOBDEFN) group multiple Process Definitions (PRCSDEFN) or nested sub-jobs into a single run request.
• Scheduled via Recurrences: Process Jobs can attach to Recurrences (RECURNAME) for automated repeating execution.

How psLens Improves Process Job Inspection

In Process Scheduler setup, reviewing job definitions requires clicking through nested job item tabs and manually checking process sequence numbers.

psLens displays job properties, nested process definitions, execution sequence numbers, and run modes in a clean, unified view.

Search Page

URL: /processjobs?db={database}

• Search: Search for job definitions by job name (prefix match).
• Metadata Card: Results display the job description, owner, and modification timestamps.

Detail Page

URL: /processjobs/{JOBNAME}?db={database}

The Detail Page displays:

• Job Properties: Basic settings, such as description, run control validation, and server settings.
• Job Items & Sequence: A table showing all processes and sub-jobs nested within this job, including:
  • Run order/sequence number.
  • Process Type and Process Name.
  • Description.
  • Run mode (e.g., Serial, Parallel).
• Export as Markdown: Export the job definition and its sequence table to a markdown document.

4 - Recurrences

Recurrences define repeating schedule patterns used by the PeopleSoft Process Scheduler. Whenever a process or job is scheduled to run on a repeating schedule (e.g., daily, weekly, hourly), it is linked to a recurrence definition.

psLens allows you to search and view recurrence patterns to understand when a scheduled task is slated to run next and how frequently it triggers.

Object Relationships

Recurrences drive automated scheduling for batch requests:

• Schedules Processes & Jobs: Recurrence definitions (RECURNAME) attach to Process Definitions (PRCSDEFN) or Process Jobs (PSPRCSJOBDEFN) to automate recurring execution.

How psLens Improves Recurrence Schedule Inspection

In PIA, inspecting process recurrences requires opening schedule setup windows and calculating future execution times manually.

psLens displays recurrence frequency parameters, active run windows, and next-run predictions on a single screen.

Search Page

URL: /recurrences?db={database}

• Search: Search recurrence definitions by name (prefix match).
• Metadata Card: Shows the description, owner, and modification timestamps.

Detail Page

URL: /recurrences/{RECURNAME}?db={database}

The Detail Page displays:

• Recurrence Pattern Details: Shows recurrence settings such as:
  • Frequency (Daily, Weekly, Monthly, Hourly).
  • Run times (e.g., Daily at 12:00 AM, or every 5 minutes).
  • Selection of specific days of the week or month.
  • Start and end dates/times.
• Next Run Prediction: Displays when the recurrence is next due to execute.
• Export as Markdown: Export the recurrence schedule parameters as a markdown file.

5 - Server Definitions

Server Definitions represent the Process Scheduler Servers that are defined inside PeopleSoft. These servers execute the batch processes (like Application Engines, SQRs, etc.) and manage scheduling recurrences and daemon processes.

psLens allows you to search and browse server definitions to see how a server is configured, check its live heartbeat status, see active running processes, review what process classes and categories it is authorized to run, check operational schedules, and view its notification routing.

Object Relationships

Server Definitions act as the execution engines for batch processing:

• Executes Process Requests: Server Definitions (PSSERVERDEFN) execute Process Definitions (PRCSDEFN) and Process Jobs (PSPRCSJOBDEFN) assigned to their queues.
• Monitors System Status: Server instances update live heartbeat and CPU metrics in PSSERVERSTAT.

How psLens Improves Server Definition Inspection

Monitoring Process Scheduler servers in PIA requires switching between Process Monitor server status pages, daemon configuration windows, and process category assignments.

psLens consolidates real-time server heartbeats, active running processes, CPU/memory metrics, daemon settings, authorized process categories, and status notification lists into a single view.

Search Page

URL: /servers?db={database}

• Search: Search for server definitions by name (prefix match, e.g., PRCS%).
• Metadata Card: Shows the description, operating system, daemon status, and modification timestamps.

Detail Page

URL: /servers/{SERVERNAME}?db={database}

The Detail Page displays:

• Server Status: Shows real-time heartbeat and diagnostics from PSSERVERSTAT including:
  • Current status (Running, Down, Suspended, Overloaded, etc.) with relative “time ago” timestamps.
  • CPU and Memory utilization.
  • Free disk space and thresholds.
  • AE/OE Server counts.
• Active Running Processes: Live grid of active processes (Initiated, Processing, Running) currently executing on the server from PSPRCSRQST.
• Server Definition Properties: Displays configuration metrics like version, sleep time, heartbeat frequency, max concurrent API aware/unaware tasks, distribution node details, CPU/Memory threshold configs, and load balancing/redistribution option choices.
• Server Daemon Details: Shows daemon configuration:
  • Enabled state, daemon group, sleep time, recycle counts.
  • Active daemon process instance (with direct link to its Process Monitor view).
• Process Categories: Authorized process categories with priority and max concurrent execution counts.
• Process Types: Specific process types the server is configured to run, categorized by operating system, priority, and concurrent limits.
• Server Operation Times: Scheduled operation windows when the server is active (24/7 or day/time ranges).
• Status Notifications: List of users and roles notified upon server status changes (e.g., when the server goes down or encounters an error), displaying active status flags as checkboxes.
• Export as Markdown: Export the entire server definition structure and live status/child tables as a markdown file.