Objectives

The primary objective of TWS KM is to ensure the availability, maximum schedule/job throughput performance, and integrity of your scheduling environment. This section describes how to use TWS KM to achieve these goals. A PATROL Developer or Operator Console can be used, as required, to change any of the default behaviors listed below.

The KM also provides specific monitoring of the status of prompts, jobs and schedules to ensure that any problems are detected and reported.

Monitoring Server Availability

TWS KM monitors the TWS Master server processes to ensure availability (i.e. The processes netman, batchman, jobman, and mailman are running). The parameter TWSServerStatus monitors availability of all of the above processes. In the event of any process not running the parameter will go into an alarm state. As a result of this several recovery actions are initiated; these being a window appearing on the PATROL Console indicating the status of all five key processes, and the same information recorded as a parameter annotation point.

Monitoring CPU Availability

TWS KM monitors the link status of all the CPU’s as defined within TWS. If the CPU becomes unlinked for more than two collection cycles (allowing for Jnextday to run each day) then an alarm is raised. Each CPU can be managed within the Knowledge Module, with the correct login details provided by the PATROL operator, allowing the following actions; link, unlink, start, stop.