Active workloads - WLMAWORK

The Active workloads (WLMAWORK) views display information about an active workload within the CICSplex identified as the context.

Supplied views

To access from the main menu, click:

Active workload views > Active workloads

Table 1. Views in the supplied **Active workloads** (WLMAWORK) view set
View	Notes
Active workloads EYUSTARTWLMAWORK.DETAILED	Detailed information about a selected active workload.
Active workloads EYUSTARTWLMAWORK.SET	Set active workload attributes.
Active workloads EYUSTARTWLMAWORK.TABULAR	Tabular information about all active workloads within the current context.

Actions

Table 2. Actions available for WLMAWORK views
Action	Description
GET	Optional parameter. YES requests records from every CMAS managing the workload. NO requests records from a single CMAS managing the workload. NO is the default value if the parameter is not specified.
SET	Set active workload attributes.

Fields

Table 3. Fields in WLMAWORK 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. A value of 0 means WLM is not calculating abend probabilities for the workload.
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. A value of 0 means WLM is not calculating abend loads for the workload.
Automatic affinity creation	AFFAUTO	Indicates whether CICSPlex SM is to automatically create an affinity relationship for transactions that are not associated with any installed 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.
Default affinity relation	AFFINITY	The default affinity relation applied to transactions not associated with any installed transaction group. The affinity relation values are: GLOBAL - All users at all terminals LUNAME - Terminal logical unit name USERID - User ID BAPPL - 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. NONE - No affinity relation was defined
Default affinity lifetime	AFFLIFE	The default affinity lifetime used with the default affinity relation. This value is applied to transactions that are not associated with any installed transaction group. After the first instance of a transaction, subsequent instances of the transaction are run on the same target region: DELIMIT - Until the pseudoconversation mode is END LOGON - For the duration of the terminal session PCONV - For the duration of the pseudoconversation PERMANENT - For as long as the workload is active SIGNON - Until the terminal user signs off SYSTEM - Until the target region terminates ACTIVITY - For as long as the CICS BTS activity is active PROCESS - For as long as the CICS BTS process is active UOW - For as long as the unit-of-work is active NONE - No affinity lifetime was defined
Default algorithm type	ALGTYPE	The algorithm to be applied to all transactions that are not associated with any installed transaction group: QUEUE - Routes transactions to the target region that has the lowest routing weight at the time of the routing evaluation. The routing weight of a target region is a combination of factors that include: The current task load The current target health state The link speed from the router to the target The probability of transaction abend at the target The effect of any outstanding RTA events at the target LNQUEUE - Routes transactions to the target region that has the lowest routing weight at the time of the routing evaluation. The routing weight of a target region is a combination of factors that include: The current task load The current target health state The effect of any outstanding RTA events at the target The probability of transaction abend at the target Note - The link speed from the router to the target is not factored into the routing weight calculation for the LNQUEUE algorithm GOAL - Routes transactions to the target region which is best able to meet the transaction's average response time goal, as predefined using z/OS Workload Manager. If a specific target region cannot be resolved from the evaluated GOAL set, then the QUEUE algorithm is applied to the remaining target set. LNGOAL - Routes transactions to the target region which is best able to meet the transaction's average response time goal, as predefined using z/OS Workload Manager. If a specific target region cannot be resolved from the evaluated LNGOAL set, then the LNQUEUE algorithm is applied to the remaining target set.
Active target regions	AORCNT	The number of active CICS systems, identified as target region for the workload.
Default target scope	AORSCOPE	The name of the CICS system or CICS system group that is to be the target for any dynamic transactions or programs not associated with a transaction or program group.
Description	DESC	The description of the workload.
Event name	EVENTNAME	The name of a real-time analysis event that will affect the routing of transactions in this workload. If a real-time analysis event is generated, WLM uses the information as part of the target selection criteria. An event can optionally be associated with a workload when the workload specification is created. If this field is blank, no event is associated with the workload. The name of an event is the same as an installed real-time analysis definition (RTADEF) or status definition (STATDEF)
Optimization status	OWSTATE	This field reports the sysplex optimization status of the current workload. The value is an amalgamation of all of the workload router optimization statuses, and all of the workload target optimization statuses. The possible values are: ACTIVE All targets and routers in the workload are executing in optimized workload state. PARTIAL At least one target and one router are executing in optimized workload mode. Use the Active routing regions and Active target regions hyperlinks to determine which regions are not running in an optimized state. INACTIVE The workload is not running in an optimized state, for one or more of the following reasons: No routing regions in the workload are running in an optimized state No target regions in the workload are running in an optimized state No regions in the workload are running in an optimized state The optimised workload routing function is DISABLED for the current target region The workload was designated as being non optimized by specifying a value of 0 for the RS server update frequency on the CICSplex definition or CICS system definition for this workload.
Reporting CMAS	RPTCMAS	The name of the CMAS that provided the information in this record. If the GET operation optional parameter EXPLODE is not specified or is specified as NO, then this attribute will be set to blanks and only one record will be returned for the workload. If the GET operation optional parameter EXPLODE is specified as YES, then this attribute will be set with the name of the CMAS that provided the information in this record. A separate record will be returned for the workload from each CMAS that manages the workload. When the IBM distributed WUI menus and views are used to request the WLMAWORK tabular view, the EXPLODE parameter will be set to YES.
Shared status	SHARED	Indicates whether the workload has been shared with a pre-CICS TS 1.3 CMAS. If it has, the installation of CICS BTS related definitions are inhibited.
Workload status	STATUS	The status of the workload: ACTIVE - All the target and routing region connections that this workload depends upon are available FROZEN - A target or routing region connection that this workload depends upon has been lost As long as a workload remains frozen: Transactions will continue to be routed according to any existing affinities New affinities can be created as long as they do not involve other CMASs. Global or permanent affinities, which require other CMASs to be notified, cannot be created Install and discard action commands are not allowed for any aspect of the workload The cause of a lost connection could be the target or routing region, one of the CMASs that manage the workload or a connection between the CMASs. To determine why a workload is frozen: Check the contact status in the Target region in active workload (WLMAWAOR) and Active workload routing regions (WLMAWTOR) views to determine which target or routing region is affected Check the MAS view to determine the status of the target or routing region Check the status of all connections for the target or routing region Determine which connection(s) were lost and take appropriate action to re-establish the connections.
Active routing regions	TORCNT	The number of active CICS systems, identified as routing regions, that are associated with the workload.
Active transaction group affinities	WAFFCNT	The number of active transaction group affinities that are associated with the workload.
Active workload definitions	WDEFCNT	The number of active workload definitions that are associated with the workload.
Name	WORKLOAD	The name of the workload. This is also the name of the installed workload specification definition.
Owning system ID	WRKLOWNER	The CICS system ID of the CMAS that created the workload.
Active transaction groups	WTGPCNT	The number of active transactions groups that are associated with the workload.
Active dynamic transactions	WTRNCNT	The number of active dynamic transactions that are associated with the workload.