+

Search Tips | Advanced Search

Product usage recording with IBM MQ for z/OS products

To determine the product usage, the z/OSĀ® system records the amount of processor time that is used by the product when it processes.

z/OS can measure how much processing time is spent in doing work on behalf of the IBM MQ queue manager that is handling MQI calls, executing MQSC commands, or performing some other action to support the messaging and queuing functions that are used by our application programs. The amount of processing time is recorded in a file at hourly intervals, and the hourly records are totaled at the end of a month. In this way, the total amount of time used by the IBM MQ for z/OS product on your behalf is computed, and used to determine how much you pay for your use of the IBM MQ for z/OS product that month.

Product usage recording is implemented as follows:

For more information about product usage recording and the Sub-Capacity Reporting Tool (SCRT), see Preparing to use the Sub-Capacity Reporting Tool. For information about the MULCCAPT parameter see, Use CSQ6SYSP.

Over-riding the default product associated with usage

IBM MQ Version 9.0.3 introduces an improved method for associating IBM MQ usage with the licensed Product ID (PID) so that workload reporting tools, for example, SCRT and MWRT, correctly reflect usage.

Each of the following products uses a different PID:

There are two alternative mechanisms to associate the correct PID with a running instance of IBM MQ:
  1. Most useful for a long term deployment of IBM MQ - The CSQ6USGP macro selects the correct PID, and is built into the queue manager zPARM parameter.
  2. Most useful for a test system which needs to run for short times under different PIDs - Parameters on the START QMGR command select the PIDs. These run-time parameters, QMGRPROD and AMSPROD, can be entered on the command, or coded into the MSTR JCL.

    Note that a value entered on a START command overrides any values encoded into ZPARM.

In all cases, the selected PIDs are shown in startup messages CSQY036I and CSQ0619I.

For Managed File Transfer, the PID is selected using an fteSetProductId command.

If no value is set by the preceding mechanisms, a default PID is used.

Sample scenarios