Troubleshooting overview
Troubleshooting is the process of finding and eliminating the
cause of a problem. Whenever you have a problem with HATS, the troubleshooting
process begins by recording the issue as it occurred. A basic troubleshooting
strategy at a high level involves:
- Recording the symptoms of the problem
- Recreating the problem
- Eliminating possible causes
Recording the symptoms of the problem
Depending on the type of problem you have, you might receive a
message that indicates something is wrong. Always record the error
message that you see. As simple as this sounds, error messages sometimes
contain cryptic codes that might make more sense as you investigate
your problem further. You might also receive multiple error messages
that look similar but have subtle differences. By recording the details
of each one, you can learn more about where your problem exists.
The HATS Messages book provides explanations and user actions for
error messages. Refer to the HATS Messages book to access error code information.
Recreating the problem
Think back to what steps you took that led you to the problem.
Try those steps again to see if you can easily determine a repeatable
sequence of events to recreate the error. If you can identify a repeatable
test case, you will have an easier time determining what solutions
are necessary to correct the problem. Ask these questions of yourself
when approaching any error involving HATS.
- How did you first notice the problem?
- Did you do anything different that made you notice the problem?
- Is the process that is causing the problem a new procedure, or
has it worked successfully before?
- If this worked before what has changed? The change can refer to
any type of change made to the system, ranging from adding new hardware
or software, to configuration changes to existing software.
- What was the first symptom of the problem you witnessed?
- Were there other symptoms occurring around that point of time?
- Does the same problem occur elsewhere?
- Is only one machine experiencing the problem or are multiple machines
experiencing the same problem?
- What messages are being generated that could indicate what the
problem is?
Eliminating possible causes
To save time and narrow the scope of your problem,
eliminate components that are not causing the problem.
Some tools you can use are:
- The host terminal:
- Step through the host screens to verify navigation through the
host application is still as you expect.
- Use the Host Screen Preview tab
to see how each screen will look in a production environment.
- Play your macros to ensure they still recognize the host screens
and correctly navigate through the host application.
- For more information, see the section on using the host terminal in Getting Started. Also see the chapter on macros
and the host terminal in the HATS User's and Administrator's Guide.
- The project settings editor:
- Open the project editor to confirm the project-wide
settings.
- Use the Events tab to ensure that
the order of screen events is not causing the problem. Maybe a new
screen event you just added is not being recognized because of another
event higher in the priority list. Using the check boxes, you can
enable and disable events to see what effects they have on your running
application.
- For information about modifying a HATS
project see the HATS
User's and Administrator's Guide
- The screen event editor:
- Screen Customizations display the Screen Recognition Criteria tab while the Screen
Combinations display Begin
Screen and End Screen tabs.
Use the appropriate tab to check that the screen recognition criteria
are still being met for your screen events based on any changes that
might have occurred on the host screen.
- Use the Actions tab
to check the actions to perform when the screen event is recognized.
Actions can be enabled or disabled. To enable an action, select the
check box. To disable an action, clear the check box.
- Use the Global Rules and Text Replacement tabs to confirm your settings
based on any changes that might have occurred on the host screen.
- For more information, see the information about using the screen event editor in the HATS User's and Administrator's
Guide.
- The display terminal:
- Use the display terminal while testing your project in the Rational® SDP internal
test environment to watch your project interact with the host. Seeing
what is happening during run time can be very helpful in debugging
macro and screen recognition problems.
- For more information, see the information about previewing your project in Getting Started.
These tools are just some of the methods to use to
help determine what might be the cause of your problem. For more information,
search knowledge bases to find topics related to your problem, to
determine if anyone else has experienced the problem, and to learn
if a fix is available. See Searching for information and Getting fixes for more
information.