{'fraction_non_alphanumeric': 0.028047464940668825, 'fraction_numerical': 0.0, 'mean_word_length': 5.72463768115942, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Remote terminal emulation in the procurement of teleprocessing systems

This paper addresses some of the problems which exist when benchmarking interactive computing. The teleprocessing workload may be emulated by a program running internal to the System Under Test (SUT), known as an internal driver or internal stimulator. The limitations of internal drivers are discussed, especially with respect to procurement testing. The use of live operators and tape loops are also discussed, but these are also limited techniques. The most attractive alternative is to employ another, external, computer system to emulate the teleprocessing workload; this approach is called remote terminal emulation. The emulation constraints are delineated; terms applicable to the process are defined, including: Remote Terminal Emulator (RTE), scenario, script, and scene. Ten RTE's, representative of current capabilities, are briefly described.