Remove TMSLC & ATO CPU speed dependency

TPFUG_Req_Number: S03001
Contact Originator Id: jack.opgenorth@eds.com
Abstract: The application time-out value (ATO) and the TMSLC parameters maxtime and runtime must account for different CPU speeds within the same loosely-coupled complex. This requirement was previously submitted (98008) but is being resubmitted out of continuing need by the TPF user community to address this issue.
Description: Heterogeneous instruction processor speeds within a loosely-coupled system are common and result in unpredictable results for transactions that may unnecessarily trip the application time out (ATO) value on a slower processor in the complex. The heterogeneous processing speeds of processors within loosely-coupled complexes is a reality. In a recent performance task force on April 9, 2003, Two separate customers presented information that installations are operating CPU speeds that are greater than 30% in at least two significant installations and one installation has operated systems in that situation in the past 12 months. It's hard to imagine this issue become less important in complexes as they grow into the 32-way loosely coupled support.

As a result of this problem, other transactions may be preempted unnecessarily during TMSLC processing due to heterogeneous processor speeds and equal runtime values for a given TMSLC name. The control program should assign a processing speed value during IPL. This value could then be used to build consistent ATO values, maxtime and runtime values across a heterogeneous complex. This type of routine should not delay IPL by a significant amount of time.
Alternative Solutions: User Exit processing could be implemented to establish unique workload dependent CPU speeds.
Solution Considerations: There will be some issues with migration to the new methodology. It is unclear what the best implementation strategy might be. However, fewer applications will be affected the sooner the change can be implemented, since resource control mechanisms have not been fully deployed. Prior to migration, each customer will have to [Deleted] the impact of migration and deploy in a manner that provides the least disruption of service to their customers. The implementation of the logic should attempt to provide coexistence logic so that service interruptions can be minimized.