IFAURP control statements

To generate reports on registered products, CUSTOMER is the only required control statement, and NAME is the only required keyword.

The CUSTOMER statement is optional if the following are both true:

You have used the CUSTOMER statement in a previous execution of IFAURP.
You use a history file as input when you execute IFAURP.

Customers who are interested in usage pricing but want to generate ‘quick’ reports before making any decision on usage pricing, can do so by supplying only a CUSTOMER control statement with the NAME keyword. This single statement will allow IFAURP to process all files and generate all reports. An example of such a control statement is:

CUSTOMER(NAME('Acme Tulle and Dye Company'))

If you are collecting data on any non-IBM processor, you must supply a PROCESSOR control statement as well, or the program issues message IFA328S for each unrecognized processor.

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.

The supported control statements are:

CUSTOMER
VENDOR
SYSPLEX
PROCESSOR
TRANSFER

Following is a list of those control statements that are either recommended or required by IBM® for usage pricing. Once the required control statements are in a history file, those statements become optional if the history file is used as input on future executions of IFAURP.

CUSTOMER: required
NAME: required
ADDRESS: recommended
CONTACT: recommended
PHONE: recommended
VENDOR: required
PRODOWNER: required and must be ‘IBM CORP’
NAME: ‘IBM Corporation’ or as supplied by IBM representative
ADDRESS: required and supplied by IBM representative
CODE: required
SYSPLEX: required (if PROCESSOR statement not present)
ID: required
PLEXDATE: required
PROCESSOR: required (if CLUSTER keyword not present)
CLUSTER: required (if PROCESSOR keyword not present)
PRODUCT: required
PRODOWNER: required and must be ‘IBM CORP’
PRODNAME: required
START: required
PROCESSOR: required (if SYSPLEX statement not present)
(type,model,ser): required
PRODUCT: required
PRODOWNER: required and must be ‘IBM CORP’
PRODNAME: required
START: required

Notes on control statement syntax:

You must supply the keywords on each statement in the order shown in the syntax example.
Keywords themselves must be in UPPER CASE, while many of the values supplied for them need not be.
The keyword values enclosed within quotes can consist of any printable character in the US English EBCDIC character set, including a blank.
Code uppercase letters, words, and characters exactly as they appear in the syntax.
Lowercase letters, words, and symbols in the syntax represent variables. Substitute specific information for them.
An ellipsis (...) follows an item that you can code more than once. Never code ... on a control statement.
Brackets surround an optional item or items and indicate that you can code one or none of the enclosed items. Never code [ or ] on a control statement.
A vertical bar (|) indicates an exclusive OR. Never code | on a control statement. It is used between choices within braces or brackets; it indicates that you code only one of the items within the braces or brackets.
Braces ({ }) surround required, related items and indicate that you must code one of the enclosed items. Never code { or } on a control statement.