Are you using the Terminal Emulation package from Automation Anywhere or are you automating a third-party application?

The Terminal Emulation package supports a wide range of terminals, including the 3270 and 5250, along with favorites like VT100. If you must use a third-party application, you can scrape the screen to get data from it (in 80x25 format, for example) and send various keystrokes.

I'd also like to chime in while you provide your answer to Aaron.

I did extensive mainframe automation using the A360 package and my experience was that I had to add waits and screen validation because it moved faster than the mainframe screens loaded.

Be sure that you've identified the type of mainframe and selected the right settings in the connect package otherwise there might be compatibility issues.  

Try optimizing screen navigation, using faster terminal emulators, and reducing unnecessary waits or retries.

If you're using the Terminal Emulation package, make sure the terminal type matches your mainframe (e.g., 3270, 5250). Mismatched settings can slow down screen loads or cause input issues.

Also, avoid fixed delays use Wait for screen text or Wait for cursor to sync bot actions with screen readiness. Bots often move faster than the mainframe responds, so proper waits improve both speed and reliability.

If you're using a third-party emulator, native field-level access won't work, you'd need to rely on screen scraping and keystrokes, which is generally slower.

I am currently using a Terminal Emulator Package. However, I would like to know if there are any enhancements from AA for mainframe automations, other than using a terminal emulator.

We are interacting with AS 400 using terminal emulations. For 200 transactions, it takes around 7 hours to complete. We are looking for solutions to optimize the bot.