3270io

Measure whether a change actually moved throughput or latency, by running the same workflow at the same concurrency on both sides and saying which differences the numbers support.

Write a workflow JSON document that drives a 3270 application, using the schema and the validator rather than guessing at the format.

Find the concurrency at which a host stops scaling — where response time starts climbing faster than load — by stepping up in stages and comparing.

Turn a finished run's counters, percentiles and step latencies into an answer someone can act on, without overstating what the numbers support.

Run a concurrent load test against a 3270 host and report what it did, from a first smoke run through to a result worth quoting.

Hold a steady, modest load for a long period to surface the problems that only appear with time — leaks, pool exhaustion, log growth, gradual slowdown.

Explore an unknown 3270 application automatically, mapping its screens and transitions, then report what was found and what to try next.

Summarise a whole application for a stakeholder — what it is, its main areas, the operations it supports, and what is still not understood.

Turn discovered screens into business meaning — annotate what each screen and field is for, then catalogue the named operations the application supports.

Carry out a business operation the user asked for in plain language — run it on the live session, or export it as a reusable workflow.