The indication that a software product is not performing as expected might be as obvious as an ABEND, as minor as a misspelling in the documentation, or as subtle as a warning message that is not always displayed when it should be.
The first step of problem reporting is to determine whether a perceived abnormal condition is a product error, an operating system error, or a matter of user perception. If you think that the product is working contrary to the documentation, find the area in the guide that is inconsistent with the actual performance of the product. If the guide agrees with the operation of the product, this is generally not considered an error. If the guide is vague or inconsistent, this could be an error in the documentation.
|
Copyright © 2004 CA.
All rights reserved.
|
|