Terminal data

Terminal data is important in solving problems, because it can help you determine what data was entered just before the transaction failed, and if there is any output.

The more you know about the information that was input at the terminal on which the transaction failed, the better your chance of duplicating the problem in a test environment. However, this information might not be precise, especially if there are many fields on the input screen. You are recommended to provide a quick and easy way for terminal operators to report problems, so that they can report the error while they can still see the data on the screen (or at least remember more clearly what it was).

The output from a transaction is sometimes easier to capture. If you have a locally attached printer, you can make a copy. (The problem might be that the printer output is incorrect.)

The items to look for on the input side are:
  • Were all necessary input fields entered?
  • Were the contents of the input fields correct?
  • Which transmit key was used, (that is ENTER, a function key, or a PA key) ?
On the output screen, check the following points:
  1. Do all the required fields contain data?
  2. Is the data correct?
  3. Is the screen format as it was designed?
  4. Are there any non-display fields used to pass data that might not be protected?


dfhs1c0026.html | Timestamp icon Last updated: Monday, 5 June 2017