HORIZONT 1 TWS/Graph HORIZONT Software for Datacenters Garmischer Str. 8 D München Tel ++49(0)89 / TWS/Graph The Best View to TWS How to use the monitor

HORIZONT 2 TWS/Graph TWS/Graph Status Monitor Create job lists Monitor milestones Generate tickets (BMW) Monitor if production is late (Caja Madrid) This presentation shows you four examples how to use the monitor:

HORIZONT 3 TWS/Graph Example 1: Create Lists The first example shows how create easily job lists with the monitor

HORIZONT 4 TWS/Graph Create HTML Lists List all jobs that are waiting List all jobs that are active List all jobs that are complete List all jobs that are in error This (simple) example shows you how to create a homepage that meets following requirements:

HORIZONT 5 TWS/Graph Create new file 1.Create a new monitor definition

HORIZONT 6 TWS/Graph Insert top level 2.Insert top level (any text is ok)

HORIZONT 7 TWS/Graph Insert ERROR object 3.Insert Operation object to create ERROR list

HORIZONT 8 TWS/Graph Create other objects 4.Create Operation objects for ERROR, WAITING, ARRIVING, and COMPLETE

HORIZONT 9 TWS/Graph Arrange objects New with V5R2: Order can be changed

HORIZONT 10 TWS/Graph Save definitions 5.Save definition, then start

HORIZONT 11 TWS/Graph Start monitor 6.Specify all needed HTML options

HORIZONT 12 TWS/Graph Review status Monitor is now up and running. No errors!

HORIZONT 13 TWS/Graph Resulting HTML Top level entry point...

HORIZONT 14 TWS/Graph Resulting HTML Access to lists…

HORIZONT 15 TWS/Graph Resulting HTML PS: You can use the link to access e.g. ERROR lists directly. As long as you use this definition, the file name doesn’t change!

HORIZONT 16 TWS/Graph Resulting HTML Detailed job information for all jobs that are complete. Automatically updated every five minutes!

HORIZONT 17 TWS/Graph Modify list layout in TWSGRAPH.CFG Modify TWSGRAPH.CFG: LIST_POS=CPO_OP_ contains the names of columns Remember: All variable names are listed in TWSGRAPH.LBL

HORIZONT 18 TWS/Graph Modify Sort order in TWSGRAPH.CFG Change HTML Sort Order

HORIZONT 19 TWS/Graph Example 2: Milestones The second example shows how to use milestones to monitor production

HORIZONT 20 TWS/Graph Milestones Probably the best way to monitor the Critical Path is to insert “milestones”

HORIZONT 21 TWS/Graph Create Dummy Workstation 1.Create a dedicated dummy workstation to be used only for monitoring

HORIZONT 22 TWS/Graph Create Dummy Workstation 2.Create “milestones” as successors to “important” jobs…

HORIZONT 23 TWS/Graph Create Dummy Workstation 3.Specify “deadline”…

HORIZONT 24 TWS/Graph Production with Milestones 4.Milestones are now inserted into production (without any functional effect to TWS)

HORIZONT 25 TWS/Graph Create Monitor Definition 5.The status monitor of TWS/graph needs only one object

HORIZONT 26 TWS/Graph Start Monitor 6.Start the monitor

HORIZONT 27 TWS/Graph HTML with Milestones 7.The resulting list shows if you are in time… …or not: Status L(ate)

HORIZONT 28 TWS/Graph Pros and Cons +Simply to use +Excellent performance (TWS/Graph must monitor only the milestones, and not the whole stuff) +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' in the status monitor definition - Milestones must be maintained We think Milestones is the best method to monitor thousands of jobs:

HORIZONT 29 TWS/Graph Example 3: BMW The third example shows how BMW uses the monitor. BMW has its headquarter in Munich. BMW is using TWS/Graph, TWS/Audit, TWSBatchAD, TWSBatchCP, SmartJCL and XINFO.

HORIZONT 30 TWS/Graph Initial Situation Some critical jobs where checked manually No checks between 00:00 and 05:00 Tickets where created manually

HORIZONT 31 TWS/Graph Target Generate Alerts and Tickets automatically -For Error Jobs -For Late Jobs Generate Status Information -For the programmers who are responsible for the tickets -For non IT-departments

HORIZONT 32 TWS/Graph Status Monitor Web Designer BMW is major test site for the new web application to maintain the monitor definition.

HORIZONT 33 TWS/Graph Status Monitor Web Designer TEC and Remedy parameters can be maintained together with TWS/Graph definitions

HORIZONT 34 TWS/Graph File Export to TWS/Graph In the actual test installation TWS/Graph Web exports monitor definitions to TWS/Graph Client MONITOR.LST Web to EXE

HORIZONT 35 TWS/Graph Refresh Rate The refresh rate is 5 minutes. One “refresh“ takes 3-4 seconds and requires 0,1 CPU seconds.

HORIZONT 36 TWS/Graph HTML Status Information via Intranet Department names are used as entry points The HTML directory is shared, anybody (who is authorised) can view the files

HORIZONT 37 TWS/Graph Alerts and Tickets In case of Error- or Late jobs a Perl script is started

HORIZONT 38 TWS/Graph Perl Script 1.TWS/Graph passes TWS, TEC, and remedy Parameters to the script 2.The Script generates and sends Command „postemsg“ to the TEC

HORIZONT 39 TWS/Graph TEC Events TEC-Events generated by TWS/Graph

HORIZONT 40 TWS/Graph Remedy Tickets Remedy Tickets generated by TEC

HORIZONT 41 TWS/Graph Example 4: Caja Madrid The fourth example shows how Caja Madrid uses TWS/Graph. Caja Madrid is a Spanish bank, the headquater is in Madrid. Caja Madrid is using TWS/Graph, SmartJCL and XINFO.

HORIZONT 42 TWS/Graph Initial Situation Tickets are generated automatically (EQQUX007) They have few but important key applications The Batch Window is too small Operating is not able to see possible delays in time

HORIZONT 43 TWS/Graph Target Operating needs early warnings when a critical job will probably not end in time 06:00 05:00

HORIZONT 44 TWS/Graph Technical Overview Only critical end jobs must be defined to TWS/Graph TWS calculates Planned Duration for every job while extending the Current Plan TWS/Graph searches all predecessors of the critical jobs TWS/Graph uses the Planned Duration to find the critical path for every critical job TWS/Graph calculates the estimated execution time of every critical path and shows the remaining buffer time Based on Caja Madrid’s requirements, HORIZONT developed a monitor concept:

HORIZONT 45 TWS/Graph Jobs on the critical path(s) Das kann jetzt (5.1) auch der Status Monitor for einen oder mehrere Ende-Jobs TWS/Graph can monitor as many critical end jobs as needed. Here we have two critical end jobs.

HORIZONT 46 TWS/Graph Late Options Late time as an offset to IAT Aa a Predecessor levels that should be taken into account Use the TWS/Graph dialog to define an object for every critical end job The critical job (Application Id and Operation Number

HORIZONT 47 TWS/Graph Calculated remaining duration Path The end job and all predecessors that are not complete After having started the monitor, TWS/Graph automatically builds a flowchart with all jobs that are on the critical path

HORIZONT 48 TWS/Graph Calculated remaining duration Information window Number of jobs on the critical path Status Calculated Late-Time: 17:00 Remaining runtime: 3 hours Actual buffer: 1 hour

HORIZONT 49 TWS/Graph Calculated remaining duration The actual buffer is calculated frequently 13:30

HORIZONT 50 TWS/Graph Calculated remaining duration If it looks like the critical end time will be missed, the buffer becomes negative 14:01

HORIZONT 51 TWS/Graph Calculated remaining duration The Monitor signalises “Late”

HORIZONT 52 TWS/Graph Calculated remaining duration Jobs are running now, some jobs are complete Now the buffer is sufficient again 14:07

HORIZONT 53 TWS/Graph Calculated remaining duration 14:30 Path becomes shorter

HORIZONT 54 TWS/Graph Calculated remaining duration 15:00 Summary: TWS/Graph can show you where you are and the best estimate of when the Batch will end

HORIZONT 55 TWS/Graph Some figures 6 critical jobs are monitored Refresh-Rate is 1 hour Runtime (one Monitor for 6 Jobs) -18 Minutes right after “Begin of production” -10 Minutes just before “End of production” Runtime (6 Monitors parallel) -Each monitor requires 5 down to 2.5 minutes Even we where concerned about performance, but the result was better than expected:

HORIZONT 56 TWS/Graph Benefits of TWS/Graph Status Monitor Easy to install (no installation if you have TWS/Graph) Different targets can be addressed (Lists, Tickets, Late) No system modifications needed (Exits etc.) All jobs controlled by TWS can be monitored, z/OS as well as End2End jobs Let us summarize the benefits of TWS/Graph’s integrated Status Monitor:

HORIZONT 57 TWS/Graph Do you have any questions? Create job lists Monitor milestones Generate tickets (BMW) Monitor if production is late (Caja Madrid)

HORIZONT 58 TWS/Graph HORIZONT Software für Rechenzentren Garmischer Str. 8 D München Tel ++49(0)89 / TWS/Graph Many thanks for your attention! The Best View to TWS