Skip to Content

Message format

Most BMC messages consist of a message identifier followed by message text.

Message identifier

Message identifiers can include a prefix, a message number, and a severity indicator, or some combination of them:

  • The prefix BMC clarifies that a BMC product or component issued the message. Any other prefix identifies the product or component that issued the message.

    Warning

    Note

    Some messages do not have a prefix.

    For LOCAL COPY PLUS, if you have selected to customize your message prefix with the 3-character product code (such as ETA or DLP), you should look for your message number preceded by the BMC prefix only.

  • The number uniquely identifies the message.

  • The severity indicator tells you the seriousness of the reported situation and whether action is required. The following table lists the severity indicators. Not all products issue all codes.

    Severity indicators

    Indicator

    Meaning

    A (action)

    A problem occurred, and you must take an action in response.

    (Utility products for DB2 only) The software issued a write-to-operator-with-reply (WTOR) message to the MVS system console, indicating that you must respond for the software to continue.

    (BMCSORT only) The software encountered a critical error but terminates in an orderly fashion. You must take some corrective action.

    B (tuning)

    The software continues processing, but you can use the information that is provided to tune future jobs.

    C (information)

    The purpose of the message is to provide information only. No action is required.

    C (cancellation)

    A problem caused the job to be cancelled. You must take specific action to correct the error before resubmitting the job.

    D (diagnostic)

    The purpose of the message is to provide diagnostic information when diagnostic tracing is active. No action is required.

    E (error)

    The software cannot complete your request due to a problem. In most cases, the software terminates in an orderly fashion. You must take specific action to correct the error before processing can resume.

    (Utility products for DB2 only) The software encountered a problem, probably in the specified command or JCL.

    I (information)

    The purpose of the message is to provide information only. No action is required.

    P (performance)

    A condition that could adversely affect performance was detected.

    R (reply)

    You must reply to the message before the software can continue.

    S (severe error)

    A severe error occurred. The software encountered an unexpected error but terminates in an orderly fashion.

    T (trace error)

    A trace error has occurred.

    U (unrecoverable error)

    The software cannot continue processing (as when an abend occurs).

    W (warning)

    The software continues processing, but you need to investigate the reported issue.

    x (variable indicator)

    Depending on the situation specified in the message, the indicator changes between I (information), W (warning), E (error), C (critical), and S (severe).

    Warning

    Note

    For CHECK PLUS messages BMC52401 through BMC52599, you can change the severity indicator on any message whose original indicator is I (an informational message). Changing the severity indicator results in the check job completing with a different return code. For details about changing these indicators, see the MSGSEV installation option described in the CHECK PLUS for DB2 Reference Manual.

    In the following sample, SVO is the prefix, and the message reports standard information:

     SVO0106I Release v.r.m of SVOS has been started.

Message text

The following special conventions are used in message entries, as needed, to approximate the message text that you receive:

Message conventions

For

Convention

Example

Variable text

Italics

A data type mismatch occurred in column columnNumber.

The variable columnNumber represents the number that you see when you receive this message.

Optional text

[ ]

DISPLAY TYPE type FOR reportListType [sysdata] NOT FOUND

The message that you receive might omit the sysdata value.

Conditional text

{ | }

{PLAN ¦ PACKAGE} objectName MAY REQUIRE CHANGES TO SQL TEXT

The message that you receive will contain one of the enclosed values.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

Messages library