The contents of the PROCESSOR control statement identify processors that:

1. Have not already been defined as part of a sysplex via a SYSPLEX control statement or have been excluded from the SYSPLEX as of a specific PLEXDATE
2. Are not a CEC included under a 9672–E0x or 9672–P0x
3. Are running products that have been selected for usage pricing

Products selected for usage pricing on this specific processor are identified by the PRODUCT keyword. Each product requires its own PRODUCT keyword. Sample PROCESSOR control statements can be found in examples 1 - 7 under Usage pricing examples.

Syntax

PROCESSOR((type,model, serial_number)
          [PRODUCT(PRODOWNER(product_owner)
                  PRODNAME(product_name)
                  {START(yyyymmdd[,ALIGN(mm)])|STOP|RESTART|TESTDATE(yyyymmdd))}])

PROCESSOR((type,model,serial_number)

Specifies a processor where products exist that are billed using measured usage pricing where type, model, and serial_number identify the processor. If you are collecting data on any non-IBM processor, you must supply a PROCESSOR control statement as well, or the usage report program will not produce a valid Software Usage Report.

Note: These reports will not be sufficient for usage pricing until all the necessary control statements are used.

Customers wishing to participate in usage pricing are required to supply the appropriate IFAURP control statements to provide the usage report program with information about themselves and their hardware configurations and participating usage pricing products. This information is required to resolve an ambiguous situation that might arise when multiple products, processors, and vendors are involved, because a single execution of IFAURP can generate every combination of IFAURP reports possible for the entire data center, provided all the necessary data is available in a single history file.

type

One of a list of numbers (type, model and serial) that identify the processor. Value is 1-4 characters in length and consists of only alphanumeric and national characters. For example, 9021. type must be 9672 when referring to model Rxx.

model

One of a list of numbers (type, model, and serial) that identify the processor. Value is 1-8 characters in length and consists of only alphanumeric characters. For example, model must be Rxx when referring to type 9672. For example, the model for a 9672-R21 is R21.

Note: A list of the currently supported non-IBM processors appears in Type-model values for IBM and non-IBM processors. Only the type and model values listed in this table will be accepted as valid IBM® and non-IBM values.

serial_number

One of a list of numbers (type, model, and serial) that identify the processor. This value is 5 characters in length for the US and 7 characters in length for EMEA, Canada, and Latin America. It consists of only decimal digits. For example, 20012 (US), 1120012 (EMEA and Latin America).

IBM usage pricing note: The customer must ensure that the processor serial numbers supplied by these control statements agree with the processor serial numbers already registered with IBM for general software pricing.

Note: Performance monitors like RMF™ do not return the true processor serial when the processor is running PR/SM™. When running PR/SM, the second character of the 6 character processor serial number has been overlaid with the LPAR number.

PRODUCT

The PRODUCT keyword is specified for each product on this processor participating in usage pricing. When PRODUCT is specified, you must specify PRODOWNER, PRODNAME, and one of the following (START, STOP, RESTART, or TESTDATE). PRODFUNC is optional.

The values specified on the PRODOWNER, PRODNAME, and PRODFUNC identify the product to be billed. The values for these keywords are the same as those used by the product when it registered for usage data collection.

Note: Once type 89 records have been activated and processed for a product, that product's PRODOWNER, PRODNAME, and PRODFUNC values will automatically appear in the Software Summary Report. See Figure 1 for a sample report or contact the vendor for the correct values for these keywords.

PRODOWNER(‘product_owner’)

Indicates the associated ‘product_owner’ value that the product, itself, registered with the SMF data collection services. Every vendor provides the value for this field as a part of the VENDOR control statement that the vendor must provide to the customer. When the vendor is IBM, the PRODOWNER must be ‘IBM CORP’. The value is enclosed in quotes and is 1-16 characters in length.

PRODNAME(‘product_name’)

Indicates the ‘product_name’ value that the product specified when registering for usage measurement services. The value is enclosed in quotes and is 1-16 characters in length.

PRODFUNC(‘product_function’)

Indicates the ‘product_function’ value that the product specified when registering for usage measurement services. The value is enclosed in quotes and is 1-8 characters in length. Although PRODFUNC is optional, if a product registered with a product qualifier (the PRODQUAL keyword on the IFAUSAGE macro), that product MUST be specified to the usage report program with PRODOWNER/PRODNAME/PRODFUNC and PRODFUNC must match PRODQUAL.

START(yyyymmdd)

Specifies:

1. That the customer wishes to participate in usage pricing for this product
2. The date when the customer has met all the usage pricing requirements for this product on all OS/390® or z/OS® guests and LPARs on the specified processor activated the collection of SMF type 89 subtype 1 records

Specifying the START keyword causes the usage values for the identified product to appear in the Billing section of the Software Usage Report. You can specify START only once per product per sysplex. YOU CANNOT IMPLEMENT USAGE PRICING UNTIL YOU SPECIFY START.

Note: No new MULC users can START after December 1, 1998. S/390® Usage Pricing is the only usage pricing option that you may START on or after December 1, 1998.

yyyymmdd

Specifies the date when the initial measurement period for this product begins. The initial measurement period is two months.

Note:

1. IBM must receive your Software Usage Report within 72 days of this date.
2. Missing dates and dates later than IFAURP's run date will be treated as an error; IFAURP will end after issuing message IFA313S.
3. The initial measurement period for MULC users beginning before December 1, 1998, was one month in duration.

Specifying this keyword starts usage pricing for the specified product and causes the following:

1. Establishes the initial and subsequent measurement periods, as well as the billing periods, for the product (and other products by the same vendor).
2. Records the start date, measurement, and billing periods in the history file.
3. Prevents a new start date from being specified for the identified product.
4. Prevents a test start date from being specified for the identified product. See TESTDATE keyword below.

Value is 8 characters in length and consists of only decimal digits.

ALIGN(mm)

Specifies the number of the month that the initial billing period is to be aligned with. Based on the value provided, IFAURP adjusts the length of the initial billing period from 3 to 14 months based on the value provided. All subsequent billing periods will be 12 months in length. However, billing periods are on a vendor basis, so each vendor may have a billing period different from other vendors on the same processor or parallel sysplex. Once established, the same billing periods automatically apply to all of the same vendor's products added at a later date to the same processor or parallel sysplex. mm is 1-2 characters in length and consists of only decimal digits. ALIGN is accepted only on the first START keyword of a given product owner's products on given stand-alone processor or sysplex. ALIGN cannot be specified for subsequent products from the same vendor.

For those wishing to use ALIGN to set the end of the first 12–month measurement period of a processor, instead of choosing an ALIGN value based on the first month of the "billing" period, choose a numeric ALIGN value as follows:

  ALIGN = (last month of measurement period) + 2  

If the resulting value is larger than 12, subtract 12 from that value. For example, if the last month of the measurement period is to be November:

  ALIGN = 11 + 2 = 13, ALIGN = 13 - 12 =1  

Note: MULC users who did an ALIGN prior to December 1, 1998, could have an initial measurement period between 3 and 8 months in duration, with subsequent billing periods 6 months in duration. These users will migrate to 12–month billing periods at the start their first billing period that begins in 1999.

STOP

Indicates usage pricing for the identified product is to cease. This can only happen if START or RESTART was previously specified. Specifying STOP causes the usage values for the identified product to appear in the Collection section of the Software Usage Report. STOP specifies that the identified product is not to appear in the Billing section of the Software Usage Report for the measurement period corresponding to the next billing period, based on the date the usage report program is run. Specify this keyword when you want to end the usage pricing option for a particular product.

Important: If you discontinue MULC after January 1, 1999, you cannot restart MULC later. S/390 Usage Pricing is the only usage pricing option that you may START after December 1, 1998, or RESTART after January 1, 1999.

RESTART

Specifies that the identified product is to appear in the Billing section of the Software Usage Report for the measurement period corresponding to the next billing period, based on the date the usage report program is run. Specify this keyword when you want to resume the usage pricing option for a particular product after having previously stopped it.

Note:

1. IBM will not permit a MULC restart after January 1, 1999.
2. If you have discontinued ULC, you must wait at least 12 months before IBM will permit you to restart.

TESTDATE(yyyymmdd)

Temporarily specifies the date usage pricing is to begin. TESTDATE causes the same usage values to be reported as the START keyword except that the values are reported in the Collection section of the Software Usage Report instead of the Billing section. Value is 8 characters in length and consists of only decimal digits. TESTDATE is not accepted if START has been previously specified for the specified product.