Monitoring with TWS/Graph The Best View to TWS Monitoring with TWS/Graph HORIZONT Software for Datacenters Garmischer Str. 8 D- 80339 München Tel ++49(0)89 / 540 162 - 0 www.horizont-it.com 1 1 1 1 1 1 1 1 1 1 1

Monitoring Production? Is it possible to monitor a complete production? Technically yes, but…

Monitoring Production? The problem: A complete production is too big for graphical monitoring!

Monitoring Production with TWS/Graph! The solution: Monitor the critical path, and not the complete production!

TWS/Graph Status Monitor TWS/Graph has an integrated Status Monitor. It can be used to monitor your production: Monitor the critical path Monitor Milesstones Monitor if production is late Create HTML files with actual status information Send Alerts (Email or WTO to SYSLOG)

Identify Critical Jobs As a first step you must know what you like to monitor, and how to group these jobs logically, e.g. by functionality, by owner, by department etc.

Define Structure After you've made a decision what you like to monitor, you must define a structure

Define Structure Now this empty structure must be filled up with objects: Groups Applications Operations

Define Structure Use the right mouse to insert objects into the empty structure

Define Structure Top Level, e.g. the OPC subsystem

Define Structure Next Level, e.g. Operations

Define Structure Do you want to get a list of all jobs that are in error?

Define Structure Or do you want a list with all jobs that are started?

Define Structure Or do you like to monitor all jobs that are defined in OPC to be monitored? (available with TWSz 8.1)

Starting the Monitor Start

Starting the Monitor Refresh all 5 minutes Write status information to HTML

Status Monitor is up and running No job is in error Jobs are active Some critical jobs are done, some others are still waiting After the refresh the colors are changed, every colour has a special meaning

Status Monitor is up and running Job(s) in error Job(s) are active

Status Monitor is up and running All netplans can be loaded directly from the monitor, here are the active Job(s)

Complex Monitoring e.g. for special jobs ...and jobs for several departments The structure should be defined in a way that allows to monitor all interesting elements from one screen: The Focal Point

Define more Jobs/Applications

Define more Jobs/Applications

Define more Jobs/Applications

Define more Jobs/Applications

Define more Jobs/Applications

Define more Jobs/Applications

Define more Jobs/Applications

Define more Jobs/Applications

Starting the Monitor Start

Starting the Monitor

Status Monitor is up and running Jobs are waiting Some Jobs are in error, other jobs are active, other jobs are waiting Not planned

Status Monitor is up and running

Status Monitor is up and running

Status Monitor is up and running This display can be used on a big screen for the operators

HTML Output In addition to the treechart all information is presented in HTML files. Benefits are: End user needs no host connection End user needs no special knowledge End user can access status information from anywhere

HTML Output The HTML files can be used to publish TWS status information via Intranet

HTML Output

HTML Output

HTML Output Detailed job information

How to monitor late jobs

How to monitor late jobs The jobs is „late“, if it is not complete until 18:00 Selection criteria: One or more jobs (generic selection)

How to monitor late jobs These job(s) are „late“, if they are not complete until 18:00. 06:00 (=IA) + 12:00 Std. = 18:00 Selection criteria

“Late” Monitor is up and running

“Late” Monitor is up and running Job (and superior levels) are „late“ The superior Level is still red, because ERROR has higher priority than LATE

Alerts After every refresh any program can be called from TWS/Graph.

Alerts Create Message Send Email TWS/Graph has an integrated REXX interface. Parameters like the jobname or the status can be passed as a parameter to a program

WTO - Output Syslog Message zusammenbauen TWS/Graph Message Jobname 03213 18:31:33.88 STC04191 00000081 $HASP100 O8CP#14 ON STCINRDR 03213 18:31:34.09 STC04191 00000290 IEF695I START O8CP#14 WITH JOBNAME O8CP#14 , GROUP STCOPC 03213 18:31:34.09 STC04191 00000090 $HASP373 O8CP#14 STARTED 03213 18:31:34.11 STC04191 00000081 IEF403I O8CP#14 - STARTED - TIME=13.31.34 03213 18:31:34.89 STC04191 00000081 ICH70001I P390K LAST ACCESS AT 12:21:50 03213 18:31:36.50 STC04191 00000090 OPG099I HOR60DAY A R IN 03213 18:31:36.54 STC04191 00000090 OPG099I HOR60DAY HOR60010 W L CPU 03213 18:31:38.23 STC04191 00000290 - - Message zusammenbauen TWS/Graph Message Jobname Application Monitor- Status (Late) OPC- Status (waiting)

How to use TWS/Graph to avoid delays TWS/Graph can be used to find out if production will be in time, or if there are delays. There are some basic techniques to do that: Milestones TWS/Graph and OPC Deadline times

Milestones Probably the best way to monitor the Critical Path is to insert milestones and to monitor them with TWS/Graph

Milestones Now the same application with milestones (yellow symbols) PS: We used the TWS/Graph function ”Search for redundant links” to clean up the application

Milestones The status monitor of TWS/graph needs one object for every milestone

Milestones The monitor signalises if a milestone is late. In this case the daily production was delayed right after the start at 10:00

Pros and Cons Simply to use We think Milestones is the best method to monitor thousands of jobs: Simply to use Excellent performance (TWS/Graph must monitor only the milestones, and not the whole stuff) Milestones must be maintained

Using TWS-"Deadlines" TWS/Graph offers alternatives to monitor the critical path: TWS/Graph allows to check automatically all predecessors of a critical job (e.g. the online start). If one preceding job exceeds its deadline, the status LATE is shown. To do this you must specify '00:00' in the 'late time' field and 'Operation Deadline' in the 'late time origin' field. As long as you have coded deadline times, the monitor produces late alerts for these if they are in your monitored critical path. And if there is a known delay to the start of batch by, say 2 hours, you only need to change the 'late time' field to '02:00' for one monitored job (last one in the critical path)

What are TWS Deadlines? The deadlines we are using in our function are the operation deadlines. They have to be specified in the application descriptions of TWS.

Using TWS-"Deadlines" 1. Find out the last job in your critical path, e.g. the online system. In our example the last job is T82030050A-99

Using TWS-"Deadlines" 2. Define an object in the status monitor that points to the critical job The late time must be specified as an offset to the deadline. If you specify 00:10, and the deadline in TWS is 12:30, the job will be late if it is not complete until 12:40. The critical job Specify 99 for all predecessors

Using TWS-"Deadlines" 3. After having started the monitor, TWS/Graph checks automatically all predecessors of the critical job.

Using TWS-"Deadlines" 4. The status monitor shows LATE if any preceding job missed the deadline (remember: the deadline has to be specified in the application description of TWS)

Using TWS-"Deadlines" 5. If you like to see which job missed the deadline, you must select “netplan”…

Using TWS-"Deadlines" 6. TWS/Graph shows the netplan with all predecessors of the critical job, all jobs that missed the deadline are marked (here pink).

Pros and Cons In opposite to the “old” method of using milestones this new function has some disadvantages: Operation deadlines must be maintained in TWS. Poor performance (TWS/Graph must locate and analyse all predecessors) In case of delays the monitor can be adjusted easily, only the ‘late’ time must be modified in the status monitor

Many thanks for your attention! TWS/Graph The Best View to TWS Many thanks for your attention! HORIZONT Software für Rechenzentren Garmischer Str. 8 D- 80339 München Tel ++49(0)89 / 540 162 - 0 www.horizont-it.com 1 1 1 1 1 1 1 1 1 1 1