Transaction group definitions - TRANGRP

The Transaction group definition (TRANGRP) views display information about groups of logically similar transactions. The similarity may be based on affinity requirements, common shared processing requirements or any other user-determined characteristic.

Supplied views

To access from the main menu, click:

Administration views > Workload manager administration views > Transaction group definitions

Table 1. Views in the supplied **Transaction group definitions** (TRANGRP) view set
View	Notes
Transaction group definitions EYUSTARTTRANGRP.ADDTRAN	Add a transaction to a transaction group.
Transaction group definitions EYUSTARTTRANGRP.CREATE	Create a transaction group and add it to the data repository.
Transaction group definitions EYUSTARTTRANGRP.DETAILED	Detailed information about a selected transaction group.
Transaction group definitions EYUSTARTTRANGRP.REMOVE	Remove a transaction group from the data repository.
Transaction group definitions EYUSTARTTRANGRP.TABULAR	Tabular information about all transaction groups within the current context.

Actions

Table 2. Actions available for TRANGRP views
Action	Description
ADDTRAN	Add a transaction to a transaction group.
CREATE	Create a transaction group and add it to the data repository.
REMOVE	Remove a transaction group from the data repository.
UPDATE	Update a selected transaction group.

Fields

Table 3. Fields in TRANGRP views
Field	Attribute name	Description
Acceptable level of abend probability	ABENDCRIT	The abend probability for a transaction associated with the default transaction group that should cause a target region to be considered unhealthy.
Acceptable target region load level	ABENDTHRESH	The abend probability for a transaction associated with the default transaction group that should cause a target region's load level to be doubled.
Automatic affinity creation	AFFAUTO	Indicates whether CICSPlex SM is to automatically create an affinity relationship for transactions associated with the transaction group. YES - An affinity is created using the values in the Affinity Relation and Affinity Lifetime fields. NO - An affinity is not automatically created (but can be created by a customized version of the dynamic routing program EYU9WRAM). N/A - There are no values in the Affinity Relation and Affinity Lifetime fields, therefore, no affinity is created.
Affinity relationship	AFFINITY	The affinity relationship to be used when processing transactions in this transaction group. The affinity relationship values are: Global - All users at all terminals. Luname - Terminal logical unit name. Userid - User ID. Bappl - CICS BTS business application. Locked - LOCKED affinities can arise only between dynamically linked programs. A LOCKED affinity is created when a called program retains state data that is to be preserved after returning to its caller. Programs with this type of affinity are routed to the same target region until end of unit of work occurs. LOCKED can be used only for dynamic program link (DPL) requests with an associated affinity lifetime of UOW. N_a - No affinity relationship is defined If this field is blank, no affinity relation was defined. This field and the Affinity Lifetime field are closely related. If you update this value, make sure an appropriate lifetime value is also specified.
Affinity lifetime	AFFLIFE	The affinity lifetime to be used when processing transactions in this transaction group. The affinity lifetime values are: Delimit - Until the pseudoconversation mode is END. Logon - For the duration of the terminal session. Pconv - For the duration of the pseudo conversation. Permanent - As long as the workload is active. Signon - As long as the user session is active. System - As long as the AOR to which transactions are routed is active. Activity - As long as the CICS BTS activity is active. Process - As long as the CICS BTS process is active. Uow - For as long as the unit-of-work is active N_a - No affinity lifetime is defined If this field is blank, no affinity lifetime was defined. This field and the Affinity Relation field are closely related. If you update this value, make sure an appropriate affinity relation value is also specified.
Algorithm type	ALGTYPE	The algorithm to be used when selecting the best target region in the Target Scope to which a transaction in the current transaction group should be routed. Valid options are: QUEUE - Route the transaction to the target region with best combination of: Health (MaxTask, Short-on-storage, Dumping, Stalled) Task queue depth (or load) Link speed from the routing region Abend probability, when calculated RTA event impact, when defined LNQUEUE - (Link Neutral Queue) Route the transaction to the target region with best combination of: Health (MaxTask, Short-on-storage, Dumping, Stalled) Task queue depth (or load) Abend probability, when calculated RTA event impact, when defined Note - The link speed from the router to the target is not factored into the routing weight calculation for the LNQUEUE algorithm GOAL - Route the transaction to the target region that: Is the most likely to allow the transaction to meet the response time goal set for it and other transactions in its z/OS workload management class When a specific target cannot be identified, apply the QUEUE algorithm to the remaining set of target regions LNGOAL - (Link Neutral Goal) Route the transaction to the target region that: Is the most likely to allow the transaction to meet the response time goal set for it and other transactions in its z/OS workload management class When a specific target cannot be identified, apply the LNQUEUE algorithm to the remaining set of target regions Note The link speed from the router to the target is not factored into the routing weight calculation for the LNGOAL algorithm INHERIT - Use the algorithm type specified in the WLM specification (WLMSPEC) to which this transaction group is associated.
Last modification agent	CHANGEAGENT	The change agent identifier that made the last modification. DREPAPI - Resource was last changed by a CICSPlex SM API command.
Last modification agent release	CHANGEAGREL	The CICS release level of the agent that made the last modification.
Last modification	CHANGETIME	The local time when the definition was last changed.
Last modification user ID	CHANGEUSRID	The user ID that made the last modification.
Time created	CREATETIME	The local time when the definition was created.
Description	DESC	A description of the transaction group.
Description code page	DESCCODEPAGE	The code page of the description field.
RTA event	EVENTNAME	The name of an analysis definition (RTADEF) or status definition (STATDEF) that may affect transactions associated with this transaction group. If a real-time analysis event is generated by this definition, WLM uses the information to select the best routing for those transactions. If this field is blank, no analysis or status definition is associated with the transaction group.
Primary search criterion	MATCH	Identifies whether the user name (USERID) or the logical unit name (LUNAME) is to be used as the primary search criteria for transactions associated with the transaction group.
Name	NAME	The name of the transaction group.
Transaction group status	STATE	Indicates how an AOR is to be selected for transactions associated with the transaction group: ACTIVE - Selects an AOR from the AOR scope identified with the associated workload definition. DORMANT - Uses the AOR associated with the transaction when it was defined to CICS.