Messages IOAZ00 through IOAZxx

This group includes messages for the IOA (infrastructure) product.

IOAZ00I The performance trace limitations are as follows:

Explanation: This is the first of a series of information messages that together display the current performance trace limitation settings.

This message is followed by the IOAZ01I message.

Corrective Action: No action is required.

IOAZ01I The following requests groups are to be traced:

Explanation: This is the second of a series of information messages that together display the current performance trace limitation settings.

This message is preceded by the IOAZ00I message, and followed by the IOAZ02I message.

Corrective Action: No action is required.

IOAZ02I request group1 request group2

Explanation: This is the third of a series of information messages that together display the current performance trace limitation settings. The contents of this message lists the group(s) of requests to be traced. The request group can be one of the following: LIST, REPORT, ALL (where ALL means no limitation).

This message is preceded by the IOAZ01I message, and can be followed by the IOAZ03I message.

Corrective Action: No action is required.

IOAZ03I The following users are to be traced:

Explanation: This is the fourth of a series of information messages that together display the current performance trace limitation settings.

The contents of this message form part of the headers of the columns of statistics.

This message is preceded by the IOAZ02I message, and followed by the IOAZ05I message.

Corrective Action: No action is required.

IOAZ05I user-id

Explanation: This is the fifth of a series of information messages that together display the current performance trace limitation settings.

The content of this message is the user ID whose actions are to be traced. The first instance of this message is preceded by the IOAZ03I message. This message is repeated with new user-id values until all the user IDs to be traced have been displayed.

Corrective Action: No action is required.

IOAZ11E ZIIP ENCLAVE CREATION FAILED. RC=rc RSN=rsn

Explanation: The Workload Management Service (IWM4ECRE macro) failed during enclave creating for ZIIP usage. For explanations of the return code (rc) and reason code (rsn) displayed as part of this message, see the IBM manual MVS Programming: Workload Management Services. The address space continues to work, but does not use the ZIIP processor.

Corrective Action: Contact BMC Customer Support.

IOAZ12W NO ZIIP CONFIGURED TO WHICH WORK COULD BE OFFLOADED TO. ZIIP WORK WILL BE REPORTED AS "SUP_ON_CP" WORK. RC=rc RSN=rsn

Explanation: This warning message indicates that the Workload Management Service could not be configured for offloading work to the ZIIP. The address space continues to work and uses the ZIIP processor but ZIIP work will be reported as specific work.

Corrective Action: For explanations of the return code (rc) and reason code (rsn) displayed as part of this message, contact BMC Customer Support.

IOAZ13E NO ZIIP CONFIGURED TO WHICH WORK COULD BE OFFLOADED TO. ZIIP PROCESSING DISABLED. RC=rc RSN=rsn

Explanation: The Workload Management Service could not be configured for offloading work to the ZIIP. The address space continues to work, but does not use the ZIIP processor.

Corrective Action: Contact BMC Customer Support.

IOAZ14E ZIIP OFFLOAD CPU PERCENTAGE FAILED. RC=rc RSN=rsn

Explanation: The Workload Management Service failed during setting offload CPU percentage for ZIIP usage. The address space continues to work, but does not use the ZIIP processor.

Corrective Action: Contact BMC Customer Support.

IOAZ15E ZIIP ENCLAVE DELETION FAILED. RC=rc RSN=rsn

Explanation: The Workload Management Service (IWM4EDEL macro) failed during ZIIP enclave deleting. The address space continues to work, but does not use the ZIIP processor.

Corrective Action: Contact BMC Customer Support.

IOAZ16I INTERFACE TO XBM IS ACTIVE

Explanation: The message is issued when the interface to XBM is initialized successfully.

Corrective Action: No action is required.

IOAZ17I THE XBM MODIFY COMMAND IS IGNORED BECAUSE parameter_name PARAMETER IS SET TO N

Explanation: The message is issued when the XBM modify command is ignored because the parameter_name parameter was set to N, where parameter_name is one of the following: ZIIPXBMO, ZIIPXBMP, or ZIIPXBMA.

Corrective Action: No action is required.

IOAZ18I CPU TIME OFFLOADED TO ZIIP: dddD hhH mmM ss.ccS

Explanation: The message is issued upon a termination of the XBM-enabled address space. It contains the number of days (ddd), hours (hh), minutes (mm), seconds (ss) and hundredths of a second (cc) of CPU time offloaded to ZIIP.

Corrective Action: No action is required.

IOAZ19I INTERFACE TO XBM IS INACTIVE

Explanation: The message is issued when the interface to XBM is not initialized for the following possible reasons:

• The ZIIPXBMx parameter (where ZIIPXBMx is one of the following: ZIIPXBMO, ZIIPXBMP or ZIIPXBMA) in the IOAPARM parameter member is set to N.
• XBM address space is inactive, regardless the value of the ZIIP parameter.

Corrective Action: No action is required.

IOAZ1AI NO ONLINE ZIIP PROCESSORS FOUND

Explanation: The message is issued when no online ZIIP processors were found.

Corrective Action: No action is required.