Reading IBM i Message IDs

Learning Objective

By the end of this lesson, you will be able to recognize the structure of an IBM i message ID, and explain why that structure matters for understanding what a message actually means.

Simple Explanation

Messages seen in a job log, covered in the previous lesson, are not just plain text; each one has a message ID: a short prefix followed by a number, such as CPF9897 or RNQ1218. The prefix generally identifies which message file, and therefore which part of IBM i or which application, the message came from. CPF (Control Program Facility) is by far the most common prefix, covering a huge range of messages generated by IBM i's own operating system components. Other prefixes, such as RNQ, come from other message files, some IBM-supplied and some defined by a specific application.

Separately from its ID prefix, every message also has a message type, such as informational, diagnostic, or inquiry, a message that specifically expects a reply before a job can continue. Two messages with completely different prefixes can both be inquiry messages; the prefix identifies the message's source, not its type.

Why It Matters

Recognizing that a message ID has real structure, not just a random code, means you can tell at a glance roughly where a message came from, before even reading its full text: a CPF message points to IBM i's own system-level messaging, while a different prefix points to a different message file, IBM-supplied or application-specific. Separately, recognizing that a message also has its own type, such as inquiry, tells you whether it is actively waiting on a response, regardless of its prefix. Together, this structure is what makes a message searchable and identifiable when looking it up for more detail.

Practical Example

Imagine scrolling through a job log, covered in the previous lesson, and seeing a message with ID CPF9897 reporting a file-related problem. Recognizing the CPF prefix immediately tells you this is a standard, IBM-supplied system message, not something specific to a custom application, making it easier to search for and understand what that particular message number means. Elsewhere in the same job log, a message of the inquiry type is actively waiting for a reply before the job continues, regardless of which prefix that particular message happens to have.

This is a simplified, illustrative example rather than a specific real investigation, but it reflects how recognizing message ID structure helps you navigate a job log more confidently.

Common Confusions

"Does every message starting with CPF mean something went wrong?" No. CPF covers an enormous range of IBM i system messages, many of which are purely informational. The prefix tells you the message's general source, not automatically that something failed.

"Do I need to memorize what every message ID means?" No. Recognizing the general structure, prefix plus number, and knowing that this structure lets you look a specific message up for detail, is the practical skill this lesson covers, rather than memorizing every individual message ID in advance.

"Does a message's prefix tell me whether it is an inquiry message expecting a reply?" Not directly. Whether a message is an inquiry message is part of its message type, a separate property from its ID prefix. A message from almost any prefix, CPF, RNQ, or otherwise, could potentially be an inquiry message; the prefix tells you where it came from, not what type it is.

Quick Recap

• A message ID is a short prefix followed by a number, such as CPF9897 or RNQ1218.
• CPF (Control Program Facility) is by far the most common prefix, covering a wide range of IBM i's own system-generated messages.
• A message's prefix identifies which message file it came from; its message type, such as inquiry, is a separate property that expects a reply before a job continues, regardless of prefix.
• Recognizing a message ID's structure helps you understand its general source at a glance, and makes it easier to look up for more detail.

Try Asking the AI Tutor

Use the AI Tutor to ask follow-up questions about this lesson. For example, try asking:

• "How would I look up exactly what a specific CPF message number means?"
• "How can I tell whether a specific message is an inquiry message that needs a reply?"