Test Procedure

To be effective, you must follow these procedures in order and document the results of every test carefully. It is good practice to run through the tests at least twice to ensure that the results are consistent.

Follow these steps:

Document the precise actions that were performed immediately prior to the appearance of the problem.
Note: The description of the actions performed should be detailed enough to allow for you to recreate the problem at some future time if necessary.
Document the symptoms of the problem. This includes:
- Error messages
- Unexpected events
- Other details relevant to the malfunction
Wherever possible, record any error messages that appear on the screen.
If a data file has been corrupted, save the data file in a safe place for later analysis by CA Technical Support. Any information that appears even remotely relevant may prove vital in achieving a quick resolution to the problem.
Retry the operation, isolating and eliminating as many extraneous factors as possible.
Use the following table to determine your next step.

Did the Problem Recur?	Then...
No	Record as much as you can from the problem's first occurrence (log files, and so forth) so that if you ever see it again, you will have additional evidence.
Yes	Continue with Step 6.

Is an error message issued?

Yes

Look up the error message in the appropriate CA XCOM Data Transport manual and follow the instructions.

No

If no error message was issued and the operation does not complete (for example, hangs), the problem may be related to a system malfunction (for example, remote system response time problems, and so forth).

Leave the function in the "hung state" for at least 10 minutes. If the problem persists, contact a person who can verify the current status of the system and backbone network. If the system or the network is not operating normally, retry the transfer at some later time.
Run a trace to pinpoint and trace problems in your communication lines.