CICS / WebSphere

You can now specify an algorithm type at the CICSPlex SM WLM TRANGRP level (see Figure 2). By specifying an algorithm in this way, you can apply alternative algorithms to specific transaction codes in the same workload. A new SET command was implemented with this function to accommodate immediate dynamic modification of the algorithm type directly against the TRANGRP. So it’s possible to modify the algorithm type at run-time with no need to quiesce and restart any regions in the workload. There’s a one-to-one relationship between an installed workload definition (WLMDEF) and TRANGRP. The ability to discard and re-install a TRANGRP through its associated WLMDEF was retained, but using the SET command directly against the TRANGRP is a more efficient change mechanism.

 

At the WLMSPEC level, a default algorithm must be specified for the workload. This algorithm is applied to all dynamic transaction codes not encompassed by a TRANGRP associated with the same workload. The algorithm types you can specify at the WLMSPEC level are: 

  • QUEUE: queue mode
  • LNQUEUE
  • GOAL: goal mode
  • LNGOAL

Transactions that are to be evaluated by an alternative algorithm type need to be associated with a TRANGRP that identifies that algorithm type. The algorithms that can be specified at the TRANGRP level include the same algorithms that can be specified at the WLMSPEC level and an additional algorithm—INHERIT. For INHERIT, the algorithm type specified in the WLMSPEC for the workload is used.   

When migrating CICSPlex SM data repositories to CICS TS 4.2, you can retain current settings by setting the algorithm type for existing TRANGRPs to INHERIT. 

Figure 3 shows the relationship between CICSPlex SM WLM resources. The algorithm type can be specified as an attribute on a WLMSPEC or a TRANGRP definition.

4 Pages