The advice listed below will help you compile the information required.
If you are in any doubt about how to gather any of the items listed above,
wait until you can seek advice from your
support organization.
- Try to establish which program in your system seems to be the cause of
the problem. As you are reading this book, it is likely that you already believe
the CICS® Universal Client to be the
problem source.
You also need to provide the version and release number
of the product, for example Version 7.1, together with the number of any PTF
or other fix applied, for example UNnnnnn (where nnnnn is
a valid PTF number).
- You should find details of your compiler level on the product media labels
or the associated documentation. Alternatively, check the panel displayed
on the screen at compile time.
- Give the problem a severity level. Severity levels have the following
meanings:
- Severity level 1 indicates that you are unable to use a program, resulting
in a critical condition that needs immediate attention.
- Severity level 2 indicates that you are able to use the program, but that
operation is severely restricted.
- Severity level 3 indicates that you are able to use the program, with
limited functions, but the problem is not critical to your overall operation.
- Severity level 4 indicates that you are able to use the program with the
problem causing negligible hindrance.
- Also, try to classify the error and give a brief description of the problem.
Include keywords associated with the problem, such as ABEND, WAIT, LOOP, PERFORMANCE,
INCORROUT, and MESSAGE, corresponding to the problem classification types
used in the RETAIN® database.
Strings containing other keywords are also useful. These are not predefined,
and might include such items as a message or message number, an abend code,
any parameters known to be associated with the problem, or, for example, STARTUP,
INITIALIZATION, or TRANSIENT DATA.
- Finally, you should include your address, relevant contact names, and
details of the other products at your installation.
Keep a copy of the problem reporting sheet which summarizes all the information
relevant to the problem, together with any available documentation such as
dumps, traces and output from programs, translators, and compilers.