Not sure what happened there.... I'd steer away from Record and Playback. It was originally 'plugged' into OPS/MVS for old AutoMate/MVS customers that were migrating to OPS/MVS. While it is a good external tool, the underlying code generated in the OPS/REXX is not that efficient, specifically with the reliance on AutoMate/MVS command processor aliases. (BIND,UNBIND,GETSCRN,etc). I'd take a look at the OPEPI* sample OPS/REXX pgms within *.CCLXSAMP, specifically with the OPEPIPGM. This sample provides a common template that can be used for all EPI applications and that structure is - issue keystroke1, verify expected screen contents of that command AND that keyboard is unlocked, issue keystroke 2, verify screen and keyboard status, etc. The other OPEPI* demonstrate defining and allocating EPI terminals as well as a subroutine to send a keystroke to a specific field on the screen.