Usually, when you are investigating a problem, you start with a symptom,
or set of symptoms, and try to trace them back to their cause. This process
is called problem determination, and it is important
to realize that it is not the same as problem solving.
Often, the process of problem determination enables you to solve the problem.
For example:
- If you find that the cause of a problem is conflicting CICSPlex® SM topology
definitions, you can solve the problem by correcting the definitions.
- If you find that the cause of a problem is within CICS®, you can solve
the problem by modifying CICS. (For example, if CICSPlex SM’s Workload Manager will not
route to a target region because there is no CICS connection between the routing region
and the target region, you can create the links between the systems.)
However, you may not always be able to solve a problem yourself after
determining its cause. For example:
- An unexpected message may be caused by an unexpected response from another
product.
- If you think the cause of a problem is in the CICSPlex SM code, you need to
contact your IBM® Support Center for assistance.
[[ Contents Previous Page | Next Page Index ]]