Previous Topic: CA MICS Analyzer Option for CICSNext Topic: Other Miscellaneous Updates


ASG-TMON CICS TS Release 3.4 Support

We support the most recent and generally available release of ASG-TMON CICS Transaction Server Release 3.4 (support for IBM CICS TS 5.1).

Beginning with IBM CICS TS 4.1, IBM enabled CICS transaction TCBs to execute on both general purpose (CP) and specialty (zIIP/zAAP) processors. The ASG TMON support, however, did not provide raw data metrics to allow the separation of CP and specialty processor CPU times.

When running CICS TS releases 4.1 or 4.2, the CPU time-related data elements that are most frequently used for CICS transaction-related CPU time analysis and chargeback, include:

The CA MICS files that are affected are:

CICCSU - CICS User Activity File

CICCAU - CICS Application Unit Activity File

Data elements that can have a mixture of CP and Specialty Processor CPU times are:

fffCPUTM - Task CPU Time

fffTCBTM - TCB CPU Time

Where fff is CAU and CSU

With ASG TMON release 3.4, support for IBM CICS TS 5.1, TMON now provides raw data metrics that allow CPU time that is used by CICS transactions to be separated into two components:

CPU Time that is used on CP processors.

CPU Time that is used on Specialty (zIIP/zAAP) processors.

In addition, TMON release 3.4 provides raw data metrics that allow the time that is used on CP processors to be separated into two components:

CP CPU time that had to run on the CP processor.

CP CPU time that ran on CPs, but was z**P eligible.

To collect this mix of CP and z**P CPU times, change the default setting of the SPECIALTY PROCESSOR CPU control from "N" to "Y". For more information see, the ASG-TMON for CICS TS for z/OS Reference Guide Version 3.4.

When the default setting of the SPECIALTY PROCESSOR CPU control are not changed, CA MICS places zeros in all of the z**P related CPU times. Also the following data elements contain total CPU times reflecting a mix of CP and z**P CPU times:

fffCPUTM - Task CPU Time

fffTCBTM - TCB CPU Time

fffXCSTM - Task CPU Time Without zIIP/zAAP Eligible

fffXTSTM - TCB CPU Time Without zIIP/zAAP Eligible

Where fff is CAU and CSU

When changing the default setting for the SPECIALTY PROCESSOR CPU control to "Y", TMON collects z**P related CPU times, and CA MICS does the following actions:

Important! After upgrading to CA MICS Analyzer Option for CICS r12.9, use the new data element fffNZZTM for performance analysis, capacity planning, and chargeback. This upgrade is mandatory for product change CIC6770.

fffNZZTM - Normalized zIIP/zAAP CPU Time

This data element the following values:

We recommend setting this data element now, so you do not miss using CPU time after converting to 5.1.

If you use CA MICS Accounting and Chargeback, apply the co-requisite product change ACT7280. CICS accounting is performed using data in the CICCSU file.

After applying ACT7280, begin using the new computation code (1516) to charge for CPU time that is used on specialty (zIIP or zAAP) processors:

1516 -CICS NORMALIZED zIIP/zAAP CPU TIME    (CSUNZZTM)

That takes care of the CPU time that is used on specialty processors.

The CPU time that is used on CP processors is accounted for by the computation code you currently use to charge CPU time, either CSUCPUTM (1504) or CSUTCBTM (1508). Alternatively, if you want to charge a different rate for CP processor CPU time that could have executed on z**P processors, you can make use of the additional computation codes that are provided with ACT7280. Instead of using comp code 1504 or 1508, you would use:

1515 -CICS zIIP/zAAP ELIG CPU TIME ON CP    (CSUZZCTM)

- and either -

 1517 -CICS TASK CPU TIME W/O zIIP/zAAP ELIG (CSUXCSTM)

(if you had previously charged for CSUCPUTM-1504)

- or -

 1518 -CICS TCB CPU TIME W/O zIIP/zAAP ELIG  (CSUXTSTM)

(if you had previously charged for CSUTCBTM-1508)

We recommend that you use all of these new computation codes even if you select to run TMON with the default SPECIALTY PROCESSOR CPU="N". With this default setting, all CPU times appears in the non-z**P related data elements, and are charged at CP processor rates. Your accounting algorithm, however, will be ready to handle the shift in data element content when in the future, you change the setting to SPECIALTY PROCESSOR CPU="Y"