Confused by the list of multiple hits?
When you LookAt certain message IDs, and often when you use "wild cards," your LookAt request may return a list of several hits. The format of this list has caused some confusion about how to use it properly. We are looking at better ways to format this list, but, in the interim, we will try to explain how you can use LookAt more effectively.
For example, suppose you look for message ID IEA20* on the z/OS V1R3 platform, and you get the following result:
This illustrates the actual results you would receive. The list indicates that there are two variations of this ID, IEA200I and IEA208I. As you might expect, both messages can be found in z/OS V1R3.0 MVS System Messages, Vol 6 (GOS-IEA). However, message IEA208I can also be found in z/OS V1R3.0 MVS Routing and Descriptor Codes.
If you want to view the explanation for either of these messages, click on the message ID, not the title of the book. The ID will take you directly to the message explanation. You can click on the title of the book, but the title will only open the book that contains the messages to its table of contents.
If you have any suggestions for improving this list, please send us a LookAt Feedback.
Unexpected LookAt results - having trouble locating a message? Try this!
Occasionally, some messages do not get properly enabled for LookAt. As a result, you may encounter any of these conditions when looking for those messages:
If you get the beginning of a list of messages that contains your message instead of the message directly:
You will have to search for the message ID:
- Click on Search.
- Re-enter the message ID.
- Please send us a LookAt Feedback and identify the message that did not appear properly.
If you get the title page or table of contents of a message book that contains your message instead of the message directly:
You will have to search the book for the message ID:
- Click on Search.
- Re-enter the message ID.
- Please send us a LookAt Feedback and identify the message that did not appear properly and the book that LookAt opened.
If you receive a message telling you that a "book" cannot be located in the catalog, the message you requested is not currently available through LookAt:
Please send us a LookAt Feedback and identify the message that you want to find.
Want to know how to enter the ID of the message you want to LookAt?
In the "message ID" field you enter one of the following:
- The complete message ID for a message to see a specific message.
- Part of a message ID with an asterisk (*) as a "wildcard" character if you don't know the entire ID or if you want to see a set of related message IDs. The "*" can represent zero or more character positions. You can place a "wildcard" character at the beginning, in the middle, or at the end of a message ID. However, we do not recommend putting an "*" at the beginning of an ID as it will probably return a very large number of possible combinations. You can use more than one "wildcard" character in a message ID.
- When you are looking for various codes, if you usually prefix the code with the letters S, ABEND, WSC, or WAIT, LookAt will still attempt to locate the code for you. Even though these additional letters may appear in the message text, they typically do not appear in the explanations for the codes. LookAt ignores these prefixes.
Want to try some sample messages?
The examples below are all OS/390 or z/OS messages or return codes. They have been selected because they demonstrate the several results that are possible using LookAt depending on the availability of a particular message book and whether or not a book has been enabled for LookAt.
In most cases, LookAt will open directly to the message you request. In some cases, LookAt will return a list of messages that match your request in one or more books. In a few cases, LookAt will resort to a BookManager search and list the book that contains the message you requested.
- IEA200I: LookAt opens directly to this message.
- IEA21*: LookAt finds 12 messages that match this pattern in 3 different books.
- IEA21*A: LookAt finds 3 messages that match this pattern in 2 different books.
- +012: LookAt opens directly to the return code.
- EQA1000I: In z/OS V1R2 through the latest release of z/OS, LookAt opens directly to the message. In OS/390 V2R10 through z/OS V1R1, LookAt opens the book that contains this message.
- 0072: LookAt opens to this ABEND code.
- 9004: Opens a book to the top of the chapter that contains this code.
- 0123: Gets a list of books that contain this code.
What's the difference between LookAt's look up and BookManager's search?
- A LookAt look up is designed to locate the primary message explanation for any message ID you enter. You need a little background. In our libraries for z/OS, OS/390, z/VM, and VSE/ESA there are many places that mention messages. However, there is usually only one place, most likely in a messages book, that provides the complete explanation. Of course, there are instances where messages are not in a messages book and their location is not obvious. LookAt, in enabling books that contain messages, indexes the location in the library of the primary message explanation, regardless of where it is located. When you ask for a particular message ID, LookAt knows which book it's in and where in the book it can be found. With this knowledge, LookAt can open a book to exactly the right place very quickly. You might see a list of several possible message explanations when you use a "wildcard" and several IDs match what you requested or if several books contain the same message ID. Since we have not yet been able to enable every book for all the software products that contain messages, we have included a BookManager backup search when LookAt can't locate the ID you requested in its index.
- A BookManager search is very useful when you are trying to locate as much information about a topic as you can in a bookshelf. BookManager searches an entire bookshelf at a time and gives you all the hits it can find in all the books in the bookshelf. Then, it ranks the results according to where and how often the term appears.