LISTHF control statement

The LISTHF (LIST History File) control statement specifies a set of optional qualifiers to select which fault entries should be listed.

Figure 1. Syntax

1  LISTHF?  ( + & or |
2.1  ABEND_DATE
2.2.1 >
2.2.1 <
2.2.1 =
2.2.1 yyyy/mm/dd
2.2.1 TODAY-days
2.1 
2.2.1 USER_ID
2.2.1 ABEND_CODE
2.2.1 JOB_NAME
2.2.1 CICS_TRANSACTION_ID
2.1 =
2.1 literal )

Description

The qualifiers have a basic capacity to compare greater than, less than, or equal for the fault entry ABEND_DATE, USER_ID, ABEND_CODE, JOB_NAME, or CICS_TRANSACTION_ID (all of which are field names in the ENV data area) to a literal in the LISTHF control statement. Comparisons can be combined with and, or (& |) operators. The result of this simple syntax capability can be passed on to a user exit if more complex comparisons are desired.

Two special literal comparison qualifiers are recognized. An asterisk in the literal truncates the comparison for wild card capabilities, such as: 
JOB_NAME = AB*
The other special literal is TODAY-days, which is converted to today's date, minus the number of numeric days specified at days, and then converted to a string of the 2001/02/23 format before comparison. Naturally, the TODAY-days literal is only meaningful when used with ABEND_DATE, such as: 
ABEND_DATE < TODAY-30

The value specified for days must be in the range 0 - 2147483647.

When comparing ABEND_CODE, the format is four numeric digits for user abend codes and three hex digits preceded by S for system abends. For example, S0C4 for a system 0C4 and 4038 for a user 4038 abend. CICS® abend codes are four alphabetic characters, for example, ASRA.

The IDIUTIL ListHF user exit (see IDIUTIL ListHF user exit) can be used with the LISTHF control statement to apply extra selection criteria to the history file entries that should be listed.

An example showing the use of the LISTHF control statement is provided in Example 1. Listing history file entries.