Presentation is loading. Please wait.

Presentation is loading. Please wait.

XINFO HORIZONT TWS for z/OS Performance Analysis with XINFO IT-Charts

Similar presentations


Presentation on theme: "XINFO HORIZONT TWS for z/OS Performance Analysis with XINFO IT-Charts"— Presentation transcript:

1 XINFO HORIZONT TWS for z/OS Performance Analysis with XINFO IT-Charts
The IT Information System TWS for z/OS Performance Analysis with XINFO IT-Charts HORIZONT Software for Datacenters Garmischer Str. 8 D München Tel ++49(0)89 / 1 1 1 1 1 1 1 1 1 1 1

2 Reasons for TWS Performance Analysis
TWS is a key sub-system in the z/OS environment Job schedulers must work efficiently, in order to provide overall benefit Even small “wastes” in a job scheduler can have profound results: For example: On a system with 50,000 jobs per day, if 2,000 of these jobs lay on the critical path, if it takes 2 seconds instead of 1 second to submit a subsequent job, you would lose over 33 minutes per day from the batch window! In fact, you can lose much more than this if TWS performance is poor.

3 Reasons for TWS Performance Analysis
You must meet your SLA Your company recently merged different systems (or even TWS controllers), or you will merge systems in the future A high volume of ETT jobs must start at the same time and must execute immediately, like transactions in real time By reviewing performance of TWS and “tuning” it to work more efficiently, you can delay new investments in hardware

4 Components that effect TWS Performance
JES and the Workload Manager (WLM) TWS subtask interactions TWS I/O activity, location of the TWS files, the DASD subsystem, etc. TWS processor storage (50% of the CP is stored in LSR buffers) TWS dispatching priority and overall processor usage

5 TWS Subtask Interaction
User Tracker JES/WLM Tracker PIF Tracker submit EM Event Manager GS General Service WSA Workstation Analyser [LOCK] CP Current Plan JS JCL Repository Events, ETT Ready Performance is OK if all system components work well together [LOCK] Backup NMM Normal Mode Manager

6 IBM Tuning Recommendations
An excellent publication: SC IBM Tivoli Workload Scheduler for z/OS Customization and Tuning, Chapter 13, 14 and 15, Analyzing performance, tuning controller & tracker Explains indicators for performance-related problems, e.g. Long queue of computer operations in R status Delay between job end time and the time TWS reports success or failure of the operation.

7 IBM Tuning Recommendations
Many ready operations: set a higher QUEUELEN value Reduce the number of suspended events: Filter the test workload using EQQUX004 Examine JES performance Use EQQUX002 exit to locate the JCL

8 Performance Questions
To identify TWS performance problems, you should be able to answer questions like this: Are there many “ready” operations in queue? Is the TWS queue length sufficient? Does it take too long to submit subsequent jobs? Are there many “uninteresting” (suspended) events? Is response time becoming an issue?

9 Performance Data Performance data is available from a variety of sources, (e.g. RMF, SMF and TWS itself) Detailed TWS performance data can be obtained by using STATMSG keyword in JTOPTS initialization statement, e.g. CPLOCK (Current Plan locking) EVENTS (how many events were processed) WSATASK (Workstation analyzer task) GENSERV (The general service subtask)

10 Evaluation of Performance Data
It’s quite difficult to get and evaluate performance data: MLOG: Too many messages and figures TRACKLOG: Too much data, more or less "unreadable" Data has to be accumulated It would take days, or even weeks, to do that manually using standard methods such as Excel

11 Evaluation of Performance Data with XINFO
XINFO prepares performance data automatically, the results are presented graphically

12 How to get TWS Performance Data
STATMSG(…) STATIM(60) EQQPARM EQQMLOG Controller JT JT Set necessary Options JT JARC TWS Activity-Report Extend/Replan CP EQQAUDIT EQQTROUT Run EQQBATCH/EQQAUDIT

13 Analyse EQQMLOG and EQQAUDIT
EQQE006I EVENT MANAGER EVENT TYPE STATISTICS FOLLOW: EQQE006I TYPE NTOT NNEW TTOT TNEW TAVG NAVG NSUS EQQE007I ALL EQQE007I EQQE007I EQQE007I 3S EQQE007I 3J EQQE007I 3P EQQE007I EQQE007I EQQE007I USER EQQE007I CATM EQQE007I OTHR EQQE004I CP ENQ LOCK STATISTICS SINCE PREVIOUS MESSAGE FOLLOW: EQQE004I NAME NEXCL NSHRD THELD TWAIT AHELD AWAIT EQQE005I NORMAL MODE MGR EQQE005I WS ANALYZER EQQE005I EVENT MANAGER EQQN017I THE JCL REPOSITORY DATA SET WILL BE COPIED EQQN016I DDNAME OF CURRENT JCL REPOSITORY DATA SET IS EQQJS1DS EQQG013I QUEUE SIZE EQQG013I QUEUE DELAY EQQG010I GENERAL SERVICE REQUEST STATISTICS FOLLOW: EQQG010I TYPE TOTAL NEWRQS TOTTIME NEWTIME TOTAVG NEWAVG EQQG011I ALL EQQG011I RL EQQG011I OPER EQQG011I OPRL EQQG011I PREP EQQG011I JCL EQQG011I MCP EQQG011I DEPC EQQG011I R3P EQQG011I C3C EQQG011I AD EQQG011I WS EQQG011I WSRL EQQG011I CP_G XINFO IT-Charts Table XINFO Scanner OP.CPDB_030 IN RZ01XX#TWS#CPBKUP IS SET TO S JOBNAME: R01TWS01 PROCESSED IJ-SUBMIT JCL AD/IA: RZ01XX#TWS#CPBKUP PROCESSED A1-JOB CARD READ R01TWS01(JOB52600) AT: PROCESSED A2-JOB START R01TWX01(JOB52600) AT:

14 Number of TWS Jobs per Hour
Number of Jobs There is a high number of jobs during the day (normal online time) Hours

15 Jobs per Hour of each Workstation
Main load on workstation CPU3 Legend

16 Avg. Submit-/Starttimes / Workstation
30 seconds and more to submit a job is unacceptable Seconds What can be the reason? consistently 10 seconds is bad Less then 1 second is ok Time of Day

17 Time-Difference from Status S  IJ-Event
In this case, TWSz took too much time to read the JCL (on CPU1/2-Sysplex) All others are ok

18 Time-Difference from IJ  A1-Event
Submit the JCL to INTRDR: Times are less than a second (which is ok)

19 Time-Difference from A1  A2-Event
Initialize the jobs in the system: On CPU3, jobs sometimes need too much time to be “initiated” by JES (WLM) Reason was: Low (WLM) priority for TWS-Batch-Jobs, other “on demand work” had higher priority. Others are ok

20 EQQMLOG, Event Manager Statistics
01/ EQQE000I TOTAL NUMBER OF EVENTS PROCESSED BY THE EVENT MANAGER TASK IS: 01/ EQQE000I NUMBER OF EVENTS SINCE THE PREVIOUS MESSAGE IS: 01/ EQQE000I EVENT MANAGER QUEUE LENGTH STATISTICS FOLLOW: 01/ EQQE000I TOTAL Q1 Q2 Q5 Q10 Q20 Q50 Q100 >100 01/ EQQE000I 01/ EQQE006I EVENT MANAGER EVENT TYPE STATISTICS FOLLOW: 01/ EQQE006I TYPE NTOT NNEW TTOT TNEW TAVG NAVG NSUS 01/ EQQE007I ALL 01/ EQQE007I 01/ EQQE007I 01/ EQQE007I 3S 01/ EQQE007I 3J 01/ EQQE007I 3P 01/ EQQE007I 01/ EQQE007I 01/ EQQE007I USER 01/ EQQE007I CATM 01/ EQQE007I OTHR 01/ EQQE007I E2E …

21 Event Manager: Queue Length
High number of events Can be processed immediately (Q1). No more events are waiting in the queue

22 Event Manager: Event Types
High number of events Symmetric distribution in event types (which is ok)

23 Event Manager: Suspended Events
High number of suspended A3P events Reason: Events coming from another TWS Solution: Event filter exit

24 EQQMLOG, Ready Queue Statistics
01/ EQQE008I READY OPERATIONS QUEUE LENGTH STATISTICS FOLLOW: 01/ EQQE008I Q10 Q100 Q Q5000 Q >10000 01/ EQQE008I 01/ EQQE008I OPERATIONS READ AND FOUND WAITING FOR SPECIAL RESOURCES: 01/ EQQE008I OPERATIONS READ TO SELECT A WINNER: 01/ EQQE009I READY QUEUE LAST VALUE 01/ EQQE009I NEW READY OPERATIONS 01/ EQQE009I NEW STARTED OPERATIONS 01/ EQQE009I NEW COMPLETED OPERATIONS 01/ EQQE009I SELECT WINNER CALLS

25 Ready Queue: Queue Length
There is a frequently long Ready Queue between 1000 and 5000 Jobs to be checked by the WSA

26 Ready Queue: Waiting Special Resource
A high number of ready operations are waiting for Special Resource

27 Ready Queue: Select a Winner
Jobs are delayed while deciding which job should be submitted next TWS needs time to check the long ready queue, the reason is that many operations are waiting for SR

28 EQQMLOG, General Service Statistics
01/ EQQG012I GENERAL SERVICE QUEUE STATISTICS FOLLOW: 01/ EQQG012I TYPE TOTAL Q1 Q2 Q5 Q10 Q20 Q50 Q100 01/ EQQG013I QUEUE SIZE 01/ EQQG013I QUEUE DELAY 01/ EQQG010I GENERAL SERVICE REQUEST STATISTICS FOLLOW: 01/ EQQG010I TYPE TOTAL NEWRQS TOTTIME NEWTIME TOTAVG NEWAVG 01/ EQQG011I ALL 01/ EQQG011I AD 01/ EQQG011I OI 01/ EQQG011I WSD 01/ EQQG011I CALE 01/ EQQG011I PERI 01/ EQQG011I RACF 01/ EQQG011I RD 01/ EQQG011I ETT 01/ EQQG011I JV

29 General Service: Queue Size
Most of the GS-Requests can be processed immediately (Q1)

30 General Service: Queue Delay
Queue size and the delays can be an indicator of bad response times for TWS users

31 Summarizing Performance Analysis using XINFO IT-Charts
XINFO automatically collects and accumulates TWS performance data based on EQQMLOG and Tracklog XINFO keeps historical performance data as long as needed, e.g. to compare any day in actual year with the same day in previous year XINFO visualizes data XINFO enables you to see bottlenecks and problem areas in your TWS environment

32 XINFO HORIZONT Many thanks for your attention Software for Datacenters
The IT Information System Many thanks for your attention HORIZONT Software for Datacenters Garmischer Str. 8 D München Tel ++49(0)89 / 1 1 1 1 1 1 1 1 1 1 1


Download ppt "XINFO HORIZONT TWS for z/OS Performance Analysis with XINFO IT-Charts"

Similar presentations


Ads by Google