When using the initial search argument, if you do not find a similar APAR problem description in one of the software databases, try the following suggestions for varying the argument to see if you can obtain a match:

• If you have described the failure as a wait, loop, or performance type-of-failure, replace the type-of-failure keyword with one of the other two keywords. For example, what appears to be a wait state might actually be a loop or a performance problem.
• If more than one type-of-failure keyword applies (for example, an abend and a message both occur), try all combinations of those keywords.
• Delete one keyword at a time in the following order:
  1. Load module name
  2. Service level
  3. Release level
  4. Modifiers
  5. CSECT name

If you now identify a similar problem in the database, contact the IBM® Support Center to obtain the fix.

If you still do not find a matching APAR problem description, contact the IBM Support Center as directed in Contacting the IBM Support Center for assistance. They might be able to refine your search argument or keyword string and find a match in the database; otherwise, they can direct you to gather additional failure-related information.

Use the following keyword worksheet to develop the keyword strings and other information to give to the IBM Support Center.