Run mainframe transactions
Read records, enter data, and complete approved transactions through the existing application. Check each result before the workflow continues.
Mainframes
Deploy AI agents
into your mainframe.
Connect your mainframes and terminal applications to the rest of your business so agents can run entire workflows across systems.
Get your first workflow running in weeks without a replatforming project.
What agents can do
Redesign entire workflows
across your business.
Connect business systems
Connect legacy transactions to documents, payment platforms, and operational systems. Agents can coordinate the work across applications and teams.
Give your agents access.
3270 screen interfaces
Read and enter data through your application’s terminal screens.
z/OS Connect and IBM MQ
Connect to mainframe APIs and exchange messages with existing applications.
Db2 query access
Retrieve the database records your workflow needs.
Illustrative workflows
BANKING
Loan hardship support
Gather loan history from the mainframe alongside borrower documents and existing arrangements.
Flag missing evidence and prepare the case for a specialist’s decision.
Apply approved repayment changes in core banking. Update collections and verify the arrangement before confirmation.
INSURANCE
Property claims
Join policy records in the legacy system with claim history and repair estimates.
Reconcile conflicting evidence and prepare a settlement review for the claims team.
Record the approved decision. Initiate payment or assign repairs through supplier systems and verify each action.
UTILITIES
Billing investigations
Match legacy billing records to meter readings and field-service history for the disputed period.
Identify discrepancies and route proposed corrections for approval.
Apply approved billing changes. Create any required field work and confirm the outcome across systems.
- Workflow design
- We map the process across systems with your team. Together we define approvals and exception handling.
- Implementation
- We build the application actions and verify each transaction. Your team supplies access and confirms the business rules.
- Ongoing maintenance
- We repair and reverify affected actions when application behavior changes.
Before you start
Technical questions
Where does Monarch run?
Monarch offers hosted deployment or deployment in your own cloud, available as an Enterprise add-on. Agree how the deployment reaches your mainframe, which accounts it uses, and how model processing and records are handled. Review deployment and access requirements.
Which mainframes and terminals can you work with?
We assess 3270 mainframe applications, IBM i / AS/400 applications over 5250, and browser-based terminal emulators. Compatibility is tested against your workflow and access route.
Do we need an API?
We can use the terminal interface when an API cannot cover the task, or integrate through z/OS Connect and IBM MQ. We confirm the route against your workflow and access requirements.
How do permissions and approvals work?
Actions use the connected account’s permissions. Your team defines which records can change and which transactions need human approval.
What if a transaction is interrupted?
We define completion checks before rollout. An interrupted submission is checked before retrying. Unclear results go to review to avoid duplicate transactions.
Book a mainframe demo.
Show us the process your team runs today. We’ll work through how agents could carry it across your systems.