When the macro runtime has selected a new current macro screen, the macro runtime immediately begins to perform the actions in the <actions> element of that macro screen. After the macro run-time has performed all the actions, the next step is to determine the next macro screen to be processed. Within a single macro screen, the macro runtime performs the actions in the order in which they occur in the <actions> element. This is the same order in which you have ordered the actions under the Action list. You are not required to create any actions for a macro screen. If there is no <actions> element specified or the <actions> element is empty, then the macro runtime goes directly to the next section of macro screen processing, which is selecting the next macro screen to be processed.
Each Emulator provides specific automation APIs to create scripts to automate the business process. Automated Scripts contains core logics to read, write, update, and copy data in Mainframe/AS400 emulators which helps is accomplishing every-day business.
Reporting is used to translate your company’s data into an informational summary that enables you to make the correct business decision. With Web Application, you can generate reports in real-time that can be accessed from anywhere, anytime. There are third-party reporting tools available that allow you to render your data visually through a web portal or application.
A Host On-Demand Macro (HOD) is an XML script that allows a Host On-Demand client to interact automatically with a host application running on a terminal emulator session. For example: 3270 Display session, 5250 Display session, VT Display session or CICS Gateway session, and so on.