Measuring mobile workloads with WLM

IMS supports three mechanisms to track mobile workloads with MWP: tracking on LPAR level, subsystem level, and CPU level. Different configurations are required for each tracking mechanism.

You can configure your IMS system to use one of the following mechanisms:
  • Use an individual LPAR for mobile-only workloads. All defining programs can report the General Capacity Processor (GCP) CPUs that run on the LPAR as mobile CPUs.
  • Build individual subsystems of the defining programs for mobile-only workloads. The defining programs can then report the GCP CPUs that run on the subsystems as mobile CPUs.
  • Use the same subsystems for mobile and non-mobile workloads, but create different CPU reports for mobile CPU.

CPU-level tracking

If the mobile workloads are tracked on the CPU level, IMS reports the TCP/IP port number along with the logical terminal (LTERM) override name or the OTMA transaction pipe (TPIPE) name to the Workload Manager (WLM) to differentiate mobile between mobile and non-mobile workloads.

The LTERM override name is set to override the predetermined value in the LTERM field of the IMS application program's I/O PCB in the Open Transaction Manager Access (OTMA). If no LTERM override name is provided, OTMA places instead the predefined TPIPE name in the I/O PCB LTERM field.

Depending on your TCP/IP port configuration, you can differentiate the workload type by one of the following values:
TCP/IP port number
Configure IMS Connect so that each TCP/IP port handles transactions of one workload type exclusively, either mobile workloads or non-mobile workloads.
LTERM override name or TPIPE name
If both mobile and non-mobile transactions arrive on the same port, use the LTERM override name if one exists, or the TPIPE name.

Use classification rules to specify which work is mobile work that is eligible for mobile workload pricing. Set the Reporting Attribute to MOBILE to explicitly define what port numbers, LTERM override names, or TPIPE names are associated with mobile transactions. Based on the values that you provided, the IWM4CLSY macro returns a service class.

For more information about setting up classification rules for mobile workload reporting, see Defining classification rules for mobile workload

Examining the workload records

You can examine the workloads running records in the z/OS System Management Facility (SMF) records by running the ERBSCAN and the ERBSHOW commands on the extracted SMF records.

You can also consult the X'56FA' log record to determine the workload type. The X'56FA' log record contains statistical information about the transaction workloads. Although the log record does not directly indicate whether the workloads are mobile, but you can determine the workload type from the information such as job name, program name, transaction code, transaction class.

If you are using the WLM panel to classify transactions, you do not need to consult the X'56FA' log record to determine the workload type.