Published on

Automating a mainframe without touching it

How Blokera drives mainframe terminal sessions step by step, without changing the system.

Console of an IBM System/360 mainframe.
Legacy · MainframeRegister the invoice
NEW INVOICE
SUPPLIER: ACME
AMOUNT: 12,480.00
What it is doing
  • Session open
  • Screen recognized
  • 4 fields filled
How it looks in Blokera

Many critical processes still live on a mainframe. They work, but every lookup needs a person at a terminal: type a transaction, wait for the screen, copy a field, repeat.

Record or describe the steps

In Blokera, a mainframe step is a terminal session. You can record what you do on screen or describe it: which transaction to open, which fields to fill, what to read from the response. Each action becomes a step of the flow.

Run on its own

Once built, the flow runs with nobody at the terminal. Every run has a status, progress and a result or an error you can understand, so you always know what is happening.

Without touching the system

The mainframe does not change: Blokera uses the same interface people already use. No programs to modify, no new infrastructure to set up; where and how the flow runs is Blokera’s job.

The same applies to legacy web screens: forms and tables walked through step by step.