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.
Terminal emulators for IBM System Z (mainframes) and System I (AS/400) systems continue to be the primary user interface for many business-critical applications, systems programmers and application developers around the world. Terminal emulators are often underappreciated software, however their users typically require the highest level of reliability, availability, usability and security because they are essential enabler to access many core business applications and data.
This document contains a brief description of the new and updated features in the IBM HACP Extended Edition v1.7 release.
IBM HATS provides advanced customization options to create future proof, rich & complex web applications. This can be achieved by using Macros, Integration Objects and ReST APIs. Along with that, if Integration Objects can get access to the transformation connection (HATS web connection), it enables easy integration of HATS applications with third party applications.
In continuation to the previous blog about Host Access Class Library(HACL) API in IBM Pcomm-part 1-Automation Objects, this blog covers Java Objects implementation using HACL API
HACL unique features include:
HATS applications support most of the versions of IBM WebSphere Application Server Liberty (WAS Liberty) starting from liberty 16 to liberty 19.
Each of these server versions in turn support different versions of server features, which are configurable based on the needs of the deploying application.
Recently while working with a customer on HACP Extended Edition, we encountered a situation where the customer’s pages were not working as expected in a cluster environment.
If they closed the browser sessions, while having multiple HACP EE sessions active, the sessions were not getting disconnected. They could see a few LU’s still active on their mainframe.