Messages IOAT00 through IOATxx

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

IOAT00S FAILURE TO LOCK WS TRACE WORK AREA

Explanation: The tracing facility failed to lock the internal (WS) trace work area.

The tracing request is ignored. Processing continues.

Corrective Action: Contact BMC Customer Support.

IOAT01S FAILURE TO LOCATE DDNAME(ddName) SUPPLIED TO IOATRC

Explanation: The tracing facility failed to locate the ddName DD statement.

In this message, ddName is the name of the DD statement that was supplied to the trace facility as an internal parameter.

The tracing request is ignored. Processing continues.

Corrective Action: Contact BMC Customer Support.

IOAT02E APF-AUTHORIZATION REQUIRED TO INVOKE SVC DUMP

Explanation: An SVCDUMP request was received by the tracing facility. Such a request requires APF authorization for STEPLIB load libraries.

The SVCDUMP tracing request is ignored. Processing continues.

Corrective Action: Ensure that STEPLIB load libraries have APF authorization, and restart the product monitor.

IOAT03E INVALID BUFID (bufid) HAS BEEN SUPPLIED IN INPUT PARAMETERS

Explanation: The Buffer ID specified in one of the parameters contains invalid characters. Valid characters for the Buffer ID are A - Z, 0 - 9, @, #, $.

Processing of parameters is stopped.

Corrective Action: Check the input parameters in the operator command or in the DATRCIN/DATRCBF input files and make appropriate adjustments as needed. Then rerun the command or product monitor.

IOAT04E SYNTAX ERROR IN INPUT PARAMETERS

Explanation: This error message indicates there is a syntax error in one of the input statements.

Processing of parameters is stopped.

Corrective Action: Check the input parameters in the operator command or in the DATRCIN/DATRCBF input files and make appropriate adjustments as needed. Then rerun the command or product monitor.

IOAT05W BUFFER (bufid) IS NOT DEFINED. FLUSH COMMAND IGNORED

Explanation: The buffer (bufid), which is required to flush in operator MODIFY command, is NOT allocated. The Flush command is ignored.

Corrective Action: In the Flush command, check the buffer ID.

IOAT06E UNKNOWN COMMAND/KEYWORD (keyword) IN INPUT PARAMETERS

Explanation: An unknown command or keyword is specified in one of the input statements. The processing of parameters is stopped.

Corrective Action: Check the input parameters in the operator command or in the DATRCIN/DATRCBF input files and make appropriate adjustments as needed. Then rerun the command or product monitor.

IOAT07E INVALID ARGUMENT FOR KEYWORD (keyword)

Explanation: An invalid value was specified for the keyword.

The processing of parameters is stopped.

Corrective Action: Check the input parameters in the operator command or in the DATRCIN/DATRCBF input files and make appropriate adjustments as needed. Then rerun the command or product monitor.

IOAT08S INTERNAL ERROR ENCOUNTERED. MODULE: module REASON: rsn

Explanation: An internal error was encountered in the module module.

The variables in this message are:

module - the name of the module where an internal error was encountered
rsn - the exact reason for the error. Valid values are:
- DESCRIPTOR LOST
- NO DESCRIPTOR ADDR

The option to trace into a buffer is disabled. Processing continues.

Corrective Action: Contact BMC Customer Support.

IOAT09E INVALID LEVEL PARAMETER SPECIFIED IN INPUT PARAMETERS

Explanation: An invalid LEVEL parameter was detected in an input statement.

Corrective Action: Check the input parameters in the operator command or in the DATRCIN/DATRCBF input files and make appropriate adjustments as needed. Then rerun the command or product monitor.

IOAT0BW BUFFER x IS NOT DEFINED. DEFAULT BUFFER WILL BE USED INSTEAD

Explanation: This warning message indicates that redirection to the x buffer was required, but the buffer is NOT allocated. The messages are redirected to the default buffer.

Corrective Action: No action is required.

IOAT0CI THE FOLLOWING TRACE LEVELS IN THE BUFFERS: bufID[1, bufID2, . . . bufIDn]

Explanation: This information message is issued after command TRACE= with keyword BUF= is performed. It is a header for subsequent IOAD02I messages. Normal processing continues.

bufID[1, bufID2, . . . bufIDn] are one or more buffer IDs.

Corrective Action: No action is required.

IOAT0DI FOR THE DESTINATIONS: dest[1, dest2, dest3, dest4]

Explanation: This information message is issued after command TRACE= with keyword BUF= is performed. This message is a header for subsequent IOAD02I messages. Normal processing continues. dest[1, dest2, dest3, dest4] can be one or more of the following:

PRINT
CHAIN
WTO
GTF

Corrective Action: No action is required.

IOAT0FE TRACE trc_num CAN NOT BE TURNED ON AS EXTERNAL TRACE. WILL NOT BE ISSUED.

Explanation:This message indicates that the tracing for trc_num trace number (where trc_num is the trace number requested in the TRACE MODIFY command) has not been turned on because of the environment limitation.

Corrective Action:Contact BMC Customer Support.

IOAT0HI TRACING INTO A BUFFER HAS BEEN DISABLED

Explanation: This information message indicates that the tracing into a buffer facility has been disabled.

Corrective Action: No action is required.

IOAT0IE DDNAME(ddName) NOT FOUND; FAILURE TO FLUSH THE TRACE BUFFER

Explanation: The TRACE=FLUSH modify request was issued, but tracing into a buffer facility failed to perform the request, because the DD statement that was supplied to the trace facility as an internal parameter was not found.

In this message, ddName is the name of the DD statement that was supplied to the trace facility as an internal parameter.

The TRACE=FLUSH request is ignored. Normal processing continues.

Corrective Action: No action is required.

IOAT0JS FAILURE TO GETMAIN STORAGE FOR TRACE BUFFER bufID

Explanation: This message indicates an attempt to getmain trace buffer bufID failed.

The option to trace into a buffer is disabled.

The processing of parameters is stopped.

Corrective Action: Try specifying REGION=0 in the JOB JCL statement and run the product monitor again. Otherwise, contact BMC Customer Support.

IOAT0KI TRACING INTO BUFFERS IS ENABLED

Explanation: This information message indicates that the tracing into a buffer facility has been successfully initialized and enabled. Normal processing continues.

Corrective Action: No action is required.

IOAT0LI number1 LINES (number2 KB) ARE ALLOCATED FOR TRACE BUFFER x

Explanation: This information message indicates that trace buffer x of the specified size is successfully allocated. Normal processing continues.

Corrective Action: No action is required.

IOAT0MW TRACING INTO A BUFFER IS NOT SUPPORTED

Explanation: This warning message indicates the TRACE= modify command with the BUF= parameter was issued, but the tracing into a buffer facility is not supported.

The TRACE= modify command is ignored. Normal processing continues.

Corrective Action: No action is required.

IOAT0OE FAILURE TO FLUSH THE TRACE BUFFER: UNABLE TO LOCK

Explanation: The TRACE=FLUSH modify command was issued, but it could not be performed because of the failure to lock the trace buffer.

The TRACE= FLUSH modify command failed. Normal processing continues.

Corrective Action: Contact BMC Customer Support.

IOAT0RS FAILURE TO LOAD module PROCESSOR OF TRACE=command MODIFY COMMAND

Explanation: The specified load module failed to load, and therefore did not perform the command modify command.

The variables in this message are:

module - name of the load module that was attempted to be loaded
command - name of the modify command that initiated loading of the module.

The modify request is ignored. Processing continues.

Corrective Action: Contact BMC Customer Support.

IOAT0UI TRACE BUFFER (bufid) HAS BEEN WRAPPED AROUND nnnn TIMES

Explanation: This information message indicates that the tracing buffer became full with tracing records, and it has been recycled nnnn times.

Corrective Action: No action is required.

IOAT0WE FAILURE TO OPEN DDNAME(ddName) TO FLUSH TRACE BUFFER

Explanation: The specified DDNAME needed to perform the TRACE=FLUSH modify request could not be opened.

In this message, ddName is the name of the DD statement that was supplied to the trace facility as an internal parameter.

The TRACE= FLUSH modify request failed. Normal processing continues.

Corrective Action: Check the indicated DD statement, correct if necessary, and try running a product monitor again.

IOAT0XI number TRACE RECORDS HAVE BEEN FLUSHED INTO ddName FROM BUFFER x

Explanation: This information message indicates that the TRACE=FLUSH modify request was issued and successfully processed. Normal processing continues.

The variables in this message are:

number--number of trace records flushed into the output
ddName--name of the DD statement supplied to the trace facility as an internal parameter
x--ID of the flushed buffer

Corrective Action: No action is required.

IOAT0YS IOATRC RECEIVED WS ADDRESS ABOVE THE LINE; CANNOT PROCEED

Explanation: The tracing facility received an invalid internal request.

The tracing request is ignored. Processing continues.

Corrective Action: Contact BMC Customer Support.

IOAT0ZS FAILURE TO GET MCT ADDRESS

Explanation: An internal problem was encountered.

The system action is unpredictable. Action depends on the internal problem.

Corrective Action: Contact BMC Customer Support.

Parent Topic

IOA messages