Skip to Main Content
Return to Navigation

Viewing Master Scheduler Performance

Access the Master Scheduler page (PeopleTools, Performance Monitor, System Monitor, Master Scheduler).

This page displays the most recent performance data received from a Master Scheduler agent.

Note: The Performance Monitor displays Master Scheduler performance data only if a Master Scheduler has been configured.

System ID

Identifies each monitored system. The PeopleSoft system automatically generates this value incrementally. System definitions are created automatically when the first agent of a monitored system registers with the monitoring system.

Database Name

Reveals the name of the PeopleSoft application database that is running on the monitored system. The monitoring system automatically inserts this value when it recognizes and creates a monitored system.

Agent Date/Time

The date and time according to the agent clock that the domain monitor used when it last sent performance data to the monitor.

Note: The date and the time appearing on this page always apply to the system on which the agent runs. Keep this in mind if you are monitoring systems in other time zones.

Status

Appears only if the system detects stale data. Data is stale if it is older than the sample rate for that system. Data is stale if no status events have been reported in the last sample interval for the system. For example, Status shows stale data if the Process Scheduler is not booted.

Monitor Date/Time

The date and time that the monitoring system inserted the row of performance data into the monitoring database according to the database clock

Last Page Refresh

Indicates the most recent time that the system refreshed the page either by loading the page into the browser or as a result of a user clicking the Refresh button.

Process Summary

This process displays the status of the processes that are being managed by the Master Scheduler running on the selected system.

The data in this grid is derived from Event 350 (Master Scheduler Status).

Active Processes

The number of Process Scheduler jobs that are currently processing in this monitored system.

Unused Process Slots

The number of available slots that this Master Scheduler can use to run process requests.

Blocked Processes

A process can be blocked for two reasons:

  • The process is "mutually exclusive" with another process, and the other process is currently running.

  • The process is dependent on a file that another process has yet to create.

Queued Processes

The number of Process Scheduler jobs that are currently waiting to be handled by an available Process Scheduler server.

Servers

The Servers grid contains performance metrics for individual Process Scheduler servers that are running under the Master Scheduler.

This grid displays all Event 351 (Master Scheduler Detail) rows for all active Process Scheduler servers under the current system with the same agent date and time as the latest Event 350 (Master Scheduler Status). The system groups the data by server name and the metrics are accumulated.

Note: If the monitor date and time for an Event 351 is older than the current system’s event sample rate, a Stale Data icon appears at the top of the page.

Server Name

The name of the Process Scheduler server, such as PSNT, PSUNIX, and so on.

The server name is a hyperlink that launches a Server Activity secondary page for that particular server type. The Server Activity page displays all of the individual Event 351 (Master Scheduler Detail) rows. Use the Refresh button on this page to refresh the Processes grid.

Active Processes

The number of jobs that are currently being handled by a Process Scheduler server.

Queue Details

The Queue grid displays the status of the processes that are queued to be processed by the Master Scheduler.

The data is generated from Event 354 (Batch Queue Details) rows for all active Process Scheduler agents in the current system with the same agent date and time as the latest Event 350 (Master Scheduler Status).

Process Type

Displays the type of process that are queued, such as SQR, Application Engine, COBOL, and so on.

Queued Processes

Displays the number of processes that are queued per process type.

Blocked Processes

A process can be blocked for two reasons:

  • The process is "mutually exclusive" with another process, and the other process is currently running.

  • The process is dependent on a file that another process has yet to create.