The TEP error table

The terminal error program (TEP) error table maintains information about errors that have occurred on a terminal.

The table consists of two parts (shown in Figure 1):
  • The TEP error table header (TETH), which contains addresses and constants related to the location and size of the TEP error table components.
  • Terminal error blocks (TEBs), which can be either:
    • Permanent (P-TEBs), each associated with a particular terminal
    • Reusable (R-TEBs), not permanently associated with any particular terminal.
Figure 1. TEP error table
The picture shows a rectangle representing the TEP error table. The rectangle is divided horizontally into two. The top section is labeled “TEP error table header (TETH)”. The lower section is labeled “Terminal error blocks (P-TEBs and R-TEBs)”.

TEBs maintain error information associated with terminals. You must specify the total number of TEBs to be generated. The maximum number needed is one per terminal. In this case the TEBs are permanent.

You can reduce the total amount of storage used for TEBs by allocating a pool of reusable TEBs, that are not permanently associated with a particular terminal. Reusable TEBs are assigned dynamically on the first occurrence of an error associated with a terminal, and are released for reuse when the appropriate error processor places the terminal out of service.

Note: Ensure that the pool is large enough to hold the maximum number of terminals for which errors are expected to be outstanding at any one time. If the pool limit is exceeded, handling of terminal errors may become intermittent. No warning is given of this condition.

You should assign permanent TEBs to terminals that are critical to the network. For the remainder of the network, you can generate a pool of reusable TEBs.

Each TEB currently in use or permanently assigned contains the symbolic terminal identifier of the terminal, and one or more error status elements (ESEs), as shown in Figure 2.
Figure 2. Terminal error block (TEB)
The picture shows a terminal error block consisting of a symbolic terminal ID, a number of error status elements, and a common error bucket.

An ESE records the occurrence of a particular type of error associated with the terminal. The contents of an error status element are described in the TEPCD DSECT (generated by the DFHTEPM TYPE=INITIAL macro) under the comment “ERROR STATUS ELEMENT FORMAT”. The number of ESEs per TEB remains constant for all TEBs. You specify the number when the TEP tables are generated. If fewer than the maximum number of error types recognized by DFHTACP (25) are specified, one additional ESE, referred to as the “common error bucket”, is generated for each TEB.

You can permanently reserve ESE space in each TEB for specific error types. Those not permanently reserved are considered reusable, and are assigned dynamically on the first occurrence of a particular error type associated with the terminal. If an error type occurs that is not currently represented by an ESE, and if all reusable ESEs are assigned to other error types, the occurrence of this error is recorded in the common error bucket. DFHTACP can recognize far more error types than can occur in a typical terminal network. By specifying less than the maximum and allowing the sample DFHTEP to assign ESEs dynamically, you can minimize the table size, and still control and account for the types of errors relevant to the network.



dfha3c00140.html | Timestamp icon Last updated: Sunday, 4 June 2017