Controlling tasks in a CMAS

Many operations in a CMAS are run by multiple asynchronous tasks, in particular a number of tasks that are performed between CMASs in a CMAS network.

Operations such as data repository synchronization, workload management state sharing and single system image can result in a number of interdependent asynchronous tasks being established or used to run the request. The number of tasks that can be used is based on other factors, such as the size of a CMAS network, how many MASs are being managed, how many CICSplexes are defined, how much API activity is performed, the scope of WUI/API/RTA requests and all the major functions offered by CICSPlex® SM.

Although a CMAS can self-regulate its tasking model and has tolerance of delayed requests and responses through timeout mechanisms, maximum user tasks (MXT) does not apply to controlling an interdependent multitasked asynchronous tasking model. Set inappropriately, you might also experience WUI hanging for long durations if one or more of the asynchronous tasks required to run the requested function is delayed waiting for an MXT slot. Set MXT to avoid delays in task attachment.

As task usage in a CMAS grows with the additional requirements that are placed on it, for example, increased use of the API, more CMASs, more MASs, and new function use, set the MXT value to a level that continues to avoid MXT delays.

Monitor any MXT value for its relationship against the task activity in each CMAS at regular intervals. If the CMAS is starting to experience MXT delays, adjust the MXT value to avoid these delays.

To monitor the tasking activity in an individual CMAS, collect and study the statistics generated by the CICS® system that underlies the CMAS that it hosts. CICS transaction manager global statistics contain information on the effect the MXT value has on task attachment.



dfha1p5.html | Timestamp icon Last updated: Sunday, 4 June 2017