How do you unit test an Easytrieve program?

COBOL side we at least have small input files and expected outputs checked in. Easytrieve jobs here get "run in test and eyeball the report."

Anyone doing better than that?

Same idea as COBOL. Tiny fixed input PDS members, expected SYSOUT and output file checked in, compare with SUPERC or ISRSUPC after the run.

Reports are annoying because dates and page headers move. We MASK those lines out of the compare.

Same pattern here. One gotcha: Easytrieve FILE STATISTICS lines change every run. Exclude those from the compare list or your diffs are always noisy.