Types of failure keywords

Failure keywords describe typical problems and can be used to search a database to determine whether your problem is known to IBM®.

To determine the failure keyword for your SMP/E problem, read the following list and try to match the symptoms with one or more of those listed for a failure type. If you find a match, follow the procedure for that failure type, as described later in this topic.

If you do not find a match, report the problem to the IBM Support Center with the information listed at the beginning of this topic.

Abend (ABEND): SMP/E or an SMP/E subtask has ended abnormally. For example:
- Message GIM43201T indicates that SMP/E has abended. SMP/E stops running.
- Message GIM4400x indicates that an SMP/E subtask has abended. SMP/E may keep running, but the SYSMOD it was processing fails.
For information about reporting abends, see Reporting abends.
Loop or Wait (LOOP, WAIT): SMP/E seems to be looping uncontrollably or to have been suspended unexpectedly. For example, the same group of messages appears over and over.
Note: SMP/E can appear to loop for a long time, depending on what it is doing and what system it is running on. This does not necessarily mean there is a problem.

For information about reporting loops and waits, see Reporting loops and waits.
Message (MSG): An SMP/E message indicates an error. For example:
- An SMP/E message is the only symptom of a problem.
- An SMP/E message is wrong, missing, or incorrectly formatted.
- An SMP/E message does not adequately explain why it was issued.
For information about reporting message problems, see Reporting message problems.
Incorrect Output (INCORROUT): SMP/E output is missing or contains unexpected information. For example, the results of APPLY processing are different from the results of APPLY CHECK processing for the same SYSMODs.
For information about reporting incorrect output, see Reporting incorrect output.
Performance (PERFM): SMP/E command processing takes an unexpectedly long time.
For information about reporting performance problems, see Reporting performance problems.
Documentation (DOC): A programming problem appears to be caused by incorrect or missing information in SMP/E information. For example:
- Documented descriptions of SMP/E processing do not match actual SMP/E processing.
- Essential information for installing or using SMP/E is missing.
- SMP/E information is so vague that it prevents the effective use of SMP/E.
- Information in one SMP/E manual disagrees with information in another.
For information about reporting documentation problems, see Reporting documentation problems.
Note: Report a documentation problem only when it causes a programming error. For suggestions, comments, or questions about the documentation, use the Readers' Comment Form at the back of the publication.
Dialogs (DIALOG): An SMP/E dialog does not work as expected.
For information about reporting dialog problems, see Reporting dialog problems.