TWS for z/OS Workload Service Assurance (Dynamic Critical Path) Feature: Learn about available enhancements!
KatB 0600023DBB Visits (3689)
Hello Community, this entry means to summarize the main TWSz enhancement that more strongly affected Workload Service Assurance, both in terms of performances and in terms of improved functionalities.
TWS for z/OS 8.3.0
Making Risk Level changes more effective by ignoring not critical deadlines and improving times calculations for Critical Job table entries
Apar PM07794 has determined a functional improvement that can be activated by means of two new BATCHOPT keywords, IGNO
This represents the first step towards having the deadlines as optional values in TWSz .
Since Workload Service Assurance is based on TWSz late processing and the latest start time calculation is strictly dependent on the deadline, the use of IGNOREDEADL keyword allows to have more effective Risk Level changes for Critical Jobs during the workload scheduling, as this way in a critical network the late processing can be handled by considering critical jobs deadlines instead of being affected by deadlines of other oper
This allows to completely eliminate any false alarm on critical networks making the monitoring more effective.
The second keyword, TIMEDEPCHK, affects Estimated Start/End Times initialization. Estimated Start/End Times are crucial for Critical Path Handler task. Any decision and calculation depends mainly on these times. For entries added to the Current Plan via Daily Plan, these times are initialized by the Planned Start/End times. Instead, entries in the critical network coming from dynamically added occurrences does not have the Planned Start/End Times and have always the Estimated Start/End Times initialized by the Input Arrival Times. In both these cases (calculation of Planned Start/End Times by Daily Plan Batch and Input Arrival Time assignment) all the entries are handled as if the operations they refer to were time dependent (i.e. they cannot start before the Input Arrival Time). For operations that are not time dependent the Estimated Times calculation with the above criteria results to be not precise enough, as it is based on the assumption, coming from Planned Start/End Times calculation, that the Input Arrival Time is the very minimum time an operation is estimated to start. Keyword TIMEDEPCHK allows to change the calculation criteria and have more realistic Estimated Times for operations that are not time depenent.
Apars PM17976 and PM04518 (PM12591 for TWSz 8.5.0 and 8.5.1) have determined a very significant performance improvement in the Normal Mode Manager task of the Controller, respectively in the code flow that loads the Critical Job Table dataspace entries and in the late processing initialization phase,occurring at any Current Plan turn over and at any controller start. Internal algorithms that handle these flows have been strongly optimized in data access, keeping data structure unchanged for compatibility, to be high performing with big workloads (e.g 800,000 and over operations in the Current Plan).
TWS for z/OS 8.6.0
Improving the use of Workload Service Assurance in case of dynamic workloads
Often in customers' environments critical deadlines involve Business to Business service level agreements. The process usually employs ETT occurrences that, according to the old design, puts it either out of scope of Workload Service Assurance or needs some PIF type expertise to set/adjust the deadline.
TWSz 8.6.0 has changed this processing by allowing the specification of the deadline to an occurrence added via ETT/PIF, indicated as an “offset” that will be applied to the date and time of ETT/PIF add. This enhancement improves and makes more effective the use of Workload Service Assurance in case of more dynamic workloads.